Dynamics NAV users have several upgrade options available to them, with the most common path being a migration to **Microsoft Dynamics 365 Business Central**, either in the cloud or on-premises. Microsoft has ended mainstream support for most NAV versions, which means the decision to upgrade is no longer optional for organisations that want to stay secure and supported. The sections below walk through each upgrade path, what it involves, and how to choose the right approach for your situation.
Is Dynamics NAV still supported by Microsoft?
Most versions of Dynamics NAV have reached end of life and are no longer covered by Microsoft’s mainstream support. NAV 2018 was the last version to receive mainstream support, and that ended in January 2023. Extended support for NAV 2018 runs until January 2028, but extended support covers security patches only, not new features or functional updates. Older versions such as NAV 2016 and NAV 2015 have already passed both mainstream and extended support deadlines entirely.
For organisations still running unsupported versions, this creates real operational risk. Without security patches, systems become vulnerable to exploits. Without functional updates, integrations with other platforms and services gradually break down. And without Microsoft support, troubleshooting becomes slower and more expensive.
The Dynamics NAV end of life timeline is a practical trigger for most organisations to evaluate their options, not because the system stops working overnight, but because the cost and risk of staying on an unsupported platform grows steadily over time.
What are the main upgrade paths for Dynamics NAV users?
Dynamics NAV users have three primary upgrade paths: migrating to Business Central in the cloud (SaaS), upgrading to Business Central on-premises, or, in rare cases, staying on NAV with a custom support arrangement. For the vast majority of organisations, the move to Business Central is the right direction, since it is the direct successor to NAV and shares much of the same functional logic.
- Business Central SaaS (cloud): Microsoft hosts and manages the environment. Updates are automatic, and the subscription model replaces upfront licensing costs. This is the path Microsoft actively promotes and invests in.
- Business Central on-premises: Your organisation hosts the system on its own infrastructure. You retain more control over update timing, but you take on responsibility for maintenance and upgrades.
- Staying on NAV: Technically possible but increasingly difficult to justify. Custom support from a partner can extend the lifespan, but it does not resolve the underlying risk of running unsupported software.
The right Dynamics NAV upgrade path depends on your organisation’s size, infrastructure preferences, compliance requirements, and appetite for ongoing IT management. Most mid-to-large organisations find the SaaS route reduces long-term total cost of ownership, while those with strict data residency or regulatory requirements sometimes prefer on-premises.
What is the difference between upgrading to Business Central cloud and on-premises?
The core difference between Business Central cloud and on-premises is who manages the infrastructure and controls the update cycle. With the SaaS version, Microsoft handles hosting, security, backups, and automatic updates twice a year. With on-premises, your organisation or a managed service provider handles all of that.
Beyond infrastructure, there are functional differences worth understanding. The cloud version receives new features first and is the primary focus of Microsoft’s product investment. The on-premises version lags behind in feature releases and requires manual upgrades to stay current.
From a cost perspective, SaaS runs on a per-user monthly subscription, while on-premises involves upfront licensing fees plus ongoing maintenance costs. For organisations without a large internal IT team, SaaS typically reduces operational burden significantly. For those with complex customisations or integrations that are difficult to move to the cloud, on-premises may be a more realistic intermediate step.
How complex is a Dynamics NAV to Business Central migration?
A NAV to Business Central migration ranges from moderately complex to highly complex, depending on how heavily customised your NAV environment is, how many integrations exist, and how much historical data needs to be carried across. Standard NAV functionality maps well to Business Central, but custom code written in C/AL (NAV’s development language) must be rewritten in AL, the language used in Business Central. This is often the most time-consuming part of the technical migration.
Data migration is another area that requires careful planning. Moving master data, open transactions, and historical records from NAV to Business Central involves mapping old data structures to new ones, cleaning data before migration, and running validation cycles to confirm accuracy on the other side. This is where errors are most costly, a poorly executed data migration can disrupt operations from day one.
Organisations that use rigorous As-Is/To-Be analysis before migration, mapping current data structures to the target environment, significantly reduce the risk of data loss or integrity issues. This kind of structured approach to data migration management is what separates a smooth go-live from a troubled one.
Testing is equally important. Business processes that worked in NAV need to be validated in Business Central before go-live, ideally through structured test cycles that cover both standard functionality and any customised workflows.
When should a Dynamics NAV user consider a full reimplementation instead of an upgrade?
A full reimplementation makes sense when your current NAV environment is so heavily customised, outdated, or misaligned with how the business actually operates today that upgrading the existing system would cost more than starting fresh. It also applies when an organisation has grown significantly since the original NAV implementation and the system no longer fits the business model.
Signs that a reimplementation may be the better choice include:
- Extensive custom development that is difficult or expensive to replicate in Business Central
- Business processes that have changed substantially since NAV was implemented
- Multiple legal entities, currencies, or geographies that NAV was never properly configured to handle
- A desire to use the migration as an opportunity to standardise and optimise processes before embedding them in the new system
A reimplementation is a larger investment upfront, but it avoids carrying legacy problems into the new environment. Before committing to either path, it is worth conducting a proper assessment of your current system’s state, what works, what does not, and what the business actually needs going forward. Starting with a maturity assessment gives organisations a clear baseline before any budget or roadmap is committed, which prevents costly decisions made without full visibility.
How Optinus helps with your Dynamics NAV upgrade
We work with organisations navigating exactly this kind of decision, whether that means a technical upgrade to Business Central, a full reimplementation, or a structured assessment to figure out which path makes sense first. Our consultants have hands-on experience from real Microsoft Dynamics migrations at leading multinationals, not just theoretical frameworks.
- Maturity assessment to establish where your current environment stands before any roadmap is committed
- Data migration management using rigorous As-Is/To-Be analysis and testing procedures to prevent data loss and errors
- Test management to validate business processes in Business Central before go-live
- Cutover management with real-time monitoring and hypercare included, so operational continuity is never at risk
- Change management to drive genuine user adoption across the organisation, not just deliver training
We cover the full Microsoft Dynamics transformation journey, from the initial assessment through to post-go-live support, and we work both on-site and remotely across the Netherlands, Belgium, and internationally. If you are evaluating your Dynamics NAV upgrade options and want to talk through what the right path looks like for your organisation, get in touch with us and we will help you map it out.
Gerelateerde artikelen
- How does SAP S/4HANA handle data differently than older ERP systems?
- What is the role of industry best practices in transformation?
- How do you create a transformation decision log?
- How do you handle custom development in ERP transformation?
- What support is needed after a business transformation goes live?