How to Export Mailchimp Data to BigQuery

Step 1: Export the data from Mailchimp as CSV

Mailchimp exports audiences, segments, tags, campaign reports, and automation reports as CSV from the audience and campaign screens; the on-site guides cover the CSV export per data type, including the audience export and the campaign report export. Export the exact data the analysis needs — a full-audience export and a campaign-report export are different tables in BigQuery, and merging them later is harder than exporting them separately now.

Check the export before loading it: open the CSV, confirm the header row names the columns, and confirm the row count looks right. A Mailchimp export with a truncated download or a duplicated header row will load into BigQuery as bad rows, and BigQuery will not tell you which rows came from a bad export.

Step 2: Load the CSV into BigQuery

Google's batch-loading documentation states the console route for a local file:

1. Open the BigQuery page in the Google Cloud console and select the dataset that will hold the table. Create the dataset first if it does not exist; loading requires permission to run a load job and to create tables, which the BigQuery Data Editor role includes.
2. Click Create table. Under Create table from, choose Upload and browse to the CSV file. Wildcards and comma-separated lists are not supported for local files — load files one at a time.
3. Set File format to CSV and name the destination table.
4. Under Schema, tick Auto detect or type the column names and types. Auto-detect reads the header row; where Mailchimp column names contain spaces or special characters, typing the schema explicitly avoids surprises.
5. Open Advanced options and set Header rows to skip to 1 where the first row holds column names.
6. Click Create table. The console creates a load job; the table appears under the dataset when it finishes.

Two limits apply to console uploads: a file cannot exceed 100 MB, and files load one at a time. For larger exports, upload the file to Cloud Storage first and load it from there.

Step 3: Larger files — Cloud Storage and LOAD DATA

For files over 100 MB, or for many files at once, the route is Cloud Storage plus a SQL load statement:

LOAD DATA INTO mydataset.mytable
FROM FILES (format = 'CSV', uris = ['gs://bucket/path/*.csv']);

INTO appends and OVERWRITE replaces the table's contents; wildcards are allowed for Cloud Storage URIs. CSV files do not support nested or repeated data, and a gzip-compressed CSV cannot exceed 4 GB — uncompressed CSV loads faster in parallel. Batch loading itself uses the shared slot pool and is free; the storage of the loaded data and the file's time in Cloud Storage are billed.

Step 4: Check the loaded table before querying

Query the row count and a sample of rows against the CSV. Confirm the header row did not load as data (the most common skip-setting error), confirm date and number columns detected as the right types, and confirm the row count matches the export. A schema auto-detect that reads an email column as a string is correct; one that reads a date column as a string will silently break date arithmetic later. Fix the schema at load time — redefining it after the load means reloading the table.

The scheduled alternative, stated without endorsement

Third-party connectors (named in search results as examples, including Airbyte and Coupler) sync Mailchimp to BigQuery on a schedule, which the manual CSV route does not. This guide makes no recommendation, states no pricing, and verifies no connector's claims: a scheduled sync is a vendor relationship with its own permissions (Mailchimp API access and BigQuery write access) and its own failure modes. The manual route above is the only route this guide verifies end to end from the vendors' own documentation.

For other Mailchimp destinations, see the Mailchimp Export Guides by Format directory. For the CSV export itself, start with the on-site Mailchimp CSV guides linked from that directory.

Source

Sources: Google Cloud, BigQuery batch loading documentation (console upload steps, 100 MB limit, one-file-at-a-time rule, IAM permissions, supported formats) and BigQuery CSV loading from Cloud Storage (LOAD DATA syntax, wildcards, 4 GB gzip limit, no nested or repeated data), read 2026-11-01; Mailchimp CSV export availability per the on-site Mailchimp export guides, verified 2026-10-31. Facts verified 2026-11-01. Open flags: Mailchimp states no native BigQuery export on the pages opened — the negative claim rests on the Mailchimp export documentation and destination guides read for this site; third-party connector names are examples from search results only, with no capability or pricing claims verified.

This page explains how the process works and what the official rules say. It is general information, not legal advice. For a dispute about your specific situation, talk to your state motor vehicle agency or court.