Microsoft Dynamics Navision to Business Central Migration: How To Successfully Upgrade Your ERP

  1. Home
  2. Blog Details

Microsoft Dynamics Navision to Business Central Migration: How To Successfully Upgrade Your ERP

If you're still running Microsoft Dynamics NAV, you'll know that extended support ends in 2028. After that, there will be no security updates, regulatory fixes, or official Microsoft support.

This means the question is no longer whether to move, but how to manage the transition smoothly. A Navision to Business Central upgrade is now part of the roadmap. The focus is on planning it correctly, controlling costs, and using the move as an opportunity to modernise rather than simply replicate what you have today.

Let’s walk through it.

Why Moving to New ERP Is Now a Strategic Requirement

With extended support for Microsoft Dynamics NAV ending in 2028, continuing to run Navision long term is no longer possible. After that point, there will be no security updates, regulatory fixes, or official Microsoft support. That means organisations need to plan a move to a supported ERP platform.

For most NAV users, Microsoft Business Central is the most natural progression. It’s built on the same foundations as Navision, but redesigned for the cloud with modern architecture, cleaner customisation through extensions, and ongoing Microsoft investment.

Because Business Central evolved directly from NAV:

  • Core functionality remains familiar
  • Data structures are aligned
  • Migration paths are well-defined
  • User adoption is typically smoother than switching vendors entirely

The transition still requires planning and technical work. But compared to moving to a completely different ERP ecosystem, the shift to Business Central is usually more controlled and less disruptive.

What Actually Happens in a Navision to Business Central Migration?

From the outside, it sounds simple. Upgrade the version and move on. Technically, it’s more structured than that.

A typical migration involves four core workstreams running in parallel:

  • Application upgrade
  • Code conversion
  • Data migration
  • Infrastructure transition

Let’s break those down.

Step 1: Understanding Your Technical Upgrade Path

Depending on your current NAV version, you may not be able to move directly to Business Central in a single step. Older NAV versions require database and application conversions to align with Business Central’s architecture. These conversions may involve intermediate upgrade stages, particularly for systems running versions prior to NAV 2013.

This process typically includes:

  • Database schema conversion
  • Code refactoring from C/AL to AL
  • Object restructuring and extension preparation
  • Compilation and synchronisation testing

For newer NAV versions, the upgrade path is much more streamlined. For older, heavily customised systems, this phase can require more technical planning.

Step 2: Converting Custom Code (C/AL to AL Extensions)

This is where technical complexity often hides.

NAV customisations were traditionally written in C/AL and directly modified the base application. Business Central uses AL extensions instead.

The difference matters.

Extensions sit on top of the base application rather than modifying it directly. That makes future upgrades much cleaner and faster.

During migration, your team will:

  • Analyse existing custom objects
  • Identify unused or redundant modifications
  • Convert necessary code to AL
  • Rebuild functionality as extensions

This is also your opportunity to simplify. Many businesses discover they no longer need half of the customisations they built 8 to 12 years ago. Migrating everything “as is” increases cost and technical debt.

Step 3: Data Migration Strategy (Where Costs Can Escalate)

This is the area where smart decisions save serious money. It’s tempting to migrate all historical data. Ten years of transactions, archived records, everything.

But here’s the reality. The more historical data you migrate:

  • The longer testing takes
  • The more storage costs increase
  • The more performance can be affected
  • The more consulting hours you consume

A smarter approach is structured data scoping.

Many businesses choose to:

  • Migrate 1 to 3 years of detailed transactional data
  • Keep older data in a read-only archived NAV database
  • Export legacy reports for compliance retention

Finance teams often only need several years of active history for operational use. Older data can remain accessible without bloating your new environment.

This single decision can significantly reduce migration costs.

Step 4: Infrastructure Shift (On-Premise to Cloud)

Most NAV systems run on-premise. Most Business Central deployments are cloud-based.

That shift changes how infrastructure works:

  • No server maintenance
  • Automatic updates
  • Microsoft-managed security
  • Built-in disaster recovery

The technical migration involves:

  • Tenant provisioning
  • Azure Active Directory configuration
  • User permission mapping
  • Integration reconfiguration

If you’re integrating with third-party systems such as WMS, CRM, or manufacturing software, those APIs will need reviewing and potentially rebuilding.

Choosing Your Migration Approach

There are generally two structured approaches.

Technical Upgrade

This upgrades your current database and carries forward configuration, master data, and selected history. It’s faster but preserves legacy structures.

Reimplementation

This treats Business Central as a new system. You rebuild processes, reconfigure chart of accounts, and migrate only selected master data and open transactions.

It takes more change management but often results in a cleaner system.

If your NAV environment is heavily customised and over 10 years old, reimplementation is often more cost-effective long term. Our implementation guide will show you how to plan and execute a Business Central implementation

Practical Migration Tips That Reduce Risk and Cost

This is where experience really matters.

Here are proven ways to keep your Navision to Business Central migration under control:

  • Do not migrate unnecessary historical transactions
  • Archive instead of transfer wherever possible
  • Eliminate unused customisations before conversion
  • Standardise processes rather than recreating workarounds
  • Test integrations early, not at the end
  • Involve finance in data validation from day one

One common mistake is leaving data reconciliation until just before go-live. Your finance team should validate balances after each test migration cycle. That avoids last-minute surprises.

Timeline Expectations

A realistic timeline depends on complexity. For smaller environments with limited customisation, expect 2 to 4 months. For larger, multi-entity systems with integrations and heavy code conversion, expect anywhere from 4 to 12 months or more.

Rushing an ERP migration increases both cost and operational disruption. Starting earlier gives you room to plan properly.

What About Licensing Changes?

NAV used perpetual licenses. Business Central uses a subscription model.

That shifts ERP from capital expenditure to operational expenditure. Finance teams should model this carefully, especially if moving to full SaaS.

The benefit is predictable costs and automatic upgrades. The trade-off is ongoing subscription commitment. For more info on costs, check out our detailed Business Central pricing guide.

Or, if you’d like more certainty on your ongoing costs, check out our business central pricing calculator below where you can get a personalised quote depending on your business requirements.



Security and Compliance Considerations

Post-2028, unsupported NAV systems will not receive security patches. For organisations in regulated industries, that alone creates compliance exposure.

Business Central provides:

  • Regular security updates
  • GDPR-aligned data controls
  • Role-based access management
  • Audit trail enhancements

For IT leaders, this alone often justifies the migration timeline.

So When Should You Start?

You don’t need to migrate tomorrow. But you shouldn’t wait until 2027 either.

Implementation partners, internal resources, and testing capacity all become constrained when deadlines approach.

Starting now allows you to:

  • Audit your current NAV environment
  • Budget properly
  • Phase customisation conversion
  • Reduce historical data volume
  • Plan user training gradually

It turns a forced upgrade into a controlled modernisation.

Final Thoughts

A Navision to Business Central migration is not just a version upgrade. It’s a technical transition from legacy architecture to a cloud-first platform. With extended support ending in 2028, staying on NAV indefinitely isn’t viable. But with structured planning, careful data scoping, and smart code conversion, the move to Business Central can be cleaner and more cost-effective than many businesses expect.

If you approach it strategically, it becomes less about replacing software and more about setting your ERP up for the next decade. As Navision and Business Central implementation specialists, we can support you along the entire migration process. Just fill in our contact form and one of our experts will be in touch.