Ask five Business Central partners what an implementation costs, and you’ll get five different answers — and four of them won’t include the number you’ll actually pay. Some quote a “starting at” price that assumes your chart of accounts is already perfect and your legacy data exports itself. Others bundle licensing into the implementation fee, making their offer look cheaper than a competitor who separates them.
This article publishes the real Business Central implementation cost for 2026: Microsoft licensing at current list prices, partner fees by scope, the hidden costs nobody volunteers, and full 5-year TCO for three company sizes. The numbers are what we quote and what we invoice at Vanguard 360, plus what we see in competitors’ proposals. If you’re still working out how long it takes, start with our implementation timeline guide.
Business Central Cost at a Glance
| Cost item | What it costs in 2026 | How often |
|---|---|---|
| Essentials license | $80 / €69.30 per user/month | Monthly, annual commitment |
| Premium license | $110 / €95.30 per user/month | Monthly, annual commitment |
| Team Members license | $8 / €6.90 per user/month | Monthly, annual commitment |
| Licensing, 5-user firm | ~€222/month | Recurring |
| Licensing, 20-seat distributor | ~€796/month | Recurring |
| Licensing, 50-seat manufacturer | ~€2,290/month | Recurring |
| Implementation, small (finance only) | €8,000–15,000 | One-time |
| Implementation, standard (finance + supply chain) | €18,000–40,000 | One-time |
| Implementation, complex (multi-entity, manufacturing, retail) | €45,000–100,000+ | One-time |
| Ongoing partner support | €500–2,500+/month | Recurring |
| 5-year all-in TCO | ~€10,700–11,700 per user | Over 5 years |
EUR license prices are Microsoft’s eurozone list prices, excluding VAT. The rest of this article explains where each number comes from and what moves it.
Honest Pricing: What You’ll Actually Pay a Partner
A Business Central implementation has two unavoidable bills:
- Microsoft licensing — per user, per month, at published list prices. You keep paying it for as long as you run BC.
- Partner implementation fees — a one-time cost to configure, migrate, integrate, train and go live. This is what partners compete on.
Everything else — your team’s time, ISV add-ons, temporary staffing, ongoing support — sits on top. This section covers the partner fees. They don’t include Microsoft licensing or your team’s time.
Small Implementation: €8,000–15,000
What you get: Finance core — general ledger, accounts payable, accounts receivable, fixed assets, bank reconciliation, basic financial reporting. Clean data from a simple source (QuickBooks, Xero, Excel). Single legal entity. No supply chain, no manufacturing, no integrations beyond a bank feed.
What this looks like: A 10-person professional services firm migrating from QuickBooks or Xero. They need proper multi-currency (they bill in EUR and GBP), a chart of accounts that handles project-based P&L, and financial reports their accountant can stop manually reworking every quarter-end. No inventory, no purchasing, no sales orders — they raise invoices directly. Final invoice on a project like this: €10,500.
What’s included: Kick-off and discovery, CoA design, configuration of the finance module, migration of opening balances and master data, user training (finance team only), go-live support, and two weeks of hypercare.
What’s NOT included: Custom AL extensions, integration with anything that isn’t a bank feed, data from a messy legacy system that needs manual cleansing, and training of non-finance users (because there aren’t any in this scope).
Standard Implementation: €18,000–40,000
This is where most mid-market implementations land.
What you get: Everything in small, plus supply chain (purchasing, sales, inventory, warehouse), data migration from a legacy ERP or accounting system (SAP Business One, older NAV, Sage), 1–3 integrations (e-commerce platform, CRM, EDI), custom reports, and training across finance and operations teams. Single entity, maybe with intercompany if you’re consolidating.
What this looks like: A 35-person wholesale distributor with €8M revenue. They’ve been running an aging on-premise NAV 2016 system that the original partner stopped supporting. They need purchasing, sales order processing, inventory management with barcode scanning, basic warehouse (bins, put-away, pick), and an integration with their Shopify store. Finance needs dimensional reporting by business unit and product category. Three users need Premium (light production), eight need Essentials, four need Team Member access for expense entry and approvals. Final invoice: €28,000.
What’s included: Full solution design across all functional areas, configuration of finance + supply chain, data migration from legacy NAV (with data cleansing — the last 5 years of transactions, open payables and receivables, inventory with accurate costing layers), Shopify integration (orders sync to BC, inventory sync to Shopify), role-based training (finance team, warehouse team, sales team), go-live with two weeks of hypercare.
What’s NOT included: Custom AL extensions beyond standard configuration, third-party ISV solutions (if the barcode scanning needs a specialized WMS add-on instead of BC’s built-in warehouse), hardware, data migration of every historical transaction since 2009 (you don’t need it, and cleaning it costs more than it’s worth), and training of temporary/seasonal staff.
Complex Implementation: €45,000–100,000+
What you get: Everything above, plus multi-entity (international consolidation, intercompany transactions, multiple currencies with automatic rate feeds), manufacturing (production orders, routings, BOMs, capacity planning), retail (LS Central with POS), heavy custom development (AL extensions built for your specific business logic), 5+ integrations (EDI with major retailers, customs systems, third-party logistics platforms), and often a phased rollout across countries or business units. These projects need dedicated project management.
What this looks like: A manufacturer with €25M revenue, two production sites in different countries, selling through their own e-commerce and through 30 retail partners via EDI. They need manufacturing (production BOMs, routings, shop floor data collection), multi-entity consolidation with local statutory reporting in two countries, LS Central for their factory outlet POS, custom AL extensions for an industry-specific compliance reporting module, EDI integration with three major retail chains (each with different message formats), and a phased rollout — manufacturing first, then retail, then cross-entity consolidation. Final invoice: €78,000.
What’s included: Multi-phase implementation with dedicated project management, full AL extension development, integration architecture and build-out, factory and retail training, multi-wave go-live, extended hypercare (4–6 weeks after each go-live).
What’s NOT included: The LS Central license itself (sold through LS Retail, separate from Microsoft BC licensing), EDI VAN fees (you pay the network provider, not the implementation partner), and translation of training materials into local languages.
Microsoft Licensing: How Much Business Central Costs per Month
Business Central licensing is the part you can’t negotiate much. Microsoft publishes list prices; CSP partners can occasionally offer small discounts, but list is what most companies pay. On November 1, 2025 Microsoft raised Business Central cloud prices for the first time in more than five years — Essentials from $70 to $80, Premium from $100 to $110, and the Device license from $40 to $45. Team Members stayed at $8. The new prices apply to new subscriptions and to existing ones at their first renewal after that date, so if your quote still says $70, it’s out of date.
| License | USD/month (list) | EUR/month (list, excl. VAT) | Annual (EUR) | Who Needs It |
|---|---|---|---|---|
| Essentials | $80/user | €69.30/user | €831.60 | Finance, purchasing, sales, inventory, basic warehouse users |
| Premium | $110/user | €95.30/user | €1,143.60 | Manufacturing (production orders, routings), service management users |
| Team Members | $8/user | €6.90/user | €82.80 | Read-only access, expense entry, light approvals, time entry |
| Device (warehouse, shop floor) | $45/device | ~€39/device | ~€468 | Shared-device environments — warehouse scanning stations, production floor terminals |
Prices are per month on an annual commitment, paid yearly. Since April 2025, paying an annual commitment in monthly instalments costs 5% more. EUR prices for Essentials, Premium and Team Members are Microsoft’s published eurozone list prices; the Device price is an approximate conversion.
In the UK, Microsoft’s list prices are £61.50 per user/month for Essentials, £84.60 for Premium and £6.20 for Team Members, excluding VAT and paid yearly (Microsoft UK pricing, checked 29 September 2026). Comparing with accounting software? See Business Central vs QuickBooks and Xero.
The November 2025 increase came with more database storage per license (Essentials from 2 GB to 3 GB, Premium from 3 GB to 5 GB), which matters if you were close to your tenant’s storage cap. Copilot is included in Business Central at no extra cost; the agents — such as the Sales Order Agent and Payables Agent — consume Copilot Credits, billed separately on usage.
One human = one user license. You can’t buy four Essentials and let eight people share them — Microsoft audits. Device licenses are the only shared option, and they’re tied to a physical workstation. Every subscription also includes free External Accountant access; use it for your outside accountant instead of buying them a seat.
Seat Maps for Three Company Sizes
5-user professional services firm — no inventory, no manufacturing:
- 3 Essentials (finance and admin): €207.90/month
- 2 Team Members (directors): €13.80/month
- Total: ~€222/month, ~€2,660/year
20-seat wholesale distributor — finance + supply chain + warehouse scanning:
- 9 Essentials (finance, sales, purchasing): €623.70/month
- 3 Device (warehouse scanning stations): ~€117/month
- 8 Team Members (management, light users): €55.20/month
- Total: ~€796/month, ~€9,551/year
50-seat manufacturer — multi-department, some Premium:
- 21 Essentials (finance, sales, purchasing, engineering, quality): €1,455.30/month
- 5 Premium (production planning): €476.50/month
- 6 Device (shop floor): ~€234/month
- 18 Team Members (management, light users): €124.20/month
- Total: ~€2,290/month, ~€27,480/year
Over five years at today’s list prices, that’s ~€13,300 in licensing for the 5-user firm, ~€47,750 for the distributor and ~€137,400 for the manufacturer.
Factor licensing into your budget from day one. It’s not hidden — but partners who quote “all-in” prices that bundle licensing may be padding their numbers, and partners who ignore licensing in their proposal leave you to discover it when the first invoice arrives.
The 7 Hidden Costs Nobody Publishes
These aren’t implementation fees and they’re not licensing. They’re the costs that show up during and after go-live because nobody planned for them.
1. Data Cleansing Beyond the Migration Scope
Your implementation partner migrates the data you agree to migrate. But legacy data is rarely clean all the way back. You’ll find that:
- Vendor records have three versions of the same supplier with different spellings and different payment terms
- Inventory costing layers in your old system don’t match physical reality (you’ve been running Average but the GL says FIFO because someone changed the setting in 2019)
- Customer credit limits in the old system are from 2018 and nobody has updated them
- Open sales orders from six months ago are still sitting there because nobody cancelled them
Cleaning this is your job, not the partner’s — or it’s additional scope. Budget 2–5 days of internal effort for data review and cleanup, or €2,000–5,000 in additional partner time if you want them to do it.
2. The “While We’re At It” Scope Creep
During the design phase, someone will say: “While we’re implementing BC, can we also fix our pricing structure / reorganise the warehouse / automate the approval workflow we’ve been talking about for three years?”
Each of these is a legitimate improvement — but they weren’t in the original scope, and they add time. One “while we’re at it” per phase is manageable. Five in the first three weeks, and your €25K project becomes a €38K project.
The fix: keep a “phase 2” list. Every time someone says “while we’re at it,” add it to the list. Review the list at the end of each sprint. If something on the phase 2 list is genuinely blocking go-live, it gets escalated. If it’s a nice-to-have, it stays on phase 2.
3. Integration Surprises
The Shopify connector works. The bank feed connector works. The EDI integration with Retail Chain X works — except for the specific message format their German warehouse uses, which is three versions behind the standard and requires a custom mapping. That custom mapping is 3–5 days of integration development that wasn’t in the quote.
Integration estimates are best-effort until the integration is actually built and tested. Budget 15–20% contingency over the integration line items in your quote. If you don’t use it, great. If you do, it’s not a surprise.
4. The Learning Curve Tax
For the first 2–3 months after go-live, your team will be slower. Finance closes that took 2 days in the old system take 4. Warehouse picks take longer because people are scanning instead of grabbing. Sales orders require looking at the new screen instead of muscle-memorying through the old one.
This productivity dip is real and costs real money. For a 25-person company, assume 3 months at 15–20% reduced productivity — roughly 1–1.5 FTE worth of lost output over the quarter. That’s not an invoice, but it’s cash out the door in the form of overtime, missed deadlines and catch-up work.
How to plan for it: schedule go-live during your slowest quarter. Pad month-end close timelines for the first 90 days. Don’t launch a new product line or open a new warehouse during implementation.
5. Temporary Staffing and Change Management
You can’t pause accounts payable during cutover, and the people who know the old system best are the same people you need in UAT. Key roles need cover — for a mid-size company, budget €5,000–12,000 for temporary staff around go-live.
Then there’s adoption. If your team hates the new system, configuration quality doesn’t matter: resistance shows up as slow adoption, workarounds and shadow Excel processes. Budget €3,000–8,000 for extra training, floor-walking during go-live and management time spent building buy-in.
6. ISV and Third-Party Subscriptions
Barcode scanning apps, EDI connectors, advanced WMS, document capture, local compliance add-ons — many BC projects need at least one AppSource extension with its own monthly or annual fee. In our distributor example below, a single WMS connector adds €3,600 a year; a manufacturer with EDI, LS Central and compliance tools can pay €14,400 a year in add-ons alone.
Ask your partner explicitly: “What third-party software will I need to license, and what does it cost annually?” A partner who doesn’t volunteer this is hoping you won’t notice until the renewal invoice arrives.
7. Ongoing Support, Optimization and Evolution
Your implementation partner delivers the system and hands it over. After hypercare, ongoing support is a separate arrangement — typically a monthly retainer or a block of hours.
- Light support (occasional questions, minor config changes): €500–800/month or a 10-hour block
- Standard support (regular adjustments, new reports, user additions): €1,000–2,000/month
- Active development (new features, new integrations, ongoing enhancements): €2,500+/month
On top of that, the system you launch with isn’t the system you run six months later. Approval workflows need adjusting; picking workflows that worked in training break under real load. Budget €5,000–15,000 in year one for post-go-live optimization. If you budget zero, you live with friction that costs more than the fix — and under-supported BC accumulates configuration debt that’s expensive to untangle later.
What Drives Cost Up (And How to Control It)
Cost Driver: Customizations
Custom AL extensions add €5,000–30,000+ to a project. Every line of custom code is something you’ll need to maintain, test against Microsoft’s twice-yearly major updates, and potentially rebuild if BC’s standard features evolve to cover that need.
When to customize: Your business has a unique process that’s central to your competitive advantage. You’re not customizing because BC does it differently — you’re customizing because the way you do it is the reason customers choose you.
When NOT to customize: You’re replicating how your old system worked because it’s comfortable. The process can be done with standard BC features but needs a workflow tweak. Someone says “we’ve always done it this way.”
The test: Can you articulate, in one sentence, why this customization creates business value that standard features don’t? If the answer starts with “well, the team is used to…” — it’s probably not a customization worth building.
Cost Driver: Legacy Data Quality
Dirty data is the single largest source of unplanned cost in Business Central implementations. We’ve seen projects where data cleansing and re-migration consumed 30% of the total project budget.
What costs more: Inconsistent customer/vendor master data (duplicate records, different naming conventions), inventory with inaccurate quantities or costs, open transactions from years ago that were never closed, and historical data where people “fixed” things directly in the SQL database instead of through the application.
What you can do: Start cleaning your data before you select a partner. Deduplicate vendor and customer records. Reconcile inventory quantities. Close old transactions. Every hour you spend cleaning is an hour you don’t pay a €150/hour consultant to do it for you.
Cost Driver: Integration Complexity
Not all integrations are equal. A standard Shopify connector is 3–5 days of work. A legacy WMS that talks via flat files on an FTP server is 8–15 days. EDI with three retail partners, each using a different message format, is a separate workstream with its own testing cycle. When you compare quotes, compare the integration line items one by one — that’s where cheap proposals hide their assumptions.
Cost Driver: Multiple Legal Entities
Each additional legal entity adds roughly 40–60% to the base effort: its own chart of accounts, VAT setup, local statutory reporting and intercompany configuration. Three entities push a €25,000 single-company implementation toward €55,000.
Cost Driver: Decision-Making Speed
Projects with a decisive project lead who can say “we’re going with option B” in the meeting cost 15–25% less than projects where every configuration decision goes through a committee that meets every two weeks.
The clock runs whether decisions happen or not. If your project lead needs three weeks to get sign-off on the chart of accounts structure, the consultant works on other things in the meantime — but the timeline extends, and total cost rises with elapsed time.
What Brings Cost Down
- Clean data before kickoff — the cheapest hours in the project are the ones your own team spends deduplicating and reconciling.
- Standard processes — every workflow you adapt to BC’s standard way is a customization you didn’t pay for and a maintenance burden you avoided.
- A decisive sponsor with protected time — this role, not the partner and not the software, is the single biggest predictor of cost and success.
- A phased rollout — finance first, supply chain in phase 2, manufacturing in phase 3. Total cost runs 10–15% higher than a single big-bang go-live, but it spreads spend across quarters and cuts risk. For most mid-size companies the trade is worth it.
Your Implementation Team: Who’s at the Table and What It Costs You
Your team’s time commitment is the cost nobody budgets for. Here’s what each role actually needs to contribute — and what happens if they don’t.
| Role | Who | Time Commitment | Cost to the Business |
|---|---|---|---|
| Executive Sponsor | CEO, CFO, or MD | 2–3 hours/month | Low — mostly decision sign-off and roadblock removal. The sponsor doesn’t need to be in the weeds. |
| Project Lead | Operations Director, Finance Controller, IT Manager | 8–12 hours/week during build phase, 15–20 during UAT and go-live | High — this person is partially removed from their day job for 3–5 months. That’s real capacity you need to backfill or accept as lost output. |
| Finance Lead | CFO, Financial Controller | 4–6 hours/week | Medium — CoA design, dimension setup, posting groups, financial reports. These decisions are hard to reverse and the finance lead must own them. |
| Operations Lead | Ops Director, Supply Chain Manager | 3–5 hours/week | Medium — inventory, purchasing, warehouse. If the ops lead isn’t engaged, you build a system that doesn’t match how goods actually move. |
| IT/Systems Lead | IT Manager or external partner | 2–4 hours/week | Low to medium — user setup, security, integrations, infrastructure. If you have an external IT partner, include their hours in your budget. |
| Department Champions | Key users from sales, purchasing, warehouse | 2–3 hours/week (spikes during UAT) | Low individually, but these are the people who catch workflow problems nobody else notices. Don’t skip them. |
In money terms: our 20-seat distributor below spent roughly 50 person-days (€15,000) of internal time; the 50-seat manufacturer spent about 120 person-days (€36,000). No invoice arrives for this, but if these people are pulled from revenue-generating work, it’s real cost.
The single biggest team risk: Assigning a project lead who “can handle it alongside their day job.” The day job doesn’t shrink. The project lead ends up doing both jobs poorly — implementation decisions drag out, sprints fall behind, and the team loses confidence. The project lead needs protected time. If that means backfilling part of their role for the duration, budget for it.
Phase-by-Phase Cost Breakdown
Not every phase costs the same. Here’s where the money goes in a standard implementation (~€25,000 partner fee).
| Phase | % of Budget | Approximate Cost | What You’re Paying For |
|---|---|---|---|
| Initiation + Requirements | 10–15% | €2,500–3,750 | Kick-off, discovery workshops, process mapping, scope definition |
| Solution Design | 15–20% | €3,750–5,000 | Solution architecture, CoA/dimension design, integration specs, gap analysis |
| Build & Configure | 30–35% | €7,500–8,750 | Core configuration (finance, supply chain), sprint cycles, sprint reviews |
| Data Migration | 10–15% | €2,500–3,750 | Data extraction, profiling, cleansing, mapping, test migration, final migration |
| Integration Build | 10–15% | €2,500–3,750 | API connections, EDI mappings, connector configuration, integration testing |
| Training | 5–8% | €1,250–2,000 | Role-based training sessions, training materials, train-the-trainer |
| UAT + Go-Live | 8–12% | €2,000–3,000 | User acceptance testing, cutover planning, go-live execution, hypercare |
What this means for your budget: More than half the cost (build + configure + data migration + integration) is execution work. You’re paying for expertise and time, not for a software license or a product. A partner charging significantly less than these ranges is either cutting scope (skip training, minimal migration, no integration testing) or treating your project as a loss leader for the ongoing support contract. Neither is good for you.
Most partners, us included, invoice against milestones rather than up front: a deposit at kick-off, then payments at design sign-off, UAT completion and go-live. A phased rollout means phased payments. Negotiate the payment structure during the proposal, not after.
Real 5-Year TCO: Three Companies
Licensing and the partner invoice are only part of what Business Central costs. These three worked examples add everything else — support, add-ons, internal time, the productivity dip, hardware — over five years. Licensing uses the seat maps and current list prices above.
Company A: 5-User Professional Services Firm
Migrating from Xero. Finance core only. No inventory, no manufacturing.
| Cost Category | Year 1 | Years 2–5 (each) | 5-Year Total |
|---|---|---|---|
| Microsoft licensing | €2,660 | €2,660 | €13,300 |
| Partner implementation | €10,500 | — | €10,500 |
| Ongoing support (light retainer) | €3,000 | €6,000 | €27,000 |
| Internal team time | €4,000 | — | €4,000 |
| Productivity dip | €2,500 | — | €2,500 |
| Hardware | €1,000 | — | €1,000 |
| Yearly Total | €23,660 | €8,660 | €58,300 |
5-year cost per user: €11,660. Year 1 is heavy. After that: about €722/month in total.
Company B: 20-Seat Wholesale Distributor
Migrating from NAV 2016. Finance + supply chain + Shopify integration + warehouse scanning.
| Cost Category | Year 1 | Years 2–5 (each) | 5-Year Total |
|---|---|---|---|
| Microsoft licensing | €9,551 | €9,551 | €47,755 |
| Partner implementation | €28,000 | — | €28,000 |
| Ongoing support (standard) | €6,000 | €18,000 | €78,000 |
| ISV add-on (WMS connector) | €3,600 | €3,600 | €18,000 |
| Internal team time (~50 person-days) | €15,000 | — | €15,000 |
| Temporary go-live staffing | €5,000 | — | €5,000 |
| Productivity dip (20% × 3 months) | €18,000 | — | €18,000 |
| Hardware (scanners, workstations) | €4,000 | — | €4,000 |
| Yearly Total | €89,151 | €31,151 | €213,755 |
5-year cost per seat: €10,688. This is Business Central’s strongest value case — replacing an unsupported legacy ERP.
Company C: 50-Seat Manufacturer
Two countries. Manufacturing + EDI + custom AL extensions. Complex implementation.
| Cost Category | Year 1 | Years 2–5 (each) | 5-Year Total |
|---|---|---|---|
| Microsoft licensing | €27,480 | €27,480 | €137,400 |
| Partner implementation | €78,000 | — | €78,000 |
| Ongoing support (active development) | €12,000 | €33,000 | €144,000 |
| ISV add-ons (EDI, LS Central, compliance) | €14,400 | €14,400 | €72,000 |
| Custom extension maintenance | — | €8,000 | €32,000 |
| Internal team time (~120 person-days) | €36,000 | — | €36,000 |
| Temporary staffing | €12,000 | — | €12,000 |
| Productivity dip (staggered waves) | €30,000 | — | €30,000 |
| Hardware (terminals, scanners) | €8,000 | — | €8,000 |
| Yearly Total | €217,880 | €82,880 | €549,400 |
5-year cost per seat: €10,988. Ongoing costs dominate: support + ISV add-ons + extension maintenance make up 45% of the total. The one-time implementation is only 14%.
The takeaway: Per-user 5-year TCO is remarkably consistent across company sizes: roughly €10,700–11,700 per user, or about €180–195 per user per month with everything included. Expensive compared to QuickBooks. Cheap compared to running an unsupported legacy ERP.
SaaS vs On-Premise: Total Cost of Ownership
Business Central on-premise is still sold, and some companies look at it to avoid the monthly subscription. The economics are different, not automatically cheaper:
| SaaS (cloud) | On-premise | |
|---|---|---|
| Licensing model | Monthly per-user subscription, annual commitment | Perpetual licenses bought up front, plus an annual enhancement plan of ~16% of license cost |
| Infrastructure | Included — Microsoft hosts, backs up and patches | Your servers or Azure VMs, SQL Server licensing, backup and disaster recovery |
| Updates | Automatic, twice-yearly major releases | Partner-run upgrade projects you pay for; skip them and upgrade debt piles up |
| IT effort | Minimal user and permission admin | Database administration, patching, monitoring, security audits |
| Copilot and AI features | Yes | No — new AI capabilities are cloud-only |
For companies under about 50 users, SaaS is almost always cheaper once infrastructure, IT time and upgrades are counted. On-premise can win on pure TCO from around 80–100 users, or when regulatory, ISV or connectivity constraints make it the only viable option. We run the full five-year numbers for a 20-user company in our Business Central SaaS vs on-premise comparison.
What a NAV to Business Central Migration Costs
If you’re on Dynamics NAV today, the migration fits the tiers above. A NAV system with finance and supply chain and moderate customization typically lands in the standard tier, €18,000–40,000. What pushes it higher is custom code: every C/AL modification has to be rebuilt as an AL extension, replaced by a standard BC feature, or retired — and heavily modified NAV databases with years of patched data move into the €45,000+ range. The good news is that a well-run migration usually removes half of those customizations, because BC now does natively what NAV needed code for. Our NAV to Business Central migration guide walks through the process step by step.
ROI Reality Check
Year 1: negative. You spend money and you’re slower. That’s normal — everyone’s learning.
Year 2: break-even. The system stabilizes. Month-end close gets faster, inventory visibility improves, and the initial investment is behind you.
Year 3+: positive. Process automation and data visibility compound. Our 20-seat distributor cut month-end close from 5 days to 2 — about 36 person-days a year, or ~€9,000 in recovered productivity from one process improvement.
Companies with the worst current systems see ROI fastest. Running NAV 2009 on a server in the closet? BC’s return is transformational and starts showing in year one. Already on a modern cloud ERP? BC’s return is incremental, and you should be honest with yourself about why you’re switching.
What Nobody Tells You
”Go-live isn’t the finish line.”
The phrase “go-live” creates unrealistic expectations. It sounds like the end. It’s not. The two weeks after go-live are hypercare — your partner is on standby, your team is finding things they didn’t catch in UAT, and everyone is tired.
The three months after go-live are stabilization. Your finance team discovers that the depreciation calculation is slightly different from the old system and needs adjusting. The warehouse finds a picking workflow that made sense in training but doesn’t work when six people are picking simultaneously. Your sales team realizes the credit-limit check is blocking orders they would have approved manually in the old system.
This is all normal. But if you budgeted as if the project ends on go-live day, you’re under-resourced for the most important phase — the one where the system actually starts working the way you need it to.
”Your best people will resist the most.”
The employee who’s been running purchasing on the old system for 12 years — the one who knows every workaround, every shortcut, every supplier’s quirks — is often the hardest to transition. They’ve built their expertise and status on mastery of the old system. The new system flattens that. Suddenly the new hire and the veteran are both learning together, and the veteran feels their advantage eroding.
This isn’t a training problem. It’s a change management problem. Acknowledge it directly. Involve your veteran users early in design — their knowledge of the business is more valuable than their knowledge of the old software. Make them champions of the new system by giving them ownership of a specific module or workflow. The goal is to convert resistance into advocacy.
”You’ll miss the old system’s quirks.”
Every legacy system has things it does well — usually things that were custom-built for your specific business because the standard software couldn’t handle them. BC will handle 90% of those things better. The other 10% will feel like a step backward because the old custom feature was perfectly tailored to your workflow and BC’s standard feature is more generic.
Identify those 10% upfront. Decide which ones are worth customizing in BC (build an AL extension) versus which ones are worth adapting your process to BC’s way of doing things. This is a strategic decision, not a technical one — and it’s better made during design than discovered during UAT.
”The partner relationship matters more than the software.”
Business Central is the same product regardless of which partner implements it. What varies enormously is the quality of the implementation — and that depends almost entirely on the partner.
A partner who understands your industry will configure BC in ways that make sense for your business. A partner who doesn’t will configure it correctly according to the manual but in ways that create friction every day. A partner who communicates clearly will surface problems early when they’re cheap to fix. A partner who doesn’t will present a perfect dashboard while hiding scope creep and timeline slippage.
Select your partner based on industry experience, communication style, and references from companies similar to yours. Ask each one what went wrong on their last three projects. The partner’s price matters, but a €5,000 difference in implementation fees is meaningless compared to a partner who adds 3 months to your timeline or builds a system your team hates using. See our guide to choosing a Business Central partner for the full framework.
Pre-Kickoff Checklist
Before you sign with a partner, work through this checklist. If you can answer all of them, your implementation will cost less and run faster.
- We’ve identified our executive sponsor — someone who can remove roadblocks and signal priority to the organization
- We’ve designated a project lead with protected time (not someone fitting this alongside a full day job)
- We know which team members will be involved and have discussed the time commitment with each of them
- We’ve documented our current pain points — the specific things the old system does badly that we need BC to fix
- We’ve started cleaning our master data: deduplicated vendors/customers, reconciled inventory, closed old transactions
- We’ve defined scope clearly: what’s in (phase 1), what’s out (phase 2+), what’s never
- We know which integrations we need and have documented the systems, data flows, and contacts
- We’ve mapped every user to a license type (Essentials, Premium, Team Members, Device) at current list prices
- We’ve asked every partner which third-party add-ons we’ll need and what they cost per year
- We’ve set a realistic timeline — not the timeline we want, the timeline that accounts for data quality, team capacity, and decision-making speed
- We’ve budgeted for licensing, implementation, data cleansing, integration contingency, training, temporary staffing, and ongoing support
- We’ve interviewed at least three partners and checked references from companies similar to ours in size and industry
- We’ve defined what “success” looks like — specific, measurable outcomes, not “a better system”
FAQ
How much does Business Central cost per month in 2026?
Since November 1, 2025, Microsoft’s list prices are $80 per user/month for Essentials, $110 for Premium and $8 for Team Members, on an annual commitment. In the eurozone that’s €69.30, €95.30 and €6.90 excluding VAT, and in the UK £61.50, £84.60 and £6.20. In practice: ~€222/month for a 5-user firm, ~€796/month for a 20-seat distributor, ~€2,290/month for a 50-seat manufacturer.
How much does a Business Central implementation cost?
€8,000–15,000 for finance only with clean data, €18,000–40,000 for finance plus supply chain with legacy migration and 1–3 integrations, and €45,000–100,000+ for multi-entity, manufacturing, retail or heavy custom development. That’s the one-time partner fee; licensing, support and hidden costs come on top.
What is the 5-year total cost of ownership?
In our three worked examples, roughly €10,700–11,700 per user over five years — about €180–195 per user per month with licensing, implementation, support, add-ons, internal time and the post-go-live productivity dip included.
How long does a Business Central implementation actually take?
It depends on scope, data quality, and decision speed. A finance-only implementation with clean data: 6–10 weeks. Finance + supply chain with data migration from a legacy system: 3–5 months. Multi-entity with manufacturing, custom development, and complex integrations: 5–9 months. The biggest variable isn’t the software — it’s your data readiness and how fast your team can make decisions. See our full implementation timeline guide for a phase-by-phase breakdown.
Why do some partners quote €5,000 and others €50,000 for what looks like the same thing?
The €5,000 quote is typically a fixed-scope “express” implementation with severe limitations: pre-defined chart of accounts (you adapt to it, not the other way), no data migration from legacy systems (you start fresh), no integrations, no custom reports, and limited training (often recorded videos, not live sessions). It works for a startup that has no legacy data and simple needs. For an established business migrating from another system, it’s insufficient. The €40,000–50,000 quote includes custom configuration, data migration from a complex legacy system, integrations, and role-based training. Always ask: “What specifically is NOT included in this quote?”
Do I need Premium licenses for everyone?
No. Premium is specifically for users who need manufacturing (production orders, routings, capacity planning) or service management (service orders, service items, contracts). Finance, sales, purchasing, warehouse, and management users typically only need Essentials. Team Members licenses cover read-only access and basic data entry (expenses, time sheets). A 50-user manufacturer typically needs 3–7 Premium licenses, not 50.
Is Business Central on-premise cheaper than SaaS?
Usually not below 50 users. On-premise licensing is perpetual (one-time purchase plus an annual enhancement plan at ~16% of license cost), but it adds servers, SQL Server licensing, backups, IT staff and paid upgrade projects. On-premise can win on pure TCO from around 80–100 users. Microsoft also builds new AI and Copilot features for the cloud version only.
How much does ongoing support cost?
Minimum €500–800/month for light support. Realistically €1,000–2,000/month for a typical mid-size company. €2,500+/month if you’re growing fast or building custom features. Plus €5,000–15,000 in year one for post-go-live optimization. Don’t cheap out on support — under-supported BC accumulates configuration debt that’s expensive to untangle.
Can I pay for the implementation in phases?
Yes. Most partners structure payment around milestones: a deposit at kick-off, payment at design or configuration sign-off, payment at UAT completion, and the remainder at go-live. Phased rollouts mean phased payments.
What if I need custom features that Business Central doesn’t have?
That’s what AL extensions are for. Business Central’s extension model lets partners build custom functionality on top of the base application without modifying Microsoft’s code, so your customizations survive upgrades. Custom development adds €5,000–30,000+ depending on complexity. At Vanguard 360, many of our product extensions — Romanian localization, SAF-T reporting, e-Invoice, e-Transport — started as custom development for specific clients and were productized after proving their value across implementations.
Is Business Central cheaper than SAP Business One or NetSuite?
For companies under 100 users, generally yes. BC’s licensing is competitive and its larger partner ecosystem keeps implementation rates down. NetSuite bundles platform and modules, which makes a line-by-line comparison hard; SAP Business One’s smaller partner pool usually means higher hourly rates. The real difference is rarely the software — it’s implementation and ongoing support. See our Business Central vs SAP comparison and Business Central vs NetSuite for detail.
Prices in EUR unless noted, checked September 2026. Microsoft license prices are list prices from Microsoft’s Business Central pricing pages (USD and eurozone, excluding VAT); the Device license EUR price is an approximate conversion. Actual prices vary slightly by CSP partner and billing terms. Partner fees are based on Vanguard 360’s own pricing and market observations — your quote depends on your requirements.
Want to know what your implementation would cost? Book a free scoping call → or explore our Business Central implementation services. We’ll give you a detailed estimate based on your actual requirements, not a generic price range.
Where to next
Business Central implementation
How we run a project, phase by phase
Business Central Data Migration: What Actually Happens When You Move From Your Old System
How to Choose a Business Central Partner: 12 Questions That Separate the Real Ones From the Sales Pitches
Business Central SaaS vs On-Premise in 2026: The Real Cost Comparison
Not sure if you're ERP-ready?
Take our 2-minute ERP Readiness Scorecard. No sign-up needed.
Take the scorecardGet BC insights in your inbox
Practical tips, never spam.