Two-way sync
Changes in Close or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep Close 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.
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. Opportunities, Activities, Tasks, Custom Activities from Close land in MotherDuck as live tables, updated within seconds, and columns computed in MotherDuck write back to fields in Close. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Deduplication and normalization done in MotherDuck can be written back, so warehouse-side cleanup actually fixes the CRM.
Accounts, contacts, and activity from Close are queryable in MotherDuck moments after they change, so dashboards stop lagging the reality they describe.
Lead scores, churn risk, or usage segments computed in MotherDuck appear as fields in Close, where the people working accounts actually see them.
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.
| Close objects | MotherDuck objects | |
|---|---|---|
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Schemas Namespaces within a database used to organize synced tables. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Tables The main landing target for synced records and source for analysis. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Views Modeled projections used as outbound sync sources. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–MotherDuck connection.
Changes in Close or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close or MotherDuck data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Close or MotherDuck record.
Track your Close ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close and MotherDuck.
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.
Authenticate Close 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.
Pick the Close 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Close and MotherDuck: authenticate both systems, choose the objects to sync (such as Close's Users and Smart Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Close: REST API. Authentication: API key (sent via HTTP Basic auth). MotherDuck: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. 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 Close and MotherDuck 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 Close and MotherDuck records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and MotherDuck connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–MotherDuck integration in-house.
Yes — Stacksync ships production-grade connectors for both Close and MotherDuck. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Close and MotherDuck.