Dynamics NAV to Business Central: Upgrade or Reimplement?
Many companies still run Microsoft Dynamics NAV, often heavily customized over many years. Mainstream support for older NAV versions has ended, the talent pool that knows C/AL is shrinking, and Business Central online offers things NAV never could: Microsoft-hosted infrastructure, automatic updates, Power Platform integration and access from anywhere.
The question is how to get there. There are two main paths.
Path 1: Technical upgrade
A technical upgrade carries your existing data, and as much of your setup as possible, forward to Business Central. For older NAV versions this usually means upgrading through intermediate versions, converting C/AL customizations to AL extensions, and then moving to Business Central online with Microsoft's cloud migration tooling.
Works well when:
- Your processes still fit the business and users are broadly happy.
- Customizations are moderate and still needed.
- Detailed transaction history in the system matters for operations or compliance.
Watch out for: carrying years of unneeded customizations into the new platform. Every modification you keep has to be rebuilt as an extension and maintained through twice-yearly updates.
Path 2: Fresh implementation
A fresh implementation treats Business Central as a new system. You redesign processes around current standard functionality, migrate master data, open items and balances, and keep the old NAV database available for historical lookups.
Works well when:
- The business has changed significantly since NAV was implemented.
- Many customizations exist to cover gaps that standard Business Central now fills.
- Data quality in NAV is poor.
Watch out for: underestimating change management. Users who have worked in NAV for a decade need good training and a clear explanation of why things work differently.
How to decide
Start with an assessment of your current NAV environment:
- Inventory the customizations. List every modified object and report and classify each as still needed, replaced by standard functionality, or no longer used.
- Review processes. Walk through the key flows with the people who run them and note where NAV fits and where it is worked around.
- Check data quality. Look at master data, open entries and inventory valuation.
- Decide on history. Agree how much transaction history needs to live in the new system and how the rest will be archived.
In practice many projects land on a hybrid: a fresh design for the processes that changed most, with data and selected customizations carried forward where they still add value.
Don't forget the ecosystem
NAV environments usually connect to other tools: EDI, ecommerce, warehouse scanners, reporting databases and third-party add-ons. Check that each one has a Business Central online version or a replacement on Microsoft AppSource before committing to a timeline.
Next step
ERPLO has worked with NAV since NAV 2009 and with Business Central since its release. Learn about our NAV to Business Central upgrade service, or talk to an architect about which path fits your business.
