Salesforce Microsoft Dynamics 365 integration for manufacturers
What should sync between Salesforce and Microsoft Dynamics 365
| Salesforce | Microsoft Dynamics 365 | Direction | Why it matters |
|---|---|---|---|
| Accounts | Customers, bill-to customers and ship-to addresses | Dynamics → Salesforce for terms and credit | Business Central can bill a different customer than it ships to; carry both on the order. |
| Products and price books | Items, variants and price lists | Dynamics → Salesforce | Item variants and units of measure must map cleanly to Salesforce products. |
| Accepted quote | Sales order | Salesforce → Dynamics | Lines, prices, discounts and dates, with the Salesforce quote ID on the order. |
| Shipments | Posted shipments | Dynamics → Salesforce | Delivery status on the Salesforce order. |
| Invoices and balances | Posted invoices, customer ledger | Dynamics → Salesforce | Read-only for reps. |
| Companies or legal entities | Companies (BC) or legal entities (F&SCM) | Mapped once | Each order must land in the right company. |
Start with the quote-to-order flow. That's where manufacturers lose the most: orders retyped into the ERP at a different price, the wrong ship-to, or options left off. Everything else can follow.
Ways to connect Salesforce and Microsoft Dynamics 365
MuleSoft
Salesforce-owned, with Dynamics connectivity. Good when Salesforce is the hub.
Azure Integration Services
Logic Apps and Service Bus. Natural when your IT team already runs Azure.
Packaged connectors
AppExchange or Microsoft-side sync apps. Quick for standard objects; check variant and multi-company handling first.
We're tool-agnostic. The right choice depends on what your IT team already runs and how many systems will join later. MuleSoft is the common choice when Salesforce is the hub.
Where Salesforce Dynamics 365 integrations go wrong
- Which Dynamics. Business Central and Finance and Supply Chain Management have different data models and APIs. Scope starts here.
- Bill-to vs sell-to. Dynamics separates the customer you sell to from the one you bill. One Salesforce account often maps to both, or to several.
- Companies and legal entities. Multi-company setups need the company decided on the account or the quote, not guessed by the integration.
- Quotes in two places. Dynamics has its own sales quotes. Keep quoting in Salesforce and create the Dynamics order on acceptance.
- Light tools for heavy flows. Power Automate is fine for alerts; order creation needs error handling and replay, which is what an integration platform gives you.
Quote to order: the flow that pays for the integration
For a manufacturer, the integration isn't about syncing records; it's about the quote the customer accepted becoming the order you build and bill. With Revenue Cloud or CPQ in Salesforce, the accepted quote creates the Microsoft Dynamics 365 order with the same configuration and price, and the order and invoice come back linked to it. That's what lets you check, deal by deal, that what was quoted is what was ordered and billed. We call that check a Leak Ledger.
Our experience. We've connected Salesforce to SAP, NetSuite, Microsoft Dynamics, Epicor and Infor in delivered projects.
Moving off Salesforce CPQ at the same time? Design the ERP handoff into the Revenue Cloud build, not after it. See Salesforce CPQ end of sale.
Other ERP integrations
Salesforce + SAP
Quote to order, status and invoices back.
ERPSalesforce + NetSuite
Quote to order, status and invoices back.
ERPSalesforce + Epicor
Quote to order, status and invoices back.
ERPSalesforce + Infor SyteLine
Quote to order, status and invoices back.
ERPSalesforce + SYSPRO
Quote to order, status and invoices back.
ERPSalesforce + Acumatica
Quote to order, status and invoices back.
All of this sits within our Salesforce practice for manufacturers and our CRM-to-ERP integration work.
Who we are
Nteli is a Salesforce Premier Partner headquartered at Capital Factory in Austin, specializing in Quote-to-Order for specialty manufacturers, sold direct and through dealers. We implement Manufacturing Cloud, Revenue Cloud and CPQ, Experience Cloud dealer portals and MuleSoft, with 58 certifications across the team and a 4.93-star average across 10 AppExchange reviews. Before Nteli, our team built product configurators and pricing systems at Cisco, Dell and IBM.
Map your Salesforce Dynamics 365 handoff.
A 30-minute call: what should sync, which system owns pricing, and where your quotes and orders drift today.
FAQ
Does Salesforce integrate natively with Dynamics 365?
No. The two are competing CRM vendors, so integration runs through MuleSoft, Azure Integration Services, a packaged connector, or the Dynamics APIs directly.
Business Central or Finance and Supply Chain Management: does it matter?
Yes. They have different data models and APIs. Business Central exposes REST APIs; Finance and Supply Chain Management uses data entities through OData or Dataverse. The integration design follows from which one you run.
Should quotes live in Salesforce or Dynamics?
In Salesforce, where reps configure and price. The Dynamics sales order is created on acceptance, and shipments and invoices flow back.
How long does a Salesforce Dynamics 365 integration take?
Core quote-to-order flows can go live in weeks. Multiple companies, item variants and pricing ownership add scope.