Start with one meaningful update
Identify the record that changes in Close or MotherDuck, where it needs to appear, and which team depends on it.
CRM / Data warehouse
Close and MotherDuck integration
Plan how Close and MotherDuck should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Integration planning
stacksync.com Your integration scope
Start with the update your team needs
Bring the source, destination, and record types. A Stacksync engineer will help establish the available implementation path.
Review the integration scopeBuild the right connection
Turn your integration requirement into a clear implementation path
Explore a Close and MotherDuck integration with a Stacksync engineer. Stacksync support for Close is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
Establish the available connection
Bring the objects, account editions, and required directions. An engineer can review the connector path, permissions, and field access.
Define a result you can verify
Agree on record matching, acceptable delay, expected volume, and how your team will resolve failed updates.
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
Data and connection referencesAvailable documentation, candidate record relationships, and questions for your technical review.
Record coverage for your integration
Compare the record types in Close and MotherDuck, then choose the ones your workflow needs. Check each record's read and write support before mapping fields between systems.
Close
Record types to review with Stacksync
| Object or data type | Coverage and checks |
|---|---|
| Leads | Confirm support for this record type and the direction you need. |
| Contacts | Confirm support for this record type and the direction you need. |
| Opportunities | Confirm support for this record type and the direction you need. |
| Activities | Confirm support for this record type and the direction you need. |
View 2 more record types
| Object or data type | Coverage and checks |
|---|---|
| Tasks | Confirm support for this record type and the direction you need. |
| Custom Activities | Confirm support for this record type and the direction you need. |
MotherDuck
Record types covered in the setup guide
| Object or data type | Coverage and checks |
|---|---|
| Tables (confirm coverage) | See connector requirements. Confirm field permissions and sync direction. |
Connection requirements and limits
Close
- Integration interface
- REST API
- Authentication
- Confirm the credentials, API plan, and permissions required for Close.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Limitations to check
- Confirm Stacksync support for Close and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
MotherDuck
- Integration interface
- 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
- The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
- Read access
- Available for supported records
- Write access
- Available for supported records
Limitations to check
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare your technical review
Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.
Implementation reference
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheetCSV · No email required · Record matching, ownership, and test cases
Reporting datasetContacts Proposed contact table in MotherDuck (choose its name)
Plan a contact dataset while preserving its source meaning.
- Close
- Object support to establish
- MotherDuck
- Your database schema
Record identity
Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Field ownership
Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.
Fields to include
- Source person ID
- Display name
- Email address
- Organization reference
- Consent state
Reporting datasetOpportunities Proposed deal or opportunity table in MotherDuck (choose its name)
Plan a deal or opportunity dataset while preserving its source meaning.
- Close
- Object support to establish
- MotherDuck
- Your database schema
Record identity
Keep the opportunity/deal ID separate from any later order or invoice ID.
Field ownership
The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.
Fields to include
- Source deal ID
- Stage
- Amount and currency
- Expected close date
- Company reference
Reporting datasetLeads Proposed prospect or lead table in MotherDuck (choose its name)
Plan a prospect or lead dataset while preserving its source meaning.
- Close
- Object support to establish
- MotherDuck
- Your database schema
Record identity
Retain the lead ID and record its relationship to any converted contact or company.
Field ownership
Choose which system may qualify or convert the lead; do not infer identical lifecycle stages.
Fields to include
- Source lead ID
- Qualification status
- Owner reference
- Conversion reference
Reporting datasetUsers Proposed application user or identity table in MotherDuck (choose its name)
Plan a application user or identity dataset while preserving its source meaning.
- Close
- Object support to establish
- MotherDuck
- Your database schema
Record identity
Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
Field ownership
Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes.
Fields to include
- Source user ID
- Tenant reference
- Account status
- Group references
Reporting datasetTasks Proposed task or work item table in MotherDuck (choose its name)
Plan a task or work item dataset while preserving its source meaning.
- Close
- Object support to establish
- MotherDuck
- Your database schema
Record identity
Use a stable task/work-item ID and preserve its project or parent-ticket reference.
Field ownership
Choose the owner of task status and assignment; destination workflow states may require an explicit transition.
Fields to include
- Source task ID
- Parent reference
- Assignee
- Status
- Due date
Reporting datasetActivities Proposed event or activity table in MotherDuck (choose its name)
Plan a event or activity dataset while preserving its source meaning.
- Close
- Object support to establish
- MotherDuck
- Your database schema
Record identity
Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.
Field ownership
Decide whether the destination stores an immutable history or only a current-state summary.
Fields to include
- Source event ID
- Event type
- Occurred-at time
- Related record ID
- Payload version
Architecture decision
Choose how to connect your systems
Choose a method around one example record and the update your business needs. Use Contacts / Proposed contact table in MotherDuck (choose its name) to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Close and MotherDuck record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Contacts / Proposed contact table in MotherDuck (choose its name), update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Close and MotherDuck need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.
File or scheduled snapshot
- Best fit
- Consider for a one-time Close / MotherDuck migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow reference
From a business event to the right update
Open a workflow to see its trigger, record relationships, and expected result.
Contact reporting workflow
Starting event: A change to the selected Contacts or Proposed contact table in MotherDuck (choose its name) record needs a defined result in the other system.
- Start with Close Contacts and MotherDuck Proposed contact table in MotherDuck (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve the organization relationship and any owner or consent references required by the destination.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.
If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
Deal or opportunity reporting workflow
Starting event: A change to the selected Opportunities or Proposed deal or opportunity table in MotherDuck (choose its name) record needs a defined result in the other system.
- Start with Close Opportunities and MotherDuck Proposed deal or opportunity table in MotherDuck (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
- Map the customer and sales pipeline before the opportunity; map stage values deliberately.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Prospect or lead reporting workflow
Starting event: A change to the selected Leads or Proposed prospect or lead table in MotherDuck (choose its name) record needs a defined result in the other system.
- Start with Close Leads and MotherDuck Proposed prospect or lead table in MotherDuck (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve owner and campaign references and decide how conversion changes the identity relationship.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.
If it fails: Repair the lead-to-contact conversion link before replaying later updates.
Plan the customer lifecycle across Close and MotherDuck
Starting event: A customer-facing change in Close needs operational context in MotherDuck.
- Select the relevant Leads or Contacts records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
- Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
- Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.
Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.
If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.
Production readiness
Test the behavior your business depends on
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Contacts / Proposed contact table in MotherDuck (choose its name)
Test case
Test an email change, two records sharing an email, and a person associated with multiple organizations.
Expected result
The expected contact relationship is preserved with no duplicate action or unintended write.
Opportunities / Proposed deal or opportunity table in MotherDuck (choose its name)
Test case
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
Expected result
The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.
Leads / Proposed prospect or lead table in MotherDuck (choose its name)
Test case
Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.
Expected result
The expected prospect or lead relationship is preserved with no duplicate action or unintended write.
Users / Proposed application user or identity table in MotherDuck (choose its name)
Test case
Test a renamed login, disabled account, missing group, and a user existing in two tenants.
Expected result
The expected application user or identity relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failure recovery
Find the cause. Restore the data flow.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated contact change
Investigate
Inspect Close Contacts and MotherDuck Proposed contact table in MotherDuck (choose its name), their IDs, and the destination error.
Next action
Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
Rejected or repeated deal or opportunity change
Investigate
Inspect Close Opportunities and MotherDuck Proposed deal or opportunity table in MotherDuck (choose its name), their IDs, and the destination error.
Next action
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Rejected or repeated prospect or lead change
Investigate
Inspect Close Leads and MotherDuck Proposed prospect or lead table in MotherDuck (choose its name), their IDs, and the destination error.
Next action
Repair the lead-to-contact conversion link before replaying later updates.
A record type or update is unavailable
Investigate
Check the Close and MotherDuck connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
How updates move between Close and MotherDuck
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Close MotherDuck Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in MotherDuck.
MotherDuck Close Direction requires confirmation
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesConfirm that Stacksync can create or update the records you need in Close.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
Prepare Close and MotherDuck access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Close setup checklist
- Identify the Close account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Close, including read/write support, authentication, and initial-load limits.
MotherDuck setup checklist
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Close and MotherDuck planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
FAQ
Close and MotherDuck integration FAQ
-
Explore a Close and MotherDuck integration with a Stacksync engineer. Stacksync support for Close is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Contacts in Close and Proposed contact table in MotherDuck (choose its name) in MotherDuck. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Contacts / Proposed contact table in MotherDuck (choose its name) to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Close account, edition, environment, and business objects the integration must access. Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form. Use the pair worksheet to record ownership and acceptance criteria.
Related integration plans
Explore another route involving one of these systems.
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:
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 472 integrations listed for Close and MotherDuck.
Popular · 7 of 472
-
Close and Exasol -
Close and Firebolt -
Close and Google Cloud Platform -
Close and Greenplum -
MotherDuck and Vtiger CRM -
MotherDuck and Zoho SalesIQ -
MotherDuck and ZoomInfo
No integrations match .
