Dynamics NAV End of Support: A Leader's Guide to Moving to Business Central

Two colleagues with laptops in a server room corridor

Thousands of UK companies still run their business on Microsoft Dynamics NAV (Navision). It has served them well for years, but time is running out. Microsoft’s support for the remaining NAV versions is ending, and with every year the gap between NAV and its successor, Dynamics 365 Business Central, grows wider. This guide explains the deadlines, the business risks and how to plan a NAV to Business Central migration without disrupting your operations.

Key takeaways for leaders

  • Dynamics NAV 2016 extended support ends in April 2026, NAV 2017 in January 2027 and NAV 2018 in January 2028.
  • After end of support there are no more security updates, which is a growing risk for cybersecurity, compliance and insurance.
  • Business Central is NAV’s direct successor, so your team will recognise the processes and data model.
  • A good migration is also a chance to remove old customisations and lower your total cost of ownership.
  • Plan 6 to 12 months ahead. The partners with the most experience fill their calendars first.

The Dynamics NAV Support Timeline

Microsoft products follow a fixed lifecycle: five years of mainstream support followed by five years of extended support, which covers security updates only. For the last NAV versions, extended support ends on these dates:

  • Dynamics NAV 2016: 14 April 2026
  • Dynamics NAV 2017: 11 January 2027
  • Dynamics NAV 2018: 11 January 2028

Older versions such as NAV 2009, 2013 and 2015 are already out of support. Always confirm the current dates in Microsoft’s official lifecycle documentation.

The Business Risks of Staying on NAV

  • Security: without security updates, every newly discovered vulnerability stays open. For companies that need Cyber Essentials certification or cyber insurance, unsupported software can become a serious problem.
  • Compatibility: older NAV versions depend on older versions of Windows Server, SQL Server and Office, which are also leaving support.
  • Compliance: new requirements, such as HMRC’s Making Tax Digital changes and the coming move to e-invoicing, are developed for Business Central, not for NAV.
  • People: fewer and fewer consultants and developers work with old NAV versions, and the ones who do are expensive.
  • Missed opportunities: Copilot, AI agents, Power BI apps, mobile access and Microsoft 365 integration are only available in Business Central.

Why Business Central Is the Natural Next Step

Business Central is built on the same foundations as NAV. Your users will recognise the chart of accounts, posting groups, documents and processes, which shortens the learning curve dramatically. At the same time you gain a modern web interface, cloud hosting by Microsoft, two major updates every year without costly upgrade projects, and built-in AI.

Customisations are handled differently in Business Central. Instead of changing the standard code, they are built as extensions. This keeps future updates simple, but it means old NAV modifications must be reviewed. In practice, many of them are no longer needed because the standard product now covers those needs.

A Proven Migration Approach

  1. Assessment: inventory your NAV customisations, integrations, reports and data volumes, and decide what to keep, replace with standard features or retire.
  2. Decide on cloud or on-premises. Most companies choose Business Central online for lower IT overhead and automatic updates.
  3. Redesign and develop: rebuild the customisations you really need as extensions.
  4. Data migration: use Microsoft’s cloud migration tools to move master data and history, and clean up the data before you do.
  5. Testing and training: test with real scenarios and train key users.
  6. Go-live and hypercare: choose a quiet period for go-live, not year-end, and plan intensive support for the first weeks.

Learn more about our NAV to Business Central migration service.

What It Costs, and What It Saves

The migration cost depends mainly on the number of customisations and integrations. The business case, however, is usually driven by savings: no more server hardware and SQL licences, no expensive upgrade projects every few years, less manual work thanks to automation and AI, and better decisions thanks to real-time reporting. Many companies find that a well-planned migration pays for itself within a few years.

Frequently Asked Questions

When does Dynamics NAV support end?

Extended support for Dynamics NAV 2016 ends on 14 April 2026, for NAV 2017 on 11 January 2027 and for NAV 2018 on 11 January 2028. Older NAV versions are already out of support.

Can NAV keep running after support ends?

Yes, the software keeps working, but Microsoft no longer releases security updates or fixes. The risk grows over time, especially for security, compliance and compatibility with new Windows and SQL Server versions.

How long does a NAV to Business Central migration take?

A typical project for a small or medium-sized company takes 3 to 9 months, depending on the number of customisations, integrations and companies.

Can we keep our historical data?

Yes. Microsoft provides cloud migration tools to move data from NAV to Business Central, and historical data can be migrated or archived based on your reporting needs.

The question is no longer whether to move from NAV to Business Central, but when, and whether you do it on your own schedule or under pressure from a support deadline.

Would you like a free assessment of your NAV system and a migration roadmap? Contact us or book a call with one of our experts. You can also download our NAV to BC migration roadmap from the e-books page.

Related reading

Sign up for monthly Business Central insights that help you get more value from your ERP.

Subscription Form
Scroll to Top

Let's fix this. Fast.

Leave your details and one of our Business Central experts will call you back usually within the same business day.

No sales pitch, just a straightforward conversation about your situation.