{"id":14248,"date":"2026-11-02T07:09:29","date_gmt":"2026-11-02T07:09:29","guid":{"rendered":"https:\/\/ngenioussolutions.com\/blog\/?p=14248"},"modified":"2026-11-02T09:06:34","modified_gmt":"2026-11-02T09:06:34","slug":"dynamics-nav-end-of-support","status":"publish","type":"post","link":"https:\/\/ngenioussolutions.com\/blog\/dynamics-nav-end-of-support\/","title":{"rendered":"Dynamics NAV End of Support: What 2027, 2028 and 2031 Mean"},"content":{"rendered":"<div style=\"border: 1px solid #e5e7eb; border-radius: 10px; overflow: hidden; margin: 28px 0; background: #ffffff; box-shadow: 0 6px 16px rgba(0,0,0,0.06);\">\n<div style=\"background: #2d55a5;\">\n<p style=\"margin: 0; font-size: 17px; font-weight: 600; color: #ffffff; padding: 12px 18px;\">Key Takeaways<\/p>\n<\/div>\n<div style=\"padding: 18px 20px;\">\n<ul style=\"margin: 0; padding-left: 20px; font-size: 14px; line-height: 1.7; color: #1f2937;\">\n<li>NAV 2017 and NAV 2018 reach end of extended support in 2027 and 2028, respectively.<\/li>\n<li>Microsoft\u2019s 2031 milestone affects NAV licensing and service plans, not technical support or security updates.<\/li>\n<li>Unsupported NAV systems increase security, integration, compliance, and knowledge-retention risks even when business processes continue running.<\/li>\n<li>A successful Business Central migration starts with assessing customizations, integrations, data, and critical business processes.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<p>The next Dynamics NAV end of support deadline is approaching. NAV 2017 reaches the end of Microsoft extended support in January 2027, while NAV 2018 reaches that point one year later. A separate Microsoft announcement sets April 2031 milestones for NAV licensing and service plans. These dates are often grouped together, even though they affect customers in different ways.<\/p>\n<p>For a business still using Microsoft Dynamics NAV, the difference matters. A system can continue processing invoices and posting transactions after support ends. The harder question is who can address a new product vulnerability, a broken integration or a change in business requirements when the vendor lifecycle has closed. <a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2017\" target=\"_blank\" rel=\"noopener\">Microsoft\u2019s NAV lifecycle records<\/a> and <a href=\"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2026\/07\/28\/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers\/\" target=\"_blank\" rel=\"noopener\">July 2026 licensing announcement<\/a> provide the starting point.<\/p>\n<table style=\"width: 100%; background-color: #f7f9fc; border: 1px solid #172b4d !important; border-collapse: collapse !important;\">\n<tbody>\n<tr>\n<td style=\"padding: 20px; border: 1px solid #172b4d !important;\"><strong style=\"color: #172b4d;\">THE SHORT ANSWER<\/strong><\/p>\n<p>NAV 2017 extended support ends January 12, 2027. NAV 2018 ends January 12, 2028. Beginning April 30, 2031, Microsoft ends specified NAV service-plan coverage and licensing options. The 2031 milestone does not extend technical support for either version.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Dynamics NAV end of support dates at a glance<\/h2>\n<p>Microsoft Dynamics NAV end of support follows a release-by-release schedule. The final NAV version was NAV 2018, so there is no product called \u201cNAV 2027.\u201d For most organizations, the first task is confirming which release is actually running in production.<\/p>\n<table>\n<thead>\n<tr style=\"background-color: #2d55a5; color: #ffffff; font-weight: 550 !important; line-height: 22px;\">\n<td width=\"218\"><strong>NAV release \/ milestone<\/strong><\/td>\n<td width=\"218\"><strong>Microsoft date (US)<\/strong><\/td>\n<td width=\"218\"><span data-teams=\"true\">Support status<\/span><\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td width=\"148\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2015\" target=\"_blank\" rel=\"noopener\">NAV 2015<\/a><\/td>\n<td width=\"235\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2015\" target=\"_blank\" rel=\"noopener\">January 15, 2025<\/a><\/td>\n<td width=\"264\">Extended support ended<\/td>\n<\/tr>\n<tr>\n<td width=\"148\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2016\" target=\"_blank\" rel=\"noopener\">NAV 2016<\/a><\/td>\n<td width=\"235\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2016\" target=\"_blank\" rel=\"noopener\">April 15, 2026<\/a><\/td>\n<td width=\"264\">Extended support ended<\/td>\n<\/tr>\n<tr>\n<td width=\"148\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2017\" target=\"_blank\" rel=\"noopener\">NAV 2017<\/a><\/td>\n<td width=\"235\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2017\" target=\"_blank\" rel=\"noopener\">January 12, 2027<\/a><\/td>\n<td width=\"264\">Next support deadline<\/td>\n<\/tr>\n<tr>\n<td width=\"148\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2018\" target=\"_blank\" rel=\"noopener\">NAV 2018<\/a><\/td>\n<td width=\"235\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2018\" target=\"_blank\" rel=\"noopener\">January 12, 2028<\/a><\/td>\n<td width=\"264\">Extended support active<\/td>\n<\/tr>\n<tr>\n<td width=\"148\"><a href=\"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2026\/07\/28\/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers\/\" target=\"_blank\" rel=\"noopener\">NAV licensing<\/a><\/td>\n<td width=\"235\"><a href=\"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2026\/07\/28\/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers\/\" target=\"_blank\" rel=\"noopener\">April 30, 2031<\/a><\/td>\n<td width=\"264\">Not a technical support date<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Dates reflect the individual Microsoft Lifecycle product pages, which show dates in Pacific Time. The 2031 row is based on Microsoft\u2019s separate licensing announcement.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-14251\" src=\"https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-scaled.webp\" loading=\"lazy\" alt=\"Timeline showing Microsoft Dynamics NAV extended support end dates: NAV 2015 on January 15, 2025; NAV 2016 on April 15, 2026; NAV 2017 on January 12, 2027; and NAV 2018 on January 12, 2028. Also highlights April 30, 2031, as a licensing and service-plan milestone, not a technical support deadline.\" width=\"2560\" height=\"1441\" srcset=\"https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-scaled.webp 2560w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-300x169.webp 300w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-1024x576.webp 1024w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-768x432.webp 768w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-1536x864.webp 1536w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/NAV-extended-support-deadlines-versus-the-separate-April-2031-licensing-milestone-2048x1152.webp 2048w\" sizes=\"auto, (max-width: 2560px) 100vw, 2560px\" \/><\/p>\n<h3>How to check which NAV version you are running<\/h3>\n<p>In the NAV Windows client, open Help and select \u201cAbout Microsoft Dynamics NAV\u201d to find the product version and build. Your administrator or implementation partner can confirm the server version, cumulative updates, database dependencies and license model. This matters in environments where a subsidiary or test instance runs a different release from the primary company.<\/p>\n<h3>There is no \u201cNAV 2027\u201d release<\/h3>\n<p>The 2027 deadline refers to the end of extended support for the NAV 2017 product. It is not the name of an upcoming NAV release. Microsoft identifies NAV 2018 as the final version of Dynamics NAV in its <a href=\"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2026\/07\/28\/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers\/\" target=\"_blank\" rel=\"noopener\">July 2026 announcement<\/a>. Business Central is the successor platform.<\/p>\n<h2>2027: What happens when NAV 2017 support ends?<\/h2>\n<p>Microsoft lists January 12, 2027 as the end of extended support for <a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2017\" target=\"_blank\" rel=\"noopener\">Dynamics NAV 2017<\/a>. Under its <a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/policies\/fixed\" target=\"_blank\" rel=\"noopener\">Fixed Lifecycle Policy<\/a>, extended support ordinarily includes security updates and paid support for supported configurations. Those standard lifecycle benefits end when the product reaches its end-of-support date.<\/p>\n<h3>What Microsoft stops providing<\/h3>\n<p>The significant change is the loss of routine vendor security servicing and standard lifecycle support for NAV 2017. New features and design changes had already fallen outside extended support. A company running an older NAV environment also needs to consider the lifecycle of Windows Server, SQL Server, add-ons and other components; those products have their own dates.<\/p>\n<h3>What does not change<\/h3>\n<p>Your NAV installation is not remotely switched off on the deadline. Existing licenses and working business processes do not automatically disappear. Teams may still run financial close, purchase orders, fulfillment and reporting. Whether that remains a sensible operating position depends on controls, the environment, vendor commitments and how long the organization plans to remain on NAV.<\/p>\n<h3>Why some issues can still be resolved and others cannot<\/h3>\n<p>An experienced partner may be able to troubleshoot custom code, adjust reports, rebuild an interface or restore a damaged process. That is different from receiving a new Microsoft-issued security fix for an unsupported NAV product. Partner assistance can reduce certain risks, but it does not reset Microsoft\u2019s lifecycle or guarantee a remedy for a newly discovered product defect.<\/p>\n<h2>2028: NAV 2018 gives you more time, not a different outcome<\/h2>\n<p>NAV 2018 remains in extended support through <a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2018\" target=\"_blank\" rel=\"noopener\">January 12, 2028<\/a>. That additional year offers useful planning time, especially for organizations with multiple companies, specialized manufacturing workflows or hard-to-replace industry add-ons. It does not change the longer-term product direction.<\/p>\n<p>Businesses running several NAV versions should treat each environment separately. A corporate office on NAV 2018 does not make a plant still on NAV 2016 supported. Inventory the actual release used by each company, site and integration before assuming the newest instance sets the risk profile for the whole organization.<\/p>\n<h2>2031: The NAV licensing milestone is not a support extension<\/h2>\n<p>On July 28, 2026, <a href=\"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2026\/07\/28\/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers\/\" target=\"_blank\" rel=\"noopener\">Microsoft announced changes effective April 30, 2031<\/a> for Dynamics NAV customers. The announcement concerns service-plan coverage and licensing arrangements, not continued security servicing of NAV 2017 or NAV 2018.<\/p>\n<p>Microsoft states that, after April 30, 2031:<\/p>\n<ul>\n<li>Annual Enhancement Plan and Advantage Plan coverage ends.<\/li>\n<li>Customers can no longer purchase additional perpetual user licenses for existing NAV deployments.<\/li>\n<li>Dynamics NAV subscription licenses under the Solution Provider Agreement (SPA) can no longer be renewed.<\/li>\n<li>Subscription use of NAV under the Services Provider License Agreement (SPLA) is expected to end. Microsoft uses \u201cexpected\u201d for this point.<\/li>\n<\/ul>\n<table style=\"width: 100%; background-color: #f7f9fc; border: 1px solid #172b4d !important; border-collapse: collapse !important;\">\n<tbody>\n<tr>\n<td style=\"padding: 15px; border: 1px solid #172b4d !important;\"><span style=\"color: #172b4d; font-weight: 600;\"><strong>DO NOT CONFUSE THE DEADLINES<\/strong><\/span><\/p>\n<p>NAV 2017 and NAV 2018 still reach the end of Microsoft extended support in 2027 and 2028. The 2031 announcement does not supply extra years of product security updates.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>What the 2031 changes mean for growing businesses<\/h3>\n<p>A business that expects to add users, acquire another company or extend NAV into a new location should review its license model and service-plan arrangements well before 2031. An increase in headcount can become a procurement issue when additional perpetual users are no longer available. If the company relies on SPA subscriptions, renewal restrictions create a different planning concern.<\/p>\n<p>These changes do not establish a blanket rule that every NAV customer is unable to buy additional licenses today. Current eligibility and purchasing options depend on the agreement and should be checked with a Microsoft licensing partner. The precise 2031 restrictions are described in the Microsoft announcement linked above.<\/p>\n<div style=\"margin: 28px 0; padding: 18px 20px; border-left: 3px solid #4A90D9; background-color: #f7f9fc; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;\">\n<p style=\"margin: 0 0 10px 0; font-size: 12px; font-weight: bold; letter-spacing: 0.08em; text-transform: uppercase; color: #4a90d9;\">Also Read<\/p>\n<p><a style=\"display: block; text-decoration: none; color: #1a1a1a; font-size: 17px; font-weight: 500; line-height: 1.5; border-bottom: none;\" href=\"https:\/\/ngenioussolutions.com\/blog\/tally-to-dynamics-365-business-central\/\">Moving Beyond Tally with Dynamics 365 Business Central<\/a><\/p>\n<\/div>\n<h2>Running is not the same as supported: the real business risks<\/h2>\n<p>The consequences of unsupported ERP are rarely contained to IT. Finance depends on accurate postings and reports. Operations depends on inventory, shipping and purchasing. Audit teams need evidence that essential controls remain effective. A support deadline changes how those functions should assess their exposure.<\/p>\n<h3>Security and audit exposure<\/h3>\n<p>Without routine vendor security updates for the unsupported product, IT may need to rely more heavily on segmentation, access controls, monitoring, backups and incident response. Those measures can reduce exposure; they do not remove the underlying lifecycle gap. An auditor may also expect management to document why an unsupported application remains in use and how the associated risks are being managed.<\/p>\n<h3>Compliance and regulatory changes<\/h3>\n<p>Tax, reporting and recordkeeping requirements can change after the product stops receiving standard updates. A company may be able to implement a change through its own configuration, a partner or an add-on, but the responsibility for testing and maintaining that solution becomes more important. No support deadline by itself means a business is automatically noncompliant.<\/p>\n<h3>Integrations and third-party applications<\/h3>\n<p>NAV often connects to banks, warehouse systems, e-commerce platforms, EDI providers and reporting tools. A change in authentication, API behavior or a vendor connector can interrupt a process that worked for years. The risk grows when nobody owns the interface documentation or can reproduce a complete test in a nonproduction environment.<\/p>\n<h3>Skills <span style=\"font-size: 16px;\">and knowledge concentration<\/span><\/h3>\n<p>Older customizations may rely on a small group of developers or employees who understand the original design. If those people leave, a routine change can turn into a costly investigation. Documenting decision rules, custom objects and exception handling is therefore part of risk management, even if a migration is not immediate.<\/p>\n<h3>When remaining on NAV temporarily is reasonable<\/h3>\n<p>A temporary extension of the existing environment can be a defensible business decision when leadership has a dated transition plan, understands the risks, and funds compensating controls. A poorly scoped migration rushed into year-end close can cause its own disruptions. The right question is not whether a company can keep NAV running. It is how long it should, under what conditions, and with a clearly accountable owner.<\/p>\n<h2>Cannot migrate before January 2027? Build a bridge plan<\/h2>\n<p>For organizations beginning discovery in late 2026, a full migration before the NAV 2017 deadline may be unrealistic. A controlled bridge plan is more useful than an arbitrary cutover date. It should be owned jointly by IT and the business, with explicit checkpoints and an agreed exit date.<\/p>\n<ol>\n<li>Confirm the exposure. Record the NAV release, support status, databases, hosting environment, user counts, add-ons and interfaces. Separate production systems from nonproduction instances.<\/li>\n<li>Set a target window. Avoid choosing a go-live weekend before finance, operations and key vendors agree on testing, data reconciliation and blackout periods.<\/li>\n<li>Reduce risk while NAV remains in place. Review privileged access, network exposure, backup recovery tests, monitoring, third-party patching, change control and incident response. Have security leaders approve the controls.<\/li>\n<li>Reserve delivery capacity. Arrange partner discovery, internal process owners and key vendor commitments early enough to complete migration rehearsals and business acceptance testing.<\/li>\n<\/ol>\n<h3>Reduce exposure without claiming the system is fully protected<\/h3>\n<p>A documented isolation strategy, restricted administrator access and validated restores can reduce the likelihood or impact of some incidents. They do not restore Microsoft product support. Record the residual risks and reassess them if the bridge period extends.<\/p>\n<h3>Phase migration by business risk<\/h3>\n<p>A phased rollout can work when companies or sites can move without breaking intercompany posting, shared inventory or common reporting. In other cases, a coordinated cutover is safer. Map dependencies first, then choose the rollout model. \u201cPhased\u201d is not automatically lower risk.<\/p>\n<h2>Why a NAV migration starts with discovery<\/h2>\n<p>Microsoft\u2019s <a href=\"https:\/\/learn.microsoft.com\/en-us\/dynamics365\/business-central\/dev-itpro\/upgrade\/upgrade-paths\" target=\"_blank\" rel=\"noopener\">Business Central upgrade guidance<\/a> shows that many older NAV versions require intermediate upgrade steps and conversion of C\/AL customizations to AL. A direct jump from every legacy NAV installation to the latest Business Central release is not a safe assumption. For online migration, Microsoft also documents specific preparation and supported migration paths. <a href=\"https:\/\/learn.microsoft.com\/en-us\/dynamics365\/business-central\/dev-itpro\/administration\/migrate-nav\" target=\"_blank\" rel=\"noopener\">Review the NAV-to-cloud guidance<\/a> before setting the technical approach.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-14252\" src=\"https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-scaled.webp\" loading=\"lazy\" alt=\"Infographic outlining four key workstreams to assess before migrating from Microsoft Dynamics NAV: version and licensing, critical customizations, integrations and reporting, and data validation. Emphasizes completing discovery before setting the cutover date.\" width=\"2560\" height=\"1441\" srcset=\"https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-scaled.webp 2560w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-300x169.webp 300w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-1024x577.webp 1024w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-768x432.webp 768w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-1536x865.webp 1536w, https:\/\/ngenioussolutions.com\/blog\/wp-content\/uploads\/2026\/11\/Dynamics-NAV-End-of-Support-03-1-2048x1153.webp 2048w\" sizes=\"auto, (max-width: 2560px) 100vw, 2560px\" \/><\/p>\n<h3>Four questions to answer before you pick a migration date<\/h3>\n<ol>\n<li>Which NAV release and license model do we use? That establishes the actual support timeline and any contractual constraints.<\/li>\n<li>Which customizations are still essential? Identify custom code to retain, replace with standard functionality, rebuild as AL extensions or retire.<\/li>\n<li>Which integrations, reports and controls must survive? Account for banking, EDI, warehouses, reconciliations, approvals and external applications.<\/li>\n<li>What data should move, be cleaned or be archived? Decide historical scope with finance and records teams, then define how balances and transactions will be checked.<\/li>\n<\/ol>\n<p>The answers drive effort, test coverage, cutover sequencing and the amount of work that must happen before a project can be priced responsibly. NGenious documents this assessment approach in its <a href=\"https:\/\/ngenioussolutions.com\/services\/dynamics-nav-to-business-central-upgrade\/\">Dynamics NAV to Business Central upgrade services<\/a><\/p>\n<table style=\"width: 100%; background-color: #f7f9fc; border: 1px solid #172b4d !important; border-collapse: collapse !important;\">\n<tbody>\n<tr>\n<td style=\"width: 100%; padding: 15px; border: 1px solid #172b4d !important;\"><span style=\"color: #172b4d; font-weight: 600;\"><strong>PUT THE DECISIONS IN WRITING<\/strong><\/span><\/p>\n<p>Before the first scoping meeting, identify the NAV system owner, finance approver, key interface owners, target migration window, and who accepts the risks of the interim environment. Keep that record current as scope changes.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Your options: stay temporarily, upgrade or move to Business Central<\/h2>\n<p><a href=\"https:\/\/ngenioussolutions.com\/technologies\/dynamics-365-business-central\/\">Microsoft Dynamics 365 Business Central<\/a> is the successor to Dynamics NAV. The correct deployment model depends on regulatory requirements, integrations, internal capabilities and the economics of maintaining existing infrastructure.<\/p>\n<table>\n<thead>\n<tr style=\"background-color: #2d55a5; color: #ffffff; font-weight: 550 !important; line-height: 22px;\">\n<td width=\"326\"><strong>Option<\/strong><\/td>\n<td width=\"326\"><strong>Best fit and key tradeoff<\/strong><\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td width=\"208\">Keep NAV temporarily<\/td>\n<td width=\"439\">A controlled bridge for companies with a dated migration plan. Unsupported versions remain exposed to lifecycle risks.<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Upgrade to NAV 2018<\/td>\n<td width=\"439\">A narrow interim choice in unusual environments. It moves the NAV support deadline only to January 2028.<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Business Central on-premises<\/td>\n<td width=\"439\">Organizations with a substantiated on-premises requirement. Infrastructure and upgrade responsibilities remain.<\/td>\n<\/tr>\n<tr>\n<td width=\"208\">Business Central online<\/td>\n<td width=\"439\">Organizations seeking Microsoft-managed cloud operations, regular updates and a modern ERP platform; migration scope and customization fit still require assessment.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The on-premises upgrade route and cloud migration requirements vary by starting release. See Microsoft\u2019s <a href=\"https:\/\/learn.microsoft.com\/en-us\/dynamics365\/business-central\/dev-itpro\/upgrade\/upgrade-paths\" target=\"_blank\" rel=\"noopener\">supported upgrade paths<\/a> and <a href=\"https:\/\/learn.microsoft.com\/en-us\/dynamics365\/business-central\/dev-itpro\/administration\/migrate-nav\" target=\"_blank\" rel=\"noopener\">NAV-to-Business Central online migration guidance<\/a> for the current technical prerequisites.<\/p>\n<h3>Bridge to Cloud 3: an incentive worth checking<\/h3>\n<p>Microsoft\u2019s <a href=\"https:\/\/microsoftpartners.microsoft.com\/abs\/Blog\/?title=Partner+Alert%3A+Dynamics+365+Bridge+to+Cloud+3+%28BTC3%29+Promotion\" target=\"_blank\" rel=\"noopener\">Bridge to Cloud 3 partner announcement<\/a> describes a promotional offer for eligible on-premises Dynamics customers moving to specified three-year Dynamics 365 online subscriptions. It lists a 30% promotional discount, with an enrollment window from January 1, 2026 through December 31, 2027. Eligibility is restricted, including requirements tied to existing licenses and an active Enhancement Plan. Pricing, qualifying products and contract terms should be verified with the licensing partner before any business case assumes a discount.<\/p>\n<div style=\"margin: 28px 0; padding: 18px 20px; border-left: 3px solid #4A90D9; background-color: #f7f9fc; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;\">\n<p style=\"margin: 0 0 10px 0; font-size: 12px; font-weight: bold; letter-spacing: 0.08em; text-transform: uppercase; color: #4a90d9;\">Also Read<\/p>\n<p><a style=\"display: block; text-decoration: none; color: #1a1a1a; font-size: 17px; font-weight: 500; line-height: 1.5; border-bottom: none;\" href=\"https:\/\/ngenioussolutions.com\/blog\/microsoft-dynamics-365-business-central-pricing\/\">Microsoft Dynamics 365 Business Central Pricing 2026 (With Free Excel Calculator)<\/a><\/p>\n<\/div>\n<h2>What a NAV 2016 migration looked like for an auto-ancillary manufacturer<\/h2>\n<p>An auto-ancillary manufacturer running Microsoft Dynamics NAV 2016 faced challenges with legacy customizations, limited integrations, and reporting capabilities. As detailed in a <a id=\"menur5rc\" class=\"fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn\" title=\"https:\/\/ngenioussolutions.com\/resources\/case-studies\/nav-2016-to-business-central-migration-for-auto-ancillary-manufacturer\/\" href=\"https:\/\/ngenioussolutions.com\/resources\/case-studies\/nav-2016-to-business-central-migration-for-auto-ancillary-manufacturer\/\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\"Link published NGenious Solutions case study\">published NGenious Solutions case study<\/a>, the company migrated to Dynamics 365 Business Central with a focus on standardizing business processes, cleaning up data, and modernizing customizations.<\/p>\n<p>The case study reports improved visibility across finance and operations, along with a stronger foundation for future integrations.<\/p>\n<p>For businesses considering a similar transition, the key takeaway is that not every NAV customization needs to move to the new system. Assessing existing functionality, retiring redundant customizations, validating financial data, and testing critical workflows can help reduce unnecessary complexity and simplify ongoing maintenance.<\/p>\n<h2>Conclusion: do not just watch the deadline. Make a plan.<\/h2>\n<p>The Dynamics NAV end of support schedule creates different decisions for different customers. NAV 2017 has a 2027 technical-support deadline. NAV 2018 follows in 2028. The separate 2031 date affects service plans and licensing. None is a reason to approve a poorly scoped ERP project, and none should be ignored.<\/p>\n<p>Start with the real version in production, the systems connected to it, the business processes that cannot fail and the data that must be trusted after cutover. That gives IT and finance a practical basis for deciding whether to use a short bridge, move to Business Central on-premises or plan a migration to Business Central online.<\/p>\n<div style=\"margin: 25px 0 10px 0; padding: 25px 30px 12px; background: linear-gradient(115deg, #EEF4FC 0%, #E3EDFC 100%); border: 1px solid #C7D9F2; border-left: 5px solid #2D55A5; border-radius: 10px; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; box-shadow: 0 5px 18px rgba(45, 85, 165, 0.08);\">\n<p style=\"margin: 0 0 12px 0; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; font-size: 11px; font-weight: bold; letter-spacing: 0.12em; text-transform: uppercase; color: #2d55a5;\"><span style=\"background-color: #d5e4fc; padding: 6px 10px; border-radius: 4px;\">Free Consultation<\/span><\/p>\n<p style=\"margin: 0 0 12px 0; font-size: 23px; font-weight: bold; color: #172b4d; line-height: 1.4;\">Discuss Your NAV Roadmap With NGenious<\/p>\n<p style=\"margin: 0 0 24px 0; font-size: 15px; color: #45546a; line-height: 1.75;\">Book a free NAV-to-Business Central consultation to review your current environment, integration dependencies, migration options and next steps.<\/p>\n<p><a style=\"display: inline-block; font-size: 14px; font-weight: 600; color: #ffffff; background-color: #2d55a5; padding: 13px 23px; border-radius: 6px; text-decoration: none; box-shadow: 0 3px 8px rgba(45, 85, 165, 0.2);\" href=\"https:\/\/outlook.office.com\/book\/NGeniousSolutions1@ngenioussolutions.com\/?ismsaljsauthenabled\" target=\"_blank\" rel=\"noopener\"><span data-teams=\"true\">Book a Free NAV-to-Business Central Consultation<\/span> \u2192<\/a><\/p>\n<\/div>\n<h2>Frequently asked questions<\/h2>\n<h5>1. Will Dynamics NAV stop working when extended support ends?<\/h5>\n<p>No. End of support does not automatically deactivate an installed NAV environment. It ends Microsoft\u2019s applicable lifecycle support benefits for that version, including routine product security updates.<\/p>\n<h5>2. When does Dynamics NAV 2017 support end?<\/h5>\n<p>The <a href=\"https:\/\/learn.microsoft.com\/en-us\/lifecycle\/products\/dynamics-nav-2017\" target=\"_blank\" rel=\"noopener\">Microsoft US Lifecycle page<\/a> lists January 12, 2027 as the extended-support end date for Dynamics NAV 2017.<\/p>\n<h5>3. Does the April 2031 date extend NAV support?<\/h5>\n<p>No. Microsoft\u2019s <a href=\"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/business-leader\/2026\/07\/28\/explore-migration-options-for-microsoft-dynamics-nav-microsoft-dynamics-gp-and-microsoft-dynamics-sl-customers\/\" target=\"_blank\" rel=\"noopener\">April 2031 announcement<\/a> concerns service plans and specified licensing options. NAV 2017 and 2018 still reach their own support deadlines in 2027 and 2028.<\/p>\n<h5>4. Can we keep using NAV after end of support?<\/h5>\n<p>Yes, subject to your licenses and operating environment. Management should evaluate exposure, support options, legal obligations and a realistic transition plan instead of treating continued operation as proof of acceptable risk.<\/p>\n<h5>5. Can a partner support NAV after Microsoft ends support?<\/h5>\n<p>A partner may still provide operational assistance, troubleshooting and custom-development services. That does not restore Microsoft\u2019s standard lifecycle benefits or guarantee new vendor security fixes.<\/p>\n<h5>6. What is the upgrade path from Dynamics NAV?<\/h5>\n<p>Business Central is the successor. The technical sequence depends on the NAV version and destination. <a href=\"https:\/\/learn.microsoft.com\/en-us\/dynamics365\/business-central\/dev-itpro\/upgrade\/upgrade-paths\" target=\"_blank\" rel=\"noopener\">Microsoft\u2019s upgrade-path documentation<\/a> identifies intermediate steps for older releases, while its <a href=\"https:\/\/learn.microsoft.com\/en-us\/dynamics365\/business-central\/dev-itpro\/administration\/migrate-nav\" target=\"_blank\" rel=\"noopener\">cloud migration guidance<\/a> explains additional requirements for online deployment.<\/p>\n<h5>7. How long does a NAV-to-Business Central migration take?<\/h5>\n<p>There is no reliable standard duration. A small environment with limited customizations may be simpler than a multisite manufacturer with extensive C\/AL code, ISVs, EDI, historical data and round-the-clock operations. A defensible estimate follows a discovery assessment, test strategy and cutover plan.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Key Takeaways NAV 2017 and NAV 2018 reach end of extended support in 2027 and 2028, respectively. Microsoft\u2019s 2031 milestone affects NAV licensing and service&#8230;<\/p>\n","protected":false},"author":7,"featured_media":14253,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[208],"tags":[467],"class_list":["post-14248","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-central-blogs","tag-dynamics-nav-end-of-support"],"menu_order":0,"_links":{"self":[{"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/posts\/14248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=14248"}],"version-history":[{"count":11,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/posts\/14248\/revisions"}],"predecessor-version":[{"id":14262,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/posts\/14248\/revisions\/14262"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/media\/14253"}],"wp:attachment":[{"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=14248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=14248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ngenioussolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=14248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}