The one line item CFOs miss when pricing out a Business Central migration

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. 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.

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 CRM, the warehouse system, the payroll platform, and whatever homegrown reporting tool finance has relied on for years. 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.

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 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, and 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.

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.