Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

Business productivity · Two-way sync platform

Microsoft Dynamics 365 connector for two-way sync.

Keep Microsoft Dynamics 365 and your business systems aligned with Stacksync. Sync Standard entities and Custom entities within the connector’s object and field requirements, with two-way sync for eligible records.

  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Microsoft Dynamics 365

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
Record types

Microsoft Dynamics 365 objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Standard entities
Requires account access and compatible change tracking
Custom entities
Requires API exposure and compatible change tracking

Read the Microsoft Dynamics 365 object and setup guide

Connection setup

Microsoft Dynamics 365 connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
Account access
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)
How changes are detected
Incremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled.

Sync directions

  • Read data Documented
  • Write data Documented
Microsoft Dynamics 365Stacksync setup guide
Setup prerequisites for your administrator
  • Provide the Dynamics CRM environment URL and authorize the Stacksync app with Microsoft sign-in.
  • For custom entities, enable Track Changes in Power Apps/Dataverse before validating incremental updates.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Microsoft Dynamics 365 integration.

Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
Microsoft Dynamics 365Source record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Preserve each entity’s record ID and its environment context. Define the cross-system match for each custom entity instead of assuming it follows a standard customer model.
Load related records in the right order
List lookup targets and required fields for the selected entity. Load and resolve referenced records before validating a dependent create or update.

Mapping checks by record type

Accounts

Confirm object support with Stacksync

Identity
Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
Fields to consider
Source record ID · Legal or display name · Business-unit reference · Lifecycle status
Related records to resolve first
Resolve parent organizations, business units, and currency references before dependent transactions.
Test before going live
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Contacts

Confirm object support with Stacksync

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.
Fields to consider
Source person ID · Display name · Email address · Organization reference · Consent state
Related records to resolve first
Resolve the organization relationship and any owner or consent references required by the destination.
Test before going live
Test an email change, two records sharing an email, and a person associated with multiple organizations.

Leads

Confirm object support with Stacksync

Identity
Retain the lead ID and record its relationship to any converted contact or company.
Fields to consider
Source lead ID · Qualification status · Owner reference · Conversion reference
Related records to resolve first
Resolve owner and campaign references and decide how conversion changes the identity relationship.
Test before going live
Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.

Opportunities

Confirm object support with Stacksync

Identity
Keep the opportunity/deal ID separate from any later order or invoice ID.
Fields to consider
Source deal ID · Stage · Amount and currency · Expected close date · Company reference
Related records to resolve first
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test before going live
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

Products

Confirm object support with Stacksync

Identity
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Fields to consider
Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference
Related records to resolve first
Resolve units, variants, categories, and applicable price lists before order lines.
Test before going live
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Quotes, Orders & Invoices

Confirm object support with Stacksync

Identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Fields to consider
Source invoice ID · Customer or supplier reference · Line totals · Currency · Posting/payment status
Related records to resolve first
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test before going live
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Microsoft Dynamics 365 integration in four steps.

A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it.

View the four setup tests and expected results

  1. Confirm the intended Microsoft Dynamics 365 account and grant

    Use the documented setup with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity.

    Expected result: The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure.

  2. Change a custom-entity record after backfill

    Enable Track Changes in Power Apps/Dataverse for the selected custom entity, then modify a non-production record after its first load.

    Expected result: The subsequent change reaches the permitted destination and retains the expected lookup relationships.

  3. Test writes in the directions you need

    Select one eligible Microsoft Dynamics 365 object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Microsoft Dynamics 365 records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Microsoft Dynamics 365 integration.

Diagnose record matching, delayed changes, and rejected operations
Standard entities update but a custom entity does not
Verify Track Changes on that custom entity and confirm the connection targets the intended Dynamics environment.
The first load looks correct but later results differ
Incremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Microsoft Dynamics 365 object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Microsoft Dynamics 365 workflow with an engineer

Microsoft Dynamics 365 integration guides

FAQ

Microsoft Dynamics 365 connector FAQ

How should I plan an integration with Microsoft Dynamics 365?

Custom CRM entities need change tracking enabled before incremental validation. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Microsoft Dynamics 365 connector write changes back?

Stacksync supports reads and writes for eligible Microsoft Dynamics 365 objects. Check the selected fields, account permissions, and the other system’s connector. Enable Track Changes in Power Apps/Dataverse for the selected custom entity, then modify a non-production record after its first load.

Which identifiers should I preserve for Microsoft Dynamics 365 data?

Preserve each entity’s record ID and its environment context. Define the cross-system match for each custom entity instead of assuming it follows a standard customer model.

Which related records should I load first for Microsoft Dynamics 365?

List lookup targets and required fields for the selected entity. Load and resolve referenced records before validating a dependent create or update.

What should I check if Microsoft Dynamics 365 data is missing or delayed?

Verify Track Changes on that custom entity and confirm the connection targets the intended Dynamics environment.

What will we cover in a Microsoft Dynamics 365 integration demo?

Start with one workflow and a sample record from Accounts, Contacts and Leads. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Explore Microsoft Dynamics 365 connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

261 integration guides

CRM · 47

ERP · 40

Database · 49

Data warehouse · 30

Business productivity · 38

Accounting and finance · 17

AI · 5

Communications · 1

Developer tools · 11

Human resources · 13

Security and identity · 6

Storage · 4

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.

Learn more about security
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:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started