Skip to content
Bitta Apps
Implementation & migration

NAV 2017 End of Support: Moving to Business Central Online

Extended support for Dynamics NAV 2017 ends on 2027-01-11. Here are the dates for NAV 2009 through NAV 2018, Microsoft's upgrade path to Business Central online and what to do when the deadline is close.

Business Central Extension Management showing Microsoft's Business Central Cloud Migration extensions, beside the headline NAV 2017: January 2027 deadline
On this page

NAV 2017 end of support is 2027-01-11. On that date Dynamics NAV 2017 leaves extended support under Microsoft's Fixed Lifecycle Policy. After it, Microsoft provides no security updates and no assisted support for NAV 2017, and no Extended Security Update program is listed for NAV. A company still on NAV 2017 should confirm its version, inventory its customizations and commit to a route to Business Central online.

This article is for finance, operations and IT leaders at companies still running Dynamics NAV 2017, NAV 2018 or an older release. It covers the support dates for NAV 2009 through NAV 2018, what changes when support ends, Microsoft's upgrade path to Business Central online, what happens to C/AL customizations, and how to plan when the deadline is closer than the project. Sources were checked on 2026-11-04.

Still on NAV 2017? Support ends 2027-01-11. Book a free discovery call to agree practical next steps, or use the short form on the Business Central partner page. Prefer to talk now: (626) 766-9732.

Dynamics NAV end of life: support dates by version

Each NAV release has its own page in the Microsoft Lifecycle product search, and every one follows the Fixed Lifecycle Policy. Dates are as shown on each page, in Pacific Time.

Version

Mainstream support ended

Extended support ends

Status on 2026-11-20

Dynamics NAV 2018

2023-01-10

2028-01-11

Extended support

Dynamics NAV 2017

2022-01-11

2027-01-11

Extended support, ends in 52 days

Dynamics NAV 2016

2021-04-13

2026-04-14

Out of support

Dynamics NAV 2015

2020-01-14

2025-01-14

Out of support

Dynamics NAV 2013 R2

2018-01-09

2023-01-10

Out of support

Dynamics NAV 2013

2018-01-09

2023-01-10

Out of support

Dynamics NAV 2009

2015-01-13

2020-01-14

Out of support

On the Dynamics NAV 2018 end of support question, the answer is 2028-01-11. NAV 2018 has one more year than NAV 2017, but its route to the cloud is the same. NAV 2016 and every older release are already past the end of extended support.

What changes after 2027-01-11

The Fixed Lifecycle Policy splits support into two phases. Mainstream support includes security updates, non-security updates and incident support. Extended support keeps free security updates and paid support, but drops non-security updates and design changes.

For NAV 2017, that second phase is already in effect. Non-security updates stopped when mainstream support ended on 2022-01-11. What remains until January is security updates and paid support.

The Fixed Policy FAQ states that after extended support ends, unless an Extended Security Update program exists, customers lose access to:

  • Security updates

  • Free or paid assisted support options

  • Microsoft product development resources

  • Updates to online content such as Knowledge Base articles

Dynamics NAV is not on the product list in Microsoft's Extended Security Updates FAQ. Self-help content stays available for at least 12 months after end of support, according to the policy page.

The real risk is not that the system stops on 2027-01-11. The lifecycle policy describes what Microsoft stops providing, not the disabling of installed software. The risk is that the system holding the general ledger, receivables and inventory runs with no new security fixes and no Microsoft escalation path when something breaks.

The NAV to Business Central upgrade path

No NAV version migrates straight to Business Central online. Microsoft's Migrate Dynamics NAV to Business Central online article states that NAV versions before version 14 can't migrate directly to the cloud, so every route starts with an upgrade to Business Central on-premises.

Starting version

Route Microsoft documents

NAV 2015, 2016, 2017 or 2018

Business Central 14 on-premises, then Business Central on-premises version 25 or later, then Business Central online

NAV 2013 or 2013 R2

NAV 2018, then version 14, then version 25 or later, then online

NAV 2009 SP1 or 2009 R2

NAV 2013 or 2015, then NAV 2018, then version 14, then version 25 or later, then online

The supported upgrade paths page shows the same chain for the current release. To reach Business Central 2026 release wave 2 (version 29) on-premises from NAV 2017, the path is version 14, then version 25, then version 29, and it requires converting the application from C/AL to AL. Microsoft also states that new customers can't use version 14 in production, only as a path for upgrading to the latest version, and that since version 26 a direct upgrade from version 14 to the latest release isn't supported, which is why version 25 sits in the middle.

At a level a finance or operations leader can follow, the full migration runs in these steps:

  1. Prepare. Inventory customizations, add-ons and integrations. Clean and archive data. Confirm the SQL Server version and a database compatibility level of 130 or higher. Decide which companies move together.

  2. Upgrade to Business Central 14 on-premises. Microsoft requires this step for both the full migration and the reimplementation path. NAV 2013 and NAV 2009 databases reach it through NAV 2018 first.

  3. Convert C/AL customizations to AL extensions (full migration). Developers export the C/AL objects, generate initial AL files with the Txt2Al tool from version 14, and finish the code in Visual Studio Code with the AL Language extension.

  4. Upgrade on-premises to version 25 or later (full migration). The cloud migration prerequisites require the source to run Business Central 25.0 or later, on SQL Server 2016 SP1 or later.

  5. Set up cloud migration. An assisted setup in Business Central online connects to the on-premises database through Azure Data Factory, using a self-hosted Integration Runtime for a SQL Server database.

  6. Replicate, upgrade data and complete. Data replicates table by table, and later runs move only changes. A data upgrade follows, then completion makes the online environment the primary system.

  7. Follow up. Set up users and permissions, reconnect integrations and monitor the environment.

The on-premises to online migration overview adds three facts for the budget. The on-premises system stays the operative environment until migration is complete. Users, permissions, most system tables and record links don't migrate. Once the data upgrade runs, replication can't be run again from the earlier version. Microsoft recommends at least one full dry run in a sandbox before production cutover. Our sandbox vs production guide covers keeping that rehearsal away from live data.

The reimplementation alternative

Microsoft also documents a Business Central 14 reimplementation tool. After reaching version 14, it moves master data, open sales and purchase orders, opening balances, setup and a defined subset of posted history to the cloud without the climb to version 25. Legacy C/AL customizations and their data are not migrated. Microsoft labels the tool a preview feature and states that preview features aren't meant for production use, so confirm its status at project start.

After go-live

Business Central online gets two major updates a year, in April and October, and minor updates in the other months. Each major update has a five-month update period. Converted extensions need to stay compatible with each release, because during the enforced update period Microsoft might uninstall an extension that blocks the update. Our article on AL extension upgrade strategies explains how to ship new versions of those extensions without losing their data.

What happens to your NAV customizations

Business Central online runs extensions only. The customization migration guide states that all C/AL customization code must be rewritten as AL extensions before migration. Data from tables with code customizations can't be carried forward unless an extension installed both on-premises and online handles it.

The guide maps each NAV object type to an AL approach. Table changes become table extensions or new AL tables. Modified codeunits are refactored to subscribe to events. Reports are rebuilt as AL reports or report extensions. .NET add-ins need a redesign, because .NET interop isn't available in Business Central online. The upgrade considerations page adds that Codeunit 1 is retired, V1 extensions must be converted, and MenuSuite no longer controls search.

Not every customization deserves a rebuild. Some are covered by standard features or a Microsoft Marketplace (formerly AppSource) app, and some are no longer used. Our guide to migrating NAV customizations to Business Central online sets out a retire, adopt, replace, rebuild or defer decision for each item. The companion article on Business Central customization technical debt covers how to keep the rebuilt set small.

Planning when the deadline is close

From 2026-11-20 to 2027-01-11 is 52 days. Bitta Apps' implementation page gives a typical range of 8 to 16 weeks from discovery to go-live for an implementation, depending on scope, and states that complex projects need a tailored schedule. A full NAV migration adds upgrade and code conversion steps on top. For a NAV 2017 company that has not started, a cloud go-live before 2027-01-11 is not a realistic target. A committed plan is.

What can realistically be done before 2027-01-11:

  • Confirm the exact NAV version, build and SQL Server version, and check the SQL Server and Windows Server lifecycle dates in the same product search.

  • Build the customization and integration inventory, with an owner for each item.

  • Plan the full migration as the production route. Microsoft labels the BC14 reimplementation tool a preview feature and states that preview features aren't meant for production use, so evaluate it as an option, not as an equal alternative. Record which history the business needs online.

  • Start data cleanup and archiving, which shortens every later replication run.

  • Set up the Business Central online tenant and a sandbox for rehearsals.

  • Get a written scope, a fixed price and a cutover date.

If the migration lands after the date, run NAV 2017 as a system with a fixed end. Stop new C/AL development: Microsoft's customization guide says to stop C/AL development before the final cutover and do all new work in AL extensions. Keep backups and access controls current, and limit who can reach the server. Plan the cloud migration to run between environment updates, as Microsoft's migration overview recommends. Some companies weigh a move to NAV 2018 to gain a year. Microsoft's route for NAV 2015 to 2018 goes straight to version 14, so that detour adds a project without shortening the path to the cloud.

How Bitta Apps helps

Bitta Apps is a Microsoft Dynamics 365 Business Central partner and Microsoft Cloud Solution Provider. The Business Central migration readiness page lists the inventory to prepare, and a consultant replies within one business day. The Migration Readiness Assessment is a fixed-fee engagement, published at $7,500 over 7 business days. It covers a current-state review of NAV data and processes, a data-migration map of what migrates, what archives and what gets rebuilt, and a fixed-price migration proposal.

For the project itself, Business Central implementation engagements have a named engagement lead, project manager and QA. A written fixed-price proposal arrives before any build work begins, and go-live is followed by a 30-day hypercare window. AL development covers C/AL to AL conversion and version-to-version upgrades with regression test plans. Companies comparing partners can read our guide on how to choose a Business Central implementation partner, and those also running Dynamics GP can read the Dynamics GP end of support guide.

The date is fixed and the route is documented. What remains open is how much of the old system the business carries forward. A company that inventories its customizations and data in the next few weeks reaches January with a plan instead of a gap. The readiness page is the place to start.

Next step. Book a free discovery call with your NAV version and customization list to agree practical next steps for the route. The Business Central partner page has a short form, or call (626) 766-9732.

FAQ

Frequently asked questions

When does NAV 2017 support end?

Extended support for Dynamics NAV 2017 ends on 2027-01-11, according to its Microsoft Lifecycle page. Mainstream support already ended on 2022-01-11, so NAV 2017 currently receives security updates and paid support only. After 2027-01-11, with no Extended Security Update program listed for NAV, Microsoft provides neither.

Can I upgrade NAV 2017 directly to Business Central online?

No. Microsoft states that Dynamics NAV versions before version 14 can't migrate directly to the cloud. NAV 2017 first upgrades to Business Central 14 on-premises, then for a full migration to Business Central on-premises version 25 or later, and then runs the cloud migration tool to Business Central online.

What happens to my NAV customizations?

Business Central online runs extensions only, so every C/AL customization you keep must be rewritten as an AL extension. Data in tables with code customizations can't be carried forward unless an extension installed both on-premises and online handles it. Many customizations can be retired or replaced by standard features or Microsoft Marketplace apps instead of rebuilt.

Is NAV 2018 still supported?

Yes, until 2028-01-11. Dynamics NAV 2018 left mainstream support on 2023-01-10 and is now in extended support, which means security updates and paid support only. Its route to Business Central online is the same as the NAV 2017 route, through Business Central 14 on-premises.

Can I keep running NAV after support ends?

Microsoft's lifecycle policy describes the support it stops providing, not a shutdown of installed software. After the end of extended support, with no Extended Security Update program listed for NAV, there are no security updates and no free or paid assisted support from Microsoft. Running NAV past that date means carrying that risk in the system that holds your financial records.

Which Dynamics NAV versions are already end of life?

Dynamics NAV 2009, 2013, 2013 R2, 2015 and 2016 are all past the end of extended support, with NAV 2016 the most recent on 2026-04-14. NAV 2017 follows on 2027-01-11 and NAV 2018 on 2028-01-11. NAV 2015 and 2016 upgrade directly to Business Central 14 on-premises, NAV 2013 and 2013 R2 go through NAV 2018 first, and NAV 2009 SP1 and R2 go through NAV 2013 or 2015 and then NAV 2018.

Sources

Claims in this article were checked against the following on Nov 11, 2026.

  1. learn.microsoft.com/en-us/lifecycle/products/
  2. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2017
  3. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2018
  4. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2016
  5. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2015
  6. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2013-r2
  7. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2013
  8. learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2009
  9. learn.microsoft.com/en-us/lifecycle/policies/fixed
  10. learn.microsoft.com/en-us/lifecycle/faq/fixed-policy
  11. learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates
  12. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-nav
  13. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths
  14. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-nav-customization-playbook
  15. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations
  16. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-prerequisites
  17. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-business-central-on-premises
  18. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-bc14-reimplementation
  19. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/update-rollout-timeline
  20. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-data

Written by

Mohammad Nour Itani

Founder & Senior Business Central Developer

Related services

Work with Bitta Apps on this

Next step

Talk to a senior Business Central consultant, not a sales rep.

Fixed-price proposal in writing within five business days of discovery.