Skip to content
Data warehouse

Google Cloud Platform to MotherDuck integration — real-time, two-way sync

Keep Google Cloud Platform and MotherDuck in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Google Cloud Platform and MotherDuck

Keep tables consistent across Google Cloud Platform and MotherDuck, for a migration, a multi-warehouse stack, or a dataset two platforms both need.

Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.

Stacksync syncs tables between Google Cloud Platform and MotherDuck continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.

Common use cases

  • Publish change events to Pub/Sub so downstream services react to record updates as they happen.
  • Sync modeled MotherDuck tables outward to operational tools for activation
  • Share curated, synced datasets with other teams through read-only database shares

Consolidation after M&A

Bring the acquired company's warehouse data across continuously instead of through one-off dumps.

Migration without a big bang

When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.

Serve tools that only connect to one platform

Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.

What you can sync between Google Cloud Platform and MotherDuck

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Google Cloud Platform objects MotherDuck objects
Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. Tables The main landing target for synced records and source for analysis.
Pub/Sub topics Event streams used to move change events between systems in near real time. Views Modeled projections used as outbound sync sources.
Firestore documents Document data read and written through the Firestore API for app-facing syncs. Database Shares Read-only copies of a database shared with other users or teams.
Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries.
BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes.
BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. Schemas Namespaces within a database used to organize synced tables.
What ships with Google Cloud Platform ⇄ MotherDuck

Connect Google Cloud Platform and MotherDuck for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Platform–MotherDuck connection.

Real-time

Two-way sync

Changes in Google Cloud Platform or MotherDuck instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Platform or MotherDuck data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Google Cloud Platform or MotherDuck record.

Observability

Monitoring

Track your Google Cloud Platform ⇄ MotherDuck sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Platform and MotherDuck.

How the Google Cloud Platform and MotherDuck connectors work

Google Cloud Platform

Integration surface
Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols
Authentication
IAM service accounts with OAuth 2.0 tokens
Change detection
Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables
Capabilities
read · write · CDC · webhooks
Rate limits
Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide
How it works

How to connect Google Cloud Platform to MotherDuck — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Google Cloud Platform and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Google Cloud Platform connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Platform and MotherDuck objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Google Cloud Platform ⇄ MotherDuck
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Google Cloud Platform MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Google Cloud Platform and MotherDuck integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Google Cloud Platform and MotherDuck.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.