Storage on one side only
BigQuery loads through Google load jobs with no bucket to provision. Only the MotherDuck side needs an S3 bucket for staging.
Sync tables between BigQuery and MotherDuck with Polytomic. BigQuery loads through Google load jobs and MotherDuck through Parquet staged in your S3 bucket, which means storage is configured on one side only. Build ETL and reverse ETL workflows between the two on a schedule, without writing extraction code.
BigQuery loads through Google load jobs with no bucket to provision. Only the MotherDuck side needs an S3 bucket for staging.
BigQuery STRUCT and ARRAY columns map to DuckDB structured types, so repeated fields stay queryable instead of collapsing into JSON strings.
Sync on a tracking column so each run moves only what changed, which matters when BigQuery charges you for the bytes a full reload would scan.

Bec Hu
Head of Sales Ops, Chowbus
“The support is among the best I have ever encountered.”
Follow these simple steps to connect MotherDuck with BigQuery in minutes
Connect MotherDuck
Connect BigQuery
Create sync
Enable sync
Connect MotherDuck to Polytomic with an access token and your database name.
Connect BigQuery to Polytomic with a service account key, optionally scoping project and location.
Sync data in either direction between MotherDuck and BigQuery. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between MotherDuck and BigQuery.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.