Real-time
Two-way sync
Changes in MotherDuck or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ CRM
MotherDuck to Salesforce integration — real-time, two-way sync
Keep MotherDuck and Salesforce 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 MotherDuck and Salesforce
Sync Salesforce into MotherDuck continuously and push warehouse results back onto CRM records, one two-way connection instead of two pipelines.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Cases, Campaigns, Tasks and Events, Products and Price Books from Salesforce land in MotherDuck as live tables, updated within seconds, and columns computed in MotherDuck write back to fields in Salesforce. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Common use cases
- Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
- Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
- Sync modeled MotherDuck tables outward to operational tools for activation
- Share curated, synced datasets with other teams through read-only database shares
CRM analytics on live data
Accounts, contacts, and activity from Salesforce are queryable in MotherDuck moments after they change, so dashboards stop lagging the reality they describe.
Scores and segments back on the record
Lead scores, churn risk, or usage segments computed in MotherDuck appear as fields in Salesforce, where the people working accounts actually see them.
A single customer view
Join Salesforce's relationship data with billing, product, and support data in MotherDuck to build the customer picture the CRM alone cannot hold.
What you can sync between MotherDuck and Salesforce
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.
| MotherDuck objects | Salesforce objects | |
|---|---|---|
| Tables The main landing target for synced records and source for analysis. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | |
| Views Modeled projections used as outbound sync sources. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | |
| Database Shares Read-only copies of a database shared with other users or teams. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | |
| Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | |
| Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | |
| Schemas Namespaces within a database used to organize synced tables. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. |
What ships with MotherDuck ⇄ Salesforce
Connect MotherDuck and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MotherDuck or Salesforce 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 or Salesforce record.
Observability
Monitoring
Track your MotherDuck ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between MotherDuck and Salesforce.
How the MotherDuck and Salesforce connectors work
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
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect MotherDuck to Salesforce — 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.
- 01
Connect your apps
Authenticate MotherDuck and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
MotherDuck
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MotherDuck and Salesforce 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.
objects · MotherDuck ⇄ SalesforceCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
MotherDuck SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MotherDuck and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MotherDuck and Salesforce: authenticate both systems, choose the objects to sync (such as MotherDuck's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Salesforce: Records are queried with SOQL, and every standard and custom object carries a SystemModstamp field that sync engines use to order incremental changes. MotherDuck: MotherDuck is built on DuckDB, so integrations use DuckDB SQL and connect through standard DuckDB client libraries with an md: connection string. Stacksync's field mapping accounts for these differences between MotherDuck and Salesforce without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means MotherDuck and Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MotherDuck and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MotherDuck–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both MotherDuck and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on MotherDuck: Polling; no log-based CDC or webhook surface is exposed. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 MotherDuck and Salesforce.
Popular · 8 of 386
-
MotherDuck ⇄ Intercom -
MotherDuck ⇄ Kommo -
MotherDuck ⇄ Kustomer -
MotherDuck ⇄ Nimble -
Salesforce ⇄ Actian Vector -
Salesforce ⇄ Amazon Redshift -
Salesforce ⇄ Apache Doris -
Salesforce ⇄ Apache Druid
No integrations match .
