How to load data from Metabase to Redshift
Learn how to use Airbyte to synchronize your Metabase data into Redshift 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.
- 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

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
Begin by identifying the specific data you need to transfer from Metabase to Redshift. Use Metabase’s query builder to create the necessary SQL queries to extract this data. You can run these queries in Metabase and export the results as a CSV or JSON file, which are formats easily handled by Redshift.
Amazon Redshift can load data from S3, so you’ll need to create an S3 bucket if you haven't already. Log in to your AWS Management Console, navigate to the S3 service, and create a new bucket where you will temporarily store your exported data files from Metabase.
Once you've exported your data from Metabase into CSV or JSON format, upload these files to your newly created S3 bucket. You can do this using the AWS Management Console by navigating to your S3 bucket and selecting the “Upload” option to add files from your local machine.
Ensure that your Redshift cluster has the necessary permissions to access the S3 bucket. This is done by creating an IAM role with AmazonS3ReadOnlyAccess and attaching it to your Redshift cluster. This step is crucial for Redshift to be able to read data from S3.
Before loading data, you need to create a table in Redshift to match the structure of your data. Use the SQL editor in the Redshift console to define the schema (columns and data types) based on the CSV or JSON format of your Metabase export.
With your data in S3 and a corresponding table in Redshift, use the COPY command to load the data into Redshift. Connect to your Redshift cluster using a SQL client or the Redshift Query Editor and execute the COPY command, specifying the S3 file location and IAM role for authorization. Ensure to include options to handle the file format (CSV or JSON) and delimiters correctly.
After loading the data, verify that the data in Redshift matches the original data in Metabase. Run queries to check for data completeness and correctness, ensuring that no records are missing or misaligned. This verification step is critical to ensure data quality and accuracy after the transfer.