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 Salesforce 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 Salesforce Accounts needs a defined result in the other system.
Start with Dynamics 365 F&O Customers and Salesforce Accounts. 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 | Salesforce record | Record matching | Field ownership |
|---|---|---|---|
| CustomersProposed record; confirm Stacksync object support.Customer identity assessment | AccountsProposed record; confirm Stacksync object support. | 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. |
| CustomersProposed record; confirm Stacksync object support.Customer identity assessment | ContactsProposed record; confirm Stacksync object support. | 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. |
| Sales OrdersProposed record; confirm Stacksync object support.Business process handoff | OpportunitiesProposed record; confirm Stacksync object support. | Link the originating deal ID to a newly assigned order ID; do not reuse the deal ID as an order number. | Define the approval event and the customer/product data required to create an order. A sales stage alone must not authorize every order. |
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 Salesforce
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 Salesforce workflow to test, define what success looks like, and decide who handles failed updates.
Route Salesforce Cases with full F&O order and invoice context on the Account.
Keep Contacts synced with F&O customer records for accurate billing communication.
Measure Campaign-sourced revenue against actual F&O Customer Invoices rather than pipeline estimates.
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 | Salesforce |
|---|---|---|
| Integration interface | OData REST endpoint over data entities, plus the Data Management Framework for batch | REST, SOAP, and Bulk APIs |
| Authentication | OAuth via Microsoft sign-in | OAuth login via a Salesforce user |
| Change detection | Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities. | Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. |
| 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 Salesforce
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 Salesforce 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
Customer identity
Before linking Dynamics 365 F&O Customers to Salesforce Accounts, check whether the customer is an individual or a company. Match the correct record type in each system.
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 documentationSalesforce: Accounts documentation
Customer identity
Before linking Dynamics 365 F&O Customers to Salesforce Contacts, check whether the customer is an individual or a company. Match the correct record type in each system.
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 documentationSalesforce: Contacts documentation
Business process
Approved sales handoff: Salesforce Opportunities provides context for Dynamics 365 F&O Sales Orders. These are related records, not equivalent entities.
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 documentationSalesforce: Opportunities documentation
Record matching
Compare whether Dynamics 365 F&O Released Products and Salesforce Products and Price Books describe the same product or catalog item in your business.
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: Released Products documentationSalesforce: Products and Price Books documentation
This pair can involve both record sync and process handoffs. Keep the Sales Orders / Opportunities relationship explicit: copying fields and creating a downstream business transaction require different validation.
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 Accounts 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 Customers or Contacts 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 Sales Orders or Opportunities record needs a defined result in the other system.
Expected result: Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.
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 finance-owned record in Dynamics 365 F&O needs operational visibility through Accounts or Contacts.
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 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.
Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.
The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
The expected product or catalog item 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 Salesforce Accounts, 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 Customers and Salesforce Contacts, 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 Sales Orders and Salesforce Opportunities, their IDs, and the destination error.
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Check the Dynamics 365 F&O and Salesforce 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 Salesforce. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
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 Salesforce 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. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. 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 Accounts in Salesforce. 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.
This pair can involve both record sync and process handoffs. Keep the Sales Orders / Opportunities relationship explicit: copying fields and creating a downstream business transaction require different validation.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 445 integrations listed for Dynamics 365 F&O and Salesforce.
Popular · 5 of 445
Dynamics 365 F&O and Chorusai 
Salesforce and Macola ERP 
Salesforce and Manhattan Associates WMS 
Salesforce and Microsoft Dynamics GP Salesforce and Microsoft Dynamics NAV Next step
Walk through your Dynamics 365 F&O and Salesforce records, field mappings, and requirements with an integration engineer.
