

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.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- 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
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

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."
Ensure you have access to both ClickHouse and Google Firestore. Install necessary tools such as ClickHouse client for querying and Python or any programming language SDK that supports Firestore operations. Also, ensure your Google Cloud project is set up, and you have the necessary authentication credentials for Firestore access.
Use the ClickHouse client or a script to query and extract the desired data. You can execute a SELECT statement to retrieve the data you need. Export this data into a common format like CSV or JSON which can be easily processed later. For example, use:
```shell
clickhouse-client --query="SELECT * FROM your_table" --format=JSON > data.json
```
Since Firestore is a NoSQL database, ensure that your data is structured in a key-value format. If your data is in CSV, convert it to JSON objects, as Firestore requires JSON-like structures. Each row in your data should map to a document in Firestore.
Install and configure the Firestore SDK for your preferred programming language. For Python, you can do this using:
```shell
pip install google-cloud-firestore
```
Authenticate your application using a service account key JSON file from your Google Cloud Console.
Write a script that reads the transformed data file and uploads each entry as a document in the Firestore collection. Ensure you handle any data typing issues and set appropriate document IDs or use Firestore's automatic ID generation.
```python
from google.cloud import firestore
db = firestore.Client()
collection_name = 'your_collection'
with open('data.json') as f:
data = json.load(f)
for item in data:
doc_ref = db.collection(collection_name).document() # or specify a document ID
doc_ref.set(item)
```
Run your script to upload the data to Firestore. Monitor the process for any errors or issues with data integrity. Ensure that all data is correctly uploaded by verifying a few entries in the Firestore console.
After the data load, verify the integrity of the data in Firestore by checking a sample of documents. Ensure all fields are correctly mapped. Once verified, clean up any local files or resources you no longer need, such as temporary data files or authentication keys (if they were copied to a different location).
By following this guide, you can manually transfer data from ClickHouse to Google Firestore while ensuring data integrity and compatibility.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
An open-source database management system for online analytical processing (OLAP), ClickHouse takes the innovative approach of using a column-based database. It is easy to use right out of the box and is touted as being hardware efficient, extremely reliable, linearly scalable, and “blazing fast”—between 100-1,000x faster than traditional databases that write rows of data to the disk—allowing analytical data reports to be generated in real-time.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: