Two-way sync
Changes in Microsoft Dynamics 365 or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics 365 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.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Microsoft Dynamics 365 holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects Products, Activities, Custom Tables, Accounts in Microsoft Dynamics 365 to Contacts, Leads, Opportunities, Cases in Salesforce with bi-directional, real-time sync. Activity and record changes in Microsoft Dynamics 365 update the matching contact or account in Salesforce, and CRM data flows the other way wherever Microsoft Dynamics 365 can store and use it.
Owner, lifecycle stage, or account details from Salesforce sync into Microsoft Dynamics 365, so people working there have the context without switching tools.
Tickets and conversations attach to the right contact and account in Salesforce, so sales sees open issues before the next call.
Enriched fields land directly on records in Salesforce, and refreshes keep them from going stale.
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.
| Microsoft Dynamics 365 objects | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Leads Inbound records enriched and routed from external sources into sales queues. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and Cases to Salesforce — each maps to any object or custom field on the other side. | |
| Products Catalog records aligned with ERP item masters. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Products is specific to Microsoft Dynamics 365 and Campaigns to Salesforce — each maps to any object or custom field on the other side. |
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.
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365–Salesforce connection.
Changes in Microsoft Dynamics 365 or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics 365 or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Microsoft Dynamics 365 or Salesforce record.
Track your Microsoft Dynamics 365 ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 and Salesforce.
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 Microsoft Dynamics 365 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.
Pick the Microsoft Dynamics 365 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.
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 Microsoft Dynamics 365 and Salesforce: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Accounts and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Microsoft Dynamics 365 and Salesforce: Where Microsoft Dynamics 365 can store CRM context: fields kept current; Where Microsoft Dynamics 365 handles support or shared inboxes; Where Microsoft Dynamics 365 supplies contact or company data. Owner, lifecycle stage, or account details from Salesforce sync into Microsoft Dynamics 365, so people working there have the context without switching tools.
Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). Salesforce: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Microsoft Dynamics 365: CDC on custom entities does not work until Change Tracking is manually enabled per table in Power Apps/Dataverse. Salesforce: Records are queried with SOQL, and every standard and custom object carries a SystemModstamp field that sync engines use to order incremental changes. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 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 Microsoft Dynamics 365 and Salesforce records are not retained after a sync operation.
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 544 integrations available for Microsoft Dynamics 365 and Salesforce.