Dynamics NAV 2017 support ends January 11, 2027: what it means and what to do now

If your company runs on Dynamics NAV 2017, Microsoft stops shipping security updates for it on January 11, 2027. That's about eight weeks away. Your system won't switch off that day, and nobody from Microsoft will call. That's exactly why so many companies let the date pass and then find out what "unsupported" means at the worst possible moment.

Here's a plain view of what changes, what doesn't, and what a sensible next 60 days looks like.

What actually changes on January 11

NAV 2017 left mainstream support in January 2022. Since then it has been in extended support, which under Microsoft's Fixed Lifecycle Policy means security updates only. No bug fixes and no design changes. When extended support ends, the security updates stop too.

In practice:

  • No more security patches. Any vulnerability found after January 11 stays open for good.
  • Your infrastructure falls further behind. NAV 2017 was built for the Windows Server, SQL Server and Office versions of its time. Each upgrade to those becomes a compatibility question nobody can promise to answer.
  • Auditors and insurers start asking. Running core finance on software the vendor no longer patches is the kind of thing that shows up in audit findings and cyber insurance questionnaires.
  • Fewer people can help you. The number of consultants and developers who still work in C/AL and the NAV 2017 client shrinks every year.

What doesn't change: your data, your customizations and your daily operations all keep working. NAV doesn't stop on January 12. The risk builds up quietly over time.

Where the other NAV versions stand

VersionExtended support ends
NAV 2016Already ended (April 14, 2026)
NAV 2017January 11, 2027
NAV 2018January 11, 2028

If you're on NAV 2016 or earlier, you're already past the deadline. If you're on NAV 2018, you have one more year. That is less time than it sounds for a heavily customized system, because the work is in the customizations, not the date. (Dates from Microsoft's lifecycle pages.)

Business Central works differently. It follows Microsoft's Modern Lifecycle Policy: it is updated continuously, and as long as you stay current there's no end-of-support cliff like this one.

The honest answer: you don't have to be live by January 11

A rushed upgrade is riskier than a few months of running unsupported with sensible precautions. If you're not already in an upgrade project, the goal for January isn't go-live. It's knowing exactly where you stand and having a plan your CFO has signed off on.

Some companies can stay on NAV a little longer without much risk: a closed network, few external connections, solid backups, and a clear upgrade date in the next 6–12 months. Others shouldn't: anything exposed to the internet, web services talking to outside systems, or a server that's already overdue for replacement.

A realistic 60-day plan

Weeks 1–2: Take inventory. List every customization, add-on and integration. Most NAV 2017 systems have more than anyone remembers. Note who wrote each one and whether that person or partner can still be reached. Check the versions of Windows Server and SQL Server under NAV.

Weeks 2–4: Sort the customizations. This is where upgrades are won or lost. Each customization falls into one of three groups:

  1. Now standard in Business Central. Retire it. Many NAV-era changes, such as approvals, some reporting and bank reconciliation tweaks, are now built in.
  2. Still needed. Rebuild it as a Business Central extension in AL, written so it survives Business Central's regular updates.
  3. No longer used. More common than you'd think. Drop it.

Weeks 4–6: Decide on the approach. Upgrade with history, or reimplement with opening balances and a clean start? Neither is always right. A lightly customized system with clean data often upgrades well. A system with 15 years of workarounds may be cheaper and safer to reimplement. Make the decision with real numbers, not a sales slide.

Weeks 6–8: Reduce the exposure while you wait. Confirm backups and restore tests, restrict network access to the NAV server, and document a timeline. That way the gap between end of support and go-live is short, deliberate and defensible to your auditors.

What tends to go wrong

A 120-user distributor on NAV 2017 assumed their upgrade was "mostly data." The inventory turned up 340 modified objects, two add-ons from vendors that no longer existed, and an EDI integration built by a contractor who had retired. Half the customizations turned out to be standard in Business Central. Sorting them first cut the estimated development work by about 40 percent and kept the go-live date realistic.

The pattern is common: the date gets the attention, while the customizations decide the cost and the risk. For the broader picture across all NAV versions, see Dynamics NAV end of support: what it means and what to do next.

On NAV 2017 or 2018 without a plan?

Start with an upgrade readiness assessment: a focused review of your customizations, add-ons, integrations and data, ending in a written plan with options and a realistic estimate. See how Cateran approaches NAV to Business Central upgrades.