Dynamics NAV End of Support and the ERP Decision Ahead
If your company runs Microsoft Dynamics NAV, the approaching end of support is going to create a technology decision. For some Dynamics NAV organizations, moving to Microsoft Dynamics 365 Business Central will be the logical next step. The existing environment is relatively straightforward, the required functionality carries forward well, the partner understands the business, and the transition can be managed without fundamentally redesigning the ERP environment.
For other Dynamics NAV companies, the move involves converting customizations, reconsidering add-ons, changing integrations, migrating data, changing licensing, retraining users, and redesigning processes that have developed around NAV over many years. For this group, its more than an upgrade decision. It is making an ERP decision.
Dynamics NAV Support Deadlines Create a Clear Planning Window
Microsoft’s published support dates give Dynamics NAV customers a defined timeframe for planning what comes next.
Dynamics NAV 2016 reached the end of extended support on April 14, 2026.
Dynamics NAV 2017 reaches the end of extended support on January 12, 2027
Dynamics NAV 2018 follows on January 12, 2028.
End of support does not mean the ERP system stops working on that date. It means Microsoft no longer provides the same level of product support and security updates, which increases the operational and technology risk of remaining on the platform over time.
For leadership teams, these dates are important planning milestones. They provide a clear timeframe to assess the current Dynamics NAV environment, understand the scope of change ahead, evaluate the proposed path forward, and plan accordingly if a broader ERP selection is warranted before committing to a major transition.
The Risk Comes From Treating Business Central as the Default Replacement
I spent eight years helping build a Microsoft Dynamics practice at a large public accounting firm, so I understand why the Microsoft Dynamics 365 Business Central conversation happens the way it does.
If you ask a Microsoft Dynamics partner what comes after Dynamics NAV, Business Central is a logical recommendation. It is Microsoft's current ERP platform for many organizations in the Dynamics NAV customer base. Dynamics partners have invested in the product, their consultants understand it, and many have successfully moved NAV customers onto it.
That expertise has real value.
A Microsoft Dynamics 365 Business Central recommendation from your existing partner is therefore an important input into the decision. It just does not eliminate the buyer's responsibility to determine whether the proposed future environment still fits the business. The more change required to get there, the more important that validation becomes.
Understand the Scope of Change Ahead
A move from Dynamics NAV to Dynamics 365 Business Central can involve much more than moving to a newer version of the software. The extent of the change depends on how heavily the current environment has been adapted over time and how closely those decisions still align with the needs of the business.
Customizations, add-on applications, integrations, reporting, data, and business processes may all need to be reviewed as part of the transition. Some may carry forward with relatively little change. Others may need to be redesigned, replaced, or retired.
That review creates an important opportunity for leadership. Rather than automatically recreating everything that exists in Dynamics NAV today, the organization can determine which capabilities still provide value, which can be handled differently in Dynamics 365 Business Central, and which no longer need to be part of the future environment.
The greater the amount of change, the more the project begins to resemble a new ERP implementation rather than a routine upgrade. That is the point where it becomes important to step back, validate the future business requirements, and confirm that the proposed path still represents the right fit.
Let the Business Define the Decision Before the Product Defines the Answer
Before committing to a future ERP path, leadership needs a clear picture of what the business will require over the next several years.
Where does the current Dynamics NAV environment support the business well today? Where does it create constraints, workarounds, manual effort, limited visibility, or difficulty scaling? Which customizations still support important business needs? Which integrations are critical? Where does the organization need stronger automation, controls, reporting, or operational visibility?
Those requirements create the basis for evaluating the next ERP environment. The proposed Dynamics 365 Business Central path can be evaluated against them, along with other ERP options when the scope of change, business needs, or level of investment warrants a broader review.
Questions Executives Can Ask Before Approving the Next ERP Path
How much of our current Dynamics NAV environment will need to be redesigned, replaced, converted, or retired?
Which current capabilities are still important to the business, and how will the proposed solution address them?
Which third-party applications and integrations are expected to remain, change, or be replaced?
Which business processes are expected to work differently in the future environment?
What business requirements were used to evaluate and recommend the proposed ERP path?
What systems and applications will be required to support the future-state business processes?
What will the five-year cost look like across software, implementation, applications, integrations, support, and internal resources?
What experience does the proposed implementation team have with organizations of similar size, industry, and complexity?
Which business requirements or areas of the solution present the greatest implementation risk?
If the scope of change is substantial, what other ERP options have been considered and how were they evaluated?
Use these answers to understand the scope, cost, risk, and business impact of the proposed path forward. Combined with documented business requirements, they give leadership a consistent basis for evaluating the options and making a well-supported ERP decision.
Evaluate the Implementation Partner as Part of the Decision
The software decision and the implementation partner decision are closely connected, but they require separate evaluation.
A move from Dynamics NAV to Dynamics 365 Business Central can involve changes to customizations, integrations, supporting applications, reporting, data, and business processes. The implementation team needs experience managing that broader transition, not just familiarity with the software.
Look beyond the firm’s overall credentials and understand who will actually be assigned to the project. Evaluate the proposed team’s experience with organizations of similar size, industry, complexity, and operating model, along with their ability to manage integrations, solution design, data migration, testing, and business process change.
Use Dynamics NAV End of Support as a Decision Point
Microsoft’s lifecycle dates create a reason to act, but they do not determine the right ERP path for the business.
For some organizations, the evaluation will confirm Dynamics 365 Business Central and the existing Dynamics partner. For others, the scope of change, future business requirements, cost, or implementation risk may justify evaluating additional ERP options before committing to the transition.
The value comes from making that decision with a clear understanding of what the business needs next, how much of the current Dynamics NAV environment will change, and which solution and implementation approach best support the future state.
John Hannan LLC works from the client-side and helps organizations assess their current environment, define future requirements, evaluate ERP options, compare solution approaches, and manage software and implementation partner evaluations. We do not sell ERP software, so our role is focused on helping the organization reach the right decision for its business.
If Dynamics NAV end of support is approaching, use the timeline to plan deliberately. Before committing to the next path, understand what the business needs, what will change, and which ERP and implementation approach best support the future. John Hannan LLC can help you evaluate the options and move forward with a well-supported decision.
