
It’s 4 pm on a Thursday at a Dubai trading company. Just then, a seller wins a deal in the CRM. She exports the order, emails it to finance, and an accounts assistant re-types it into the ERP. Then, one wrong digit later, the wrong quantity ships. Dynamics 365 Sales integration with Business Central exists to end that scene: customers, products, prices and orders move between your CRM and your ERP without anyone re-typing them.
(That scene is illustrative, but you have probably lived a version of it.) In this guide, we show what the standard integration does, how an order flows from quote to cash, what the licences cost, how a typical project runs, and the practices that keep the sync clean.
Key takeaways
- Business Central has a built-in, standard connection to Dynamics 365 Sales. New connections run through Microsoft Dataverse and an assisted setup guide.
- Sellers see stock, Business Central prices and customer balances; finance receives submitted orders. Data syncs on a schedule, every 30 minutes by default.
- Your main costs are user licences (Microsoft lists Sales from $65 and Business Central Essentials from $80 per user/month, paid yearly) plus setup work.
What is Dynamics 365 Sales integration?
Dynamics 365 Sales is Microsoft’s CRM. In short, sellers use it for leads, opportunities, quotes and orders. Meanwhile, Business Central is Microsoft’s ERP for small and mid-sized companies, where finance and operations handle stock, shipping, invoicing and accounting.
In other words, the integration is a standard Business Central feature that connects the two. Think of it as a bridge with a timetable. Every scheduled run, approved traffic crosses in the right direction: prices and stock levels go to the sellers, and submitted orders go to finance. As a result, nobody has to carry paperwork across by hand.
Behind the scenes, the bridge is Microsoft Dataverse, the data platform under Dynamics 365 and Power Apps. In fact, Microsoft states that a first-time integration must be set up through Dataverse. In addition, records are linked in pairs, which Microsoft calls coupling. For instance, one customer in Business Central is coupled to one account in Sales.
So what changes for your team in practice? Here is the before-and-after view.
| Daily task | Without the integration | With the integration |
|---|---|---|
| Checking stock before quoting | Call or email the warehouse | Check item availability from Business Central inside Sales |
| Using the right price | Sales keeps its own price sheet | Business Central price lists sync to Sales |
| Entering a won order | Finance re-types it in the ERP | The submitted order is created in Business Central |
| Knowing if it shipped | Ask operations | The order shows Fulfilled in Sales, with events on its timeline |
| Knowing if it was paid | Ask finance | The invoice shows Paid, and the account shows the balance |
Why it matters for UAE & GCC businesses
For example, many companies in the UAE and the wider GCC sell in more than one currency and run more than one legal entity. The integration supports both, although each needs some planning.
- Different currencies. You can connect to a Dataverse environment whose base currency differs from the local currency in Business Central, for example AED in Business Central. However, that base currency must exist on the Currencies page in Business Central with at least one exchange rate. Also, currencies sync one way only, from Business Central to Dataverse.
- Group companies. Similarly, several Business Central companies or environments can sync with one Dataverse environment, and each synced record carries a company ID. For documents such as orders, sellers must enter that company ID, otherwise the document won’t sync.
- Invoicing stays in finance. First, invoices are posted in Business Central and then copied to Sales with the status Billed. Therefore, VAT and e-invoicing work stays in your finance system, which is where an add-on such as our UAE e-invoicing extension for Business Central operates.
How it works: from quote to cash
Once the connection is live, a typical order travels like this:
- Quote (Sales). The seller builds a quote with Business Central prices and checks item availability, which a background job refreshes every 30 minutes when that option is on.
- Submit (Sales). Once the customer agrees, the seller submits the order. After that, its lines are locked in Sales.
- Create order (Business Central). With Automatically Create Sales Orders on, the order appears in Business Central. The order name from Sales lands in the External Document No. field.
- Ship (Business Central). Next, the warehouse ships. Then the Last Shipment Date updates and the order shows Fulfilled in Sales.
- Invoice (Business Central). Finance then posts the invoice and can send it to Sales with the status Billed.
- Get paid (Business Central to Sales). When the payment is recorded and account statistics are updated, the invoice shows Paid and the seller sees the customer’s balance.

What does Dynamics 365 Sales integration cost?
The connector itself is standard Business Central functionality. As a result, the budget question is mostly about licences for the people who use each app, plus the work to set it up. Microsoft’s list prices are:
| Licence | Typically for | Microsoft list price | Notes |
|---|---|---|---|
| Dynamics 365 Sales Professional | Sellers with standard needs | $65 per user/month, paid yearly | Core sales features; customization is limited |
| Dynamics 365 Sales Enterprise | Sellers needing advanced customization | $105 per user/month, paid yearly | Adds Copilot with agent capabilities |
| Dynamics 365 Sales Premium | Sales teams wanting more AI | $150 per user/month, paid yearly | Includes 1,000 Copilot Credits per user/month |
| Business Central Essentials | Finance, sales order and warehouse users | $80 per user/month, paid yearly | Includes Copilot; agents use Copilot Credits sold separately |
| Business Central Premium | Companies that also need manufacturing or service management | $110 per user/month, paid yearly | Everything in Essentials plus those modules |
| Business Central Team Members | Light users who read, approve or make limited updates | $8 per user/month, paid yearly | Limited access |
Microsoft also notes that Business Central users who work with the integrated apps need Dataverse licences assigned, so check how your existing licences cover this before you buy. Beyond licences, however, your total cost depends on how many users sit in each role, how much data needs cleaning before the first sync, any custom field mappings or customizations, and the training and support you want after go-live.
How long does Dynamics 365 Sales integration take?
Microsoft doesn’t publish a standard duration, because it depends on your data and setup. However, the work always follows the same phases, which match the method we use at Mohila:
| Phase | What happens for this integration | Who is involved |
|---|---|---|
| Scoping | Agree which records sync, which app owns each one, and the sales order mode | Sales manager, finance lead, partner |
| Design | Plan field mappings, currencies, company IDs and number series | Partner, finance lead |
| Configuration | Set up the Dataverse connection, run the Sales connection guide, schedule the sync jobs | Administrator or partner |
| Data migration | Remove duplicates, couple records in the right order, run the full synchronization | Partner and data owners |
| Testing | Run quotes and orders through to invoice and payment in a test company | Key users |
| Training | Show sellers and order processors their new daily routine | Partner |
| Go-live | Switch on the scheduled sync and watch the synchronization log | Administrator, partner |
What speeds it up: both apps already in use with clean data, the standard mappings, and one company in one currency. What slows it down: duplicate customers or items, custom fields to map, several companies or currencies, and a Sales app changed by other solutions. Also note that the first full synchronization runs in the background and, according to Microsoft, can take some time. After a free consultation and a look at your data, we can give you a fixed plan.
A practical example: one order, two days
The following scenario is illustrative and does not describe a real client. For instance, picture a building-materials distributor with its head office in Dubai.
Before the integration, a contractor asks for 200 units. First, the seller emails the warehouse to check stock and waits. After that, she builds the quote from a price sheet that is two weeks old. When the contractor accepts, she sends the order to finance, where it is typed again. Finally, two days later, the contractor calls to ask whether it has shipped, and nobody in sales knows.
After the integration, the seller sees availability from Business Central while she quotes, and the price comes from the current Business Central price list. Next, she submits the order, and it appears in Business Central for the order team. Later, when the warehouse ships, the order in Sales shows Fulfilled. Finally, the account shows the invoice as Paid. Meanwhile, if the contractor changes the quantity, the team reopens the order, fixes the lines and resubmits it, and Business Central archives the earlier version.
Best practices for a smooth Dynamics 365 Sales integration
- First of all, clean and de-duplicate customers, contacts and items first, and agree which app owns each type of record.
- Next, couple supporting data first: salespeople, units of measure, currencies and customer price groups, then customers, items and orders.
- Choose one sales order mode, bidirectional or the older one-way option, because Microsoft doesn’t allow both at once.
- Equally, never edit records while signed in as the integration user, because those changes don’t sync. Likewise, don’t edit the price list that Business Central creates in Sales.
- In addition, test the full quote-to-cash flow with real-looking data before go-live, including a currency and a prepayment case.
- After importing the base integration solution, check your Dataverse auditing settings, because Microsoft notes the import can turn auditing off on some tables.
- Above all, set expectations: syncing runs on a schedule. For real-time data, Microsoft points to Business Central virtual tables or APIs.
How Mohila can help
Mohila implements and supports Dynamics 365 Sales and connects it with Dynamics 365 Business Central, so customers, products, quotes and orders flow between sales and finance without re-typing. Our implementation approach runs from scoping and design through data migration, testing, training and go-live, and we stay on for support afterwards.
Talk to an Expert
Book a free 1-hour consultation with a certified Dynamics 365 consultant to plan your Dynamics 365 Sales integration with Business Central.
Frequently asked questions
Yes. The integration is a standard Business Central feature. New connections go through Microsoft Dataverse, and an assisted setup guide walks the administrator through the connection and the main options.
The connector is standard functionality, so the main cost is user licences plus setup work. Microsoft lists Dynamics 365 Sales Professional at $65 and Business Central Essentials at $80 per user/month, paid yearly, excluding VAT and partner services. Local pricing may differ.
Microsoft doesn’t publish a standard duration. It depends on data quality, the number of companies and currencies, and any custom field mappings. The work runs through scoping, design, configuration, data migration, testing, training and go-live, and a partner can give a fixed plan after reviewing your data.
No. Data syncs through scheduled job queue entries, every 30 minutes by default, and you can change the schedule. For real-time access, Microsoft points to Business Central virtual tables or APIs.
Yes, with some setup. Dataverse can use a different base currency from Business Central if that currency and an exchange rate exist in Business Central. Several Business Central companies can also sync with one Dataverse environment, using a company ID on each record.
Sources
- Integrating with Dynamics 365 Sales – Microsoft Learn
- Use Dynamics 365 Sales from Business Central – Microsoft Learn
- Integrate with Microsoft Dataverse via data sync – Microsoft Learn
- Synchronizing data in Business Central with Microsoft Dataverse – Microsoft Learn
- Dynamics 365 Sales pricing – Microsoft
- Dynamics 365 Business Central pricing – Microsoft




