NAV 2016, 2017 & 2018 End-of-Life: What Happens Next?

Microsoft Dynamics NAV 2016, NAV 2017, and NAV 2018 are reaching the end of their supported lifecycles. If your business is running any of these versions, understanding what end-of-life means in practice — and what happens if you do nothing — is essential before making a decision about your next steps.

Microsoft Support Lifecycle: What the Dates Actually Mean

Microsoft operates a fixed support lifecycle for most of its business software products. For Dynamics NAV, this lifecycle consists of two phases: mainstream support and extended support.

During mainstream support, Microsoft releases security patches, bug fixes, and non-security updates. Extended support covers security patches only — no new features, no bug fixes, and no regulatory updates. Once extended support ends, nothing is released.

What Happens When Extended Support Ends

When extended support ends, the practical consequences are not immediate and dramatic — the software does not stop working. But the risks compound over time in ways that eventually become serious.

• Security vulnerabilities go unpatched. Any security flaw discovered after the end-of-support date will not be fixed. For finance systems handling sensitive data, this is a genuine and growing exposure.
• Regulatory compliance becomes increasingly difficult. NAV 2016, 2017, and 2018 will not receive updates for HMRC requirements, VAT rule changes, or MTD obligations.
• Third-party software stops supporting your NAV version. Payroll providers, CRM systems, and ecommerce platforms will eventually drop support for older NAV versions, creating integration failures.
• Your internal support options narrow. Fewer consultants work with legacy NAV versions over time. Finding experienced help for a critical issue becomes more expensive and slower.

NAV 2016: Already Beyond Extended Support

If your business is running NAV 2016, you are already past the end of Microsoft's extended support. This means you have been operating without security patches since January 2026. Every month that passes increases your exposure.

The good news for NAV 2016 businesses is that the migration path to Business Central is well-established. NAV 2016 environments have been through this process many times, and experienced partners understand the typical customisation patterns and data structures of this version. The migration is achievable and the timeline is predictable when planned properly.

The priority for NAV 2016 businesses should be getting a migration project scoped and started as quickly as possible.

NAV 2017: Final Year of Extended Support

Businesses on NAV 2017 have extended support until January 2027 — but this is the last year in which security patches are being released. Planning a migration now means you can execute the project in an orderly way before support ends, rather than under pressure after it does.

NAV 2017 introduced improved web client functionality and enhanced integration capabilities. Some businesses on NAV 2017 have relatively modern customisations and integrations that will require careful handling during migration to Business Central. Starting the assessment process now gives you time to understand the scope before committing to a timeline.

NAV 2018: The Last NAV Version Before Business Central

NAV 2018 is the final version of Microsoft Dynamics NAV. After NAV 2018, Microsoft launched Business Central as the product's successor. NAV 2018 businesses have extended support until January 2028, which provides a reasonable planning horizon — but not an indefinite one.

NAV 2018 is notable because it was released alongside the first version of Business Central, and migration tools specifically designed for NAV 2018 are the most mature available. The technical gap is smaller than from earlier versions, which typically makes the migration more straightforward — but accumulated customisations and data quality issues still need addressing.

Your Options After End-of-Life

Businesses facing NAV end-of-life have three realistic options: migrate to Business Central, move to a different ERP system, or stay on NAV and accept the risks.

Staying on NAV after end-of-life is a choice some businesses make, particularly if they are in the middle of other significant projects or facing budget constraints. It is not a responsible long-term position, but understanding the risks clearly allows a business to make an informed decision about timing.

Moving to a different ERP system is a legitimate option, but if your business is already invested in the Microsoft ecosystem — using Microsoft 365, Teams, Power BI, Azure — then Business Central offers integration advantages that other systems cannot match.

Migrating to Business Central is the path most NAV businesses take. It preserves continuity with the familiar NAV structure while delivering a modern, cloud-based platform. The Business Central pricing model has also become more predictable — subscription-based rather than perpetual licence plus annual enhancement fees.

What You Gain by Moving to Business Central

Beyond eliminating the risks of unsupported software, moving to Business Central delivers tangible operational improvements. The integration with Power BI is one of the most immediately valuable. Business Central's native Power BI connection means finance teams can build real-time dashboards on live operational data without any custom development.

Microsoft Copilot features embedded in Business Central automate accounts payable processing, produce cash flow forecasts, and flag late payment risks. These AI-driven capabilities were not available in any NAV version. The update model changes fundamentally too — NAV required upgrade projects every few years, whereas Business Central receives two automatic updates per year from Microsoft.

For businesses with manufacturing or supply chain operations, current Business Central versions offer significantly more capable manufacturing functionality than NAV 2016 or 2017, and comparable or better than NAV 2018 for most scenarios.

Planning Your Migration: Key Considerations

The most important thing you can do at this stage is to get an honest assessment of your current environment. The migration scope — and therefore cost and timeline — depends heavily on how much customisation has been built into your NAV system, the quality of your data, the number of external integrations, and the complexity of your business processes.

The right time to start planning is now, regardless of which version you are on. Even if your extended support date is still a year or two away, the planning, scoping, and procurement process for a migration project takes time — and beginning that process early gives you negotiating leverage, more flexibility in your go-live timing, and a smoother project overall. Read our full guide on how to choose a Business Central implementation partner before you begin your search.