When Dynamics NAV nears end of life, the first thing an IT director should do is assess where the organisation actually stands: what version is running, how deeply customised the system is, and whether the business is ready to move. The most practical next step is typically a structured migration to Microsoft Dynamics 365 Business Central, which is the direct successor to NAV. The sections below answer the most important questions to help you plan that journey with confidence.
What happens to Dynamics NAV when Microsoft ends support?
When Microsoft ends support for a version of Dynamics NAV, the software continues to run but no longer receives security patches, bug fixes, or regulatory updates. This means organisations running unsupported NAV versions face growing compliance risk, data security exposure, and incompatibility with updated Microsoft infrastructure over time.
Microsoft has been progressively ending mainstream and extended support for NAV versions. As of 2026, several NAV versions, including NAV 2013, NAV 2015, NAV 2016, and NAV 2017, have already passed their extended support end dates. NAV 2018 reached the end of mainstream support in January 2023 and is approaching the end of its extended support window. Running an unsupported ERP system is not just a technical risk; it creates audit exposure and can affect your organisation’s ability to meet regulatory requirements in finance and supply chain.
The practical consequence is straightforward: staying on an unsupported NAV version is not a viable long-term strategy. The longer you wait, the more complex and costly the eventual migration becomes, as the gap between your legacy system and current platform capabilities widens.
What are the options for organisations still running Dynamics NAV?
Organisations still running Dynamics NAV have three main options: upgrade to a newer on-premises NAV version, migrate to Microsoft Dynamics 365 Business Central in the cloud, or move to Business Central on-premises. For most organisations, migrating to Business Central in the cloud is the most future-proof path.
Here is a practical overview of the options:
- Upgrade to a newer NAV version (on-premises): Extends your runway but does not solve the long-term end-of-life problem. Microsoft is not investing in new NAV releases.
- Migrate to Business Central (cloud/SaaS): The recommended path. Gives access to continuous updates, modern integrations, and Microsoft’s full investment in the platform.
- Business Central on-premises: An option for organisations with specific data residency or infrastructure requirements, though it offers fewer automatic updates than the SaaS version.
- Switch to a different ERP platform: Possible, but significantly more complex and costly. Most organisations with existing Microsoft infrastructure benefit from staying within the ecosystem.
Evaluating these options requires a clear picture of your current system, your business processes, and your organisation’s readiness for change. A maturity assessment and ERP transformation services approach gives you that baseline before any budget or roadmap is committed.
What’s the difference between upgrading NAV and migrating to Business Central?
Upgrading NAV means moving to a newer version of the same on-premises platform, preserving your existing architecture and customisations. Migrating to Business Central means moving to a fundamentally different, cloud-native platform that shares NAV’s functional DNA but operates on a modern, continuously updated codebase.
The distinction matters for planning and risk:
- Customisations: NAV upgrades can carry forward existing customisations more directly. Business Central uses extensions rather than core code modifications, so customisations typically need to be rebuilt or replaced.
- Data model: Business Central has a different data structure in several areas, which means data migration requires careful mapping and validation rather than a simple lift-and-shift.
- Ongoing maintenance: Business Central SaaS receives automatic updates twice a year, removing the need to plan and fund future upgrades. NAV on-premises requires manual upgrade cycles.
- Integration landscape: Business Central connects natively with Microsoft 365, Power Platform, and Azure services. NAV integrations often require custom connectors that may not survive the transition unchanged.
For most organisations, a Business Central migration is the right choice despite the higher upfront complexity, because it eliminates the recurring cost and disruption of future NAV upgrades.
How long does a Dynamics NAV to Business Central migration take?
A Dynamics NAV to Business Central migration typically takes between six and eighteen months, depending on the complexity of your current system, the volume of customisations, the number of integrations, and your organisation’s readiness. Simpler environments with limited customisation can move faster; heavily customised multi-entity deployments take considerably longer.
The key factors that affect the timeline include:
- Scope of customisations: Each custom object in NAV needs to be assessed, rebuilt as a Business Central extension, or replaced with standard functionality.
- Data quality and volume: Poor data quality in the source system adds time to the migration and validation phases.
- Number of integrations: Every connected system, payroll, CRM, warehouse management, reporting tools, needs to be mapped and tested against the new environment.
- Organisational readiness: Change management and user training are often underestimated. Teams need time to learn new processes, not just a new interface.
- Testing cycles: Thorough test management and business readiness validation before go-live is non-negotiable and takes time to do properly.
Building a realistic timeline from the start, rather than compressing phases under budget pressure, is one of the most important decisions an IT director can make early in the process.
What should an IT director assess before starting the migration?
Before starting a Dynamics NAV to Business Central migration, an IT director should assess four things: the current system’s technical state, the quality of existing data, the organisation’s process maturity, and internal capacity to support the programme. Skipping this assessment phase is one of the most common reasons ERP migrations run over time and budget.
A structured pre-migration assessment should cover:
- Version and customisation inventory: Which NAV version is running, what customisations exist, and which are actively used versus legacy artefacts.
- Data quality audit: Identifying duplicate records, incomplete master data, and inconsistencies that will cause problems during migration if not resolved beforehand.
- Process mapping: Documenting current business processes (As-Is) and defining the target state (To-Be) in Business Central, including any process changes the migration should enable.
- Integration mapping: Listing all systems connected to NAV and defining how each will connect to Business Central.
- Stakeholder and change readiness: Understanding which business units are most affected, who the key users are, and what level of change management support will be needed.
- Internal capacity: Being honest about whether the internal team has the bandwidth and expertise to run the programme alongside day-to-day operations.
This assessment phase is not overhead, it is the foundation that makes everything else predictable. Without it, scope creep, data issues, and stakeholder misalignment surface mid-project when they are far more expensive to resolve.
How Optinus helps with Dynamics NAV end-of-life planning and Business Central migration
We work with IT directors and ERP programme managers at mid-to-large organisations navigating exactly this situation: a legacy NAV environment that needs to move, a board expecting delivery on time and on budget, and a team that needs a partner who has done this before. Here is what we bring to a Dynamics NAV to Business Central migration:
- Maturity assessment: We start by giving you a clear baseline, where your system, data, and organisation actually stand before any budget or roadmap is committed.
- Project and programme management: Our consultants have hands-on experience from real ERP migrations at leading multinationals, not just methodology frameworks. We manage the full programme from initiation to post-go-live.
- Data migration management: We use rigorous As-Is/To-Be analysis and testing procedures to prevent data loss and errors during the transition to Business Central.
- Cutover management: We plan and monitor the go-live cutover end-to-end, including hypercare and aftercare, so operational continuity is never at risk.
- Change management: We address both the technical and human side of the transformation, driving genuine adoption across the organisation rather than just delivering training.
- Flexible delivery: We work on-site and remotely, across the Netherlands, Belgium, and internationally.
If you are preparing for a Business Central migration or need clarity on where to start, explore our ERP transformation and migration services to see how we structure the journey. Ready to discuss your specific situation? Contact us and we will help you build a realistic plan from day one.
