Skip to content
Data warehouse

Connect MotherDuck to any app with two-way sync.

Two-way sync MotherDuck across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in MotherDuck.

These objects sync between MotherDuck and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where MotherDuck exposes them.

Databases
Cloud-hosted DuckDB databases that scope a sync's reads and writes.
Schemas
Namespaces within a database used to organize synced tables.
Tables
The main landing target for synced records and source for analysis.
Views
Modeled projections used as outbound sync sources.
Database Shares
Read-only copies of a database shared with other users or teams.
Attached Local DuckDB Databases
Local files attached alongside cloud databases for hybrid queries.
API surface

How Stacksync connects to MotherDuck.

The connector runs on MotherDuck's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Not available
MotherDuck connector documentation
What ships with MotherDuck

Connect MotherDuck for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in MotherDuck instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever 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 MotherDuck record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the MotherDuck connector.

MotherDuck is a serverless data warehouse built on DuckDB, aimed at data teams, founders, and SaaS companies working with gigabytes to terabytes rather than petabytes. It typically sits as the analytics layer downstream of operational systems, holding modeled tables for BI, customer-facing analytics, and agent workloads. Data gravity is moderate: teams land curated tables and shares there for querying, while the systems of record stay in the CRM, ERP, or application database.

  • Data / analytics engineering
  • Analysts
  • Founders and small data teams
  1. Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management

  2. Keep a reporting store in MotherDuck continuously synced from production Postgres or MySQL

  3. Sync modeled MotherDuck tables outward to operational tools for activation

  4. Share curated, synced datasets with other teams through read-only database shares

  5. Prototype analytics locally in DuckDB, then run the same SQL against synced cloud data

  6. Land CRM and application records into MotherDuck Tables on a schedule so analysts query fresh operational data with DuckDB clients instead of hitting production systems.

All MotherDuck integrations

Pick the system you need to keep in sync with MotherDuck. Each page covers the sync setup, field mapping, and common workflows for that pair.

How it works

Set up MotherDuck in minutes, without APIs.

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 MotherDuck with its 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
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MotherDuck objects to sync — Stacksync auto-detects the schema, 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 · 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
    MotherDuck database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

MotherDuck connector FAQ

What can I sync with the MotherDuck connector?

MotherDuck's core objects — Databases, Schemas, Tables, Views and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to MotherDuck?

Via SQL through DuckDB clients and drivers using a MotherDuck (md:) connection, authenticated with Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Changes are detected as follows — polling; no log-based CDC or webhook surface is exposed. Stacksync manages rate limits, retries, and schema changes automatically.

Is the MotherDuck connector two-way?

Yes. Changes made in MotherDuck propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a MotherDuck integration take to set up?

Most MotherDuck integrations go live in minutes: authenticate MotherDuck and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is MotherDuck data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. MotherDuck data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

SECURITY

Security teams trust 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
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:

Coworkers laughing in front of a laptop in a casual office setting

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