Real-time
Two-way sync
Changes in DuckDB or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
DuckDB to Salesforce integration — real-time, two-way sync
Keep DuckDB 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 DuckDB and Salesforce
Treat Salesforce like part of your database: its records live in DuckDB as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in DuckDB, where it can be queried and joined like everything else.
Stacksync mirrors Custom Objects, Accounts, Contacts, Leads from Salesforce into External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas in DuckDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Salesforce with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
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.
- Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
- Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Salesforce API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Salesforce arrive as row changes in DuckDB, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Salesforce become tables in DuckDB you can join with application data directly.
What you can sync between DuckDB 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.
| DuckDB objects | Salesforce objects | |
|---|---|---|
| Schemas Namespaces within a database used to organize tables in sync outputs. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | |
| Views SQL views used to shape or filter data for downstream consumers. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. |
What ships with DuckDB ⇄ Salesforce
Connect DuckDB and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB 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 DuckDB or Salesforce record.
Observability
Monitoring
Track your DuckDB ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Salesforce.
How the DuckDB and Salesforce connectors work
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
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 DuckDB 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 DuckDB 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.
DuckDB
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB 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 · DuckDB ⇄ 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.
DuckDB SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Salesforce: authenticate both systems, choose the objects to sync (such as DuckDB's Schemas and Tables), 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. DuckDB: It queries Parquet, CSV, and JSON files directly without importing them, which makes file-based exchange a natural sync pattern. Stacksync's field mapping accounts for these differences between DuckDB 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 DuckDB and Salesforce records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Salesforce connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Salesforce integration in-house.
-
Yes — Stacksync ships production-grade connectors for both DuckDB and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. 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 DuckDB and Salesforce.
Popular · 8 of 386
-
DuckDB ⇄ SugarCRM -
DuckDB ⇄ Twenty CRM -
DuckDB ⇄ Veeva CRM -
DuckDB ⇄ Vtiger CRM -
Salesforce ⇄ Redis Enterprise -
Salesforce ⇄ SAP ASE (Sybase) -
Salesforce ⇄ Scaleway Postgres -
Salesforce ⇄ TiDB
No integrations match .
