Crosses clouds by design
Data travels from Cloud Storage through Polytomic into S3 staging, which MotherDuck then reads.
Move data between Google Cloud Storage and MotherDuck with Polytomic. Files in your bucket become tables in DuckDB, and results can be written back out. Worth knowing upfront that this pairing crosses clouds, since MotherDuck loads through S3 staging.
Data travels from Cloud Storage through Polytomic into S3 staging, which MotherDuck then reads.
Your Google service account reads the source and AWS credentials handle staging, with no handoff between them.
Recurse through nested prefixes and capture parts of the path, so a dated folder becomes a real column.

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 Google Cloud Storage in minutes
Connect MotherDuck
Connect Google Cloud Storage
Create sync
Enable sync
Connect MotherDuck to Polytomic with an access token and your database name.
Connect Google Cloud Storage to Polytomic with a service account JSON key.
Sync data in either direction between MotherDuck and Google Cloud Storage. 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 Google Cloud Storage.
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.