Navision and NAV 2016 or earlier, now out of support: migrating to ERPNext without a multi-step Microsoft upgrade
Short answer
Every Navision release up to and including Dynamics NAV 2016 is now out of Microsoft support. Microsoft’s lifecycle pages show extended support ending in April 2026 for NAV 2016, January 2025 for NAV 2015, January 2023 for NAV 2013 and 2013 R2 and January 2020 for NAV 2009 and 2009 R2 (checked Nov 16, 2026). Microsoft’s documented route to Business Central is a stepped upgrade: NAV 2015 or 2016 to Business Central 14, then version 25, then the current release, converting C/AL to AL; NAV 2013 and 2013 R2 go through NAV 2018 first; NAV 2009 through NAV 2013 or 2015 first. A move to ERPNext skips those steps: you extract masters, open items and balances from NAV and load them into a new system. That is still a reimplementation, not a shortcut on business change. If you want to stay Microsoft, Business Central online lists Essentials at $80 / £61.50 and Premium at $110 / £84.60 per user per month (paid yearly, UK excl. VAT); ERPNext has no licence fee.
Contents
- Who this guide is for
- What Microsoft’s lifecycle pages show
- Microsoft’s route: a stepped upgrade
- The ERPNext route: a data migration
- Mapping NAV to ERPNext
- Six data problems we see in old NAV databases
- Stepped upgrade vs ERPNext: side by side
- Licence costs: official prices in USD and GBP
- Where Business Central is the better answer
- A practical cutover plan
- Decision table
- 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 businesses in the UK, the US and elsewhere that still run Navision or Dynamics NAV 2016 or earlier. Many of these systems have run for ten or twenty years, have been modified by several partners, and sit on Windows Server and SQL Server versions that are themselves past their best.
We implement ERPNext. We also tell NAV customers when Business Central is the better answer, and we say where below. If you are on NAV 2017 or NAV 2018, read our NAV 2017 guide or NAV 2018 guide; if you already reached Business Central 14, see our Business Central 14 guide. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 16, 2026: Microsoft’s lifecycle pages (Microsoft Lifecycle: Dynamics NAV 2016, Microsoft Lifecycle: Dynamics NAV 2015, Microsoft Lifecycle: Dynamics NAV 2013 R2, Microsoft Lifecycle: Dynamics NAV 2013, Microsoft Lifecycle: Dynamics NAV 2009 R2, Microsoft Lifecycle: Dynamics NAV 2009), Microsoft’s “Migrate Dynamics NAV to Business Central online” guide, Microsoft’s “Upgrading to on-premises v14” guide, Microsoft’s supported upgrade paths to Business Central, Microsoft’s Business Central 14 reimplementation tool (preview) documentation, the Business Central pricing page (US) and Business Central pricing page (UK), the Frappe Cloud pricing page, the ERPNext repository on GitHub and the ERPNext documentation linked below.
What we do not estimate
We do not put a money or time figure on an upgrade or a migration. Both depend on your customisations, data volume and how many companies you run. We show Microsoft’s published steps and prices, and a way to size the work from your own object list and data.
What Microsoft’s lifecycle pages show
| Version | Mainstream end (as displayed) | Extended end (as displayed) | Source |
|---|---|---|---|
| Dynamics NAV 2016 | 4/14/2021 | 4/15/2026 | Microsoft Lifecycle: Dynamics NAV 2016 |
| Dynamics NAV 2015 | 1/15/2020 | 1/15/2025 | Microsoft Lifecycle: Dynamics NAV 2015 |
| Dynamics NAV 2013 R2 | 1/10/2018 | 1/11/2023 | Microsoft Lifecycle: Dynamics NAV 2013 R2 |
| Dynamics NAV 2013 | 1/10/2018 | 1/11/2023 | Microsoft Lifecycle: Dynamics NAV 2013 |
| Dynamics NAV 2009 R2 | 1/14/2015 | 1/15/2020 | Microsoft Lifecycle: Dynamics NAV 2009 R2 |
| Dynamics NAV 2009 | 1/14/2015 | 1/15/2020 | Microsoft Lifecycle: Dynamics NAV 2009 |
Microsoft displays these as timestamps such as “4/15/2026 6:59:59 AM”, so we describe each end by month: NAV 2016 extended support ended in April 2026, NAV 2015 in January 2025, NAV 2013 and 2013 R2 in January 2023, and NAV 2009 and 2009 R2 in January 2020. The NAV 2009 R2 page notes that the end-of-support dates for NAV 2009 were extended to those shown. Older releases such as NAV 4.0 and 5.0 appear in Microsoft’s upgrade documentation only as starting points that must go through NAV 2013; we did not find lifecycle pages for them to cite.
Out of extended support means no security updates, no fixes and no regulatory or tax updates from Microsoft. The software still runs. The risk is everything around it: unpatched servers, payment and tax changes your partner has to hand-build, and fewer people every year who can maintain C/AL and the old clients.
Microsoft’s route: a stepped upgrade
Microsoft documents the supported routes in its NAV-to-Business-Central-online guide and its upgrade guides:
| Starting version | Microsoft’s documented route | Source |
|---|---|---|
| NAV 2015 and NAV 2016 | Business Central 14 on-premises → Business Central on-premises version 25 or later → Business Central online (or stay on-premises on the current release) | Microsoft’s “Migrate Dynamics NAV to Business Central online” guide; Microsoft’s supported upgrade paths to Business Central |
| NAV 2013 and 2013 R2 | NAV 2018 → Business Central 14 → version 25 or later → online | Microsoft’s “Migrate Dynamics NAV to Business Central online” guide; Microsoft’s “Upgrading to on-premises v14” guide |
| NAV 2009 SP1 and 2009 R2 | NAV 2013 or NAV 2015 → (via 2013: NAV 2018) → Business Central 14 → version 25 or later → online | Microsoft’s “Migrate Dynamics NAV to Business Central online” guide; Microsoft’s “Upgrading to on-premises v14” guide |
| NAV 5.0 and 4.0 | Through NAV 2013, then as above | Microsoft’s “Upgrading to on-premises v14” guide |
Three details from those pages shape the effort:
- C/AL has to become AL. The upgrade-paths page says the route from NAV 2015 to 2018 through Business Central 14 and 25 to the current release (version 29, 2026 release wave 2) “requires you convert your application from C/AL to AL”. Microsoft’s migration guide adds that data in tables with code customisations cannot be carried forward unless those customisations are converted to AL extensions.
- Version 14 is a mandatory stop. Both the full migration and the reimplementation route start by upgrading to Business Central 14. From 2025 release wave 1 (v26), a direct upgrade from version 14 to the latest release is not supported; you go through version 25.
- The lighter Microsoft option is in preview. The Business Central 14 reimplementation tool moves only essential data (masters, opening balances, setup and a defined subset of posted history) and leaves C/AL customisations behind. Microsoft labels it a preview feature that is “not meant for production use”, and you still have to reach version 14 first.
Each step is a technical upgrade plus testing. For a NAV 2009 site with years of modifications, that can mean three or four upgrade projects in sequence before you reach a supported release.
The ERPNext route: a data migration
ERPNext does not read NAV’s database, and there is no NAV-to-ERPNext converter we would recommend. That is the point: you do not need the intermediate versions at all. The work is:
- Extract from a copy of the NAV SQL Server database (or, on very old installs, from the native Navision database via exports): items, customers, vendors, chart of accounts, dimensions, BOMs, open documents and balances.
- Transform in spreadsheets or scripts: clean duplicates, map NAV posting groups to ERPNext accounts and item groups, map dimensions.
- Load with ERPNext Data Import (ERPNext Data Import documentation), opening balances (ERPNext opening balance documentation) and stock reconciliation (ERPNext Stock Reconciliation documentation).
- Rebuild the customisations you still need as custom fields, Customize Form changes, workflows, server scripts or a custom app (ERPNext Custom Field documentation, ERPNext Customize Form documentation, ERPNext Workflow documentation, Frappe Server Script documentation).
The honest catch: this is a reimplementation. Users learn a new system, reports are rebuilt, integrations are redone. What you skip is the chain of upgrades and the C/AL-to-AL conversion of code you may no longer need.
Mapping NAV to ERPNext
| NAV (Navision) | ERPNext | Notes |
|---|---|---|
| Chart of accounts, G/L accounts | Chart of Accounts (ERPNext Chart of Accounts documentation) | Restructure if the old chart has grown untidy |
| Global and shortcut dimensions | Accounting dimensions, cost centres (ERPNext accounting dimensions documentation, ERPNext Cost Center documentation) | Decide which dimensions are mandatory |
| Gen./VAT/inventory posting groups | Account defaults on item groups, customers, suppliers and companies; tax templates | Design, not a straight copy |
| Customers, vendors, contacts | Customers, suppliers, contacts, addresses | Load with Data Import |
| Items, units of measure, item variants | Items, UOM conversions, item variants (ERPNext Item Variants documentation) | Variants map to templates and attributes |
| Locations, bins | Warehouses (tree) (ERPNext Warehouse documentation) | Bins can be child warehouses |
| Production BOMs and routings | BOMs and routings (ERPNext Bill of Materials documentation, ERPNext Routing documentation) | See the NAV 2018 guide for manufacturing detail |
| Sales and purchase prices and discounts | Price lists, item prices, pricing rules (ERPNext Pricing Rule documentation) | Rebuild and test against old invoices |
| Open customer and vendor ledger entries | Opening invoices and balances | Reconcile to aged reports |
| Item ledger (stock on hand, cost) | Opening stock reconciliation per warehouse | Agree valuation with your accountant |
| Multiple companies, intercompany | Multiple companies, inter-company invoices (ERPNext inter-company invoices documentation) | One ERPNext site can hold several companies |
| Posted history | Not migrated as live ledger; keep NAV read-only | Or load summary history for reporting |
Our NAV 2018 guide covers manufacturing objects (production orders, routings, capacity) in more depth; the mapping is the same for older NAV versions.
Six data problems we see in old NAV databases
Old NAV databases carry the history of every partner who touched them. Plan for these before the first trial load, whichever route you choose:
- Duplicate and dormant masters. Customers, vendors and items created twice, or not used for years. Agree a cut-off (for example, no transactions in three years) and do not migrate the rest.
- Posting groups that encode business rules. General business, product, VAT and inventory posting groups often carry logic nobody documented. Map each combination to ERPNext account defaults and tax templates, and test a sample invoice for every combination you keep.
- Dimensions used inconsistently. Global and shortcut dimensions that were mandatory in one period and optional in another. Decide the ERPNext accounting dimensions you want going forward, not the ones you happened to have.
- Custom tables and fields. Partner-added tables (for example, extra item attributes or customer agreements) need a destination: a custom field, a custom DocType or the archive.
- Open documents in odd states. Partially shipped orders, unapplied payments and prepayments. Close or clean as many as possible before cutover; migrate the rest as open documents.
- Stock valuation. Agree with your accountant how NAV’s costing method and the value of stock on hand carry into ERPNext’s opening stock reconciliation, and reconcile the stock value to the general ledger on the day of cutover.
None of these is specific to ERPNext. On Microsoft’s route the same problems travel through every intermediate upgrade; on the ERPNext route you deal with them once, during the extract and transform.
Stepped upgrade vs ERPNext: side by side
| Question | Business Central (Microsoft route) | ERPNext |
|---|---|---|
| Intermediate versions | Yes: BC 14 and 25, plus NAV 2018 or 2013/2015 for older starts | None |
| Customisations | Convert C/AL to AL extensions, or drop them (reimplementation tool, preview) | Rebuild what you still need; drop the rest |
| Posted history in the new system | Kept on the full upgrade path | Not as live ledger; archive NAV |
| Licence | Per user per month (online); partner quote for on-premises | No licence fee (GPL-3.0) |
| Hosting | Microsoft cloud, or on-premises | Self-hosted or Frappe Cloud |
| Skills | Business Central and AL partners | Frappe/ERPNext partners and in-house Python developers |
| User change | Familiar to NAV users | New system to learn |
Licence costs: official prices in USD and GBP
| Plan | US price | UK price (excl. VAT) | Source |
|---|---|---|---|
| Business Central Essentials | $80 per user/month | £61.50 per user/month | Business Central pricing page (US); Business Central pricing page (UK) |
| Business Central Premium (adds service management and manufacturing) | $110 per user/month | £84.60 per user/month | Business Central pricing page (US); Business Central pricing page (UK) |
| Business Central Team Members | $8 per user/month | £6.20 per user/month | Business Central pricing page (US); Business Central pricing page (UK) |
| Business Central on-premises licences | Sold through partners; not priced on Microsoft’s page | Partner quote | Microsoft partner |
| ERPNext | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud | Sites from $5/month; servers from $40/month | Indicative £3.78 / £30.22 | Frappe Cloud pricing page |
Business Central prices are per user per month, paid yearly, checked on Nov 16, 2026; UK prices exclude VAT. A worked example at list price for full users (add Team Members for light users):
| Full users | Essentials, per year (USD / GBP) | Premium, per year (USD / GBP) |
|---|---|---|
| 10 | $9,600 / £7,380 | $13,200 / £10,152 |
| 25 | $24,000 / £18,450 | $33,000 / £25,380 |
| 50 | $48,000 / £36,900 | $66,000 / £50,760 |
These are list price × users × 12 from Microsoft’s pages. They exclude the upgrade or migration project, partner support and any discounts.
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.22), checked on Nov 16, 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.3238 per £1 for 12 Nov 2026, the latest published figure when we checked on Nov 16, 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.
Where Business Central is the better answer
- Your NAV modifications are light and you are on NAV 2015 or 2016, so the route is relatively short.
- You need your full posted history in the live system, not in an archive.
- You depend on an ISV add-on that exists for Business Central and has no ERPNext equivalent.
- Your business runs on Microsoft 365, Power BI and Power Automate and you value that integration.
- Your users and finance team want the least change; Business Central will feel familiar.
ERPNext is the better fit when you are on NAV 2013 or older and facing several upgrade steps, your C/AL modifications are heavy enough that converting them is a rewrite, per-user licences are a large share of IT cost, and your processes fit ERPNext’s standard modules after a fit test.
A practical cutover plan
Weeks 1 to 3: inventory
Record your exact version and cumulative update, list modified objects, integrations, reports and add-ons, and count companies, users and open documents. Check the lifecycle of the Windows Server and SQL Server underneath.
Weeks 3 to 6: two quotes, one fit test
Ask a Business Central partner to price the stepped upgrade from your object list. In parallel, load a copy of your masters into ERPNext and run a month of real transactions.
Weeks 6 to 8: decide
Compare effort, five-year licence and support cost, and fit gaps. Pick a go-live at a period end, ideally your financial year end, to make opening balances clean.
Months 3 to 6: build, rehearse, cut over
Run at least two trial migrations, one month-end in parallel, then cut over. Keep NAV read-only for history and audits.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| NAV 2015 or 2016, light modifications | Business Central | Shortest Microsoft route, history kept |
| NAV 2013 or 2009, heavy modifications | Price ERPNext seriously | Several upgrades plus a rewrite vs one migration |
| Critical ISV add-on on Business Central | Business Central | No equivalent elsewhere |
| Per-user licences a big share of cost | ERPNext | No licence fee |
| Must stay on-premises long term | Either: current BC on-premises or self-hosted ERPNext | Both support self-hosting |
Best for, and wrong choice when
ERPNext is best for
Long-running Navision and NAV 2009 to 2016 sites with heavy modifications, simple to moderate distribution or manufacturing, and an appetite to clean up processes rather than carry them forward.
Business Central is best for
NAV 2015 and 2016 sites with light modifications, Microsoft-centred IT, ISV add-on dependencies, or a need to keep posted history in the live system.
ERPNext is the wrong choice when
You need full ledger history in the new system, rely on an ISV vertical with no ERPNext equivalent, or cannot spare people to learn a new system this year.
Frequently asked questions
When did Dynamics NAV 2016 support end?
Microsoft’s lifecycle page shows extended support ending 4/15/2026 (displayed with a 6:59:59 AM timestamp), so it ended in April 2026. Mainstream support ended in April 2021 (checked Nov 16, 2026).
Is Navision still supported?
No. NAV 2016, 2015, 2013, 2013 R2, 2009 and 2009 R2 are all past extended support on Microsoft’s lifecycle pages, and older releases such as NAV 4.0 and 5.0 appear only as upgrade starting points in Microsoft’s documentation.
Can I upgrade NAV 2009 directly to Business Central?
No. Microsoft documents NAV 2009 SP1 and R2 going through NAV 2013 or NAV 2015 (and from 2013 through NAV 2018), then Business Central 14, then version 25 or later.
Can I upgrade NAV 2016 directly to the latest Business Central?
No. Microsoft’s path is NAV 2016 to Business Central 14, then version 25, then the current release, converting C/AL to AL along the way.
Is there a tool to migrate Navision to ERPNext?
We do not know of a supported converter. A migration to ERPNext extracts masters, open items and balances from the NAV database and loads them with ERPNext Data Import and opening balance tools.
What does Business Central cost?
Microsoft lists Essentials at $80 (UK £61.50), Premium at $110 (£84.60) and Team Members at $8 (£6.20) per user/month, paid yearly, UK prices excluding VAT (checked Nov 16, 2026).
Can I keep my NAV history?
In ERPNext, not as live ledger history. Keep NAV read-only, or a reporting copy of its database, for history and audits.