How to load data from ClickHouse to BigQuery
Learn how to use Airbyte to synchronize your ClickHouse data into BigQuery 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: Export Data from ClickHouse
Prerequisites
- Access to a ClickHouse instance with the necessary permissions to export data.
- A Google Cloud account with billing enabled.
- Access to Google Cloud Storage and BigQuery.
- The gcloud CLI installed and configured on your local machine.
- The clickhouse-client installed on your local machine or on the server where ClickHouse is running.
- Identify the data you want to export from ClickHouse. Make sure you have the necessary permissions to access the data.
- Use the clickhouse-client to export the data to a CSV or TSV file. For large datasets, consider compressing the file using gzip to save space and reduce upload time.
Example command to export a table to a TSV file:
clickhouse-client --query="SELECT * FROM database.table FORMAT TSV" > data.tsv
If you want to compress the data:
clickhouse-client --query="SELECT * FROM database.table FORMAT TSV" | gzip > data.tsv.gz
Step 2: Upload the Exported Data to Google Cloud Storage
- Create a new bucket in Google Cloud Storage (GCS) or use an existing one to store the exported data file.
gsutil mb gs://your-bucket-name
- Upload the data file to the GCS bucket.
gsutil cp data.tsv.gz gs://your-bucket-name/path/to/data/
Step 3: Prepare the Data for BigQuery
- If your data is compressed, BigQuery can handle the gzip compression automatically during the load job.
- Define the schema for your BigQuery table. You can either manually define the schema or let BigQuery attempt to auto-detect it during the import. For complex datasets, it’s generally better to define the schema explicitly.
Step 4: Create a Dataset and Table in BigQuery
- Create a new dataset in BigQuery.
bq mk your_dataset_name
- If you’ve defined a schema, create a table with that schema in the dataset.
bq mk --table your_dataset_name.your_table_name path/to/schema.json
Step 5: Load Data into BigQuery
- Load the data from the GCS bucket into the BigQuery table. You can use the bq command-line tool for this.
bq load --source_format=CSV --autodetect your_dataset_name.your_table_name gs://your-bucket-name/path/to/data/data.tsv.gz
If you have a schema file:
bq load --source_format=CSV your_dataset_name.your_table_name gs://your-bucket-name/path/to/data/data.tsv.gz path/to/schema.json
- Monitor the load job to ensure it completes successfully.
Step 6: Verify the Data in BigQuery
Once the load job is complete, run a query against the table to verify that the data has been imported correctly.
bq query --use_legacy_sql=false 'SELECT * FROM your_dataset_name.your_table_name LIMIT 10'
Step 7: Clean Up
- After verifying the data, you may want to clean up by removing the exported data file from the GCS bucket to avoid storage costs.
gsutil rm gs://your-bucket-name/path/to/data/data.tsv.gz
- If you created a new dataset and table specifically for this import and no longer need them, you can remove those as well.
bq rm -r -f your_dataset_name
Notes:
- This guide assumes that you are familiar with the command-line tools for ClickHouse, Google Cloud Storage, and BigQuery (clickhouse-client, gsutil, and bq, respectively).
- Always ensure that your data is backed up and securely handled throughout this process.
- For large datasets, consider using batch operations and monitoring to manage the data transfer efficiently.
- You may need to adjust the field delimiter and other format options in the bq load command depending on the format of your exported data file.
- If you encounter errors during the BigQuery load job, check the error messages and adjust your schema or data file accordingly.