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 Dynamics 365 F&O 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 Dynamics 365 F&O Customers or the proposed customer table in SQL Server needs a defined result in the other system.
Start with Dynamics 365 F&O Customers and the proposed customer table in SQL Server. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before 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 verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
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
| Dynamics 365 F&O record | SQL Server record | Record matching | Field ownership |
|---|---|---|---|
| CustomersProposed record; confirm Stacksync object support.Reporting dataset | Proposed customer tableProposed table; choose its name and schema. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| Customer InvoicesProposed record; confirm Stacksync object support.Reporting dataset | Proposed customer invoice tableProposed table; choose its name and schema. | Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. | The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite. |
| Vendor InvoicesProposed record; confirm Stacksync object support.Reporting dataset | Proposed supplier bill tableProposed table; choose its name and schema. | Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. | Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice. |
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 Dynamics 365 F&O 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 Dynamics 365 F&O and SQL Server workflow to test, define what success looks like, and decide who handles failed updates.
Give legacy applications live F&O data through familiar SQL Server Schemas instead of OData calls.
Power custom portals that read and write Sales Orders via SQL Server while F&O remains the system of record.
Retire point-to-point ERP extracts by maintaining one synced set of F&O Tables in SQL Server.
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 | Dynamics 365 F&O | SQL Server |
|---|---|---|
| Integration interface | OData REST endpoint over data entities, plus the Data Management Framework for batch | SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers |
| Authentication | OAuth via Microsoft sign-in | Database credentials entered as a connection string or as parameters |
| Change detection | Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities. | 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 F\&O
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 Dynamics 365 F&O 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 customer 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: Dynamics 365 F&O: Customers 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: Dynamics 365 F&O: Customer Invoices documentation
Reporting dataset
Plan a supplier bill 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: Dynamics 365 F&O: Vendor Invoices documentation
Reporting dataset
Plan a sales order 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: Dynamics 365 F&O: Sales Orders documentation
Reporting dataset
Plan a supplier or vendor 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: Dynamics 365 F&O: Vendors documentation
Reporting dataset
Plan a journal or ledger entry 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: Dynamics 365 F&O: General Journal Entries documentation
Use Dynamics 365 F&O Customers and SQL Server Proposed customer 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 Customers or Proposed customer table in SQL Server (choose its name) record needs a defined result in the other system.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Customer Invoices or Proposed customer invoice table in SQL Server (choose its name) record needs a defined result in the other system.
Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Vendor Invoices or Proposed supplier bill table in SQL Server (choose its name) record needs a defined result in the other system.
Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A finance-owned record in Dynamics 365 F&O needs operational visibility through a selected destination dataset.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
The expected customer relationship is preserved with no duplicate action or unintended write.
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
The expected customer invoice relationship is preserved with no duplicate action or unintended write.
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
The expected supplier bill relationship is preserved with no duplicate action or unintended write.
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
The expected sales order 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 Dynamics 365 F&O Customers and SQL Server Proposed customer table in SQL Server (choose its name), their IDs, and the destination error.
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Inspect Dynamics 365 F&O Customer Invoices and SQL Server Proposed customer invoice table in SQL Server (choose its name), their IDs, and the destination error.
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Inspect Dynamics 365 F&O Vendor Invoices and SQL Server Proposed supplier bill table in SQL Server (choose its name), their IDs, and the destination error.
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Check the Dynamics 365 F&O 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 changesFull and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.
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 Dynamics 365 F&O. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects Dynamics 365 F&O 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 environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required. 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 Customers in Dynamics 365 F&O and Proposed customer 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 Dynamics 365 F&O Customers and SQL Server Proposed customer 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.
Further reading
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 447 integrations listed for Dynamics 365 F&O and SQL Server.
Popular · 4 of 447
SQL Server and Manhattan Associates WMS 
SQL Server and Microsoft Dynamics GP SQL Server and Microsoft Dynamics NAV 
SQL Server and Plex ERP Next step
Walk through your Dynamics 365 F&O and SQL Server records, field mappings, and requirements with an integration engineer.
