Dynamics NAV
Navision
Dynamics GP
Dynamics SL
Dynamics AX
Business Central
ERP Software | Herbst Software

Dynamics NAV
End of Life

ERP Alternatives for Operational Businesses

A practical guide for NAV, Navision, GP, SL and AX users weighing up Business Central, operational ERP alternatives and the option to stay put.

Reading time
~12 min
Topic
ERP migration
Audience
NAV / GP / SL / AX users
The decision facing NAV users

For many businesses still using Microsoft Dynamics NAV, often still referred to as Microsoft Navision, the next ERP decision is becoming harder to ignore.

NAV has been a strong operational ERP system for a long time. Many distribution, stock-heavy, manufacturing, food, engineering and service-led businesses have built important processes around it. For some, it still sits at the centre of purchasing, stock control, sales order processing, finance, reporting and day-to-day operations.

But the ERP landscape around NAV has changed.

Microsoft has moved its business applications strategy towards Dynamics 365 Business Central and other cloud-led Dynamics 365 products. At the same time, older Microsoft ERP systems such as Dynamics NAV, Dynamics GP, Dynamics SL and Dynamics AX are moving through reduced support, extended support or end-of-support phases depending on the product and version.

That does not mean every business has to rush into a decision. It also does not mean Business Central is the wrong path. For many companies, Business Central may be the right next step.

But for operational businesses with complex stock, distribution, purchasing, production, fulfilment or deployment requirements, it is worth reviewing the options carefully before committing to a migration path.

Who this is for

Practical questions, real answers.

This guide is written for NAV, GP, SL and AX users who are asking practical questions:

01 Is Dynamics NAV being discontinued?
02 What is Microsoft Navision called now?
03 When does NAV support end?
04 Do we have to move to Business Central?
05 What are the alternatives to NAV, GP, SL or AX?
06 What should we look for in a replacement ERP?

At Herbst, we work with businesses that need ERP software to support real operations, not just accounting or administration. That means stock visibility, purchasing control, sales order management, operational reporting and joined-up processes across the business.

This article explains what legacy Microsoft ERP users should consider before making their next move.

Quick explainer

Common questions about NAV, Navision and Microsoft ERP end of life

Q01

What is Microsoft Navision called now?

Microsoft Navision became Microsoft Dynamics NAV. The product later evolved into what is now Microsoft Dynamics 365 Business Central.

Many businesses still use the name Navision because that is what the system was called when they first implemented it. In practical terms, when people search for "Navision replacement", "Microsoft Navision discontinued" or "Dynamics NAV end of life", they are usually researching the future of their existing NAV environment and whether they should migrate, upgrade or replace it.

Q02

Is Dynamics NAV being discontinued?

Yes, Dynamics NAV is no longer Microsoft's current strategic ERP product for new implementations. Microsoft's focus has moved towards Dynamics 365 Business Central.

The important point is that support depends on the version of NAV being used. For example, Dynamics NAV 2018 entered mainstream support after release, but mainstream support has now ended and extended support is scheduled to end in January 2028.

For businesses still running older NAV versions, the support position may be more limited.

Q03

When does Dynamics NAV support end?

For Dynamics NAV 2018, Microsoft lists the mainstream end date as 10 January 2023 and the extended end date as 11 January 2028.

Businesses on older versions of NAV should check their specific version and support arrangement. The practical question is not only "when does support end?" but also "how much risk, cost and operational friction are we accepting by staying where we are?"

Q04

Do businesses have to move to Business Central?

No business should assume there is only one route forward.

Business Central may be the right option for many NAV users, especially where the business wants to stay within the Microsoft ecosystem and is comfortable with the migration path, licensing model, deployment approach and process changes involved.

However, operational businesses should also review ERP alternatives. If the business relies heavily on stock control, purchasing, distribution, production, industry-specific workflows or on-premise/hybrid flexibility, it may be worth comparing Business Central with a more operationally focused ERP system before committing.

Q05

What alternatives exist to NAV, GP, SL and AX?

The main options are usually:

  1. 1. Stay on the current legacy Microsoft ERP system for now.
  2. 2. Move to Dynamics 365 Business Central or another Microsoft Dynamics 365 product.
  3. 3. Move to another ERP platform that better fits the business's operational model.

The right answer depends on complexity, risk, budget, internal resources, integrations, reporting requirements and how much operational change the business can absorb during migration.

Why this conversation

Why legacy Microsoft ERP systems are being reviewed

Many Microsoft ERP users are not reviewing their systems because they suddenly dislike them. In many cases, the opposite is true. The ERP has supported the business for years.

The challenge is that legacy ERP environments tend to become more fragile over time.

Businesses may start to face issues such as:

⚠
reduced support availability
⚠
rising maintenance costs
⚠
dependence on older infrastructure
⚠
fewer specialists available to support the system
⚠
difficulty integrating with newer tools
⚠
reporting limitations
⚠
security and compliance concerns
⚠
expensive customisation dependencies
⚠
pressure to move towards cloud ERP
⚠
disruption risk during major upgrades

For NAV users, this can feel particularly difficult. NAV was often implemented deeply into the business. Many companies have custom processes, reports, integrations and workflows built around it. Replacing it is not just a software decision. It is an operational decision.

That is why we believe the conversation should not start with "which software should we buy?" It should start with:

The better question

What does the business need the next ERP system to control, connect and improve?

For some companies, the answer will lead naturally to Business Central. For others, especially those with strong stock, distribution or operational control requirements, it may be worth reviewing alternatives.

Lifecycle overview

Microsoft ERP support timeline overview

Support timelines vary by product and version...

Microsoft ERP system
Current practical position
Key planning point
Dynamics NAV / Navision
This guide focus
NAV has been succeeded by Dynamics 365 Business Central. NAV 2018 mainstream support has ended, with extended support scheduled to end in January 2028.
NAV users should review whether Business Central or another ERP alternative is the better operational fit.
Dynamics GP
Microsoft has announced that Dynamics GP support will end on 31 December 2029, with security updates and patches available, if needed, until 30 April 2031.
GP users have a planning window, but should not leave ERP replacement decisions too late.
Dynamics SL
Dynamics SL users should review lifecycle status by version. Microsoft has directed many SL users towards Business Central as a modernisation path.
SL replacement planning should focus on project, finance, operational and reporting requirements.
Dynamics AX
Mainstream and extended support have already ended for several older AX versions, including AX 2009 and AX 2012 variants.
AX users should review risk, infrastructure, security, integrations and migration complexity.

The key issue is not only the date on a Microsoft lifecycle page. The more important business question is whether the existing system still supports the way the company operates today.

If the ERP system is becoming difficult to maintain, difficult to integrate, or difficult to report from, the business may already be paying the cost of delay.

Migration realities

Common challenges with moving from NAV to Business Central

Business Central is a strong and widely used ERP option. It may be the most straightforward route for some NAV users, especially if they want to stay close to Microsoft technologies.

However, a Business Central migration should not be treated as a simple version upgrade.

For many NAV users, moving to Business Central can involve process review, data migration, extension redevelopment, reporting changes, user retraining and changes to how customisations are handled.

Common challenges include:

01

Customisations may not transfer easily

Many NAV systems have been customised over years. These customisations may support very specific operational processes.

Before moving to Business Central, businesses need to understand which customisations are still needed, which can be replaced by standard functionality, and which may need to be rebuilt differently.

02

Operational workflows may need to change

A migration is often presented as a software move, but operational teams experience it as a change in how they work.

Purchasing, stock control, dispatch, production, finance and reporting may all be affected.

03

Costs can extend beyond licensing

Licensing is only one part of the decision. Businesses also need to consider implementation, data migration, customisation, training, testing, integrations, reporting and internal project time.

04

Deployment preferences matter

Some businesses are ready for a cloud-first ERP approach. Others still require on-premise or hybrid flexibility due to infrastructure, control, connectivity, industry or operational requirements.

The deployment model should fit the business, not the other way around.

05

Operational fit should come before brand familiarity

It can feel natural to stay in the Microsoft ecosystem. But the right ERP decision should be based on process fit, operational control, reporting needs, total cost and implementation risk.

For businesses with complex stock, purchasing or distribution requirements, this comparison deserves careful attention.

Decision framework

What are your options?

Most legacy Microsoft ERP users have three broad choices.

Option 01

Stay on legacy ERP

When it may make sense

The system is stable, support is available, risk is understood and no immediate operational change is needed.

Risks to consider

Support limitations, security exposure, rising maintenance costs, integration issues and increasing reliance on legacy knowledge.

Option 02

Move to Business Central

When it may make sense

The business wants to stay within the Microsoft ecosystem and Business Central fits operational, financial and deployment needs.

Risks to consider

Migration complexity, customisation changes, process disruption, training requirements and cost.

Option 03

Move to another ERP platform

When it may make sense

The business needs stronger operational fit, stock control, distribution workflows, industry functionality or deployment flexibility.

Risks to consider

Requires careful vendor evaluation, migration planning and change management.

There is no single right answer for every business.

The wrong approach is to move because of pressure alone. The better approach is to review the current system, define operational requirements, compare options and make a controlled decision.

Self-assessment

Signs you should review ERP options

A business does not need to wait until the final support date to start reviewing ERP options.

It may be time to assess your next move if:

your NAV system depends heavily on old customisations
support is becoming harder to find
reporting is slow, manual or spreadsheet-heavy
stock accuracy is difficult to trust
purchasing is disconnected from stock and finance
users rely on workarounds outside the ERP
integrations are fragile or expensive to maintain
operational teams are duplicating data entry
finance lacks real-time visibility into operations
the business is growing beyond the system’s current structure
management cannot get reliable reporting quickly
cloud migration is being discussed but not fully understood

These issues are not just IT problems. They affect ordering, fulfilment, customer service, cash flow, purchasing, stock availability and management decision-making.

For operational businesses, ERP replacement should be treated as a business control project, not just a software project.

Replacement criteria

What to look for in a NAV replacement ERP

When reviewing NAV replacement ERP options, the goal is not to find the newest system...

Here are the areas we believe operational businesses should review carefully.

01

Stock control

If stock sits at the centre of your business, the ERP must give clear visibility over quantities, movement, availability, locations and value.

A replacement ERP should support stock control with real-time visibility so teams can make better purchasing, sales and fulfilment decisions.

02

Purchasing and supplier management

Purchasing should not sit apart from operations. Purchase orders, supplier records, goods received, stock updates and finance should work together.

This is especially important for businesses where purchasing decisions affect margins, stock availability and customer delivery.

03

Sales order processing

Sales teams need confidence in what can be sold, when it can be delivered and how orders affect stock and finance.

A good ERP system should connect sales activity with fulfilment, invoicing and reporting.

04

Integrated inventory management

Operational businesses need more than stock records. They need connected inventory management across departments.

That means stock, purchasing, sales, finance and reporting should share the same core data. This is where integrated inventory management across the organisation becomes important.

05

Distribution and fulfilment

For distributors, the ERP must support the movement of goods through the business.

That includes order management, dispatch, delivery planning, stock visibility, pricing, customer records and reporting. Businesses in this space should review whether they need distribution ERP software for connected operations, rather than a system designed mainly around finance.

06

Industry-specific workflows

Food and drink, agri, quarry, engineering, manufacturing and distribution businesses often need workflows that generic ERP systems do not handle well without significant configuration.

For example, a food or drink business may need stronger control over stock, batches, purchasing and traceability. In that case, food and drink software with integrated stock control may be a more useful reference point than a generic ERP comparison.

07

Reporting and management visibility

The next ERP should help management understand what is happening across the business.

If teams still need to export data into spreadsheets to understand stock, sales, purchasing or margin, the ERP may not be doing enough.

08

Deployment flexibility

Some businesses want cloud ERP. Others need on-premise or hybrid flexibility.

The right deployment approach depends on operations, infrastructure, connectivity, security, internal resources and business preference.

09

Implementation support

ERP replacement is not only about the software. It is about implementation, data, people and process.

The right partner should understand how the business works and help reduce disruption during migration.

Asking the right question

Business Central vs operational ERP alternatives

Business Central may be the right path for many Microsoft ERP users. It has the advantage of being part of the Microsoft ecosystem, and many businesses will value that continuity.

However, operational businesses should compare Business Central against ERP alternatives before making a final decision.

The question is not

Is Business Central good or bad?

The better question

Is Business Central the best fit for our operational requirements, deployment preferences and migration risk?

A business with straightforward finance-led requirements may reach a different conclusion from a business with complex stock, distribution, purchasing, production or industry-specific workflows.

This is where operational ERP alternatives should be reviewed.

If the business needs strong control over stock, purchasing, sales, distribution and operational reporting, the ERP should be assessed against those requirements first.

For a broader understanding of how ERP connects the business, it may also be useful to review how an ERP system connects inventory and operations and what software management in business means in a practical operational context.

The Herbst position

Why Herbst Insight is a strong fit for operational businesses

At Herbst, we focus on ERP software for businesses that need practical control across operations.

That includes businesses where stock, purchasing, sales, finance, reporting and day-to-day workflows need to work together in one connected environment.

For NAV users reviewing their next move, Herbst Insight may be a strong fit where the business:
needs operational ERP capability, not only finance functionality
wants strong stock and purchasing control
relies on distribution, fulfilment or industry-specific workflows
needs better visibility across departments
wants practical reporting without excessive manual work
prefers a more flexible ERP conversation than a default migration path
needs an ERP partner that understands operational complexity

We are not suggesting that every NAV, GP, SL or AX user should avoid Business Central. That would be too simplistic.

Instead, we believe businesses should review the options properly.

If Business Central is the right fit, that will become clear through the review process. But if your business has complex operational requirements, it is worth discussing whether an operational ERP alternative could offer a better fit, a more practical implementation path or stronger day-to-day control.

Pre-decision review

ERP migration considerations before you decide

Whether you move from NAV to Business Central, replace GP, review SL, migrate away from AX or explore another ERP system, the migration process needs careful planning.

Before choosing a platform, review these areas.

01

Data

What data needs to move? What should be cleaned first? What historical data is actually useful?

Poor data migration can create problems long after go-live.

02

Processes

Which processes should be preserved, improved or removed?

A migration is an opportunity to simplify, but businesses should avoid losing important operational controls.

03

Customisations

Which customisations are business-critical? Which are old workarounds? Which can be replaced with standard ERP functionality?

04

Reporting

What reports does management actually use? Which reports are manual today? What visibility is missing?

05

Integrations

What systems need to connect with ERP? This may include ecommerce, CRM, finance tools, warehouse systems, production tools, reporting platforms or industry-specific applications.

06

Users

Which teams will be most affected? Purchasing, warehouse, sales, finance, operations and management may all experience the migration differently.

07

Timing

ERP migration should be planned around business cycles, seasonal pressure, stock periods, financial year-end and team availability.

08

Risk

Every ERP project carries risk. The goal is not to pretend risk does not exist. The goal is to identify it early and manage it properly.

Twelve questions

A practical ERP review checklist

Before deciding your next move, ask:

  1. 01
    What version of NAV, GP, SL or AX are we currently running?
  2. 02
    What is our current support position?
  3. 03
    Which parts of the system are business-critical?
  4. 04
    Where are teams using spreadsheets or manual workarounds?
  5. 05
    Which integrations are essential?
  6. 06
    How reliable is our stock information?
  7. 07
    How well do purchasing, stock, sales and finance connect?
  8. 08
    What reporting does management need but cannot get easily?
  9. 09
    Do we want cloud, on-premise or hybrid flexibility?
  10. 10
    What operational disruption can we tolerate during migration?
  11. 11
    Is Business Central the best fit, or should we compare operational ERP alternatives?
  12. 12
    What would a successful ERP replacement look like 12 months after go-live?

This checklist helps shift the conversation from software pressure to business fit.

Frequently asked questions

FAQ: Dynamics NAV end of life and ERP replacement

Microsoft Navision evolved into Dynamics NAV, and Dynamics NAV has since been succeeded by Dynamics 365 Business Central. Many businesses still use the Navision name, but Microsoft’s current strategic ERP direction is Business Central and Dynamics 365.

The system does not suddenly stop working. However, businesses may face reduced support, limited updates, higher maintenance complexity, security concerns and increasing difficulty integrating with newer systems. The practical risk grows over time.

No. Business Central is one option, and it may be the right choice for many businesses. However, NAV users should also review ERP alternatives, especially if they have complex stock, distribution, purchasing or deployment requirements.

The best ERP replacement depends on the business. A finance-led company may need one type of system, while a stock-heavy or distribution-led business may need a more operational ERP platform. The right choice should be based on process fit, reporting, stock control, deployment needs, implementation risk and long-term support.

Yes. Businesses using Dynamics GP, SL or AX can review Microsoft migration paths, including Business Central or other Dynamics 365 products, as well as non-Microsoft ERP alternatives. The best route depends on system complexity, operational requirements, integrations, budget and risk.

Some ERP platforms still support on-premise or hybrid deployment models. This may matter for businesses with specific infrastructure, control, connectivity or operational requirements. The key is to make deployment part of the ERP review, rather than assuming cloud is the only suitable option.

Talk through your migration options

Talk through your migration options

If you are using Dynamics NAV, Navision, GP, SL or AX and are reviewing your next ERP move, it is worth taking time to compare the options properly.

Business Central may be the right path. But if your business depends on stock control, purchasing, distribution, operational reporting or industry-specific workflows, an operational ERP alternative may also deserve serious consideration.

At Herbst, we can help you talk through your migration options and review whether Business Central or an operational ERP alternative is the better fit for your business.

If you are using Dynamics NAV, Navision, GP, SL or AX and are reviewing your next ERP move, it is worth taking time to compare the options properly.

Talk through your migration options with Herbst