Microsoft Dynamics NAV (Navision) users face an important reality: NAV is approaching end of mainstream support, and Business Central is its cloud successor. A NAV-to-BC migration is not just a version upgrade — it's a strategic opportunity to modernize your ERP, eliminate technical debt, and move to a cloud-native platform. This playbook covers everything you need to know.
Understanding the NAV-to-BC Migration Landscape
Before diving into methodology, let's be clear about what this migration involves:
- Not just an upgrade: Business Central is a different application from NAV. There is no automatic upgrade path for heavily customized NAV environments.
- Custom code must be rewritten: NAV customizations (written in C/AL) cannot run in Business Central. They must be rewritten in Business Central's AL extension language.
- Data migration is required: NAV data must be migrated to Business Central's data model, which has evolved significantly.
- Good news: Business Central includes migration tools and templates that accelerate the process significantly.
Phase 1: Assessment & Planning
NAV Environment Assessment
The first step is a comprehensive assessment of your current NAV environment:
- NAV version inventory: What version of NAV are you running? (NAV 2009, 2013, 2015, 2017, 2018?). Older versions require more migration effort.
- Customization inventory: Document all custom objects (tables, forms, reports, codeunits). Classify each as: still needed, replace with BC standard functionality, rewrite in AL, or decommission.
- ISV/add-on inventory: Which third-party add-ons are installed? Do they have Business Central equivalents on AppSource?
- Data volume: How many years of data? What are the transaction volumes? Data age affects migration complexity and selective migration decisions.
- Integration inventory: What systems integrate with NAV? Each integration needs a BC equivalent.
Phase 2: Customization Decision Matrix
For each NAV customization identified in the assessment, apply this decision framework:
| Customization | Business Need | Decision |
|---|---|---|
| Custom approval workflow | Still required | Replace with BC native workflow engine |
| Custom report format | Still required | Rewrite using BC Report Layout AL extension |
| Custom form modification | Still required | Rewrite as BC Page Extension |
| Custom table extension | Still required | Rewrite as BC Table Extension |
| Legacy feature workaround | BC has native feature | Use BC standard functionality, retire customization |
| Old integration codeunit | Integration redesigned | Rewrite using BC API / web services |
Phase 3: Data Migration
Microsoft provides the Business Central Cloud Migration tool that handles migration from NAV 2017 and later. For older NAV versions, additional steps are required.
Key data migration considerations:
- Historical data strategy: Most organizations migrate the current fiscal year plus 1–3 prior years. Older data is archived rather than migrated, reducing complexity significantly.
- Open transactions: All open customer invoices, vendor invoices, sales orders, and purchase orders must be migrated with 100% accuracy.
- Balance validation: Post-migration, reconcile all control accounts (AR, AP, inventory, fixed assets) to verify completeness.
- Multiple migration rehearsals: Run 3+ full migration rehearsals before cutover to validate data quality and timing.
Phase 4: Testing Strategy
A NAV-to-BC migration requires testing at three levels:
- Unit testing: Each custom AL extension tested in isolation
- Integration testing: End-to-end process flows tested (order-to-cash, procure-to-pay, record-to-report)
- Data validation testing: Reconcile migrated data to NAV source for completeness and accuracy
Phase 5: Cutover & Go-Live
NAV-to-BC cutovers typically happen over a long weekend. The cutover sequence:
- Day 1 (Friday): Final NAV backup, final data migration run, begin cutover validation
- Day 2 (Saturday): Complete open transaction migration, run reconciliation checks
- Day 3 (Sunday): Final validation, user acceptance sign-off, go-live decision
- Day 4 (Monday): Business operations begin on Business Central, hypercare begins
Common NAV-to-BC Migration Pitfalls
- Underestimating customization rewrite effort (multiply your estimate by 1.5x)
- Assuming BC standard features match NAV customizations exactly (they often don't — this is actually an opportunity)
- Skipping change management and user training (the UI is significantly different from NAV)
- Not running multiple migration rehearsals (one is never enough)
- Not testing on production-scale data volumes (performance issues appear at scale)