How do you build a business case for leaving Dynamics NAV?

To build a business case for leaving Dynamics NAV, you need to quantify the cost and risk of staying on an unsupported system, compare it against the investment required to migrate, and present a clear path forward that leadership can approve with confidence. The case typically covers end-of-support risk, total cost of ownership, operational limitations, and the strategic value a modern ERP platform delivers. The sections below address the most common questions organisations ask when building that case.

What happens to Dynamics NAV when Microsoft ends support?

Microsoft has ended mainstream support for all versions of Dynamics NAV, with extended support for the final on-premises version (NAV 2018) having concluded in January 2023. This means Microsoft no longer releases security patches, bug fixes, or regulatory updates for NAV. Organisations still running NAV in 2026 are operating on a platform that no longer receives official protection or compliance updates.

In practice, this creates several compounding problems. Tax law changes, VAT rule updates, and local compliance requirements can no longer be handled through standard Microsoft updates. Your IT team or partner must build and maintain custom fixes, which increases cost and introduces risk with every change. As the NAV ecosystem shrinks, it also becomes harder to find qualified consultants who still work with the platform, and integration with newer Microsoft tools such as Power BI, Teams, and Azure becomes increasingly limited or unstable.

Staying on an end-of-life ERP is not just a technical inconvenience. It is a business continuity risk that grows with every passing year.

What are the financial risks of staying on Dynamics NAV?

The financial risks of staying on Dynamics NAV fall into three categories: rising maintenance costs, compliance exposure, and opportunity cost. Together, these often make the status quo more expensive than migrating, even before accounting for the strategic upside of a modern platform.

Rising maintenance costs are the most visible. Without vendor support, every update or fix requires custom development. Partners who still support NAV charge a premium for this work, and the complexity grows as the gap between NAV and current Microsoft infrastructure widens.

Compliance exposure is harder to quantify but carries real financial consequences. If your NAV system cannot keep pace with tax, financial reporting, or data protection requirements in the countries you operate in, the liability sits with your organisation. Audits, penalties, and remediation costs can be significant.

Opportunity cost is often underweighted in business cases. NAV’s reporting capabilities, automation options, and integration ecosystem are limited compared to Dynamics 365 Business Central. Every month spent on NAV is a month in which finance teams work around system limitations, data is exported manually, and decisions are made on delayed information. Understanding your ERP transformation options early helps you put a realistic number on what staying put is actually costing the business.

What should a business case for an ERP migration include?

A strong ERP migration business case includes a current-state assessment, a cost-benefit analysis, a risk comparison, a recommended migration approach, and a governance structure. It should give decision-makers enough clarity to commit budget and resources without requiring them to understand every technical detail.

The core components are:

Current-state assessment: What version of NAV are you running, how many users, which processes depend on it, and where are the known pain points?
Cost of staying: Maintenance fees, custom development, compliance risk, and productivity losses on the current system.
Cost of migrating: Licensing, implementation, data migration, training, and post-go-live support.
Expected benefits: Process efficiency, reduced manual work, improved reporting, better integration, and compliance confidence.
Risk assessment: What are the risks of migrating, and how are they mitigated? What are the risks of not migrating?
Recommended approach: Upgrade to Business Central, replace with a different ERP, or a phased migration strategy.
Timeline and governance: Who owns the project, what are the key milestones, and how will progress be reported?

Before committing to a roadmap, many organisations benefit from a structured maturity assessment that gives them a clear baseline of where they actually stand. This prevents the common mistake of building a business case on assumptions rather than facts, which tends to unravel once the project starts.

What’s the difference between upgrading NAV to Business Central and replacing it entirely?

Upgrading NAV to Business Central means moving to Microsoft’s current cloud-based ERP platform, which is the natural successor to NAV and shares the same underlying architecture. Replacing NAV entirely means selecting a different ERP system, such as SAP S/4HANA or another platform, and treating the migration as a full system replacement rather than an upgrade path.

For most mid-market organisations already on NAV, the Business Central upgrade path offers a faster, lower-risk route. The data model is familiar, many NAV customisations can be migrated or replicated, and Microsoft partners with NAV experience can translate that knowledge directly. The migration from Dynamics NAV to Business Central is still a significant programme of work, but it carries less organisational disruption than a full platform switch.

A full replacement makes sense when the business has outgrown what Business Central can offer, when the organisation operates at a scale or complexity that requires SAP-level functionality, or when a merger or acquisition has introduced a different ERP standard across the group. In those cases, the business case needs to account for a longer timeline, higher implementation cost, and deeper change management requirements.

The right answer depends on your current process complexity, your integration landscape, and your long-term growth plans. Both paths require careful planning, but they carry very different cost and risk profiles.

Who needs to approve a Dynamics NAV migration business case?

A Dynamics NAV migration business case typically requires approval from the CFO or Finance Director, the CIO or IT Director, and relevant business unit leads whose operations depend on the system. In many organisations, the CEO or board also needs to sign off, particularly when the investment is material or the programme spans multiple years.

Each stakeholder group has different priorities. Finance will focus on total cost of ownership, return on investment, and budget phasing. IT will scrutinise the technical approach, integration risk, and resource requirements. Business unit leads will want to understand how the migration affects day-to-day operations and what the go-live transition looks like. The board or C-suite will want confidence that the programme is governed properly and that delivery risk is managed.

A well-structured business case addresses all of these audiences without requiring separate documents. It leads with the strategic rationale, supports it with financial analysis, and closes with a clear governance and delivery model. Including a section on how cutover and data migration risk will be managed is particularly effective with technically cautious stakeholders, as these are the phases that most often cause concern at board level.

How Optinus helps you build and deliver a NAV migration business case

We work with organisations at every stage of a Dynamics NAV migration, from building the initial business case to managing the full programme through to post-go-live support. Our approach is practical and grounded in hands-on experience from real ERP migrations at leading multinationals, not just methodology frameworks.

Maturity assessment: We give you a clear, evidence-based picture of where your organisation stands before any budget is committed, so the business case reflects reality rather than assumptions.
Business case development: We help you structure the cost-benefit analysis, risk comparison, and migration approach in a format that works for finance, IT, and the board.
Data migration management: We use rigorous As-Is/To-Be analysis and testing procedures to protect data integrity throughout the transition.
Cutover management: We plan and monitor the go-live transition in detail, with hypercare and aftercare included, so operational continuity is never at risk.
Change management: We address both the technical and human side of the migration, helping your teams adopt the new system rather than just being trained on it.
Available on-site and remote: We work with organisations across the Netherlands, Belgium, and internationally, adapting to your preferred engagement model.

Whether you are at the earliest stage of exploring a migration or already preparing for programme approval, our ERP migration services cover the full journey from assessment to transformation. Get in touch with us to discuss your situation and find out how we can help you build a business case that gets approved and a migration that delivers.

home|

blog|