Dynamics NAV On-Premises End of Life: What NAV Users Should Do Next
Many companies still run Microsoft Dynamics NAV, and many of those systems still work well day to day. But every version of NAV is either already out of support or close to it. This article lists Microsoft’s official support dates for each version, explains the risks of staying, and walks through what an upgrade to Microsoft Dynamics 365 Business Central involves.
Official Dynamics NAV Support Dates by Version
All NAV versions follow Microsoft’s Fixed Lifecycle Policy: about five years of mainstream support (fixes and regulatory updates), then five years of extended support (security updates only). After extended support ends, Microsoft provides no updates of any kind.
| Version | Mainstream support ended | Extended support ends |
|---|---|---|
| NAV 2009 / 2009 R2 | January 13, 2015 | January 14, 2020 |
| NAV 2013 | January 9, 2018 | January 10, 2023 |
| NAV 2013 R2 | January 9, 2018 | January 10, 2023 |
| NAV 2015 | January 14, 2020 | January 14, 2025 |
| NAV 2016 | April 13, 2021 | April 14, 2026 |
| NAV 2017 | January 11, 2022 | January 11, 2027 |
| NAV 2018 | January 10, 2023 | January 11, 2028 |
As of November 2026, NAV 2009 through NAV 2016 are fully out of support. NAV 2017’s support ends in January 2027, and NAV 2018, the final NAV release, ends in January 2028.
Business Central on-premises has its own dates. Business Central Spring 2019 (version 14), the last version with the classic C/AL development environment, followed the Fixed Lifecycle Policy and reached end of support on October 14, 2025. Later Business Central on-premises versions follow the Modern Lifecycle Policy, under which each major release is supported for about 18 months, so on-premises customers need to upgrade regularly to stay supported.
Sources: Microsoft Lifecycle pages for NAV 2009, NAV 2009 R2, NAV 2013, NAV 2013 R2, NAV 2015, NAV 2016, NAV 2017, NAV 2018, and Ending Support in 2025.
The Risks of Staying on NAV
- No security updates. Unsupported ERP software holding financial and customer data is a real exposure, and it can affect audits and cyber insurance.
- Aging infrastructure. Older NAV versions depend on old versions of Windows Server and SQL Server that are themselves out of support.
- Harder to find help. Fewer consultants work in C/AL and the classic client every year, and their time costs more.
- Integration problems. Modern banking, tax, EDI, and e-commerce services expect current APIs.
- A bigger jump later. The longer you wait, the more versions, data, and customizations you have to carry forward at once.
Moving to Business Central: Cloud or On-Premises
Business Central is the direct successor to NAV. It uses the same core concepts, including posting groups, dimensions, item ledger entries, and the general ledger, so NAV users adapt quickly.
Business Central online (cloud) is where most companies are going. Microsoft hosts it, updates it twice a year, and handles backups and security. You stop managing servers.
Business Central on-premises is still available for companies with specific hosting or connectivity requirements. You keep control of servers, but you also take on regular upgrades to stay on a supported version.
The Upgrade Path for Customizations and Extensions
This is usually the biggest part of a NAV upgrade.
From C/AL to AL Extensions
NAV customizations were written in C/AL directly inside the base application. Business Central no longer allows that. Customizations must be rebuilt as AL extensions that sit on top of the standard application. This makes future updates far easier, but existing code must be reviewed and converted.
Review Before You Convert
Many NAV customizations were added years ago to fill gaps that Business Central now covers out of the box. A good upgrade starts by sorting each customization into one of three groups:
- Retire: replaced by standard Business Central features
- Replace: covered by an AppSource app (for example Avalara for sales tax, Continia for document capture, SPS Commerce for EDI, Lanham or Insight Works for warehouse operations, or LS Central for retail)
- Rebuild: truly unique processes rebuilt as AL extensions
Data Upgrade
Depending on your NAV version, data is upgraded technically through intermediate versions or moved with Microsoft’s cloud migration tools. Older versions such as NAV 2009 and 2013 often need extra steps.
Cost and Timeline Factors
- Your starting version. NAV 2009 and 2013 require more work than NAV 2017 or 2018.
- Amount of custom code. This is often the largest cost driver.
- Third-party add-ons and whether current versions exist for Business Central
- Integrations such as EDI, e-commerce, payments, and reporting
- Data volume and quality
- Cloud vs. on-premises
A NAV 2017 or 2018 system with modest customization can often be upgraded in three to five months. Older or heavily customized systems commonly take six to twelve months.
Plan Before Your Support Runs Out
If you are on NAV 2016 or older, you are already running unsupported software. If you are on NAV 2017 or 2018, your support ends in 2027 or 2028, and an upgrade started now finishes with time to spare.
DPFE Corp has worked with business software since 1980 and has years of NAV experience as a Microsoft Dynamics 365 Business Central partner in Southern California. Learn more on our Dynamics NAV to Business Central Upgrade page, or contact us to review your NAV system and upgrade options.