Practical guide to upgrading from Dynamics NAV to Business Central, covering C/AL to AL migration, customisation challenges, and support planning.
IT managers, business owners, and finance managers running Dynamics NAV who need to plan their migration to Business Central or handle ongoing NAV support.
What does it take to migrate from Dynamics NAV to Business Central, and what should we plan for?
Microsoft Dynamics NAV (originally Navision) is one of the most widely deployed ERPs for small-to-mid-market businesses globally. In Australia, it's common across distribution, professional services, and light manufacturing.
Microsoft stopped developing NAV in 2018, replacing it with Dynamics 365 Business Central, a cloud-native platform built on the same foundations but with a fundamentally different architecture. NAV ran on-premises with C/AL code. Business Central runs in Azure with AL extensions.
If you're running NAV, the question isn't whether to move. It's when and how.
Support timeline. NAV 2018 extended support runs until January 2028. Earlier versions (2017, 2016, 2015, 2013) have already exited support. If you're on anything older than NAV 2018, you're running completely unsupported.
Skills availability. NAV developers are migrating their skills to Business Central. The C/AL developer pool is shrinking, which means higher rates and longer timelines for any NAV-specific work.
Security and compliance. Unsupported versions don't receive security patches. Australian tax and reporting requirements keep changing (STP Phase 2, updated BAS), and NAV can't keep up without manual intervention.
Integration limitations. NAV's integration capabilities are dated compared to modern platforms. Web services exist but are limited. Many NAV integrations use direct SQL or ODBC, which are fragile and hard to maintain.
Migration to Business Central (cloud). The standard path. Move to Microsoft's cloud-hosted Business Central. Automatic updates, no infrastructure to manage, strong Microsoft 365 integration. Most NAV users end up here.
Migration to Business Central (on-premises). If you need on-premises for data sovereignty, compliance, or connectivity reasons, Business Central still has an on-premises option. Less common but available.
Alternative ERP migration. If your NAV environment has outgrown what Business Central offers (complex manufacturing, multi-entity, advanced warehousing), consider NetSuite, Dynamics 365 F&O, or industry-specific alternatives.
Staged migration. Migrate core modules first (financials, purchasing), then secondary modules (warehousing, manufacturing) in later phases. Reduces risk per phase but extends the overall timeline.
C/AL to AL conversion. This is the biggest technical task. All C/AL code needs converting to AL extensions. Microsoft provides some conversion tools, but complex customisations with deep table modifications or heavily modified base pages need manual rewriting.
Page and report changes. NAV used classic client pages and RDLC reports. Business Central uses a web-based interface and different report rendering. Custom pages and reports need redesigning.
Integration modernisation. NAV integrations often use:
Data migration. NAV data structure is similar to Business Central, but not identical. Master data, open transactions, and historical data all need mapping and validation.
Large volumes of custom C/AL code mean longer, more expensive migration.
Older versions require more work. NAV 2009 is a significantly bigger project than NAV 2018.
These all need replacing. Often the largest hidden cost in NAV migrations.
Business Central's web interface is different from NAV's Windows client. Plan for retraining.
NAV add-ons may not have BC equivalents. Check availability early.
Business Central is the cloud-native successor to NAV. It runs on the same core code base but uses AL instead of C/AL, runs in Azure, and receives continuous updates. Think of it as NAV rebuilt for the cloud.
Technically yes, for now. But mainstream support has ended for NAV 2018 and earlier. Extended support for NAV 2018 runs until 2028. After that, you're on your own. The skills pool is shrinking, so the longer you wait, the harder the migration becomes.
Typically 3-9 months depending on your NAV version, customisation volume, and data complexity. NAV 2018 migrations are simpler (closer architecture). NAV 2009 or earlier migrations are more complex and may take 6-12 months.
C/AL code doesn't run in Business Central. All customisations need converting to AL extensions. Some can be automated with conversion tools, but complex customisations need manual rewriting and testing.
For most use cases, yes. Automatic updates, cloud hosting, better integration with Microsoft 365, modern UI, and a growing extension marketplace. The trade-off is less control over upgrades and a different customisation model.
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
