TL;DR: The line item CFOs miss is integration debt — connecting Business Central to your existing CRM, warehouse, payroll, and reporting tools. It never appears on a vendor sheet, and it’s what rewrites the TCO months in.
The spreadsheet looks clean. Licenses, implementation, training, data migration — every line item accounted for, signed off, ready to present to the board. Then six months into the Business Central rollout, a cost appears that nobody budgeted for, and it’s big enough to make the whole TCO comparison look naive in hindsight.
Most finance leaders evaluating a migration do the comparison correctly on paper. They pull Dynamics 365 Business Central pricing against Finance and Operations, stack it next to SAP or NetSuite, and build a total cost of ownership model that accounts for per-user licensing, implementation partner fees, and a reasonable buffer for customization. Business Central’s list price is public — $80 per user per month for Essentials, $110 for Premium (Microsoft Business Central pricing page, retrieved August 2026) — so that part of the model is easy to get right. It’s a disciplined process, and it’s exactly what a CFO should do before signing off on an ERP change. The problem isn’t the rigor. It’s the scope of what gets modeled in the first place.
Where the standard TCO model stops short
Licensing tiers get scrutinized because they’re visible and quotable — a partner can hand you a per-seat number in the first call. Implementation cost gets modeled because it’s the line everyone’s been burned by before, so it earns healthy skepticism and padding. What consistently gets left out is the cost of integration debt: connecting Business Central to the systems already running your operations. That’s not a licensing question. It’s a systems-architecture question, and it rarely shows up until a solutions architect is deep into discovery. The usual candidates:
- The CRM, whatever the sales team already relies on for pipeline and customer records.
- The warehouse or inventory system, if it isn’t already Microsoft-native.
- The payroll platform, which almost never migrates alongside the ERP.
- Whatever homegrown reporting tool finance has patched together over the years.
Why generic comparisons can’t price it for you
Integration cost is slippery because it doesn’t scale linearly with company size. It scales with how many disconnected systems already exist and how custom they are. A 200-employee company with three bolted-on tools can spend more on integration than a 2,000-employee company running mostly Microsoft-native software. That’s precisely why generic vendor comparisons and published pricing sheets can’t catch it: it’s not a Business Central problem, a SAP problem, or a NetSuite problem. It’s specific to your current stack, and no comparison article, including this one, can price it for you in the abstract.
What a defensible estimate actually needs
What CFOs comparing Dynamics 365 vs. SAP, or Business Central vs. NetSuite, actually need isn’t another pricing table. It’s a TCO estimate built around their existing systems, their integration surface area, and their actual license count — not a vendor’s best-case scenario. That’s the gap between a plausible budget and a defensible one. It’s the difference between presenting a number the board trusts and explaining one they don’t.
If you want that number before it becomes a surprise in month six, you can see your real migration cost using our ROI calculator — built to surface the integration and TCO variables generic pricing pages leave out.
For a fuller picture of what a Business Central migration involves, see our Business Central solutions.
This same blind spot shows up on the licensing side too — see what a Business Central license actually costs once the add-ons are counted for the costs most quotes leave out. And if your rollout spans Finance and Operations rather than Business Central alone, licensing isn’t the module IT directors most often underestimate — see the Dynamics 365 module most IT directors underestimate during a Finance and Operations rollout for a look at what is. For a baseline on list pricing before add-ons, our Business Central pricing breakdown is a useful starting point.
Frequently Asked Questions
What cost do CFOs most often miss when budgeting a Business Central migration?
Integration debt: connecting Business Central to the CRM, warehouse system, payroll platform, and any homegrown reporting tools already in use. It rarely appears in vendor pricing sheets because it depends on your existing stack, not the ERP.
Why doesn't integration cost scale with company size?
It scales with how many disconnected systems already exist and how custom they are. A smaller company running several bolted-on tools can spend more on integration than a larger company on mostly Microsoft-native software.
Can a generic ERP pricing comparison catch integration cost?
No. Published pricing pages and vendor comparison sheets price the license and, sometimes, implementation. Integration cost is specific to your current systems, so it has to be modeled against your own environment, not read off a rate card.
What should a defensible Business Central TCO estimate include beyond the license?
Implementation partner fees, your actual integration surface area, and your real license count — not a vendor's best-case scenario. That combination is what separates a plausible budget from one the board can trust.
Where does this same blind spot show up outside of Business Central migrations?
On the licensing side too: add-on modules and third-party ISV products get priced separately from the base license, and that stack is often left out of the first-pass budget the same way integration cost is.
Daniel Harper
Contributor, Dynamics 365 GroupThis article is written by Daniel Harper for Dynamics 365 Group. Product behavior, deployment choices, and licensing can change, so confirm current Microsoft documentation before making an implementation decision.
Calculate Your Dynamics 365 Migration ROI
See how much you could save with a free, instant ROI estimate — no signup required.
Get Your Free ROI Estimate
