Upgrading from Dynamics NAV to Business Central: Step-by-Step Guide
Upgrading from Microsoft Dynamics NAV to Dynamics 365
Business Central is a transformative project that modernizes your ERP, moves
your infrastructure to the cloud (or optimizes it on-premises), and gives you
access to modern capabilities like built-in AI, native Microsoft 365
integration, and automated updates.
Because legacy NAV systems often feature heavy
modifications and older coding languages (C/AL), a structured approach is
essential. The end-to-end upgrade process follows these core steps:
Phase 1: Assessment and Strategy
Assess Your Existing NAV Environment
Catalog your current NAV version, database size,
third-party add-ons, reports, and integrations (e.g., banking, CRM, warehouse
tools).
Review all existing customizations. Determine
whether custom code is still necessary or if modern standard Business Central
handles that functionality out-of-the-box.
Choose Your Upgrade Path
Direct Upgrade / Cloud Migration: Migrating data and converting custom
code into modern AL extensions to move to Business Central Online.
(Note: Older NAV versions generally require stepping through an intermediate
supported version like Dynamics NAV 2018 or Business Central v14 on-premises
first).
Reimplementation: Starting fresh with a clean Business Central
environment, reconfiguring core setups, and migrating only master data and open
balances. This is often recommended for heavily modified legacy systems to
eliminate technical debt.
Phase 2: Preparation and Clean-Up
Data Cleansing and Archiving
Review historical data: decide what needs to be moved
over versus what can stay in an archived read-only database.
Clean up master data (customers, vendors, items,
charts of accounts) by removing duplicates, obsolete records, and formatting
inconsistencies. Good data prevents errors during migration.
Convert Customizations (C/AL to AL)
If you are maintaining custom modifications, rewrite
legacy C/AL code into extension-based AL code compatible with modern Business
Central framework versions.
Phase 3: Migration and Technical Execution
Set Up the Target Environment & Run Test
Migrations
Provision your Business Central online tenant (or
on-premises server) and configure user licenses.
For cloud paths, configure the Cloud Migration Tool
(leveraging Azure Data Factory) to map your on-premises database to your online
tenant.
Perform initial test migrations (dry runs) in a
sandbox environment. Never run the production migration on the first try.
Rebuild and Test Integrations
Reconnect and test all third-party software, banking
connections, e-commerce platforms, and electronic data interchange (EDI)
setups.
Phase 4: Validation and Testing
Conduct User Acceptance Testing (UAT) and Financial
Reconciliation
Involve core team leads (finance, sales, purchasing,
operations) to test daily workflows in Business Central.
Run parallel validations comparing opening balances,
inventory counts, and financial reports between NAV and Business Central to
ensure absolute accuracy.
Role-Specific Training
Train your team on the modern Web Client interface,
role centers, and shortcuts. Focus training around real daily job functions
rather than generic software overviews.
Phase 5: Go-Live and Post-Support
Execution of Final Cutover
Schedule the final data replication and cutover during
a low-volume business period (e.g., over a weekend).
Switch off write-access to the legacy NAV system so it
becomes read-only.
Post-Go-Live Monitoring
Closely monitor system performance, user transactions,
and data integrations during the first few weeks. Keep your implementation
partner closely engaged to rapidly resolve adoption roadblocks or minor
technical snags.