If you’re evaluating Business Central in 2026, you’ve probably noticed something frustrating: nobody publishes real pricing. Partners give you a range as wide as a barn door (« between 50,000 and 500,000 euros »), Microsoft’s own website talks about per-user licensing but stays silent on implementation, and every consultant tells you the same thing: « it depends on your scope ».
We’ve delivered Business Central projects for more than a decade. Here is the honest breakdown we wish we had when we were on the buyer’s side of the table. Real numbers, real ranges, and the cost drivers that actually move the needle.
The three cost buckets every Business Central project has
Every Business Central deployment, whether you call it an implementation, a migration, or a re-implementation, breaks down into three cost buckets: licensing, implementation services, and ongoing support. Confusing them is the most common mistake buyers make. A partner quoting you 80,000 euros for « everything » is almost certainly excluding licensing or post-go-live support, and you will discover that on the invoice three months in.
Licensing is what you pay Microsoft. Implementation services is what you pay your partner. Ongoing support is the monthly or annual envelope you pay the partner to keep things running once you’re live. These three buckets behave very differently and need to be evaluated separately.
Microsoft licensing in 2026: what you actually pay
Microsoft offers Business Central in two main editions: Essentials and Premium. Essentials covers finance, sales, purchasing, inventory, projects, warehousing and basic manufacturing. Premium adds full manufacturing and service management. In 2026, Essentials runs around 70 to 100 euros per named user per month, depending on your region and Microsoft partner agreement. Premium runs around 100 to 130 euros per named user per month.
On top of the per-user license, you have Team Members licenses for read-only or limited-use staff (around 7 to 10 euros per month). Then there is Storage if you exceed the base allowance, and AppSource extensions if you install third-party modules. For a 100-user company on Essentials, you are looking at roughly 84,000 to 120,000 euros per year in licensing alone. This is a recurring cost that scales linearly with your headcount, so budget for growth.
If you choose Business Central On-Premises rather than Online, the licensing model is different (perpetual license plus annual maintenance), and it makes economic sense only above 200 to 300 users with stable headcount. For everyone else, Online is the right answer in 2026.
Implementation services: what 2026 prices really look like
Implementation services is the most variable bucket and the one buyers underestimate the most. Here are realistic 2026 ranges based on the projects we’ve delivered and the RFPs we’ve reviewed.
Small implementation (10 to 30 users, simple processes, single entity, minimal customization): 50,000 to 120,000 euros. Three to six months of work. Suitable for service companies, small distributors, or organizations replacing an entry-level accounting tool.
Mid-sized implementation (30 to 150 users, moderate process complexity, one or two legal entities, some customization or integrations): 120,000 to 350,000 euros. Six to twelve months. The sweet spot for most PME-ETI.
Complex implementation (150 to 500+ users, multi-entity, manufacturing or warehousing, significant integrations, custom AL extensions): 350,000 to 1,500,000 euros. Twelve to twenty-four months. This is where careful scope management makes the difference between profitability and pain.
The five cost drivers that actually matter
Two companies with the same headcount can pay wildly different implementation fees. Here are the five factors that explain 80 percent of the variance.
First, process complexity. A clean trading company with a single product flow costs a fraction of a multi-site manufacturer running make-to-order with subcontracting. Process complexity drives configuration time, testing time, and training time.
Second, customizations and AL extensions. Every custom AL extension is hours of analysis, development, testing and documentation. Worse, every extension is technical debt you will pay for at every BC update. Cut ruthlessly. Most NAV customizations from 2012 are now standard BC features.
Third, data quality and migration scope. If your historical data is clean and you migrate only open transactions and master data, you save weeks. If you want full history with three duplicated customer records and obsolete SKUs, expect 20 to 30 percent of the project budget to go into data work alone.
Fourth, integrations. Each connector (CRM, e-commerce, EDI, banking, BI) adds 5,000 to 30,000 euros depending on protocol and data volume. Plan integrations early; retrofitting them after go-live is twice as expensive.
Fifth, change management and training. Skipping training to save 15,000 euros is the most expensive cost-cutting decision you can make. Plan 1 to 2 days of hands-on for power users and targeted sessions for end users. The difference shows up in week one adoption.
Hidden costs nobody talks about
Even good partners forget to mention four categories of cost in their initial quote. Ask explicitly about each before signing.
Internal time on your side. Plan 0.5 to 1 full-time-equivalent project sponsor plus 10 to 20 percent of key users’ time for the duration of the project. This is real money and it is rarely in the partner’s quote.
Post-go-live support. The first three months after go-live are hectic. Budget 10 to 20 percent of the implementation cost for stabilization, bug fixes, and small enhancements. After that, ongoing support typically runs 15 to 25 percent of the implementation cost per year.
BC semi-annual updates. Microsoft releases two major BC updates per year. Each one requires regression testing of your custom extensions. Budget 5,000 to 20,000 euros per update window depending on customization volume.
AppSource subscriptions. Third-party modules (advanced reporting, EDI, payroll connectors, document management) add up. A typical mid-sized BC environment runs 5 to 15 AppSource extensions, totaling 10,000 to 40,000 euros per year on top of Microsoft licensing.
How to read a Business Central quote without getting burned
A trustworthy BC implementation quote has six characteristics. If yours is missing any of them, push back before signing.
It separates licensing, services and support. It lists assumptions explicitly (number of users, number of legal entities, integrations included). It defines what is in scope and what triggers a change request. It includes a clear list of deliverables per phase. It names the actual people who will work on the project, not just the partner’s logo. And it includes a realistic post-go-live envelope, not just an open invitation to call.
If a partner quotes you a single flat number with no breakdown, no assumptions, and no named team, you are buying a lottery ticket, not a Business Central implementation.
Why the cheapest quote is usually the most expensive
The most expensive Business Central project we’ve ever rescued was originally won by the cheapest bidder. The partner had quoted 120,000 euros all-in for a 60-user manufacturing implementation. Eighteen months later, the client had paid 380,000 euros, the system was unstable, and they were still running their old ERP in parallel because the new one couldn’t close a month.
The pattern repeats: under-scoped initial quote, junior consultants doing the work, no real discovery, customizations piled on top of customizations to make the standard product fit, and a partner who says yes to every request because they need the change order revenue. The cheapest quote is rarely a gift. It’s an option to pay more later, with no guarantee on the outcome.
The Asio Services way: pricing that respects your money
We believe the most respectful thing a Business Central partner can do is tell you the real number before you sign. That is why we start every engagement with a paid discovery phase where we look at your processes, your data, and your team before quoting the full project. The discovery cost is small (a few thousand euros) and it pays for itself by eliminating the change-request surprises that wreck most projects.
We will also tell you when Business Central is not the right answer for you, when a customization is not worth keeping, and when your data is not ready to be migrated. We refuse projects we cannot deliver well, because a bad Business Central project hurts everyone, including us.
→ Book a free discovery call with Asio Services. We will walk through your situation, give you a realistic range, and tell you what we would do differently than the partners you’ve already talked to.
