techone --guide=nav-to-bc
Migrating Navision (Dynamics NAV) to Dynamics 365 Business Central
The move can use a full migration path or a reimplementation with selected data. The Dynamics NAV version, C/AL customizations, data, integrations and target operation determine the route.
TL;DR
- Who this guide is for
- Companies on older Microsoft Dynamics NAV (Navision) deciding whether to stay put or move to Dynamics 365 Business Central.
- What it covers
- Which intermediate versions the supported path requires, when to use full migration or reimplementation, and what needs to happen to data and customizations.
- End of support
- Extended support for Dynamics NAV 2016 ended on April 14, 2026. Dynamics NAV 2017 ends on January 11, 2027 and Dynamics NAV 2018 on January 11, 2028. Earlier versions listed here are already out of support.
- Recommended path
- Compare a full migration with C/AL customizations converted to AL against a reimplementation with selected data. Microsoft supports both under different conditions.
- How to start
- A current state analysis: scope of customizations, data volume, integrations. It tells you what to carry over, what to rewrite and what to simplify.
When It Is Time to Move
The lifecycle depends on the version. Supported intermediate upgrade steps matter as well, because older Dynamics NAV versions cannot migrate directly to the current cloud service.
Dynamics NAV 2009 R2, 2013 and 2015
These versions are past extended support. The official route to Dynamics 365 Business Central online uses several intermediate versions, depending on the source release.
Dynamics NAV 2016
Extended support ended on April 14, 2026. The supported route to the current Dynamics 365 Business Central online service passes through on-premises versions 14 and 25.
Dynamics NAV 2017
Extended support ends on January 11, 2027. This version also requires intermediate releases on the supported route to the current Dynamics 365 Business Central online service.
Dynamics NAV 2018
Extended support ends on January 11, 2028. Plan according to customizations, data and testing needs rather than only the final support date.
What end of support means
After extended support ends, regular security and product fixes are no longer available through the standard lifecycle. The system may continue to run, but more operational and security risk shifts to the customer and its partners.
How the move works
Current Microsoft documentation describes two routes. Full migration carries data and customizations but requires supported on-premises versions and conversion of C/AL customizations to AL. Reimplementation from Dynamics 365 Business Central version 14 transfers only essential business data, opening balances and setup.
The choice follows the value of history, the scope of customizations, data quality and willingness to change processes. A full migration does not mean every old function should be retained. The ERP process analysis guide explains how to prepare the decision.
Current state analysis
What runs as standard in Dynamics NAV and what is a customization. Data volume and quality, the list of integrations and connected systems. Without this, the move is planned blind.
A decision on every customization
For each customization, verify whether current Dynamics 365 Business Central covers it, whether it should be converted to an AL extension or whether the process should work differently.
Prepare the Target Dynamics 365 Business Central Environment
Depending on the route, prepare the intermediate versions, convert extensions, configure target processes and validate integrations.
Cloud migration and go-live
Run and validate repeat data transfers, complete user acceptance testing and prepare cutover. Retain the source system or its data according to the approved archive and fallback plan.
What Data Actually Migrates
Data scope depends on the chosen route. Full migration moves data and customizations through supported intermediate versions. Reimplementation from version 14 moves selected master data, opening balances, setup and a subset of posted history.
Data in tables with custom logic cannot move to the cloud without further work. The relevant customizations need AL extensions and mapping. Inventory custom objects, fields, tables and dependencies before the project.
Master data
Customers, vendors and items are cleaned, validated and mapped before transfer. Exact scope depends on the companies and migration route.
Selected transactions and balances
Open documents, opening account balances and ledgers. The scope is chosen by what you need live from day one.
Setup tables
Code lists, chart of accounts and module setup are transferred or reconfigured according to the chosen route. Area owners need to approve the result.
Customizations and custom fields
Custom C/AL logic is converted to AL extensions. Tools can support part of the conversion, but a developer still resolves conflicts and unsupported parts and tests the result.
Document history
Full migration and reimplementation treat history differently. The live scope follows operational, legal and audit requirements; the rest can remain in a searchable archive.
Where AI Can Help During Migration
AI can help read legacy code, draft transformation scripts or prepare test scenarios. It does not replace Microsoft's supported migration route, control totals or acceptance by responsible users.
Mapping and transformation
AI can help draft transformation code and mapping documentation. Final rules must be explicit, versioned and tested.
Consolidation and cleanup
Suggested duplicates or unusual values can speed review. The owner of the relevant records decides whether data should change.
Validation and reconciliation
Document counts, relationships and balances are checked deterministically. AI may help prepare scripts, but it cannot certify accounting correctness.
AI may speed preparation. Repeatable tests and control totals still have to prove the migration is correct.
Continuity and Proof
The transition also requires integrations, identities, reporting and ownership of ongoing operations to be validated again. Our Dynamics 365 Business Central implementation service covers delivery after discovery, while the ERP integration service covers connected systems.
For IBG we connected Dynamics CRM, Dynamics NAV and SharePoint. For Tesil Fibres we contributed to the Czech part of a Dynamics 365 Finance implementation during a move from Oracle E-Business Suite. These are related Dynamics experiences, not public references for a complete Dynamics NAV to Dynamics 365 Business Central migration.
Frequently Asked Questions
Is it worth starting now, or waiting?
Base the schedule on the support end date for your version, the scope of customizations, required intermediate releases and time for repeat testing. Analysis can compare full migration and reimplementation before you commit to either route.
What is the difference between a new system and an upgrade?
Full migration uses supported intermediate versions and carries data and customizations converted to AL. Reimplementation from Dynamics 365 Business Central version 14 transfers selected business data and setup only. The first retains more history, while the second can reduce legacy customizations; the analysis determines which route fits.
What happens to our customizations?
C/AL logic needs conversion to AL extensions. Tools can support part of the conversion, but a developer resolves conflicts and unsupported parts. For each customization, we also assess whether current standard functionality covers it or the process should work differently.
How does moving the data from Dynamics NAV actually work?
The procedure depends on whether you choose full migration or reimplementation. Both use test transfers, checks of counts, relationships and balances and approval by data owners. Custom tables and fields require corresponding extensions and mapping.
Does the complete data history migrate?
The full migration route is designed to move data and the customized solution through supported intermediate versions. Reimplementation moves selected master data, opening balances, setup and limited history. The scope must meet operational, accounting and audit requirements and include a plan for the source archive.
How long does the move take and how much does it cost?
The source version, required intermediate steps, customizations, data volume, integrations and chosen route determine the schedule and cost. We estimate after inventorying the objects, database and functions in use.
Microsoft Cloud Solution Provider
You handle the move to Dynamics 365 and the licensing with one partner. We go through your situation and take care of both.
Running on old Dynamics NAV?
We will walk through the state of your installation and tell you what the move to D365 BC would involve and in what order.
Book a consultation