How to load data from Redshift to BigQuery

Learn how to use Airbyte to synchronize your Redshift 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 Redshift 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 Redshift 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 Redshift 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: Extract Data from Amazon Redshift

  1. Connect to Redshift: Use a SQL client or command-line tool to connect to your Redshift cluster.
  2. Unload Data:
    • Choose the tables or data you want to transfer.
    • Use the UNLOAD command to export the data to Amazon S3 as delimited text files (CSV). For example:

UNLOAD ('SELECT * FROM your_table')

TO 's3://your-bucket/your-data-prefix'

CREDENTIALS 'aws_access_key_id=your_access_key_id;aws_secret_access_key=your_secret_access_key'

DELIMITER ','

ADDQUOTES

ALLOWOVERWRITE

PARALLEL OFF;

  • Ensure the S3 bucket is in a region that is convenient for transferring to Google Cloud.

Step 2: Prepare the Data Files

  1. Verify Data Format:
    • Check that the data is in a format supported by BigQuery (CSV, JSON, Avro, Parquet, or ORC).
    • If necessary, transform the data into one of these formats.
  2. Split or Compress Files (Optional):
    • If the files are very large, consider splitting them into smaller chunks or compress them using GZIP to speed up the transfer process.

Step 3: Transfer Data from S3 to Google Cloud Storage

  1. Set up Google Cloud Storage:
    • Create a Google Cloud Storage (GCS) bucket in your Google Cloud project if you don’t already have one.
  2. Transfer Files:
    • Use the gsutil command-line tool to transfer files from Amazon S3 to GCS. First, configure gsutil with your Google Cloud credentials.
    • Run the gsutil cp command to copy files from S3 to GCS. For example:

gsutil cp s3://your-bucket/your-data-prefix* gs://your-gcs-bucket/your-data-prefix

  • Alternatively, you can use the Google Cloud Storage Transfer Service, which allows you to create a one-time transfer job or a schedule for recurring transfers from S3 to GCS.

Step 4: Load Data into BigQuery

  1. Create a Dataset and Table in BigQuery:
    • Go to the BigQuery console.
    • Create a new dataset if necessary.
    • Define the schema for your table that matches the data you’re importing.
  2. Load Data:
    • Use the BigQuery web UI, command-line tool (bq), or API to create a load job that points to the files in your GCS bucket.
    • Configure the job with the appropriate options such as file format, delimiters, etc.
    • For a CSV file, the command might look like:

bq load --source_format=CSV --autodetect --skip_leading_rows=1 your_dataset.your_table gs://your-gcs-bucket/your-data-prefix*

  • Monitor the job for completion and check for any errors.

Step 5: Verify Data Integrity

  1. Check the Loaded Data:
    • After the load job is complete, verify that the data in BigQuery matches the original data from Redshift.
    • Run some test queries to ensure the data types and values are as expected.
  2. Data Validation:
    • Consider performing a row count and some aggregation queries on both Redshift and BigQuery to ensure the data matches.
    • Look for discrepancies and re-import data if necessary.

Step 6: Clean Up

  1. Remove Temporary Files:
    • Once you have verified the data transfer, you can delete the files from S3 and GCS to avoid incurring storage costs.
    • Use the aws s3 rm and gsutil rm commands to remove the files.
  2. Close Connections:
    • Ensure that all database connections to Redshift are closed and that you’ve logged out of the AWS and Google Cloud consoles.