Dynamics NAV end of support comes in two stages, on January 11, 2027, for NAV 2017 and on January 11, 2028, for NAV 2018, the last NAV version. After that, Microsoft no longer provides security updates. This affects senior management, IT managers and finance managers in wholesale, retail, manufacturing and the supplier industry whose order processing, warehousing and accounting have been running on custom developments in Navision for years.
NAV 2017 keeps running after January 11, 2027, but without security updates. Microsoft intends for Business Central to be its successor. For NAV 2017, the path to Business Central involves two intermediate versions and requires that every C/AL customization be rewritten in AL, replaced with a standard solution, or eliminated. Project costs are therefore primarily determined by the customizations and interfaces. Evaluate each customization individually before deciding between an upgrade, a new implementation, or another ERP system. For NAV 2017, the time available until January is not sufficient for the transition; a bridge plan is necessary to maintain operations until go-live.
NAV 2017 End of Support: What Ends on January 11, 2027
Extended support for Dynamics NAV 2017 ends on January 11, 2027 (Microsoft Lifecycle). For NAV 2018, January 11, 2028, is the last day of support (Microsoft Lifecycle). Both versions follow the Fixed Lifecycle Policy. During extended support, only security updates are provided; no other bug fixes or new features are included (Microsoft Fixed Lifecycle Policy).
After the cutoff date, security updates will also cease. The NAV 2017 lifecycle page does not mention an ESU program similar to the one for Windows Server. Technically, NAV will continue to run, but new vulnerabilities in the NAV server, the web client, and the web services will remain unpatched. According to Microsoft partner Comsol, the rate for the maintenance contract for NAV and Business Central On-Premises will increase from 20 to 21 percent as of October 6, 2026, effective with the next renewal (Comsol, 06.10.2026).
According to Microsoft, the upgrade path from NAV 2017 to the current on-premises version 29 of Business Central goes through versions 14 and 25.
Microsoft Learn, November 2026
Navision's Successor, Business Central: The Path Through Two Interim Versions
From NAV 2015 to NAV 2018, the supported migration path leads first to Business Central version 14, then to version 25, and only then to the current on-premises version 29. It requires that the application be migrated from C/AL to AL (Microsoft Learn). Every customization in the NAV code is therefore rewritten, replaced by standard functionality or removed.
The duration and cost depend on this. For a new implementation using standard processes, the Microsoft partner NAVAX estimates that it takes 8 to 12 weeks to reach production (NAVAX). There are ten weeks remaining until the NAV 2017 deadline, and for many retailers, inventory counts and year-end financial statements fall within that timeframe. A transition before January 11, 2027, is therefore not realistic for most companies. A go-live in 2027 is feasible, with operations secured until then.
Model Calculation: NAV Business Central Migration Costs for a Wholesaler
All figures are assumptions. A wholesaler of industrial supplies with three warehouses runs NAV 2017 with 45 users, 60 C/AL customizations and six interfaces, namely EDI with two major customers, web store, warehouse management, shipping provider and bank. The chosen path is a new implementation of Business Central online. The inventory takes 10 to 15 person-days. Standard functionality replaces 20 customizations, at 0.5 to 1 person-day of setup each, 10 to 20 in total. Another 25 customizations are rebuilt as AL extensions, 2 to 4 person-days each, 50 to 100 in total. Nobody uses the remaining 15 any more, so they are dropped. The six interfaces take 3 to 6 person-days each, 18 to 36 in total. We assume 15 to 25 person-days for data migration with two test migrations, and another 15 to 25 for testing and training.
In total, the estimate comes to 118 to 221 person-days. The largest item is the AL extensions. Each customization that is dropped instead saves 2 to 4 person-days in this calculation. Added to this are licenses for 20 users with Essentials at 69.30 euros and 25 Team Members at 6.90 euros per user per month. With annual billing, this amounts to 18,702 euros per year, list price plus VAT (Microsoft, as of November 2, 2026).
Your Options When Dynamics NAV Support Ends
| Option | Effort | Costs | Risk |
|---|---|---|---|
| Upgrade to Business Central with all customizations | Months, from versions 14 to 25 | Licenses, conversion of each customization in AL | Old customizations are carried over, even unused ones |
| New Implementation of Business Central with Standard Processes | According to NAVAX, 8 to 12 weeks for a standard launch | Licenses, Setup, Import of Master Data and Balance Data | History remains in the old system; departments change processes |
| Another ERP system | Selection process and implementation | Depends on the project; maximum effort | Longest path, NAV needs a bridge solution until then |
| Extract Special Functions | Weeks per function | Custom application with an interface to the ERP system | One more application in operation, but fewer adjustments to the ERP system |
| Isolation as a Bridge | Days | Low | New gaps remain open; this is acceptable only if there is a fixed end date |
| Do nothing | None | None for now | No security updates after January 11, 2027, a finding in NIS2 and ISO 27001 audits |
The options can be combined. The process for such a project is described on our page Legacy Modernization with a Migration Plan.
Which Approach Is Best Suited for Which NAV System?
The upgrade is suitable for systems with few, documented customizations and a history that is needed in the new system. For companies that have spent many years developing their own C/AL code, we believe a fresh implementation is the better option, because any customizations carried over will have to be rewritten anyway. A different ERP system is worth considering for manufacturers, groups with subsidiaries in multiple countries, and companies that maintain parallel financial reporting under HGB and IFRS. According to the comparison portal ERP Pilot, Business Central is often not the right choice in these cases (ERP Pilot, 10/2026).
Special functions such as pricing for major customers, label printing, or integration with warehouse technology are often best handled in a separate application that interfaces with the ERP. This ensures that the next ERP migration will not be dependent on them. Continuing to operate NAV 2017 after the cutoff date is only justifiable as a temporary solution with a fixed end date. This requires a web client and web services that are not accessible from the Internet, access only via VPN, and a dedicated network segment for the NAV servers.
NAV Migration Plan in 15 Business DaysYou receive a list of all C/AL customizations, reports and interfaces in your NAV system, with usage data. For each customization, we recommend a path, namely standard functionality in Business Central, an AL extension, a separate application alongside the ERP or removal, each with an effort estimate. In addition, you receive a bridge plan for operations after January 11, 2027, a schedule up to go-live and a scope of work for selecting the ERP partner. You then decide between upgrade, new implementation and another ERP system and request quotes on the same basis. Initial consultation: 30 minutes, free of charge, response within one business day.
Frequently Asked Questions
How much does it cost to migrate from NAV to Business Central?
According to Microsoft's price list, Business Central online costs 69.30 euros for Essentials, 95.30 euros for Premium and 6.90 euros for Team Members per user per month, with annual billing, as of November 2, 2026. Project costs depend on the number of customizations and interfaces. An ERP partner can only quote a binding price after the inventory.
When is the end of support for NAV 2018?
The last day of support is January 11, 2028. NAV 2018 will therefore remain in extended support for one additional year. The path to Business Central is the same: via Version 14 and Version 25.
Will NAV 2017 continue to run after support ends?
Technically, yes, but Microsoft will no longer provide security updates. Please determine internally whether this complies with information security and insurance requirements.
The Next Step
torck modernizes legacy systems in industry and retail without interrupting operations and develops custom functions as standalone applications that interface with the ERP system. You can find out how we do this on the page Legacy Modernization. For further reading, see Modernize or Replace Legacy Software and ERP Integration for SAP and Dynamics. One day later, on January 12, 2027, Windows Server 2016 will reach end of support; see our post on this End of Support for Windows Server 2016. Schedule an Initial Consultation.