Dynamics NAV to Odoo Migration: Comparison, Risks and Roadmap

The short version

There are three workable paths for a company on Dynamics NAV, and none of them is right for everyone.

1. Stay on NAV for now, with a documented risk plan and a funded exit date.
2. Move to Microsoft Dynamics 365 Business Central, the path Microsoft supports and documents.
3. Reimplement the business on Odoo, treating the move as a fresh design and not a technical upgrade.

Start by confirming which NAV version you run. That one fact tells you whether Microsoft still services your system and how much time you have to decide.

Product facts in this guide are cited to Microsoft's and Odoo's official pages. Recommendations are NGYN's and are marked as ours.

Is Navision really being retired?

Navision was the name of the Danish ERP product Microsoft acquired in 2002. Microsoft later renamed it Microsoft Dynamics NAV. Many finance and operations teams still say "Navision" out of habit, and in most conversations the two names mean the same product.

Dynamics NAV is no longer sold as a current product. Microsoft Dynamics 365 Business Central is Microsoft's successor to it, and Microsoft's own lifecycle pages for NAV link to migration guidance for Business Central.

• A product being replaced is not the same as your system stopping. An installed NAV system does not switch off when support ends. It keeps running on your servers. What changes is the servicing Microsoft provides around it.
• There is no single shutdown date. Each NAV version has its own support dates under Microsoft's Fixed Lifecycle Policy.
• Your version decides your position. A company on NAV 2018 and a company on NAV 2013 face different timelines and different risks.

Mainstream Support, Extended Support and end of support

Microsoft's Fixed Lifecycle Policy describes three stages.

Source: Microsoft Fixed Lifecycle Policy, checked October 5, 2026.

The policy also states that both phases "require a product's supported service pack to be installed to continue to receive full support". In practice, being inside the support window is not enough. You also need to be on a supported update level. Ask your NAV partner which cumulative update you are running.

Dynamics NAV end-of-support dates by version

Every supported NAV version is now past Mainstream Support. NAV 2017 and NAV 2018 are in Extended Support, which means security updates and paid support continue, but non-security fixes and feature requests do not.

A note on the dates. Microsoft states that its lifecycle dates are shown in Pacific Time, and the published timestamps can appear as the following calendar day in other time zones or in raw data. This table uses Microsoft's end-of-support calendar date in Pacific Time. Microsoft can revise lifecycle dates, so confirm yours on the linked page before you rely on it.

If you run NAV 2016: support ended on April 14, 2026. Your system still runs, but you should treat the risk review in the next section as current work, not future work.

If you run NAV 2017: end of support is January 11, 2027. A replacement project will almost certainly not finish before then, so plan for a period of running out of support, and decide how you will manage it.

If you run NAV 2018: end of support is January 11, 2028. That is enough time for an orderly evaluation and migration if you start the decision now.

What end of support changes, and what it does not

What Microsoft's policy says. After end of support, Microsoft no longer provides non-security updates or accepts design change requests, and security updates are available only where an Extended Security Update program exists for the product. Microsoft also notes that older products "may not meet today's more demanding security requirements".

What that does not mean. An out-of-support NAV system is not automatically insecure, non-compliant or unusable. Whether it is a problem depends on how it is hosted, what it connects to and what your auditors, insurers and customers expect.

The following is NGYN's advice on what to assess. None of it is a Microsoft statement.

Your three realistic options

Option A: remain temporarily on NAV

Staying on NAV for a defined period can be a reasonable decision. It is reasonable when a replacement project is already scheduled, the environment is stable, the risks above have been assessed, specialists and tested recovery procedures are available, integrations and infrastructure are under control, and management has approved a firm exit plan.

The conditions we recommend before choosing it:

• A named owner for the NAV environment.
• A known support arrangement with a partner or developer.
• A security and infrastructure review.
• Backups with a tested restore.
• A change freeze on non-essential NAV development.
• A written exit deadline.
• A budget and an executive sponsor for the replacement.

Staying on NAV with no date and no budget is not a strategy. It is a decision that has not been made yet.

Option B: move to Business Central

Business Central shares its lineage with NAV, but it is not simply "NAV in the cloud". Its deployment, extension model, upgrade cadence and licensing are different and need their own evaluation.

Microsoft documents the route in Migrate Dynamics NAV to Business Central online. The key points from that page:

• The move is staged. NAV versions cannot migrate directly to the cloud. NAV 2015 through 2018 upgrade first to Business Central version 14 on-premises, then to a current on-premises version, then to Business Central online. NAV 2013 must first reach NAV 2018, and NAV 2009 has a further step before that.
• There are two paths. A full migration moves all data and customizations. A reimplementation moves essential business data only: master data, opening balances and setup.
• Customizations must become extensions. C/AL is the older NAV programming language. AL is the language used for Business Central extensions. Microsoft states that "all C/AL code customizations must be converted to AL extensions", and that data in tables with code customizations cannot be carried forward unless those customizations are converted.
• Microsoft recommends rehearsal. The guidance calls for data cleanup first and at least one dry run in a sandbox before production cutover.

A Microsoft-to-Microsoft move is still a project. It needs discovery, cleanup, testing, training and cutover planning.

Business Central is probably the stronger choice when:

• The company is standardized on Microsoft 365, Teams, Power BI, Azure or Power Platform.
• Users and your partner have strong NAV or Business Central skills.
• Microsoft product continuity is a priority.
• Existing customizations can be rationalized and converted to supported extensions.
• Limiting process and screen changes matters more than rethinking how the business runs.
• The financial or industry capabilities you need are well served in the Microsoft ecosystem.

Option C: reimplement on Odoo

Moving from NAV to Odoo is a reimplementation, not a database conversion. There is no tool that turns a NAV database into an Odoo database. Records and workflows are extracted, mapped, transformed, imported, tested and reconciled.

What that involves:

• Legacy customizations are not rebuilt by default. Each one is reviewed and either replaced by a standard process, configured, or rebuilt because it is required.
• Edition matters. Odoo Community is open source with no licence fee. Odoo Enterprise is the commercial edition, with additional applications and Odoo's hosting, upgrade and support services. A database runs one edition, so the choice applies to the whole system. Check Odoo's editions comparison for the applications you need.
• Fit must be proven. Accounting, localization, statutory reports, manufacturing, warehouse and industry requirements need to be validated against Odoo 19, not assumed.
• Process redesign is where the value is. Copying NAV behaviour screen for screen usually costs more and delivers less than adopting a standard workflow.

Odoo deserves serious consideration when:

• You want finance, sales, purchasing, inventory, manufacturing, projects, field work, service, CRM and website on one application platform.
• You do not want to carry every NAV customization forward.
• Deployment choice matters: Odoo's cloud, Odoo's platform hosting, or your own servers.
• An open-source Community option is strategically relevant.
• You want to redesign workflows, not complete another technical upgrade.
• Per-user licensing and ownership cost need a fresh look.
• You are willing to do a proper fit-gap analysis first.

Odoo is not automatically cheaper, faster or easier. That depends on scope, edition, user count, custom development, infrastructure, data, integrations and your own team's capacity.

Dynamics NAV vs Business Central vs Odoo

This comparison does not score the products. Several rows depend on your version, edition and configuration.

Confirm any row that drives your decision against the vendor's current page. Sources are listed at the end.

Choose Business Central when your company runs on Microsoft tools, your people know NAV well, and your customizations can be converted to extensions at a cost you accept.

Evaluate Odoo when you want one platform across more of the business, you would rather retire customizations than convert them, and you are ready to change how some work is done.

Delay only when you have documented controls around the current system and a funded exit plan with a date.

Module-by-module NAV to Odoo migration map

This map is a discovery framework. It is not a promise of one-to-one field mapping, and the Odoo targets are starting points to validate in a fit-gap analysis.

Go-live dependencies. Workstream A comes first, because everything else depends on companies, users and sequences. Finance opening balances need a closed period in NAV. Inventory needs a stock count close to cutover. Manufacturing and projects need inventory and finance reconciled. Integrations go live last.

What data should move from NAV to Odoo?

Sort NAV data into four categories before anyone builds an import.

Why migrating everything is not automatically safer

Moving every posted entry "to be safe" usually raises risk instead of lowering it.

• Migration complexity. Posted history has to satisfy the new system's rules for taxes, accounts and products. Years of history multiply the mapping and the errors.
• Data quality. Old records carry old mistakes, retired codes and duplicates into a clean system.
• Auditability. An auditor usually wants the original record. A transformed copy in a new system is weaker evidence than the untouched source.
• Reporting needs. Most comparisons need summarized prior-period figures, not every line.
• Operational access. Staff need recent history every day and old history rarely.

The archive needs working search, access control, backup with tested recovery, and a named owner. NAV in read-only mode, a restored database copy, or an export to a reporting database can each do this.

Tax and legal retention periods vary by jurisdiction and record type. Confirm yours with your accountant and legal advisor before deciding what to archive and for how long. This guide is not legal advice.

How Odoo imports data

Odoo 19 imports CSV and Excel files through a standard import tool, with a Test step that checks the file before anything is written. Each record can carry an External ID, which Odoo's documentation describes as "a unique identifier for a line item", adding that "it is possible to use an External ID (ID) from previous software to facilitate the transition to Odoo".

Using NAV numbers as External IDs lets you repeat an import without creating duplicates, and link related records such as invoices to customers. Odoo also advises splitting large files into smaller batches to avoid timeouts. The source is Odoo's export and import documentation, linked under sources.

Recommended NAV to Odoo migration phases

We recommend a phase-gated plan. Each phase ends with a deliverable and an approval, and the next phase does not start until that approval is given.

UAT means user acceptance testing: the people who will do the work confirm the system supports it. Hypercare is the period of closer support straight after go-live.

In phase 3, every gap is classified as one of seven things: a process change, standard configuration, an integration, an approved third-party module, a small customization, significant custom development, or out of scope. That classification is what makes the later estimate credible.

In phase 7, no customization should start without a written record: the business problem, why standard Odoo is not sufficient, the process alternative considered, acceptance criteria, owner, estimated effort, test cases, security and data impact, upgrade implication and who supports it.

Why the pilot comes before customization

Users coming from NAV often ask for the old behaviour before they have seen the new one. That is natural. It is also how customization debt gets carried from one system into the next.

Running a pilot on standard Odoo first changes the conversation.

• Some gaps disappear. A screen that looked wrong alone often makes sense once people run the whole workflow.
• The remaining gaps are real. After a pilot, a gap is something a user experienced, not something they predicted.
• Less code means less upkeep. Every customization has to be developed, tested, supported and carried through each upgrade.

Standard first does not mean standard only. Gaps that are legal, financial, operational or customer-facing still need to be resolved before go-live. The goal is not zero customization. The goal is justified customization.

Migration reconciliation controls

A successful import does not prove a successful migration. Reconciliation against NAV, and acceptance by the business, are what prove it.

• Source record counts captured from NAV for every object.
• Imported record counts match, or every difference is explained.
• Rejected and corrected rows logged and re-imported.
• Duplicate detection run on customers, vendors and products.
• Customer control total agrees to the receivables account.
• Vendor control total agrees to the payables account.
• AR aging matches NAV by customer and bucket.
• AP aging matches NAV by vendor and bucket.
• Trial balance matches NAV at the cutover date.
• Retained earnings agree after opening entries.
• Bank balances agree to the last reconciled statement.
• Tax balances agree to the last filed return.
• Fixed-asset cost and accumulated depreciation agree.
• Inventory quantities agree by location.
• Inventory value agrees by item and location.
• Lot and serial numbers carry over without breaks.
• Open sales orders agree in count and value.
• Open purchase orders agree in count and value.
• Active manufacturing orders agree, including consumed material.
• Active projects agree on budget and billed to date.
• Roles and permissions tested by real users.
• Integrations monitored through a full cycle.
• Cutover duration measured in rehearsal.
• Rollback decision point and decision owner defined.
• Sign-off owner named for finance, operations and IT.

Cost and timeline drivers

We do not publish one cost or duration for NAV to Odoo. Without knowing your environment, any figure would be a guess.

What moves the effort:

• The source system: NAV version, database and infrastructure, custom objects, add-ons, reports, print forms and integrations.
• The business: number of legal entities, countries, currencies and localizations, modules in use, user count, manufacturing and warehouse complexity, project accounting.
• The data: quality, volume, how much history you keep, attachments.
• The target: Odoo Community or Enterprise, hosting choice, customization approved after the pilot.
• The delivery: availability of your own people, training needs, one cutover or a phased rollout, cutover constraints such as year-end, and the hypercare you want.

Total cost of ownership has more lines than licences:

For how Odoo implementations are priced in Canada, see how much an Odoo ERP costs. NGYN's hourly rate and support plans are on the fee table, and the support terms are in the Service Level Agreement.

NAV migration-readiness checklist

Print or save this list. The more of it you can answer, the more accurate your estimate will be.

• Exact NAV version and cumulative update confirmed.
• Database version confirmed.
• Infrastructure owner identified.
• Source-code and licence access confirmed.
• C/AL customizations inventoried.
• Custom tables inventoried.
• Add-ons inventoried.
• Integrations inventoried.
• Reports inventoried, with the ones still used marked.
• Companies and currencies documented.
• Data volumes measured.
• Data owners assigned.
• Retention decisions documented.
• Accounting controls documented.
• Inventory reconciliation requirements documented.
• Critical workflows selected for the pilot.
• Business subject-matter experts assigned.
• User roles documented.
• Training owners assigned.
• Cutover constraints documented.
• Rollback authority identified.
• Hypercare team assigned.
• NAV archive approach defined.
• Executive sponsor confirmed.
• Budget and decision deadline set.

If you are unsure whether you need outside help for this, read when you need an Odoo consultant.

Frequently asked questions

Is Microsoft Dynamics NAV discontinued?

Dynamics NAV is no longer Microsoft's current product. Business Central replaced it. Existing NAV installations keep running, and each version has its own support end date under Microsoft's Fixed Lifecycle Policy.

Is Navision the same as Dynamics NAV?

Yes, in everyday use. Navision is the original product name. Microsoft renamed it Microsoft Dynamics NAV, and many users kept the older name.

When does Dynamics NAV 2018 support end?

January 11, 2028, according to Microsoft's lifecycle page for NAV 2018. Mainstream Support ended on January 10, 2023, so the product is in Extended Support until then.

When does Dynamics NAV 2017 support end?

January 11, 2027, according to Microsoft's lifecycle page for NAV 2017. Its Mainstream Support ended on January 11, 2022.

What replaced Microsoft Dynamics NAV?

Microsoft Dynamics 365 Business Central. It is available as an online service and on-premises, and Microsoft publishes upgrade and migration guidance from NAV.

Can we continue using NAV after support ends?

Yes. The software does not stop. You take on more of the risk yourself: security, compatibility, recovery and access to people who know the system. Treat it as temporary, with controls and an exit date.

Should we migrate from NAV to Business Central or Odoo?

It depends on your situation. Business Central tends to fit companies built around Microsoft tools that want continuity. Odoo tends to fit companies that want to redesign processes on a broader platform and retire old customizations. A fit-gap analysis of your real requirements should decide it.

Can NAV data be migrated to Odoo?

Yes, through extraction, transformation and import, not a direct conversion. Master data, opening balances and open transactions are normally migrated. History is migrated selectively or archived.

Can Odoo replace NAV accounting?

Often, but it must be validated. Check the localization for your country, your tax and statutory reports, how you use dimensions, and consolidation or multi-currency needs, before you commit.

Can Odoo replace NAV inventory and manufacturing?

Odoo has Inventory and Manufacturing applications that cover locations, lots, serial numbers, bills of materials, operations and work centres. Costing method, bin control, capacity planning and quality processes are the areas to test in a pilot. See our Odoo manufacturing ERP page.

Should we migrate all NAV transaction history?

Usually not. Migrate what operations need, bring summarized balances for comparison, and keep older detail in a searchable read-only archive. Confirm retention rules with your advisors first.

What happens to NAV customizations?

Each one is reviewed. Some are replaced by standard Odoo features, some by a changed process, and some are rebuilt as Odoo modules because the business needs them. None transfers automatically, because NAV and Odoo use different languages and data models.

Can Odoo use our old NAV record identifiers?

Yes. NAV customer, vendor and item numbers can be kept as reference fields, and used as External IDs during import so records link correctly and repeated imports do not create duplicates.

Should we choose Odoo Community or Enterprise?

Decide after the fit-gap. Community has no licence fee, and you take on hosting, upgrades and support. Enterprise adds applications and Odoo's services for a per-user subscription. One database runs one edition, so list the applications you need and check each against Odoo's editions page.

How long does a NAV-to-Odoo migration take?

There is no honest single answer. Duration depends on the number of companies, modules, customizations, integrations, data quality and how much time your own people can give. A phase 1 and 2 assessment produces a schedule you can rely on.

How much does a NAV-to-Odoo migration cost?

It depends on the same drivers. An estimate is credible only after discovery and fit-gap, so be cautious with any fixed figure offered before that work.

Can NAV remain available as a read-only archive?

Yes. Restrict users to read-only access, keep the database backed up, confirm that searches and key reports still work, and assign an owner. Check your NAV licence terms and the support status of the server it runs on.

What should we prepare before requesting an estimate?

Your NAV version, companies, countries and currencies, modules, user count, and lists of customizations, add-ons, integrations and reports. The readiness checklist above covers the full list.