Dynamics NAV support is ending — your version matters
Mainstream support for all versions of Dynamics NAV has already ended. Extended support for NAV 2016 ends April 2026, NAV 2017 in January 2027, and the final version NAV 2018 in January 2028. After these dates, Microsoft issues no further security patches, regulatory updates, or bug fixes. If you are on NAV 2015 or earlier, you are already beyond extended support.
In short: Dynamics NAV and Business Central are the same product lineage — Business Central is what NAV became when Microsoft rebuilt it for the cloud in 2018. Upgrading is not a platform change; it is moving to the current and future version of the system you already run, with significantly more capability, no server infrastructure overhead, and continuous updates from Microsoft going forward.
Dynamics NAV end of support dates
Microsoft follows a fixed 10-year support lifecycle for NAV. Here is where each supported version stands today.
| Version | Mainstream support ended | Extended support ends | Status |
|---|---|---|---|
| NAV 2015 | January 2020 | January 2025 | ⚠ Beyond extended support |
| NAV 2016 | April 2021 | April 2026 | ⚠ Extended support ending soon |
| NAV 2017 | January 2022 | January 2027 | Extended support active |
| NAV 2018 | January 2023 | January 2028 | Extended support active (final version) |
Extended support means security and regulatory updates only — no new features, no bug fixes, and no compatibility guarantees with new versions of Microsoft 365, Windows, or SQL Server. Planning your migration now, rather than when support expires, gives you control over timing and scope.
What you gain by moving to Business Central
Business Central is not simply NAV in the cloud. Seven years of development separates the products, and the gap in capability is substantial.
Outlook, Teams, Excel, SharePoint, and OneDrive all connect directly. Raise POs from Outlook, share BC data in Teams channels, analyse in Excel live.
Live executive dashboards connected directly to Business Central data — no manual exports, no end-of-month spreadsheet builds.
AI assistance for bank reconciliation, purchase order suggestions, financial narrative generation, and more — expanding continuously with Microsoft’s AI investment.
Cloud deployment removes on-premise servers, SQL licences, and the IT maintenance burden of keeping NAV running. Microsoft manages updates automatically.
Two major updates per year, delivered automatically. No expensive version upgrade projects every three years. New features arrive continuously.
Role-tailored browser interface with full mobile access. NAV’s Windows client is gone — Business Central works on any device, anywhere.
Hundreds of certified extensions from Microsoft partners covering industry verticals, integrations, and additional functionality — replacing NAV’s more limited add-on landscape.
Native connection to Dynamics 365 Sales via Dataverse — a unified quote-to-cash process without third-party middleware.
Business Central vs Dynamics NAV: the key differences
| Business Central | Dynamics NAV | |
|---|---|---|
| Deployment | Cloud-first (SaaS); on-premise available | On-premise; cloud via hosting partner |
| Updates | Automatic, twice-yearly via Microsoft | Manual version upgrades, typically every 3–5 years |
| Development language | AL (modern, extension-based) | C/AL (legacy, being retired) |
| Microsoft 365 integration | Native — deep | Very limited |
| Power BI | Native connector | Via manual data export |
| Microsoft Copilot AI | Built in, expanding | Not available |
| Interface | Browser / mobile (responsive) | Windows client (legacy) |
| Support status | Fully supported Continuous investment |
End of life Extended support only, ending 2026–2028 |
| Pricing model | Per user/month subscription — transparent | Perpetual licence + annual enhancement plan |
| Server infrastructure | None required (cloud deployment) | On-premise SQL Server and Windows Server required |
What the migration involves
The NAV to Business Central migration has three main technical elements that drive complexity and cost:
1. Customisation review and rewrite — NAV customisations written in C/AL code cannot be directly imported into Business Central. Each one needs to be reviewed: some can be replaced by standard Business Central functionality that did not exist in NAV; others need rewriting as AL extensions; a proportion can simply be retired as no longer needed. This review often reveals that many years of accumulated NAV customisations can be significantly simplified.
2. Data migration — master data (customers, suppliers, items), open transactions (open sales orders, purchase orders, outstanding invoices), and financial opening balances all migrate to Business Central. Historical transaction detail typically remains accessible in the old system as a read-only archive for a period rather than being fully migrated, which keeps costs proportionate.
3. Integration re-mapping — any third-party systems connected to NAV (payroll, eCommerce, field service tools, industry-specific software) need their integrations reviewed and updated for Business Central. Some will have native Business Central connectors; others will need API development.
Typical timescale: 12–24 weeks from project kick-off to go-live, depending on customisation complexity and number of integrations.
The Advantage methodology
NAV migrations are more complex than migrations from third-party accounting software because of the customisation layer. Our Analyse phase is particularly thorough for NAV projects — it is where we establish an accurate scope and fixed cost.
Full audit of your NAV customisations, data model, integrations, and version. The output is a fixed scope, cost, and timeline — not an estimate that grows during the project.
Customisation development, data migration, Business Central configuration, Microsoft 365 integration, and user training — delivered in structured phases with sign-off at each milestone.
Post-go-live support, Power BI dashboard build-out, and continuous improvement as the team moves from NAV habits to Business Central capabilities.
Frequently Asked Questions — Dynamics NAV to Business Central
Common questions from UK businesses still running Dynamics NAV and evaluating the move to Business Central — answered by Advantage, Microsoft Solutions Partner.
Is Dynamics NAV the same as Business Central?
Dynamics 365 Business Central is the direct successor to Microsoft Dynamics NAV — the same product lineage, rebranded and rebuilt for the cloud in 2018. Before NAV, the product was known as Navision. So Navision became NAV, and NAV became Business Central.
Functionally, Business Central covers everything NAV did and significantly more. The architectural difference is that Business Central is cloud-native, uses a modern AL development language instead of C/AL, connects natively with Microsoft 365, and receives continuous updates from Microsoft rather than periodic version upgrades.
When does Dynamics NAV support end?
Mainstream support for all versions of Dynamics NAV has already ended. Extended support — which covers security and regulatory updates only, not new features or bug fixes — continues as follows: NAV 2016 until April 2026, NAV 2017 until January 2027, and NAV 2018 (the final version) until January 2028. NAV 2015 and earlier are already beyond extended support.
Starting your migration planning now rather than close to the deadline gives you more control over timescale, budget, and business disruption. Migrations that are rushed because a deadline is imminent almost always cost more and cause more disruption than those planned with adequate lead time.
How difficult is it to upgrade from Dynamics NAV to Business Central?
The complexity depends primarily on how heavily customised your NAV system is. Standard NAV processes and data migrate relatively cleanly. Customisations written in C/AL need to be reviewed and either rewritten in AL, replaced by standard Business Central functionality, or retired — this is the main driver of project cost and timescale.
Advantage conducts a full customisation audit as the first step of any NAV migration project. This audit determines the actual complexity and cost before any migration work begins, so there are no surprises part-way through the project.
What happens to my NAV customisations when I move to Business Central?
NAV customisations written in C/AL cannot be directly imported into Business Central. Each needs to be reviewed: some can be replaced by standard Business Central functionality that has expanded significantly since NAV was developed; others need rewriting as AL extensions; and some can simply be retired as no longer relevant to how the business operates today.
This review is often a useful exercise in its own right — many NAV systems carry years of accumulated customisations that were built to work around limitations that Business Central has since resolved natively. The migration is an opportunity to simplify and modernise rather than simply recreate what was there before.
Can I stay on Dynamics NAV after support ends?
Technically yes, but the risks accumulate over time. Once extended support ends, Microsoft issues no further security patches, regulatory updates, or bug fixes. For UK businesses, this creates compliance risk as HMRC’s Making Tax Digital requirements evolve — VAT return submission via unsupported software may become increasingly unreliable. Security vulnerabilities discovered after support ends go unpatched.
There is also an increasing practical friction: newer versions of Windows, Microsoft 365 apps, and browsers become less compatible with old NAV versions over time, creating maintenance headaches and support challenges. The longer a migration is deferred, the more it costs when it eventually happens.
What do I gain by upgrading from NAV to Business Central?
The most significant gains are: native Microsoft 365 integration across Outlook, Teams, Excel, and SharePoint; Power BI reporting connected directly to live ERP data without manual exports; Microsoft Copilot AI for finance and operations tasks; continuous automatic updates with no manual upgrade projects; a modern browser and mobile interface; removal of on-premise server infrastructure (for cloud deployment); and access to the AppSource marketplace of certified extensions.
For most businesses that have been on NAV for five or more years, the capability difference is substantial — not incremental.
Does Advantage manage NAV to Business Central migrations?
Yes — Advantage manages NAV to Business Central migrations for UK businesses, from initial customisation audit and scoping through to data migration, AL extension development, Microsoft 365 integration, user training, and post-go-live support. We also provide Power BI dashboards as part of every migration, giving finance directors the reporting visibility that NAV never offered.
Call us on 020 3004 4600 or contact us online to discuss your current NAV version, how customised your system is, and what a realistic migration would involve.
