January 11, 2027 is circled on a lot of calendars right now. That's the day Microsoft ends extended support for Dynamics NAV 2017, and for organizations still running it, the date raises an obvious question. Does NAV stop working?
The short answer is no. Your users will still log in on January 12. Orders will still process and your financials will still post. But the support deadline does change something important, and it's worth understanding before you decide whether to stay on or start .
What Microsoft Stops Providing
After January 11, 2027, Microsoft will no longer deliver any of the following for NAV 2017.
- Security updates. Newly discovered vulnerabilities will not be patched, regardless of severity.
- Bug fixes. Known and future defects stay in the product as they are.
- Regulatory updates. Tax, reporting, and compliance changes won't be built in.
- Technical support. You won't be able to open a Microsoft support case for NAV 2017, even for a critical issue.
In other words, Microsoft stops maintaining the product altogether. Anything that needs fixing from that point on falls to your internal team or your , without Microsoft's engineering resources behind them.
Why Some Problems Become Unfixable
Here's the part that can get a little confusing, not every issue lives in the same layer of NAV.
Problems in the application layer, like a report calculation, a posting routine, or a custom workflow, can usually still be fixed after support ends. The code is accessible, and an
Problems in the platform layer are different. Microsoft builds and compiles that layer, and only Microsoft can change it. Think about a NAV system that connects to a payment processor, a tax engine, or a shipping carrier. Those services update their security protocols and APIs on their own schedule. If a connection breaks because of an outdated authentication method in the NAV client or service tier, a partner could once escalate that to Microsoft. After January 11, there's no one to escalate to. A partner can build workarounds around the edges, but can't modify the compiled components where the real problem sits.
That's the distinction that matters most. A bug in your customizations is usually still fixable. A bug in the platform is not.
What Keeps Working
The support deadline doesn't touch day-to-day operations. After January 11, users can still sign in, sales and purchase orders keep flowing, general ledger entries and financial statements work, and your SQL database keeps storing and serving data like it always has. Your C/AL customizations and custom reports also stay exactly where they are, though maintaining them long term is easier with dedicated .
This is why many companies will keep running NAV 2017 well past 2027. The software doesn't expire. What fades is the protection layer that keeps it secure, compliant, and compatible.
Six Risks That Grow Over Time
Some things you need to look out for as your NAV system ages past the extended support deadline:
Security. Unpatched vulnerabilities stay open indefinitely, and that risk compounds for any system holding financial data. Organizations in this position often lean on and a strong plan to offset the gap.
Compatibility. Future versions of Windows, SQL Server, Office, and browsers have no obligation to support NAV 2017. These gaps tend to appear gradually, which makes them easy to underestimate.
Third-party software. ISVs will continue dropping support for older NAV versions, making integrations harder to build or maintain.
Compliance. Tax, payroll, and localization rules keep changing. Without regulatory updates, keeping up becomes a manual effort, if it can be done at all.
Expertise. The pool of developers who know NAV well is shrinking, and so is the number of partners willing to support it.
Licensing. New NAV licenses are no longer sold. If you need to add users as you grow, that's a constraint you face today.
When Staying Put Is a Reasonable Choice
None of this means everyone needs to migrate right away. Staying on NAV 2017 past January 2027 can be a sound decision if your environment is stable with no major changes coming, the system has little or no internet exposure, your growth and complexity are holding steady, a sale or retirement of the business is planned, or a migration is already scheduled and you're bridging the gap on purpose.
The key is making it a deliberate decision rather than a default. Planning ahead also keeps you out of the worst-case scenario, which is being forced into a rushed migration on short notice.
Signs You've Outgrown NAV
The clearest signal is a gap between what your business needs and what NAV 2017 was designed to do. A few common drivers stand out.
You want AI and automation. AI-assisted forecasting, anomaly detection, reduced manual data entry, and are built into Business Central. Retrofitting them onto NAV isn't realistic.
Your reporting has hit a ceiling. If your team exports data to spreadsheets just to answer everyday questions, the reporting gap is costing you time every day.
You need cloud integrations. Connecting NAV's on-premises architecture to e-commerce, payment, shipping, or CRM platforms turns every integration into a custom project.
Your team works remotely. NAV 2017 wasn't built for checking inventory or approving orders from a phone or tablet.
Security expectations keep rising. Cyber insurance requirements and customer expectations are harder to meet on a platform that no longer gets security updates.
You want to retire on-premises hardware. Moving to the cloud shifts server costs and IT overhead to the vendor, often at a lower total cost.
If two or three of these sound familiar, the conversation has likely shifted from whether to move to when and how.
Your Options at a Glance
| Option | Best For |
|---|---|
| Stay on NAV temporarily | A short-term bridge |
| Upgrade to NAV 2018 | Rare cases, generally not recommended |
| Business Central on-premises | Organizations that need local deployment |
| Business Central online | Most organizations |
The right choice depends on where your business is headed, not just where it stands today. Tigunia's overview of covers the trade-offs between cloud and on-premises in more depth.
The Bottom Line
Running NAV 2017 after January 11, 2027 is possible, and plenty of organizations will do it. The more useful question is whether running unsupported software fits your security requirements, growth plans, and long-term technology strategy. Having a clear plan matters far more than reacting to a date on Microsoft's lifecycle calendar.
If you'd like help assessing where your NAV system stands and which path makes sense, the team at works with NAV customers on everything from short-term support to a full .
This article is adapted from Tigunia's original post,