Dynamics NAV 2017 end of support (January 2027): moving UK and EU SMBs to ERPNext rather than Business Central
Short answer
Microsoft’s lifecycle page for Dynamics NAV 2017 lists January 12, 2027 as the extended support end date (mainstream support ended on January 12, 2022; checked Nov 12, 2026). That is about two months away, the nearest Microsoft ERP deadline in our series. Microsoft’s route is an upgrade to Business Central. Its supported upgrade path from NAV 2017 runs through Business Central version 14 and version 25, and Microsoft notes that the path requires converting your application from C/AL to AL. So your NAV customisations get rebuilt whichever way you go. Business Central is licensed per user: Essentials $80 / £61.50, Premium $110 / £84.60, Team Members $8 / £6.20 per user per month, paid yearly (official US and UK pages; UK excludes VAT). ERPNext has no licence fee (GPL-3.0); Frappe Cloud hosting starts at $5 a month for a site and $40 for a server. Our view: Business Central is the safer move if your partner, add-ons and users are deep in the Microsoft stack. ERPNext is worth pricing for UK and EU manufacturers and distributors of 10 to 150 users whose NAV is heavily customised, because that rebuild cost lands on both options anyway.
Contents
- Who this guide is for
- The NAV dates, exactly as Microsoft lists them
- The part nobody can skip: your C/AL customisations
- Per-user licence vs no licence
- Mapping NAV 2017 to ERPNext
- How the migration works on each path
- Questions to ask before you sign either quote
- Business Central or ERPNext: a decision table
- A NAV 2017 to ERPNext plan, starting now
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for owners, finance directors and IT managers at small and mid-sized companies in the UK and the EU that still run Microsoft Dynamics NAV 2017, typically with 10 to 150 users in manufacturing, distribution or wholesale. You have probably been told by your partner that Business Central is the only next step. It is the obvious one, and often the right one. This guide puts ERPNext next to it honestly.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed, including NAV 2016 and NAV 2018. If you also run Dynamics GP somewhere in the group, see our Dynamics GP to ERPNext guide.
Sources: Microsoft Lifecycle: Dynamics NAV 2017 and Microsoft’s supported upgrade paths to Business Central for dates and the upgrade route; the Business Central pricing page (US) and Business Central pricing page (UK) for Business Central prices; the Frappe Cloud pricing page, ERPNext repository on GitHub, ERPNext Data Import documentation, ERPNext opening balance documentation and ERPNext accounting dimensions documentation for ERPNext. All checked on Nov 12, 2026.
What we do not do here
We do not estimate implementation or upgrade fees for either option. They depend on how many objects you have customised, your add-ons, your data and your partner. Any number we gave without seeing your system would be invented.
The NAV dates, exactly as Microsoft lists them
| Product | Policy | Start date | Mainstream end date | Extended end date |
|---|---|---|---|---|
| Dynamics NAV 2017 | Fixed Lifecycle Policy | October 27, 2016 | January 12, 2022 | January 12, 2027 |
Microsoft shows these dates in Pacific Time, and the page displays the end dates as 1/12/2022 and 1/12/2027. After the extended end date, Microsoft’s Fixed Lifecycle Policy means no more security updates or paid support for the product. For context, the hub lists NAV 2016 (extended support ended April 2026) and NAV 2018 (extended support ends January 2028), both from Microsoft’s lifecycle pages.
What this means in practice:
- NAV 2017 does not stop working on January 12, 2027. What stops is Microsoft’s security patching and support for the product.
- The operating systems and SQL Server versions NAV 2017 runs on have their own lifecycles. Check them separately, because they often force the issue sooner than the application does.
- You will not finish a replacement project in two months. The realistic question is how long you accept running an unsupported ERP, and how you reduce the risk while you move. Typical steps are network isolation, restricted remote access, tested backups and a frozen change policy.
The part nobody can skip: your C/AL customisations
NAV 2017 customisations are written in C/AL, directly in the base application objects. Microsoft’s supported upgrade paths page is explicit. To reach current Business Central from NAV 2017 (version 10), you go through Business Central Spring 2019 (version 14) and Business Central 2024 release wave 2 (version 25), and this path requires you to convert your application from C/AL to AL. Microsoft also notes that from 2025 release wave 1 (version 26), a direct upgrade from version 14 to the latest release is not supported; the path goes through version 25.
That is the key fact for this decision. A NAV 2017 site with years of C/AL changes faces a rebuild on both paths:
| Customisation work | Business Central path | ERPNext path |
|---|---|---|
| Modified base objects (tables, pages, codeunits) | Re-implemented as AL extensions, because the base app can no longer be modified directly | Replaced by standard ERPNext features, configuration, or a custom Frappe app |
| Custom reports | Rebuilt as AL reports or replaced | Rebuilt with report builder, query or script reports, or print formats |
| Integrations (EDI, web shop, banking) | Re-pointed to Business Central APIs or rebuilt | Rebuilt against the Frappe REST API |
| Third-party add-ons | Need a Business Central (AL) version from the ISV | Need an ERPNext equivalent: standard feature, marketplace app or custom build |
| Data | Upgraded in place through intermediate versions | Migrated: extract, transform, load |
Business Central keeps two real advantages here: your data upgrades in place, and your partner and ISVs already know the model. ERPNext’s advantage is that you are not constrained to rebuilding NAV’s structure. You can replace customisations with standard features where they now exist, and you stop paying per-user licences afterwards.
Do a customisation inventory first
Before choosing, list every modified object and every add-on, and classify each one: still needed, needed but now standard in both products, or obsolete. Expect some old customisations to be obsolete, or covered by standard features in either product. You only find out which by doing the inventory. It is also the single best input to both quotes.
Per-user licence vs no licence
Business Central prices, from Microsoft’s official US and UK pricing pages, checked Nov 12, 2026:
| Business Central licence | US (USD) | UK (GBP, excl. VAT) | What it covers |
|---|---|---|---|
| Essentials | $80.00 per user / month, paid yearly | £61.50 per user / month, paid yearly | Finance, sales and operations |
| Premium | $110.00 per user / month, paid yearly | £84.60 per user / month, paid yearly | Everything in Essentials plus service management and manufacturing |
| Team Members | $8.00 per user / month, paid yearly | £6.20 per user / month, paid yearly | Limited access: read data, approve workflows, create or update select information |
Microsoft’s EU country pages price in local currencies; we show only the official US and UK pages here. EU readers should check their own country’s Microsoft pricing page or partner quote.
A NAV 2017 manufacturer that uses production orders would typically need Premium for manufacturing users. Here is a year of licences at list price, assuming every user needs a full licence (the worst case; light users may be Team Members):
| Full users | Essentials, per year (USD / GBP) | Premium, per year (USD / GBP) | ERPNext licence |
|---|---|---|---|
| 10 | $9,600 / £7,380 | $13,200 / £10,152 | $0 / £0 |
| 25 | $24,000 / £18,450 | $33,000 / £25,380 | $0 / £0 |
| 50 | $48,000 / £36,900 | $66,000 / £50,760 | $0 / £0 |
| 150 | $144,000 / £110,700 | $198,000 / £152,280 | $0 / £0 |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.75) and servers from $40 a month (about £30.00), checked on Nov 12, 2026. The GBP figures are indicative conversions, not Frappe prices.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3335 per £1 for 10 Nov 2026, the latest published figure when we checked on Nov 12, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
ERPNext is not free to run. You pay for hosting, implementation, support and upgrades, and Business Central buyers pay for implementation and support too. The licence line is what differs, and it grows with every user you add. If you are on a perpetual NAV licence today with only an annual enhancement plan, moving to Business Central online also changes you from a capital purchase to a subscription. Compare that honestly in your business case.
Mapping NAV 2017 to ERPNext
| Dynamics NAV 2017 | ERPNext | Notes |
|---|---|---|
| Companies | Companies (multi-company in one site) | Inter-company postings via inter-company documents |
| Chart of accounts and G/L accounts | Chart of Accounts | Rebuild the structure; carry account numbers if finance wants them |
| Global and shortcut dimensions | Cost Centers and Accounting Dimensions | Map each NAV dimension to a cost centre or a custom accounting dimension |
| Posting groups (general, customer, vendor, inventory, VAT) | Account defaults on item groups, customer and supplier groups, and tax templates | The biggest conceptual change; design it in discovery, not during data loading |
| VAT posting setup | Item and sales/purchase tax templates | Test every VAT scenario you use, including EU cross-border and reverse charge |
| Customers, vendors, contacts | Customer, Supplier, Contact, Address | Clean duplicates before migration |
| Items, item variants, units of measure | Item, Item Variants, UOM conversions | Check variant attributes and conversion factors |
| Locations and bins | Warehouses (nested) | Bin-level logic is simpler in ERPNext; test pick processes |
| Production BOMs and routings | Bill of Materials with operations, Workstations | Load active BOMs only |
| Production orders | Work Orders and Job Cards | Migrate open orders or finish them in NAV |
| Sales and purchase documents | Quotations, Sales Orders, Delivery Notes, Sales Invoices; Purchase Orders, Receipts, Invoices | Migrate open documents; archive closed history |
| Fixed assets | Assets with depreciation schedules | Load net book value and remaining life |
| Jobs | Projects, Tasks, Timesheets | Check job costing and billing rules |
UK and EU compliance: test it, do not assume it
VAT returns, Making Tax Digital submission in the UK, EU e-invoicing obligations and Intrastat reporting vary by country and change often. In NAV they are usually handled by localisation or an add-on. Treat each as a requirement in the ERPNext pilot. Either confirm a working route (standard feature, a maintained app, or an integration with your filing tool) or keep the existing tool. We would rather tell you a gap exists than discover it at your first VAT quarter.
How the migration works on each path
Business Central: upgrade through intermediate versions
Your partner converts C/AL to AL, upgrades the database through version 14 and version 25 to the current release, then reapplies customisations as extensions. If you are going to Business Central online, a cloud migration step follows. The benefit is continuity: the data model is familiar, and history comes with you.
ERPNext: a designed data migration
There is no Microsoft or Frappe-published NAV-to-ERPNext tool that we know of. You extract from the NAV SQL Server database, or through NAV’s own export features such as configuration packages, then transform and load with ERPNext’s ERPNext Data Import documentation. It supports CSV and Excel templates and can insert or update records. Post opening balances against a temporary opening account, as the ERPNext opening balance documentation describes. Load open receivables and payables as opening invoices, and opening stock through stock reconciliation.
Our usual history policy: migrate masters, open documents and opening balances, plus monthly G/L balances for two or three prior years for comparison reporting. Keep NAV running read-only (isolated) or extract history to a reporting database for audit. In the UK, HMRC record-keeping rules still apply to the history you leave behind, so plan read access for as long as you need it.
Questions to ask before you sign either quote
Whichever way you lean, ask the same questions of your Business Central partner and your ERPNext partner. Put the answers side by side. The differences are usually clearer than the brochures make them look.
Ask both partners
- Which of our C/AL customisations will you rebuild, which become standard features, and which do you recommend dropping? Show it object by object.
- Which of our add-ons have a supported version on your platform, and who maintains it?
- How will you test our VAT return, Making Tax Digital submission and any EU e-invoicing or Intrastat needs before go-live?
- What history do you migrate, and how do we read the rest for audit?
- How many trial migrations are included, and what counts as a pass?
- Who supports us after go-live, during which hours, and what does it cost per year?
- What happens to the quote if the customisation inventory grows during discovery?
Ask the Business Central partner specifically
- Online or on-premises, and what changes in cost and upgrade cadence between them?
- Which users really need Premium, and which can be Team Members?
Ask the ERPNext partner specifically
- Frappe Cloud or self-hosted, which region, and how are backups and upgrades handled?
- Which customisations will be built as a custom Frappe app, and how do they survive ERPNext upgrades?
Business Central or ERPNext: a decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| You want the most familiar path and plan to keep your NAV partner | Business Central | Same data model, in-place upgrade, partner continuity |
| Your critical add-ons already have Business Central versions | Business Central | The ISVs did the rebuild for you |
| NAV is heavily customised and most of it must be rebuilt anyway | ERPNext (price both) | Rebuild cost lands on both paths; ERPNext removes the per-user licence afterwards |
| You need manufacturing for many users | ERPNext (price both) | Business Central manufacturing needs Premium per user |
| You want to self-host or control where the data lives | ERPNext | Open source; self-host or pick a Frappe Cloud region |
| Your team lives in Microsoft 365 and Power BI | Business Central | Native integration |
| You have no appetite for a designed data migration | Business Central | In-place upgrade keeps your history |
A NAV 2017 to ERPNext plan, starting now
| Phase | Work | Done when |
|---|---|---|
| Stabilise (now to January 2027) | Isolate the NAV server, tighten remote access, test backups and restores, freeze changes | A written risk acceptance for running unsupported NAV |
| Inventory and discovery (6–8 weeks) | Customisation and add-on inventory, process mapping, compliance requirements, history policy | Signed scope and both quotes requested on the same inventory |
| Pilot (8–12 weeks) | Load one company’s masters and a recent year of balances; run a month-end close and a VAT return test | Finance closes a pilot month and agrees the numbers |
| Build (3–5 months) | Configure, rebuild the customisations you kept, integrations, reports, training | User acceptance testing signed off |
| Dress rehearsals (2 cycles) | Full trial migrations from a NAV copy, with reconciliation | Balances match NAV |
| Cutover (period or year start) | Close the period in NAV, load openings, go live | First month and first VAT period closed in ERPNext |
These durations are our planning ranges for a 10 to 150 user NAV site, not a promise. Heavy customisation or several companies push them up. The point of the first phase is that you will run NAV 2017 past January 2027 on any realistic plan, so manage that risk deliberately.
Best for, and wrong choice when
ERPNext is the right NAV 2017 replacement when
You are a UK or EU manufacturer or distributor with 10 to 150 users, NAV is heavily customised so a rebuild is coming either way, you want to stop paying per user, and you will fund a proper pilot including VAT and compliance testing.
ERPNext is the wrong choice when
Your critical add-ons have Business Central versions and no ERPNext equivalent, your users depend on native Microsoft 365 integration, or you cannot spare finance staff for a pilot and two dress rehearsals.
Business Central is the wrong choice when
Per-user Premium licences for manufacturing users will be your largest recurring ERP cost, and the C/AL rebuild means you would not keep much of NAV anyway.
Frequently asked questions
When does Dynamics NAV 2017 support end?
Microsoft’s lifecycle page lists January 12, 2027 as the extended support end date for Dynamics NAV 2017, under the Fixed Lifecycle Policy. Mainstream support ended on January 12, 2022 (checked Nov 12, 2026).
Can I keep using NAV 2017 after January 2027?
The software keeps running, but Microsoft stops security updates and support. Running an unsupported ERP is a risk you should accept explicitly and reduce with isolation, access control and tested backups while you move.
Can NAV 2017 upgrade directly to Business Central?
Not directly to the current release. Microsoft’s upgrade paths page routes NAV 2017 through Business Central version 14 and version 25, and states that the path requires converting your application from C/AL to AL.
How much does Business Central cost per user?
Microsoft lists Essentials at $80 / £61.50, Premium at $110 / £84.60 and Team Members at $8 / £6.20 per user per month, paid yearly (UK prices exclude VAT; checked Nov 12, 2026).
Is ERPNext free?
ERPNext is open source under GPL-3.0 with no licence fee. You pay for hosting (Frappe Cloud lists sites from $5 a month and servers from $40 a month), implementation and support.
Does ERPNext handle UK VAT and Making Tax Digital?
Treat it as a pilot requirement. ERPNext has tax templates for VAT, but confirm your VAT return and MTD submission route, and any EU e-invoicing or Intrastat needs, before you commit.
How do NAV dimensions map to ERPNext?
Map NAV global and shortcut dimensions to ERPNext cost centres and custom accounting dimensions, and redesign posting groups as account defaults and tax templates.