How to load data from Elasticsearch to Postgres destination
Learn how to use Airbyte to synchronize your Elasticsearch data into Postgres destination within minutes.


Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
Building in-house pipelines
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
After Airbyte
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Streamline AI workflows with Airbyte: load unstructured data into vector stores like Pinecone, Weaviate, and Milvus. Supports RAG transformations with LangChain chunking and embeddings from OpenAI, Cohere, etc., all in one operation.
Move Large Volumes, Fast
Quickly get up and running with a 5-minute setup that enables both incremental and full refreshes for databases of any size, seamlessly scaling to handle large data volumes. Our optimized architecture overcomes performance bottlenecks, ensuring efficient data synchronization even as your datasets grow from gigabytes to petabytes.
An Extensible Open-Source Standard
More than 1,000 developers contribute to Airbyte’s connectors, different interfaces (UI, API, Terraform Provider, Python Library), and integrations with the rest of the stack. Airbyte’s AI Connector Builder lets you edit or add new connectors in minutes.
Full Control & Security
Airbyte secures your data with cloud-hosted, self-hosted or hybrid deployment options. Single Sign-On (SSO) and Role-Based Access Control (RBAC) ensure only authorized users have access with the right permissions. Airbyte acts as a HIPAA conduit and supports compliance with CCPA, GDPR, and SOC2.
Fully Featured & Integrated
Airbyte automates schema evolution for seamless data flow, and utilizes efficient Change Data Capture (CDC) for real-time updates. Select only the columns you need, and leverage our dbt integration for powerful data transformations.
Enterprise Support with SLAs
Airbyte Self-Managed Enterprise comes with dedicated support and guaranteed service level agreements (SLAs), ensuring that your data movement infrastructure remains reliable and performant, and expert assistance is available when needed.
What our users say

Raman Singh
Predictable, straightforward pricing model that simplified budgeting and significantly reduced overall spend

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
How to Sync to Manually
Step 1: Set up your PostgreSQL database
- Install PostgreSQL if it is not already installed.
- Create a new database or select an existing one where you want to import the Elasticsearch data.
- Define the schema in PostgreSQL that matches the structure of the Elasticsearch data you want to move. This includes creating tables and setting the appropriate data types for each field.
Step 2: Extract data from Elasticsearch
- Determine the data you want to move from Elasticsearch. Identify the indices and the type of documents.
- Use Elasticsearch’s REST API to extract the data. You can use tools like curl or Postman, or you can write a script in a language like Python using libraries like requests to automate the process.
- Use the Elasticsearch Scroll API to retrieve large amounts of data without putting too much pressure on the cluster.
- Save the extracted data into a JSON file or any other format that you find convenient for temporary storage.
Step 3: Transform the data
- Write a script to read the data from the temporary storage and transform it into a format suitable for PostgreSQL. This typically involves converting JSON objects into SQL insert statements or CSV format.
- Ensure that the data types in Elasticsearch are compatible with those in PostgreSQL. For example, you might need to convert timestamps or handle nested JSON objects.
- Validate the transformed data to ensure that it adheres to the constraints and data types defined in your PostgreSQL schema.
Step 4: Import data into PostgreSQL
- Use PostgreSQL’s COPY command if you have transformed your data into CSV format. This command allows for bulk loading of data, which is efficient for large datasets.
- If you have SQL insert statements, you can execute them using a PostgreSQL client. This could be done through a command-line tool like psql or through a script using a PostgreSQL driver for your programming language (e.g., psycopg2 for Python).
- Depending on the size of your data, you might want to batch your insert operations to avoid overwhelming the database.
Step 5: Verify the data import
- Once the data import is complete, run queries in PostgreSQL to ensure that the data has been correctly imported.
- Check for any missing or corrupted data and for the integrity of relationships if you have any relational data.
- If you find any discrepancies, you may need to adjust your transformation script and repeat the import process for the affected data.
Example Script Outline in Python
Below is a very simplified outline of a Python script that could be used for steps 2 and 3:
import requestsimport jsonimport psycopg2# Elasticsearch detailses_url = 'http://your-elasticsearch-server:9200'index_name = 'your_index'scroll_timeout = '1m'# PostgreSQL detailspg_conn = psycopg2.connect("dbname=your_db user=your_user password=your_password")pg_cursor = pg_conn.cursor()# Step 2: Extract data from Elasticsearchdef extract_data(es_url, index_name, scroll_timeout):# Initial searchquery = {"query": {"match_all": {}}}response = requests.post(f"{es_url}/{index_name}/_search?scroll={scroll_timeout}", json=query)results = response.json()scroll_id = results['_scroll_id']documents = results['hits']['hits']# Scroll until no more documentswhile True:response = requests.post(f"{es_url}/_search/scroll", json={'scroll_id': scroll_id, 'scroll': scroll_timeout})results = response.json()scroll_id = results['_scroll_id']hits = results['hits']['hits']if not hits:breakdocuments.extend(hits)return documents# Step 3: Transform datadef transform_data(documents):transformed_data = []for doc in documents:# Transform your Elasticsearch document to match your PostgreSQL schematransformed_data.append(transform_function(doc))return transformed_data# Replace with your actual transformation logicdef transform_function(doc):return (doc['_source']['field1'], doc['_source']['field2'])# Step 4: Import data into PostgreSQLdef import_to_postgres(transformed_data, pg_cursor):insert_query = "INSERT INTO your_table (column1, column2) VALUES (%s, %s)"for data in transformed_data:pg_cursor.execute(insert_query, data)pg_conn.commit()# Main executiondocuments = extract_data(es_url, index_name, scroll_timeout)transformed_data = transform_data(documents)import_to_postgres(transformed_data, pg_cursor)# Close PostgreSQL connectionpg_cursor.close()pg_conn.close()
This script is a rough outline and will need to be adapted to your specific use case, including handling data types, relationships, and error checking.