Still running Dynamics NAV 2017 and wondering what happens when Microsoft stops supporting it?
While Microsoft ends extended support for Dynamics NAV 2017 on January 11, 2027, your ERP won’t stop working that day.
Your software won’t suddenly shut down. Your users won’t be locked out. Your data won’t disappear. For many organizations, NAV 2017 will keep running the exact same way it has for years.
But that also doesn’t mean the date is irrelevant. Microsoft’s support deadline changes what happens behind the scenes, even when nothing seems to be changing on the surface. Understanding those changes is critical when deciding whether to stay on NAV or begin planning your next ERP move to its successor, Microsoft Dynamics 365 Business Central.
What Happens to Dynamics NAV on January 11?
Starting January 11, 2027, Microsoft will no longer provide the following items for Dynamics NAV 2017:
- Security updates: Patches will not be available for vulnerabilities discovered within the NAV 2017 system, no matter how serious.
- Bug fixes: Any defect in the software, known or newly discovered, stays as is.
- Regulatory updates: Changes to tax rules, reporting requirements, or other compliance-driven updates won’t be built into the product.
- Technical support: You can no longer open a support case with Microsoft for a NAV 2017 issue, even a critical one.
Essentially, your NAV system itself keeps operating as it did the day before, only now you’re on your own. There’s no technical support available from the publisher. Ever.
It’s also worth being clear about what “no technical support” means in practice. It doesn’t just mean losing access to a help desk. It means Microsoft stops maintaining the product entirely from this point forward. Any troubleshooting, workaround, or fix becomes something your internal team or an implementation partner must address, without Microsoft’s engineering resources behind it.
As NAV developers ourselves, we find that a majority of the issues or adaptations companies need while continuing to use a legacy ERP can be addresses. However, it also helps to understand why an internal team or partner cannot always fill any gaps you may encounter. That’s because not every fix lives at the same level of the system.
Some problems sit in the application layer. These are things like a report calculation, a posting routine, or a custom workflow. These are also the issues a skilled partner can usually still patch because the code is available to change.
Other problems sit deeper, in the platform layer that Microsoft built and compiles. A common example is a NAV system that connects to an outside service such as a payment processor, a tax calculation engine, or a shipping carrier. These outside services update their own security protocols and APIs on their own schedule, regardless of what happens to NAV.
Before January 11, if that connection broke because of something like an outdated authentication method built into the NAV client or service tier, a partner could ask Microsoft to address it. After that date, now there is no one left to ask. A partner can still write code around the edges, but they cannot open up and modify the compiled platform components where the actual problem lives.
This is the distinction worth sitting with. A bug in your customizations is usually still fixable after January 11. A bug in the platform itself is not, no matter how skilled your internal team or implementation partner is.
What Doesn’t Change on January 11?
The list above covers what goes away. Here’s what keeps running exactly as it always has for Dynamics NAV 2017 after January:
- Users can still log in. Nothing about the support deadline touches authentication or access. Your team opens NAV the same way on January 12 as they did the day before.
- Orders are still processed. Sales orders, purchase orders, and everything tied to them continue to flow through the system without interruption.
- Financials still post. General ledger entries, journals, and financial statements keep working exactly as designed. Microsoft’s support calendar has no bearing on your books.
- Your SQL database keeps working. The database engine underneath NAV doesn’t know or care what Microsoft’s lifecycle page says. It keeps storing and serving data the same way it always has.
- Your customizations don’t disappear. Any C/AL code, custom reports, or modifications you’ve built over the years remain exactly where they are. Nothing gets wiped or disabled (though maintaining them long-term is easier with dedicated custom development support).
The list above is why many organizations will continue to run NAV 2017 well past its support date. The software itself doesn’t degrade or expire. What changes is everything working behind the scenes to keep it secure, compliant, and compatible going forward, and that’s the piece worth planning around even though nothing dramatic happens on day one.
The Risks of Staying on NAV 2017 after 2027
Losing support doesn’t mean losing your system. As we’ve mentioned though, it means losing the layer that protects it. And that’s important to understand. Here’s where that shows up:
1.Security
No new patches means any vulnerability discovered after January 2027 stays open indefinitely. Cyber risk doesn’t stay flat over time. It compounds, especially for systems holding financial data. Organizations in this position often turn to dedicated IT security services to offset the gap Microsoft’s updates used to cover, along with a solid data backup and disaster recovery plan in case something does go wrong.
2.Compatibility
NAV 2017 was built to work with the technology of its era. Future versions of Windows, SQL Server, Office integrations, and web browsers aren’t obligated to keep compatibility with it. Compatibility gaps tend to show up gradually, not all at once, which can make them easy to underestimate.
3.Third-Party Software
Independent software vendors (ISVs) eventually stop supporting older NAV versions too, if they haven’t already. When that happens, new integrations get harder to build, and existing ones get harder to maintain.
4.Compliance
Industry-specific requirements, tax updates, and payroll or localization rules change constantly. Once Microsoft stops issuing regulatory updates, staying compliant becomes your problem to solve manually, if it can be solved at all.
5.System Knowledge
Developers who know NAV well are a shrinking pool. As the platform ages further, finding resources who can effectively troubleshoot or extend it becomes a risk in itself. This is one of the reasons organizations still running NAV often lean on a partner with dedicated Dynamics NAV services to fill the gap, and that pool of partners willing to offer this kind of support will only keep shrinking as more of the industry moves on. Investing in ongoing training and support also helps keep that knowledge from walking out the door.
6.Licensing
This one’s already true today, but it’s worth a reminder that you can no longer buy new NAV licenses. You can only use the ones you have. If your business grows and you need to add users, that’s a real constraint, not a future one.
When Staying on NAV 2017 Might Make Sense
If everything up to this point has felt a little daunting, that’s not the intent. None of this is meant to push you toward a migration you don’t need yet. The goal is simply to lay out what’s true, so you can decide from a place of clarity instead of guesswork. It’s also intended to provide you important information that avoids putting you in the worse case scenario of being forced to migrate your NAV system on short notice.
There are legitimate reasons to delay a software move, and pretending otherwise doesn’t help anyone make a good decision. Staying on NAV 2017 past January 11, 2027, can make sense if:
- Your environment is stable, with no internal change expected.
- The system has no meaningful internet exposure.
- Your operations, growth, and complexity aren’t projected to change.
- You have a planned retirement or sale of the business.
- A software migration is already scheduled, and you’re bridging the gap intentionally.
None of these are excuses. They’re valid business reasons, as long as they’re a decision and not a default.
When It’s Time to Move Off NAV
It’s time to move off NAV 2017 when your business needs have outgrown what the platform can do. The clearest sign is a mismatch between what your organization needs to operate effectively vs. what NAV 2017 was ever designed to deliver.
Today’s business environments tend to move much faster than the one NAV 2017 was built for. Customers expect real-time answers. Competitors are automating processes that used to take a full team. Employees expect to work from anywhere, on any device, without waiting for a desktop connection. Meeting those demands takes a platform that was designed for them, not one that predates them.
If some of this already sounds familiar, our blog on 6 signs your business technology is failing you covers the broader warning signs in more detail.
Against that backdrop, certain business drivers make continuing on NAV increasingly harder to justify. These include:
You need AI-driven tools or automation.
AI is no longer a future consideration for most businesses. It’s a current one. NAV 2017 wasn’t built with modern AI capabilities in mind and retrofitting them onto a legacy platform isn’t realistic. If any of the following sound familiar, that’s a sign your ERP needs to catch up:
- You want AI-assisted demand forecasting instead of manual spreadsheet models.
- You’re looking for automated anomaly detection in financial or inventory data.
- You want to reduce manual data entry through intelligent automation.
- You’d like to leverage agentic ERP and integrated agents to execute multi-step tasks.
Platforms like Business Central are built to support these capabilities natively. NAV 2017 simply wasn’t.
Your Reporting Needs Have Outgrown NAV
As businesses grow, so does the demand for real-time visibility. NAV’s reporting tools were designed for a prior era of business intelligence, one built around static reports rather than live dashboards. If your team is exporting data to spreadsheets just to get the answers NAV can’t provide directly, that’s a clear signal the reporting gap has become a daily tax on productivity. Modern business intelligence solutions close that gap by connecting your data to reporting tools built for how businesses need to make decisions today. For a closer look at what’s included, our guide to Business Central modules breaks down each one.
You Want Cloud Integrations that NAV Wasn’t Built For
Modern operations increasingly depend on connecting to cloud services, whether that’s e-commerce platforms, payment processors, shipping providers, a CRM system, or other SaaS tools. NAV 2017’s on-premises architecture makes those integrations harder to build and more expensive to maintain. Every new connection becomes a custom project instead of a standard configuration, if it can be done at all.
Your Workforce is Mobile and Needs Data Access NAV Doesn’t Easily Support
Remote and hybrid work aren’t temporary trends. If your team needs to check inventory, approve orders, or pull reports from a phone or tablet while offsite, NAV 2017 wasn’t designed for that kind of access. Employees end up waiting until they’re back at a desktop to get basic answers, which slows decisions down at exactly the moments speed matters most.
Modern Security Requirements Have Gotten Stricter
Customer expectations, cyber insurance requirements, and industry regulation have all raised the bar on data security in recent years. A platform that no longer receives security updates makes it harder to meet standards that keep climbing. This is one of the clearest cases where the business driver and the support deadline point in the same direction.
You Want to Lower Infrastructure Costs by Moving Off On-premise Hardware
Maintaining your own servers means ongoing hardware costs, IT overhead, and capacity planning that scales with your business. Moving to a cloud-based platform shifts much of that burden to your vendor, often at a lower total cost than maintaining equivalent infrastructure in-house.
If two or three of these sound like your organization, that’s usually a sign the conversation should shift from “should we move” to “when and how.”
Your ERP Upgrade Options
| Option | Best For |
| Stay on NAV temporarily | Short-term bridge |
| Upgrade to NAV 2018 | Rare situations, not recommended |
| Business Central on-premises | Organizations needing local deployment |
| Business Central online | Most organizations |
No option here is inherently right or wrong. The right one depends on where your business is headed, not just where it is today. If you’re weighing the differences between on-premise and cloud deployments more closely, our breakdown of Business Central hosting options walks through the trade-offs in more detail. And whichever direction you’re leaning, our NAV to Business Central upgrade services page covers what the process looks like. If an on-premises deployment is the better fit for your business, our hosting solutions cover that path as well.
Thinking About Migrating Off Legacy Software?
Migration doesn’t have to mean starting from scratch or losing what already works. Get answers to the 4 most common concerns about legacy migration, see the hidden costs of staying put, and walk through the key advantages and planning steps for a smooth transition to modern ERP.
Learn More
That last one tends to be the most revealing.
NAV 2017 After 2027: What to Do Next
Running NAV 2017 after January 11, 2027 isn’t impossible. Many organizations will continue doing exactly that.
The more important question is whether continuing to run unsupported software aligns with your business goals, security requirements, and long-term technology strategy. Should you stay on NAV 2017 or move to Business Central? The answer depends less on the calendar and more on where your business is headed.
Understanding the risks and having a plan is far more important than reacting to a date on Microsoft’s support calendar.
The good news is that evaluating whether to stay on NAV 2017 or move forward isn’t a decision you have to make alone. Tigunia can help you assess where your current system stands, what risks matter most for your business, and which upgrade path fits your goals, whether that’s Business Central online, an on-premises deployment, or a temporary bridge while you plan your next move. If you’re also weighing which implementation partner is the right fit, our guide on how to choose a Business Central partner is a good next stop.
If you’re ready to talk through your options, we’re here to help you figure out what makes sense for where your business is going.
NAV 2017 Microsoft Support End Frequently Asked Questions
Will Dynamics NAV 2017 stop working on January 11, 2027?
No. Your software keeps running the same way it did the day before. What changes is that Microsoft no longer provides security patches, bug fixes, regulatory updates, or technical support for the product.
Can I still get help if something breaks in NAV 2017 after January 2027?
It depends on where the problem lives. Issues in your customizations, such as a report or a workflow, can often still be fixed by a skilled partner. Issues built into the compiled platform itself no longer have anyone to ask, since Microsoft stops maintaining that layer entirely.
Is it against my license to keep using NAV 2017 past the support date?
No. Losing support doesn’t mean losing your right to use the software. You can keep running NAV 2017 as long as it meets your needs, though you won’t be able to purchase new licenses.
How do I know if I should stay on NAV or move to Business Central?
The decision usually comes down to your risk tolerance, growth plans, and how far your business needs have outgrown the platform. Our team at Tigunia can walk through your specific situation and help you weigh the options.
What’s the biggest risk of staying on NAV 2017 after support ends?
Security tends to be the top concern, since new vulnerabilities go unpatched indefinitely. Compatibility, compliance, and a shrinking pool of NAV expertise are also worth weighing.
Where can I learn more about making this decision?
Our resources hub has case studies, guides, and blog articles covering ERP decisions like this one, along with the specifics of a Business Central move.
