Upgrading from Dynamics NAV to Microsoft Dynamics 365 Business Central
Business Central is the cloud successor to Dynamics NAV, built by the same team on the same underlying data model. That's the good news — this isn't a rip-and-replace project like moving off a different ERP entirely. The bad news is that "similar data model" doesn't mean simple, especially if your NAV instance has years of C/AL customisations sitting on top of it.
Book a NAV Upgrade Review
Why NAV customers are moving to Business Central now
Microsoft has been retiring mainstream support for older NAV versions on a rolling basis, and extended support for NAV 2018 ends in January 2028. Once a version falls out of support, it stops receiving security patches and tax/regulatory updates — a real problem given how often UK payroll, VAT and Making Tax Digital requirements shift. Businesses on 2009, 2013, 2015/16 or 2017 are already past that point.
Beyond the support clock, there's a genuine capability gap. NAV on-premises means your own hardware, your own patching schedule, and no native Power BI or Copilot. Business Central runs in the cloud, updates itself twice a year without a consultant on-site, and comes with Microsoft 365 and Power Platform integration NAV was never built to offer.
Where your NAV version sits on Microsoft's support lifecycle
| NAV Version | Support Status |
|---|---|
| NAV 2009 / 2013 | Ended |
| NAV 2015 / 2016 | Ended |
| NAV 2017 | Ended January 2027 |
| NAV 2018 Extended | Ends January 2028 |
| Business Central | Current |
Why your customisations need more than a straight upgrade
C/AL (older NAV)
Custom code was written directly into the core NAV object base — fast to build at the time, but tightly welded to that specific version, and a nightmare to carry forward untouched.
AL (Business Central)
Customisations are built as separate extensions that sit alongside the core BC platform. This means your custom logic survives future Microsoft updates instead of breaking every time BC upgrades.
In practice, this means a proper NAV-to-BC upgrade includes converting existing C/AL customisations into AL extensions — not copying them across and hoping. It's the single biggest reason some NAV upgrades take longer than customers expect, and it's exactly the part we scope properly before quoting anything.
What migrates from NAV, and what needs rebuilding
What carries across cleanly
Master data, open transactions, and standard configuration — since NAV and BC share the same underlying table structure, this part is genuinely straightforward.
What needs rework
C/AL customisations (rebuilt as AL extensions), third-party ISV add-ons (need BC-compatible versions), and any heavily modified core objects specific to your NAV build.
The gotchas we check for first
Multi-hop upgrades from very old versions
Some NAV 2009 or 2013 upgrades need an intermediate step before reaching Business Central. We map the actual upgrade path during discovery rather than assuming a single direct jump.
ISV add-ons with no BC-compatible version
If a third-party add-on your NAV instance depends on was never updated for BC, that functionality needs a genuine replacement, not a promise it'll "probably still work."
Undocumented customisations nobody remembers the reason for
Years-old C/AL code with no documentation is common. Part of our discovery process is figuring out what a customisation actually does before deciding whether to rebuild it or retire it.
A realistic NAV-to-BC upgrade timeline
Discovery & Customisation Audit
2–3 weeks reviewing every customisation and ISV add-on currently in use.
Conversion & Rebuild
4–10 weeks converting C/AL customisations to AL extensions, scaling with how much custom code exists.
UAT, Training & Go-Live
2–3 weeks testing against real scenarios and a planned cutover.
Cloud Business Central, or Business Central on-premises?
Most NAV customers move to the cloud SaaS version of Business Central, since it removes patching and hardware entirely. A smaller number, usually with strict data residency requirements or heavy on-premises integrations, choose Business Central on-premises instead. We'll tell you honestly which fits your situation rather than defaulting to whichever is easier for us to sell.
The NAV customers upgrading right now
Manufacturing
Long-standing NAV manufacturing customers with years of custom BOM and routing logic.
Distribution
Businesses with heavily customised warehouse and multi-site logic built over a decade.
Professional Services
Firms with custom project costing extensions layered onto a base NAV install.
Multi-entity groups
Organisations running several NAV companies that want proper cloud consolidation.
What changes on the licensing side
NAV licensing was typically a one-off perpetual cost plus an annual enhancement plan. Business Central licenses per user, per month, on a subscription model, which usually lowers the up-front cost of the move considerably — the bulk of a NAV upgrade project cost sits in the customisation conversion work, not the licence itself.
What NAV-to-BC upgrades typically deliver
Aggregate results from recent NetMonkeys Business Central implementations.
On-premises servers to patch and maintain, once fully cloud-hosted.
Reporting ROI with native Power BI replacing manual NAV report layouts.
Yearly feature updates delivered automatically, versus manual NAV version upgrades.
Data model continuity — nothing rebuilt from scratch, unlike a switch to a different ERP.
Why upgrade from NAV with NetMonkeys
NAV Specialists Since Launch
We've been upgrading NAV to Business Central since the platform first launched, not a recent addition to our services.
C/AL Conversion Experience
We've migrated dozens of NAV customers, including heavily customised C/AL deployments others have turned away.
Microsoft Solutions Partner
Certified across Business Applications, re-verified annually.
UK Consultants
Every consultant and project manager is UK-employed.
Dynamics NAV to Business Central: common questions
Which NAV versions can you upgrade from?
Every version from NAV 2009 through 2018, including heavily customised C/AL builds. Very old versions sometimes need an intermediate upgrade step, which we scope during discovery.
Will our custom NAV code just work in Business Central?
Not directly. C/AL customisations need converting into AL extensions to work properly and survive future BC updates. This is usually the largest part of the project, and we assess the scope of it upfront.
Do we have to move to the cloud, or can we stay on-premises?
Business Central is available both as cloud SaaS and on-premises. Most NAV customers move to the cloud version, but on-premises remains an option where data residency or integration requirements demand it.
What happens to our third-party NAV add-ons?
We check whether a BC-compatible version exists for each one during discovery. Where it doesn't, we scope a proper replacement rather than leaving a functionality gap.
How long do we have before our NAV version loses support entirely?
It depends on your version — several are already past end of support, and NAV 2018 Extended support ends in January 2028. We can check your specific version's status as part of an initial review.
Still running Dynamics NAV?
A free review of your current NAV version, customisations and support status, with a straight answer on what an upgrade would involve.