Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Keep supported Microsoft Dynamics 365 and SQL Server records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Example workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving Microsoft Dynamics 365 Accounts or the proposed company table in SQL Server needs a defined result in the other system.
Start with Microsoft Dynamics 365 Accounts and the proposed company table in SQL Server. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve parent organizations, business units, and currency references before dependent transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyUse two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Review records and field ownershipMapping essentials
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| Microsoft Dynamics 365 record | SQL Server record | Record matching | Field ownership |
|---|---|---|---|
| AccountsProposed record; confirm Stacksync object support.Reporting dataset | Proposed company tableProposed table; choose its name and schema. | 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. | Assign ownership separately for relationship details and finance-controlled billing details. |
| ContactsProposed record; confirm Stacksync object support.Reporting dataset | Proposed contact tableProposed table; choose its name and schema. | 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. | Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone. |
| OpportunitiesProposed record; confirm Stacksync object support.Reporting dataset | Proposed deal or opportunity tableProposed table; choose its name and schema. | Keep the opportunity/deal ID separate from any later order or invoice ID. | The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect Microsoft Dynamics 365 and SQL Server
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Microsoft Dynamics 365 and SQL Server workflow to test, define what success looks like, and decide who handles failed updates.
Two-way sync of accounts and contacts with a Postgres or SQL database so engineers query SQL while sales works in Dynamics.
Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.
Bi-directional sync between SQL Server rows and CRM objects so .NET line-of-business apps and sales tools share one dataset
Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Requires account access and compatible change tracking. Confirm field permissions and sync direction. |
| Requires API exposure and compatible change tracking. Confirm field permissions and sync direction. |
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | Microsoft Dynamics 365 | SQL Server |
|---|---|---|
| Integration interface | REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface | SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers |
| Authentication | Microsoft OAuth sign-in | Database credentials entered as a connection string or as parameters |
| Change detection | Incremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled. | Native SQL Server CDC captures changes after an administrator enables CDC and creates the Stacksync wrapper procedures. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
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:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
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.
Setup guides: Authorize Dynamics 365 CRM
Setup guides: Authorize SQL Server
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 Microsoft Dynamics 365 and SQL Server planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Plan a company dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Microsoft Dynamics 365: Accounts documentation
Reporting dataset
Plan a contact dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Microsoft Dynamics 365: Contacts documentation
Reporting dataset
Plan a deal or opportunity dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Microsoft Dynamics 365: Opportunities documentation
Reporting dataset
Plan a prospect or lead dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Microsoft Dynamics 365: Leads documentation
Reporting dataset
Plan a product or catalog item dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Microsoft Dynamics 365: Products documentation
Reporting dataset
Plan a customer invoice dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Microsoft Dynamics 365: Quotes, Orders & Invoices documentation
Use Microsoft Dynamics 365 Accounts and SQL Server Proposed company table in SQL Server (choose its name) for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Accounts or Proposed company table in SQL Server (choose its name) record needs a defined result in the other system.
Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Contacts or Proposed contact table in SQL Server (choose its name) record needs a defined result in the other system.
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.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Opportunities or Proposed deal or opportunity table in SQL Server (choose its name) record needs a defined result in the other system.
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.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A customer-facing change in Microsoft Dynamics 365 needs operational context in SQL Server.
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.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
The expected company relationship is preserved with no duplicate action or unintended write.
Test an email change, two records sharing an email, and a person associated with multiple organizations.
The expected contact relationship is preserved with no duplicate action or unintended write.
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.
Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.
The expected prospect or lead relationship is preserved with no duplicate action or unintended write.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
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.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect Microsoft Dynamics 365 Accounts and SQL Server Proposed company table in SQL Server (choose its name), their IDs, and the destination error.
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Inspect Microsoft Dynamics 365 Contacts and SQL Server Proposed contact table in SQL Server (choose its name), their IDs, and the destination error.
Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
Inspect Microsoft Dynamics 365 Opportunities and SQL Server Proposed deal or opportunity table in SQL Server (choose its name), their IDs, and the destination error.
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Check the Microsoft Dynamics 365 and SQL Server connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
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.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesIncremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled.
Apply updatesSelected writable fields update in SQL Server. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesNative SQL Server CDC captures changes after an administrator enables CDC and creates the Stacksync wrapper procedures.
Apply updatesSelected writable fields update in Microsoft Dynamics 365. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects Microsoft Dynamics 365 and SQL Server with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Provide the Dynamics CRM environment URL and authorize the Stacksync app with Microsoft sign-in. Use a single generated primary key per table and grant the Stacksync user the required table access. Use the pair worksheet to record ownership and acceptance criteria.
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 Accounts in Microsoft Dynamics 365 and Proposed company table in SQL Server (choose its name) in SQL Server. 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.
Use Microsoft Dynamics 365 Accounts and SQL Server Proposed company table in SQL Server (choose its name) for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 546 integrations listed for Microsoft Dynamics 365 and SQL Server.
Popular · 8 of 546
Microsoft Dynamics 365 and MarkLogic 
Microsoft Dynamics 365 and Neo4j 
Microsoft Dynamics 365 and OCI Database (Oracle Cloud) 
Microsoft Dynamics 365 and OpenSearch 
SQL Server and Gainsight 
SQL Server and Ironclad 
SQL Server and ServiceMax 
SQL Server and Adobe Sign Next step
Walk through your Microsoft Dynamics 365 and SQL Server records, field mappings, and requirements with an integration engineer.
