INTEGRATIONSMICROSOFT DYNAMICS 365 BUSINESS CENTRAL + SALESFORCEConnect Business Central to Salesforce
Your sales teams work in Salesforce; your finance, stock and delivery run in Business Central. An integration turns won opportunities into sales orders without retyping, and gives the account team visibility of invoices, outstanding balance and delivery. Sales and finance then work from the same numbers.
ISO 9001 & 27001
- Account to customer comes from Salesforce
- Opportunity to sales order comes from Salesforce
- Items and prices to Salesforce goes to Salesforce
- Outstanding balance and credit limit goes to Salesforce
- Invoices and delivery status goes to Salesforce
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
You see this combination at mid-sized organisations that were already using Salesforce before they chose Business Central, or that deliberately keep sales and finance in separate systems. Out of the box, Microsoft connects Business Central to its own CRM, Dynamics 365 Sales, through Dataverse. For Salesforce, Microsoft has no comparable integration.
Without an integration, someone retypes the opportunity as a sales order, sales emails to ask whether a customer can still order, and nobody is sure which price is right. With an integration, it's settled that Business Central leads for items, prices, credit limit and invoices, and Salesforce for the customer relationship and the pipeline.
For each item: which direction it goes, when, and why. This is the starting point; in the first conversation we fit it to your situation.
- 01Account to customerSalesforce → Microsoft Dynamics 365 Business Centralon the first won opportunity
The Salesforce account becomes a customer in Business Central, with the right VAT and posting groups. The customer number goes back to the account.
- 02Opportunity to sales orderSalesforce → Microsoft Dynamics 365 Business Centralat Closed Won
The opportunity and its products become a sales order or sales quote in Business Central, with item numbers, quantities and agreed prices.
- 03Items and prices to SalesforceMicrosoft Dynamics 365 Business Central → Salesforceon a change in Business Central
Items and prices from Business Central fill the products and price books in Salesforce, so a salesperson only sells what exists, at a price that's right.
- 04Outstanding balance and credit limitMicrosoft Dynamics 365 Business Central → Salesforcedaily or on a change
For each account, the outstanding balance, overdue items and credit limit are added to Salesforce. Before a new deal, the account team can see whether there's room.
- 05Invoices and delivery statusMicrosoft Dynamics 365 Business Central → Salesforcewhen an invoice or shipment is posted
Posted invoices and shipments become visible on the account or opportunity, so service and sales don't have to ask how things stand.
Not always. If an existing integration for Microsoft Dynamics 365 Business Central and Salesforce does exactly what you need, we'll tell you.
Microsoft provides a built-in CRM integration for Dynamics 365 Sales through Dataverse, not for Salesforce. Microsoft AppSource and Salesforce AppExchange list apps from other parties for this combination.
An app like that works if your data model stays close to the standard: accounts, contacts, products and orders without many custom fields. If you have custom objects in Salesforce, extensions in Business Central or several companies, check exactly which fields an app takes along and what happens when something doesn't fit.
- You have custom objects or fields in Salesforce, such as contract lines or project phases, that need a place in Business Central.
- You work with several companies in Business Central and the opportunity determines which company delivers and invoices.
- Pricing agreements, tiered prices or discount rules need to come out the same in both systems.
- You want to hold back an opportunity if the customer is over their credit limit.
- Fields the Business Central standard API doesn't know need to come along; that requires a custom API page.
AI reads, sorts and prepares a suggestion. Where it matters, a person decides.
Credit check for the salesperson
Before Closed Won, AI adds a short summary to the opportunity: outstanding balance, overdue items, credit limit and payment behaviour. If the customer is over the limit, the order goes to finance for review instead of straight to Business Central.
Orders that deviate
An opportunity with a price below the agreed minimum, or a product that's blocked in Business Central, doesn't automatically become a sales order. AI explains what deviates; a person decides.
Which system leads
Business Central leads for items, prices, customer number, credit limit and everything that's been posted. Salesforce leads for the relationship, contacts and the pipeline. Make the financial fields in Salesforce read-only.
Webhooks expire
Business Central webhooks expire after three days, and the notifications only say which record has changed. The integration needs to renew subscriptions and fetch the data for each notification. Also build a periodic check for missed changes.
Limits on both sides
Business Central allows 6,000 OData requests per five minutes per user, with 5 being processed at the same time. Salesforce has its own API limits. So schedule a first sync of all accounts and products outside office hours, in batches of at most 100 operations.
Posting groups for new customers
A customer without the right posting groups for VAT and revenue can't be invoiced correctly. Have the integration create new customers from a customer template per country or customer type.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Account to customer, Opportunity to sales order, Items and prices to Salesforce, Outstanding balance and credit limit, Invoices and delivery status.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: Which system leads, Webhooks expire, Limits on both sides, Posting groups for new customers.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.
No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Does Microsoft have a standard integration between Business Central and Salesforce?
No. Microsoft provides a built-in integration with Dynamics 365 Sales through Dataverse, not with Salesforce. For Salesforce there are apps from other parties on AppSource and AppExchange, or you build an integration on the APIs of both systems.
Does a won opportunity become a sales order or a quote in Business Central?
You choose. If it still needs to be checked or scheduled, a sales quote or an open sales order that a team member releases is a safe start. For simple standard orders, the integration can create a released order straight away.
Can sales see the credit limit and outstanding balance in Salesforce?
Yes. The integration fetches each customer's balance, overdue items and credit limit from Business Central and puts them on the account in Salesforce. Those fields are read-only there; finance makes changes in Business Central.
Which authentication does the integration use for Business Central?
OAuth through Microsoft Entra ID, with service-to-service authentication because the integration runs without a user. You register an app in Entra ID and give it the right permissions in Business Central. The old web service keys no longer work in Business Central online.
How do both systems stay up to date with changes?
On the Business Central side with webhooks through the subscriptions API, which you renew within three days. Because a notification only says which record has changed, the integration then fetches the data. A periodic comparison catches changes that were missed anyway.
Related services
- Connect Business Central to ShopifyConnect Business Central to Shopify: what Microsoft's Shopify Connector does, where VAT and payouts behave differently, and when you need custom work as well.
- Connect Exact Online to SalesforceConnect Exact Online to Salesforce: opportunities to the right administration, payment status back, and a set-up that fits within the Exact API limits.
- Connect Twinfield to SalesforceConnect Twinfield to Salesforce: won opportunities become invoices in the right administration, and open items come back to your account team in Salesforce.
- Connect AFAS to SalesforceConnect AFAS to Salesforce: accounts, opportunities and invoices flow both ways, within the API limits and with AFAS as the financial source of truth.
- Connect Salesforce to ShopifyConnect Salesforce to Shopify: what data to exchange, which building blocks Salesforce provides, which system leads on what, and where things go wrong.
- Connect Claude to SalesforceConnect Claude to Salesforce through the hosted MCP servers or the Salesforce in Claude plug-in. What Claude can read and change, and what to set up first.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.
- Microsoft Learn: integrating with Dynamics 365 Sales
- Microsoft Learn: webhooks (subscriptions)
- Microsoft Learn: operational limits for Business Central online
- Microsoft Learn: service-to-service authentication
- Microsoft Learn: web services authentication
- Microsoft Learn: Business Central API v2.0
- Salesforce Object Reference: OpportunityLineItem