Cost depends heavily on who does the work: how to choose an implementation partner.
You are reading about implementation cost — the one-off project fee paid to a partner. Three other pages cover the rest of the picture: Cost calculatorLicence pricing per userUK prices in sterlingCost of switching from 1C
“How much does it cost” is almost always the first question we hear at the start of a project. The honest answer: it depends. But that isn't a cop-out. A Business Central implementation is built from predictable parts, and once you understand their logic, the budget stops being a black box.
What the cost is made of
A project budget usually splits into four blocks:
- Microsoft licences. Business Central is sold as a per-user monthly subscription. There are two main licence types — Essentials and Premium — and the difference matters for manufacturing and service companies.
- Implementation work. The largest line for most projects: process analysis, configuration, development, testing and team training.
- Custom development (AL). Extensions for processes the standard system doesn't cover. The closer your processes are to standard, the smaller this line.
- Post go-live support. The SLA agreement, updates and ongoing development. This is a recurring cost, not a one-off.
What drives the price most
Three factors shape the budget more than anything else:
1. Number of users
It's a direct multiplier on licences and an indirect one on training. A 15-user project and a 150-user project are different stories in complexity.
2. Process complexity
Standard distribution with a simple warehouse goes live quickly. Manufacturing with multi-level BOMs, quality control and order-based costing is a different complexity class.
3. Amount of customization
Every deviation from standard means development, testing and future support. The cheapest way to save is to align your processes with the standard wherever it doesn't hurt the business.
Rule of thumb: for mid-market companies, plan for 8–20 weeks of work. Only a process audit gives an exact figure — before that, any estimate is very rough.
Hidden costs people forget
The most common surprises come not from the implementation itself but from what sits next to it:
- Data migration. If the old system kept data loosely, it will need cleaning before transfer.
- Integrations. Links to your website, bank, EDI or other systems are a separate scope of work.
- Training. A system works only as well as the people using it.
- Your team's time. Key employees will be involved in the project — a real, if non-monetary, cost.
How to make the budget predictable
The most reliable approach is to start with a process audit, not with licences. The audit shows which processes are standard and which need development, and that's what forms a real estimate. We run this audit for free: afterwards you get a concrete figure for your scope, not a “from-to” range.
Budget structure: what each line costs
Here is a typical split of a one-off implementation budget. The shares shift depending on how close your processes are to the system standard.
| Cost line | Share of budget | What drives it |
|---|---|---|
| Analysis and design | 10–15% | Number of processes, how well "as is" is documented |
| System configuration | 30–40% | Number of modules, complexity of accounting policy |
| Data migration | 10–20% | State of master data, depth of history |
| Custom development (AL) | 0–25% | How many processes fall outside the standard |
| Training and go-live | 10–15% | Number of users and roles |
| Contingency | 10% | Always budget for it — that is realism, not pessimism |
The biggest saving hides in the fourth line, not in a discount on rates. Every customisation costs twice: once to build, then again to maintain through each Business Central update.
Cost by company size
Small business: 5–15 users
Finance, sales, purchasing, simple inventory. Minimal customisation, standard reports, migration of balances and master data without deep history. Timeline: 8–10 weeks. The most predictable category — almost everything is covered by the standard.
Mid-market: 20–50 users
Multiple warehouses, lot tracking, dimensions for analytics, bank and e-commerce integration. Usually 2–4 small customisations. Timeline: 12–16 weeks. This is where budgets drift most often if scope is not fixed upfront.
Manufacturing or distribution: 50+ users
BOMs, routings, capacity planning, costing, warehouse logic. Premium licence required. Timeline: 16 weeks and up. The budget is driven by the depth of production accounting, not by headcount.
Fixed price or time and materials
| Fixed budget | Time and materials | |
|---|---|---|
| Best when | Scope is clear, processes documented | Scope is still being defined |
| Client risk | Paying for built-in contingency | Budget may grow |
| Flexibility | Through change requests | High |
| Needed upfront | Detailed requirements | Priorities and a budget cap |
A healthy compromise: fix the price of the analysis phase only. It produces a document any vendor can quote against precisely — and it does not lock you to us.
Five questions to ask before signing
- What exactly is in the quoted figure — and what is not. Data migration and training are often excluded.
- The hourly rate after go-live. Post-project rates are often higher than project rates.
- Who pays for configuration mistakes. This should be in the contract.
- What happens during Business Central updates. Microsoft ships two major updates a year; customisations need maintenance.
- Do you own the code of your customisations. A "no" ties you to that partner permanently.
Frequently asked questions about cost
How much does Business Central implementation cost for 20 users?
For a 20-user company with standard processes, implementation work starts at roughly $1,290 per month under a package, plus Microsoft licences at $80–110 per user. The final figure depends on the number of modules, migration scope and any customisation needed.
Why won't partners quote a price immediately?
Because cost is driven by process complexity, not headcount. A 50-user distributor can cost less than a 15-user manufacturer. An honest estimate follows a process analysis — usually one or two workshops.
How much are Microsoft Business Central licences?
Licences are sold per user per month in two tiers, Essentials and Premium, roughly $80–110 per user. The current price list is always on the Microsoft website and depends on licence type and subscription terms.
Can implementation be phased to spread the budget?
Yes, and for most companies it is the safest route. Phase one covers finance and sales, then inventory, then manufacturing and analytics. Each phase delivers a working result and spreads the cost over time.
Is it cheaper to extend our legacy system or move to Business Central?
Compare three-year total cost of ownership, not one-off spend. Legacy systems carry support, customisation, risk and downtime costs — the last item usually settles the argument.
How much does support cost after go-live?
Support is a recurring line, not a one-off. It covers SLA-based incident resolution, managing the two annual Business Central updates and ongoing development. Scope is agreed against your processes.