How to load data from MySQL to BigQuery

Learn how to use Airbyte to synchronize your MySQL 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

Bespoke pipelines are:
  • Inconsistent and inaccurate data
  • Laborious and expensive
  • Brittle and inflexible
Furthermore, you will need to build and maintain Y x Z pipelines with Y sources and Z destinations to cover all your needs.

After Airbyte

Airbyte connections are:
  • Reliable and accurate
  • Extensible and scalable for all your needs
  • Deployed and governed your way
All your pipelines in minutes, however custom they are, thanks to Airbyte’s connector marketplace and AI Connector Builder.

Start syncing with Airbyte in 3 easy steps within 10 minutes

Set up a MySQL connector in Airbyte

Connect to or one of 400+ pre-built or 10,000+ custom connectors through simple account authentication.

Set up BigQuery for your extracted MySQL data

Select where you want to import data from your source to. You can also choose other cloud data warehouses, databases, data lakes, vector databases, or any other supported Airbyte destinations.

Configure the MySQL to BigQuery in Airbyte

This includes selecting the data you want to extract - streams and columns -, the sync frequency, where in the destination you want that data to be loaded.

Take a virtual tour

Check out our interactive demo and our how-to videos to learn how you can sync data from any source to any destination.

Demo video of Airbyte Cloud

Demo video of AI Connector Builder

Setup Complexities simplified!

You don’t need to put hours into figuring out how to use Airbyte to achieve your Data Engineering goals.

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

Tech Lead at Symend

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

Learn more
Chase Zieman headshot

Chase Zieman

Chief Data Officer

“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.”

Learn more

Rupak Patel

Operational Intelligence Manager

"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."

Learn more

How to Sync to Manually

Step 1: Export Data from MySQL

1. Identify the Data to Export: Decide which tables or data sets you need to export from MySQL.

2. Choose Export Format: BigQuery supports CSV, JSON, Avro, and Parquet formats. Choose a format that suits your needs (CSV is commonly used for simplicity).

3. Export the Data:

- Connect to your MySQL database using a command-line tool or a database management tool like phpMyAdmin.

- Use the `mysqldump` command to export your data. For example, to export a table to a CSV file, you can use:

```sh

SELECT * FROM your_table_name

INTO OUTFILE '/path_to_export/your_table_name.csv'

FIELDS TERMINATED BY ','

ENCLOSED BY '"'

LINES TERMINATED BY '\n';

```

- Make sure that the account used to run the `mysqldump` command has the necessary permissions to access the data and write to the file system.

Step 2: Prepare Data for BigQuery

1. Clean and Format Data: Ensure that the data is clean (e.g., no null bytes, properly escaped newlines, etc.) and conforms to BigQuery’s data types and format requirements.

2. Split Large Files: If you have very large CSV files, consider splitting them into smaller chunks to make the upload process more manageable and to avoid timeouts.

3. Compress Files (Optional): Compress the CSV files using GZIP to reduce upload time and storage costs in BigQuery.

Step 3: Upload Data to Google Cloud Storage (GCS)

1. Create a Google Cloud Storage Bucket:

- Go to the Google Cloud Console.

- Navigate to "Storage" and create a new bucket.

- Set the storage class and location according to your needs.

2. Upload Files to GCS:

- Use the `gsutil cp` command to upload your files to the GCS bucket:

```sh

gsutil cp /path_to_export/*.csv gs://your-bucket-name/

```

- Ensure that you have the necessary permissions to upload files to the GCS bucket.

Step 4: Import Data into BigQuery

1. Create a Dataset in BigQuery:

- Go to the BigQuery console.

- Create a new dataset where you will store your imported tables.

2. Create Table Schema:

- Define the schema for your BigQuery table, matching the structure of the MySQL data you exported.

- You can create the schema manually in the BigQuery UI or define it in a JSON file.

3. Load Data from GCS to BigQuery:

- In the BigQuery UI, navigate to your dataset and click on "Create table".

- Set the "Create table from" option to "Google Cloud Storage" and provide the path to your CSV files in the bucket.

- Choose the file format and specify the schema.

- Configure additional settings like field delimiter, encoding, etc., as per your CSV format.

- Click on "Create table" to start the import process.

4. Verify Data Import:

- Once the data is imported, run some queries to ensure that it looks correct and matches the source data in MySQL.

Step 5: Clean Up

1. Remove Temporary Files:

- After confirming the successful import, you can delete the exported files from your local system and the GCS bucket to avoid unnecessary storage charges.

2. Monitor Cost and Performance:

- Check the BigQuery billing and performance to understand the cost implications of the data import and subsequent queries.