Business Central integration with Dynamics 365 Sales connects your finance and CRM systems so sales reps and finance teams work from the same customer, inventory, and order data. Instead of switching screens or re-entering information, a salesperson can check stock levels, credit status, and pricing from Business Central without leaving Dynamics 365 Sales. This guide covers how the integration works, what it costs in 2026, common pitfalls, and a step-by-step setup path for U.S. businesses.
If you searched for this topic, you are probably trying to answer one of three questions: does this integration make sense for my business, how much does it cost to license and implement, or how do I actually set it up without breaking anything. We will answer all three, using current Microsoft pricing and the latest connector capabilities.
Table of Contents
- What Is Business Central Integration with Dynamics 365 Sales?
- How Integration Actually Works (Architecture)
- Key Benefits of Business Central Integration with Dynamics 365 Sales
- What Does Business Central and Dynamics 365 Sales Integration Connect?
- How the Business Central and Dataverse Connector Works?
- Business Central and Dynamics 365 Sales Integration Approaches
- Limitations of the Business Central/Dataverse Connector
- Common Challenges When Integrating Business Central with Dynamics 365 Sales
- Step-by-Step: How to Set Up Business Central Integration with Dynamics 365 Sales
- How AI Agents Are Changing the Integrated Sales Process
- 2026 Pricing and Licensing for Business Central and Dynamics 365 Sales
- Business Central vs. Dynamics 365 Sales: Who Owns What Data
- Common Mistakes to Avoid
- Real-World Use Case: Quote-to-Cash Without Rekeying
- Which Integration Approach Is Right for Your Business?
- Why Choose Dynamics Square for Your Business Central and Dynamics 365 Sales Integration?
- Frequently Asked Questions
What Is Business Central Integration with Dynamics 365 Sales?
Business Central integration with Dynamics 365 Sales is a native Microsoft connection, built on Dataverse, that synchronizes records such as accounts, contacts, sales orders, and item availability between the two applications. It lets a Dynamics 365 Sales user view Business Central data, like inventory and pricing, directly inside a sales record, and it lets Business Central pull quote and order data created in Sales.
The two systems serve different purposes. Dynamics 365 Sales is the front-office CRM: it manages leads, opportunities, quotes, and relationship history. Business Central is the back-office ERP: it manages financials, inventory, purchasing, and order fulfillment. Left unconnected, sales reps quote deals without knowing real stock levels, and finance teams re-key customer and order data that already exists in the CRM. The integration closes that gap through a bidirectional sync rather than manual exports.
How Integration Actually Works (Architecture)
We already knew, every new Business Central–to–Dynamics 365 Sales connection goes through Microsoft Dataverse that holds the shared schema both applications talk to. There is no direct link between the two applications.
The flow looks like this:
Dynamics 365 Sales ↔ Microsoft Dataverse ↔ Business Central
Nevertheless, below we discussed the four pieces that make the sync work and understanding them matters more than knowing the setup screens, because they explain why data sometimes does not move the way you expect. Including:
Integration table mappings: Each Business Central table that needs to sync (Customer, Item, Sales Order Header) is paired with a matching Dataverse table (Account, Product, Sales Order). This pairing is what Microsoft calls an integration table mapping, and there must be one for every table you want synchronized.
Integration field mappings: With each table mapping, individual fields are matched one to one. A Business Central customer's "Credit Limit" field maps to a specific Dataverse column on Account, for instance. This is also where you added a transformation rule if a value needs reformatting between the two systems, say a status code that's stored as a number in one system and a label in the other.
Coupling: Before two records can sync, they need to be coupled like Business Central's Customer 10000 gets linked to a specific Account row in Dataverse. Once coupled, changes to either record's mapped fields flow to the other.
Synchronization rules: These govern behavior beyond simple field copying, for example what happens to an opportunity's owner field, or how a posted invoice's salesperson code determines record ownership on the Sales side.
Note: On top of the standard Dataverse-level sync, Business Central layers Sales-specific settings once you connect it to Dynamics 365 Sales means which entities are Sales-specific (products, price lists, sales orders), whether sales order sync runs one-way or bidirectionally, and whether item availability updates on its own schedule.
Key Benefits of Business Central Integration with Dynamics 365 Sales
Connecting the two platforms gives sales and finance teams one accurate, shared version of customer and order data instead of two disconnected systems. The practical result is fewer data-entry errors, faster quote-to-cash cycles, and better visibility for both sales reps and finance staff, without requiring custom development for standard scenarios.
| Benefit | What It Means in Practice |
|---|---|
| Scheduled, predictable data sync | Updates to a customer record, order, or price in one system reflect in the other on a job queue schedule, by default every 30 minutes for most Sales entities. That's a world away from a manual export, even if it is not instantaneous, and it is worth setting that expectation with stakeholders early. |
| Less manual re-entry | Customers, contacts, and orders created in Dynamics 365 Sales do not need to be typed again into Business Central. |
| Inventory visibility for sales reps | Reps can check stock availability and pricing from Business Central while building a quote in Sales, so quotes reflect what can actually be delivered. |
| Unified customer view | Finance sees upcoming sales activity; sales sees credit status, order history, and invoices, all from a single coupled record. |
| Customizable sync direction | The Dataverse connector supports filtered, entity-level sync settings, so you can control which fields and record types move between systems and in which direction. |
| Automation-ready | Power Automate can extend the base integration with workflows, such as notifications on sync errors or approval routing on large orders. |
What Does Business Central and Dynamics 365 Sales Integration Connect?
There are two separate mapping layers are involved: the base Dataverse mapping that every Business Central–Dataverse connection uses, and a second, Sales-specific mapping that only activates once Dynamics 365 Sales is connected.
| Business Central | Dynamics 365 Sales / Dataverse | Sync Direction | Why It Matters Operationally |
| Customer | Account | Bidirectional | A rep updates a phone number or address in Sales; finance does not have to chase that change separately in Business Central. |
| Contact | Contact | Bidirectional | Keeps the same person record usable by both a salesperson and an AR clerk without two versions drifting apart. |
| Item | Product | Bidirectional | New items entered into Business Central show up as sellable products in Sales without a manual catalog update. |
| Resource | Product | Bidirectional | Covers billable services and labor the same way items cover physical goods. |
| Vendor | Account | Bidirectional | Relevant mainly where Sales users need vendor visibility for a combined ERP/CRM view. |
| Salesperson | User | Business Central → Sales | Ties order and quote ownership to the same person record on both sides, which matters for commission and pipeline reporting. |
| Opportunity | Opportunity | Bidirectional | Let’s finance see a deal is in motion before it becomes a firm order, useful for cash-flow forecasting, not just sales forecasting. |
| Unit of Measure | Unit Group | Business Central → Sales | Prevents a rep from quoting "10 units" when the actual selling unit is a case of 24. |
| Customer Price Group | Price List | Business Central → Sales | Reps see the price the customer is entitled to, not a generic list price. |
| Sales Price | Product Price List | Business Central → Sales | Same reasoning, at the item level, pricing changes in the ERP show up in the CRM without a manual price-list refresh. |
| Sales Order | Sales Order | Configurable: legacy (one-way) or bidirectional | This is the entity worth planning, see the setup section below. |
| Posted Sales Invoice | Invoice | Business Central → Sales | Gives sales visibility into what's been billed, useful when a customer calls asking about an invoice. |
How the Business Central and Dataverse Connector Works?
The Business Central and Dataverse connector is the tool Microsoft uses to link Business Central with Dynamics 365 Sales and other Dataverse-based apps. It works by "coupling" a record in one system to its equivalent in the other, for example an account in Sales to a customer in Business Central, and then syncing changes to coupled fields on a scheduled or near-real-time basis.
Setup happens in two stages. First, you connect Business Central to Dataverse using the assisted setup guide, which lets you choose which entities (customers, contacts, vendors, items) to synchronize. Second, you configure the Dynamics 365 Sales-specific settings inside Business Central, including which sales orders, quotes, and price lists should flow between the systems.
According to Microsoft, integration is only supported between Business Central and Dynamics 365 Sales; other apps that alter the standard Sales data model, such as older Project Service Automation customizations, can break the sync.
A detail worth knowing before you start: reconnecting through Dataverse, whether because you are setting up for the first time, upgrading, or re-enabling after turning integration off, applies Microsoft's default table mappings and can overwrite any custom sync configuration you had in place.
Furthermore, once the connection is live, six synchronization jobs run in a fixed order to respect record dependencies (units of measure and products must exist before prices and orders that reference them can sync):
unit of measure,
resource-to-product,
item-to-product,
customer price group-to-price list,
sales price-to-product price
and posted sales invoice-to-invoice
Most run on a 30-minute cycle by default, and each can be rescheduled from the Job Queue Entries page in Business Central if your data volume calls for a different cadence.
Business Central and Dynamics 365 Sales Integration Approaches
Here are the three ways, and picking the wrong one is a more common source of integration pain than any technical bug in the connector itself.
Approach 1: Native Dataverse Integration (the default path)
This is the architecture described above, and it should be the starting point for most businesses. It is the path Microsoft builds, maintains, and documents, which means upgrades and platform changes are handled for you rather than by a developer on your payroll.
Use it when both applications are cloud-based, your synchronization needs match the standard entities (customers, items, orders, prices, invoices), and you had rather configure a connection than build one. Most single-company, cloud-only U.S. businesses land here, and for good reason, it costs nothing beyond your existing licenses, and it is the option Microsoft supports long-term.
Approach 2: Power Automate as an Extension Layer
Power Automate does not replace the native connector. It sits alongside it and handles the workflow logic the base sync does not do on its own. It means sending a Teams notification when a large order syncs, routing an approval when a quote exceeds a discount threshold, or pushing a sync failure alert to an admin instead of letting it sit unnoticed in a log.
Think of it as, Business Central / Dataverse → Power Automate → the next action. If your integration needs are "move the data" plus "then do something with it," this is where the "then do something" part lives.
Approach 3: APIs, Virtual Tables, and Custom Integration
Now, this is where a business outgrows the standard entity list. Non-standard applications, custom Dataverse entities, complex transformation rules that go beyond a simple field mapping, or a genuine need for real-time (not scheduled) data all point here. Business Central Virtual Tables expose live, read-through data in Dataverse without duplicating it, and the Business Central APIs support direct, on demand read/write access for scenarios the job queue cannot serve fast enough.
It is the appropriate option for a narrower set of businesses, those with customization deep enough that the standard mapping genuinely does not fit real-time requirement the 30-minute job queue cannot meet. For most standard sales and finance data, it is more infrastructure than the problem calls for.
Limitations of the Business Central/Dataverse Connector
The Business Central/Dataverse connector is reliable for standard sync scenarios, but it is not a universal, real-time, fully customizable integration platform. Businesses with heavily customized environments, multi-entity setups, or on-premises Business Central should understand its boundaries before committing to it as their only integration path.
Sync delays: Data moves on a scheduled basis (every 30 minutes by default for most tables), not instantly, so there can be a short lag between an update in one system and its appearance in the other.
Complex customizations are harder to map: Businesses with heavily customized Business Central environments often need extra configuration or development work to integrate cleanly.
Field mapping gaps: Not every Business Central field has a direct Dataverse or Dynamics 365 Sales counterpart, which can leave some data unsynced without custom mapping.
Performance at scale: Large data volumes or complex sync scenarios can slow down both systems if not properly managed.
Security and compliance overhead: Keeping sensitive financial and customer data compliant across two connected systems takes deliberate permission and role planning, not just a default setup.
No native Quote entity sync: As covered above, quotes only enter Business Central once activated in Sales, at which point they become sales orders. Businesses expecting quote-stage visibility in both systems before activation need a custom approach
Common Challenges When Integrating Business Central with Dynamics 365 Sales
Most integration problems are not technical failures. They come from decisions made, or skipped, during planning: unclear data ownership, mismatched customizations, and permissions that were never fully mapped out. Knowing these challenges ahead of time is the fastest way to avoid a stalled or reworked project.
Data migration accuracy: Inaccurate or incomplete migration during initial setup creates discrepancies that are expensive to untangle later.
Conflicting customizations: Both systems can be extensively customized. Getting those customizations to work together, rather than against each other, takes planning before go-live, not after.
Keeping pace with platform updates: Microsoft updates both applications regularly, and integrations built around specific field structures can require re-testing after major releases.
Permissions and security roles: Every integration user account needs precisely scoped permissions in both systems. Over-permissioned accounts are a common audit finding.
Sync settings that get overwritten: As noted above, reconnecting through Dataverse resets to default synchronization settings, which can silently undo custom configurations if no one is watching for it.
Step-by-Step: How to Set Up Business Central Integration with Dynamics 365 Sales
Here are the five steps that help you to set up the Business Central Integration with Dynamics 365 Sales:
Step 1: Confirm prerequisites
Active cloud subscriptions to both apps, admin access in both, a Dataverse environment linked to your Sales tenant. Set up your integration user now like a dedicated, non-interactive account, never a personal login.
Step 2: Prepare Dynamics 365 Sales
Assign the Business Central Integration Administrator role to whoever runs setup, and the Integration User role to the dedicated account. Import the Business Central Integration Solution if you want coupled-record links.
Step 3: Connect Business Central to Dataverse
Assisted Setup → Set up Microsoft Dataverse Connection. Creates the default table mappings including Customer, Vendor, Contact, Salesperson, Currency.
Step 4: Connect Business Central to Dynamics 365 Sales
Assisted Setup → Set up the Dynamics 365 Sales Connection. Decide whether to import the Sales Solution, turn on Automatically Synchronize Item Availability, and pick your sales order model.
Step 5: Choose your sales order sync model
Now, you must pick one of two mutually exclusive options, and this decision shapes how your sales team works day by day. It includes
Bidirectional Synch of Sales Orders: Orders move both ways, lines lock until synced, Business Central archives each change.
Legacy Sales Order Integration: One way, Sales to Business Central only, needs a Sales admin credential. Still supported but avoid it for a new setup.
Step 6: Map and test in order
Sync jobs run in dependency order means units of measure and products first, then prices, then a few customers and contacts, then a handful of test orders. Syncing orders before the products or prices they reference is the most common setup mistake.
Step 7: Test before production
Run a small batch through customer sync, item availability, pricing, a quote-to-order conversion, and a full order-to-invoice cycle. Check the integration account's permissions at the same time.
Step 8: Document everything
Save your table mappings, sync direction choices, and job queue schedule. Reconnecting through Dataverse resets to defaults and can silently overwrite custom settings.
How AI Agents Are Changing the Integrated Sales Process
Integration itself has not changed its core mechanics much in the past year, but what sits on top of it has. As of the 2026 release waves, both applications ship agentic capabilities that lean directly on the synchronized data this integration provides.
Business Central sales order agent monitors a designated mailbox, reads incoming customer emails asking about products or availability, checks real inventory, and drafts a quote or order for a Business Central user to review and send. It is a production-ready feature as of Business Central's mid-2026 update wave, and it bills on a consumption basis through Copilot Credits rather than through the per-user license, so it is worth budgeting for separately from your Essentials or Premium seats. In addition, if you are specifically researching the Business Central sales order agent, that consumption-based billing detail is the one that most often gets missed in planning.
Business Central Copilot AI agents for sales work in the other direction. Copilot in Sales gives reps record summaries and meeting prep inside the CRM, and Microsoft has layered specific agents on top of that for lead qualification, opportunity research, and deal-closing support, each pulling from the same coupled customer and order data this integration keeps in sync.
2026 Pricing and Licensing for Business Central and Dynamics 365 Sales
As of the November 2025 Microsoft price update, Business Central licenses cost $80 per user per month for Essentials and $110 per user per month for Premium, while Dynamics 365 Sales licenses range from $65 per user per month for Sales Professional to $105 for Sales Enterprise. Actual costs depend on user mix, implementation scope, and whether you qualify for Microsoft's multi-app attach pricing. You can also read the blog for Business Central Essentials vs Premium.
| License | Monthly Price (Per User) | Best For |
|---|---|---|
| Business Central Team Member | $8 | Light, read-mostly users who need visibility but not transaction entry |
| Business Central Essentials | $80 | Core financials, inventory, sales, and basic CRM functionality |
| Business Central Premium | $110 | Essentials plus manufacturing and service management |
| Dynamics 365 Sales Professional | $65 | Core sales force automation for smaller teams |
| Dynamics 365 Sales Enterprise | $105 | Full CRM with advanced customization and embedded AI insights |
| Dynamics 365 Sales Premium | $150 | Advanced forecasting, conversation intelligence, and Copilot features |
A few things to budget for beyond the license line item:
Attach pricing: If a user already holds one Dynamics 365 application license, Microsoft's multi-app discount can bring the price of an additional app down substantially, which matters if the same person needs both Business Central and Sales access.
Implementation costs: Licensing is only part of the total cost. Implementation, data migration, and integration configuration typically add a separate one-time investment on top of the recurring subscription.
Storage: Microsoft increased including storage alongside the late-2025 price change, so check your current entitlement before assuming you need a paid add-on.
Copilot Credits: If you turn on Sales Order Agent or lean on the newer Copilot agent capabilities in Dynamics 365 Sales, budget for consumption-based Copilot Credit usage separately from your per-user license fees. Credits are billed on usage, not seats, so cost scales with how much the agents do rather than with headcount.
For the authoritative, always-current numbers, refer to Microsoft's official Dynamics 365 pricing page, since list prices are subject to change.
Business Central vs. Dynamics 365 Sales: Who Owns What Data
The cleanest integrations start by deciding, in writing, which system is the source of truth for each type of data. Finance-owned fields, like credit limits and payment terms, should stay authoritative in Business Central. Sales-owned fields, like account ownership and pipeline stage, should stay authoritative in Dynamics 365 Sales.
| Data or Process | Owned By | Why |
|---|---|---|
| Credit limits, payment terms | Business Central | Finance controls risk and billing policy |
| Inventory and item availability | Business Central | Reflects real stock and fulfillment capacity |
| Lead and opportunity stage | Dynamics 365 Sales | Sales owns the pipeline and forecasting process |
| Quotes (pre-activation) | Dynamics 365 Sales | Created and revised by reps before they become firm orders |
| Sales orders (post-activation) | Business Central | Fulfilled, shipped, and invoiced from the ERP |
| Account ownership | Dynamics 365 Sales | Reflects territory and relationship assignment |
Common Mistakes to Avoid
Skipping the ownership conversation: Teams that do not agree on data ownership before go-live end up with sync conflicts that are hard to trace back to a root cause.
Assuming "Dynamics 365" means automatic compatibility: Business Central and Dynamics 365 Sales share a brand name but are separate applications; the connection between them is deliberate work, not something that happens by default.
Manually overriding sync direction settings: Business Central will revert manual changes to integration table mapping direction back to its configured default, so changes need to go through the connection setup, not ad hoc edits.
Forgetting to re-document after a reconnect: Because reconnecting through Dataverse resets custom sync settings, any team that skips documentation risks losing weeks of configuration work without realizing it until data stops syncing correctly.
Under-scoping security roles: Giving the integration user account broader access than it needs increases audit risk without adding any functional benefit.
Enabling both sales order sync options at once: Bidirectional Sync of Sales Orders and Legacy Sales Order Integration are mutually exclusive. Trying to run both, or switch between them without a clean cutover, is a quick way to end up with duplicate or orphaned orders.
Real-World Use Case: Quote-to-Cash Without Rekeying
A distribution company with a five-person sales team and a shared finance department is a common scenario. Before integration, a rep would build a quote in Dynamics 365 Sales without visibility into current stock, and finance would manually create the matching sales order in Business Central once the deal closed, often catching pricing or inventory mismatches after the fact.
After integrating, the rep checks live inventory and current pricing from Business Central while still working inside the Sales quote screen. Once the quote is activated, it flows into Business Central as a sales order without anyone re-typing customer or line-item details. Finance processes fulfillment and invoicing from data that already matches what the customer agreed to, cutting the quote-to-invoice cycle and reducing the back-and-forth between departments that used to happen over email.
Read more case studies here.
Which Integration Approach Is Right for Your Business?
As we know, every business's mix of customization, on-prem legacy systems, and existing tooling shifts the calculation. Therefore, choose the right approach as per your business requirements from the below table:
| Business requirement | Suitable approach |
| Standard cloud Business Central + cloud Sales, customers/items/orders sync | Native Dataverse integration |
| Notifications, approvals, or extra workflow steps around synced data | Native integration + Power Automate |
| Non-standard entities, complex transformations, or external systems | API or custom integration |
| A genuine real-time data requirement | Business Central Virtual Tables or APIs, not scheduled sync |
| On-premises Business Central | A separate on-premises integration path; see Microsoft's on-premises documentation, since the cloud-only Dataverse path does not apply directly |
| Multiple companies or entities with complex currency or tax rules | Native integration with multi-company synchronization enabled, or a partner-led assessment if customization runs deep |
Why Choose Dynamics Square for Your Business Central and Dynamics 365 Sales Integration?
Dynamics Square has helped U.S. businesses plan and execute Microsoft Dynamics 365 integrations for more than 15 years, backed by certified Microsoft consultants and a track record of 500+ successful implementations across manufacturing, distribution, and professional services.
Why businesses work with us:
Deep Dynamics 365 expertise: We work across Business Central, Dynamics 365 Sales, and the wider Dynamics ecosystem, so your integration is designed by people who understand both the finance and sales sides of the platform, from core Business Central accounting software functionality through to CRM side sales processes.
Certified Microsoft consultants: Our team holds current Microsoft certifications and stays current as Microsoft updates the Dataverse connector and licensing structure.
U.S.-based support with a national footprint: We serve clients from offices in California, Texas, Illinois, and New Jersey, with additional presence across the USA, UK, and Canada.
Configuration, not guesswork: We help you make the data-ownership, sync-direction, and integration approach decisions upfront, so you avoid the rework that comes from skipping that step.
Ready to connect Business Central and Dynamics 365 Sales without the trial and error? Call us at +1 281 899 0865 or email arish.siddiqui@dynamicssquare.com to schedule a free consultation. Book your demo from here.
Frequently Asked Questions
It gives sales reps visibility into Business Central data, like inventory levels and pricing, while they work in Dynamics 365 Sales, so quotes are accurate and orders move to fulfillment without manual re-entry.
Create a dedicated connection user in Dynamics 365 Sales, install the Business Central Integration Solution if you need coupled-record links, and then connect Business Central to Dataverse using the assisted setup guide to choose which entities sync.
You need valid subscriptions to both applications, the correct security roles in Dynamics 365 Sales (including the Business Central Integration Administrator role), and the Business Central Integration Solution installed if you want coupled-record access.
Yes, sync settings can be customized by entity and field. However, reconnecting through Dataverse, whether for a first-time setup, an upgrade, or re-enabling after turning integration off, resets to Microsoft's default mappings and can overwrite your custom configuration.
Turning the integration off or upgrading requires reconnecting through Dataverse to turn it back on, which reapplies default synchronization settings. Document your custom mappings beforehand so you can reconfigure them afterward.
Yes, on-premises integration is supported, but the setup process and requirements differ from the cloud (online) version, and Microsoft documents them separately.
Licensing starts at $80 per user per month for Business Central Essentials and $65 per user per month for Dynamics 365 Sales Professional, based on Microsoft's list pricing after the November 2025 update. Implementation and configuration costs are separate and depend on your data volume and customization needs.
