Bramvia — Business Central Experts
NAV 2017 support ends on January 11, 2027. The next day, Windows Server 2016, which many NAV 2017 systems run on, stops receiving security patches. What actually happens, your three options, what moving costs, and how much time is really left.
Short answer: Microsoft ends extended support for Dynamics NAV 2017 on January 11, 2027. The next day, January 12, 2027, Windows Server 2016 stops receiving security patches, and a large share of NAV 2017 installations run on it, often with SQL Server 2016, which already lost support on July 14, 2026. Nothing switches off: NAV keeps running. What stops is every fix and security update for the application and, very likely, for the server under it, in the same week. You have three options: stay and buy time with paid Extended Security Updates for the server, upgrade to NAV 2018, which only moves the deadline to January 11, 2028, or move to Business Central online, where there is no server to maintain. With about three months left, almost every NAV 2017 company needs a short bridge for the server; the decision that matters is to set the move date now.
Next step: estimate your upgrade with the migration planner below, or book a free 30-minute assessment to review your customisations before January 2027.
Sound familiar?
- Your NAV 2017 server has not been touched in years, and nobody wants to be the one who touches it.
- Your IT provider is not sure whether the server is Windows Server 2016 or newer.
- The cyber insurance renewal asked whether you run unsupported software.
- You have heard "we'll upgrade next year" for three years running.
Two deadlines in the same week
| Date | What ends | What it means |
|---|---|---|
| July 14, 2026 (passed) | SQL Server 2016 extended support | No more security patches for the database |
| January 11, 2027 | Dynamics NAV 2017 extended support | No more fixes or security updates for NAV 2017 |
| January 12, 2027 | Windows Server 2016 extended support | No more patches unless you pay for Extended Security Updates |
| January 11, 2028 | Dynamics NAV 2018 extended support | The last NAV version runs out of support |
| April 30, 2031 | NAV license sales and renewals | Microsoft stops selling and renewing NAV licenses |
Check your own server with two questions to your IT provider: which Windows Server runs the NAV service, and which SQL Server hosts the database. The full two-question check.
What actually happens on January 12
- NAV keeps working. Users log in, invoices post, reports run.
- No more fixes from Microsoft, including security updates, for NAV 2017.
- The server under it stops getting patches too, if it is Windows Server 2016. Vulnerabilities found after that date stay open.
- Insurers, auditors and large customers notice. Unsupported software in production is a standard question on cyber insurance renewals and supplier audits.
- Compatibility narrows over time: newer Windows, Office, browsers and third-party tools stop being tested against NAV 2017.
Your three options
1. Stay on NAV 2017 and buy time. For the server, Microsoft sells Extended Security Updates for Windows Server 2016 for up to three years (included at no extra cost if the server runs in Azure). Nothing equivalent exists for NAV 2017 itself. It is a reasonable bridge if the move is already decided and dated, not a plan.
2. Upgrade to NAV 2018. It is the last NAV version and is supported until January 11, 2028. That buys one year, costs a real upgrade project, and you face the same decision again in 2028, with nothing new from the cloud along the way.
3. Move to Business Central online. No server to patch, two updates a year, Copilot and AI agents, Power BI included. For a small US company with few customizations, a NAV to Business Central project typically costs $25,000-45,000; mid-market with moderate C/AL code and integrations, $45,000-100,000; heavy legacy code and several entities, $100,000-200,000+. The full cost breakdown. Qualifying NAV customers also get 30% off Business Central online licenses under Bridge to Cloud 3, for enrollments through December 31, 2027.
The value is not just a newer version: it is less manual work, faster numbers and a platform that is patched for you. Compare cost, value and risk over five years with your own figures.
How much time is really left
From October 2026, January 11, 2027 is about three months away.
- Lightly customized NAV 2017 (standard processes, few modifications, one company): 3-4 months. Started now, live around the deadline or shortly after; bridge the server for those weeks.
- Moderate customizations or integrations: 4-6 months. Plan to go live in the first quarter of 2027 and cover the gap with a bridge (server ESU and NAV support).
- Heavy C/AL code or several companies: 6-9 months, in phases. Decide now, bridge the server, and stop adding customizations to NAV 2017.
The path from NAV 2017 goes through converting C/AL customizations to AL extensions and upgrading the data. How many steps it takes depends on your version, customizations and data, which is what the assessment maps.
How we help
We start with a free one-week assessment: your NAV version and cumulative update, the Windows Server and SQL Server under it, your customizations and integrations. You get the real deadline for your system, the option that fits and its cost. If you need a bridge, we support your NAV while the migration runs. Each phase is invoiced only after you accept it.
FAQ
When does Dynamics NAV 2017 support end? On January 11, 2027. After that date Microsoft releases no more fixes or security updates for NAV 2017.
Will Windows Server 2016 be supported after 2027? Not with standard support: extended support ends on January 12, 2027. After that, security patches are available only through paid Extended Security Updates for up to three years, or at no extra cost if the server runs in Azure.
What is the latest version of Dynamics NAV? NAV 2018 is the last Dynamics NAV version, supported until January 11, 2028. Its successor is Dynamics 365 Business Central.
Will NAV 2017 stop working on January 11, 2027? No. It keeps running. What stops is support: fixes, security updates and Microsoft assistance.
Should we upgrade NAV 2017 to NAV 2018? Only if you need one more year and accept doing the upgrade work twice. NAV 2018 support ends on January 11, 2028, and it brings nothing from the cloud.
How much does it cost to move from NAV 2017 to Business Central? For a small US company with few customizations, typically $25,000-45,000, plus licenses from $80 per full user per month, 30% less under Bridge to Cloud 3 if you qualify. More customization and more entities raise the number. What drives the cost.
Free assessment · Evaluación gratuita
Tell us your current system and how many users you have. First reply within one working day. / Cuéntanos tu sistema actual y cuántos usuarios sois. Respondemos en un día laborable.
Still on NAV 2017? Request the free assessment: within a week you know your real deadline, including the server, and what each option costs.
Bramvia in: Spain · United States · Mexico · United Kingdom · Ireland · Canada · Colombia · Argentina · Chile · Peru · Australia · New Zealand · South Africa · Philippines · Poland · MCP server · Safety stock calculator