Real-time
Two-way sync
Changes in Close or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.
CRM
Close to Microsoft Dynamics 365 Sales integration — real-time, two-way sync
Keep Close and Microsoft Dynamics 365 Sales 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 Close and Microsoft Dynamics 365 Sales
Run Close and Microsoft Dynamics 365 Sales side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Tasks, Custom Activities, Custom Fields, Users in Close with Custom Tables, Accounts, Contacts, Leads in Microsoft Dynamics 365 Sales in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
Common use cases
- 01 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
- 02 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
- 03 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.
- 04 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.
Common sync patterns
Migration with a parallel run
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Divisional or regional split
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
Where both track pipeline: deal visibility across systems
Deal stage and value on shared accounts stay visible from either CRM.
What you can sync between Close and Microsoft Dynamics 365 Sales
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 | Microsoft Dynamics 365 Sales objects | How this pairing syncs | |
|---|---|---|---|
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Contacts Person records linked to accounts; synced with marketing and support systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Activities Emails, calls, appointments, and tasks; read out for activity analytics. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. | Users is specific to Close and Custom Tables to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. | Smart Views is specific to Close and Accounts to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. |
How changes propagate between Close and Microsoft Dynamics 365 Sales
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Close Microsoft Dynamics 365 Sales Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Sales Close Sub-second propagation
DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.
DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Close ⇄ Microsoft Dynamics 365 Sales
Connect Close and Microsoft Dynamics 365 Sales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Microsoft Dynamics 365 Sales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close or Microsoft Dynamics 365 Sales 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 Close or Microsoft Dynamics 365 Sales record.
Observability
Monitoring
Track your Close ⇄ Microsoft Dynamics 365 Sales sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Microsoft Dynamics 365 Sales.
How the Close and Microsoft Dynamics 365 Sales connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
Microsoft Dynamics 365 Sales
- Integration surface
- Dataverse Web API (OData v4 REST)
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- Dataverse change tracking with delta tokens, plus registered webhooks on table events
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are governed by Dataverse service protection limits evaluated per user and time window.
How it works
How to connect Close to Microsoft Dynamics 365 Sales — 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 Close and Microsoft Dynamics 365 Sales with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Close
connected
Microsoft Dynamics 365 Sales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close and Microsoft Dynamics 365 Sales 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 · Close ⇄ Microsoft Dynamics 365 SalesCustomers 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.
Close Microsoft Dynamics 365 SalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Microsoft Dynamics 365 Sales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Microsoft Dynamics 365 Sales: authenticate both systems, choose the objects to sync (such as Close's Leads and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Microsoft Dynamics 365 Sales: Data lives in Dataverse tables exposed through an OData v4 Web API, so standard query options handle filtering, expansion, and paging. Stacksync's field mapping accounts for these differences between Close and Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and Microsoft Dynamics 365 Sales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Microsoft Dynamics 365 Sales integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Close and Microsoft Dynamics 365 Sales. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. On Microsoft Dynamics 365 Sales: Dataverse change tracking with delta tokens, plus registered webhooks on table events. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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
Every pair below is a real-time, two-way sync. Search all 454 integrations available for Close and Microsoft Dynamics 365 Sales.
Popular · 6 of 454
-
Close ⇄ SugarCRM -
Close ⇄ Twenty CRM -
Close ⇄ Veeva CRM -
Close ⇄ Vtiger CRM - Microsoft Dynamics 365 Sales ⇄ SugarCRM
- Microsoft Dynamics 365 Sales ⇄ Twenty CRM
No integrations match .
