NAV to Business Central Upgrade Assessment
Dynamics NAV is out of mainstream support, and many companies are working out what the move to Business Central really involves. The honest answer depends on a handful of factors: version, how customisations are built, add-ons, data quality and integrations. This assessment turns those into a score and a short action list.
1. Which NAV version do you run today?
Older versions need more steps and often a technical upgrade path before the move.
2. How are your customisations built?
Code changes inside base objects are the biggest upgrade cost driver.
3. How many custom tables, pages, reports and codeunits do you have?
4. Do you use third-party add-ons or ISV solutions?
5. How clean is your master and ledger data?
6. How many integrations connect to NAV (EDI, e-commerce, banking, BI, web services)?
7. How large is your database and how much history do you need?
8. Do you have a test environment and a person who knows the business processes?
9. Have you decided SaaS versus on-premises for Business Central?
10. Is there an executive sponsor, budget range and a target go-live window?
How to use the assessment
Answer each of the ten questions for your current NAV environment. Scores are added and shown as a percentage of the maximum, then matched to one of four bands. The result is a planning aid, not a quote: it tells you where the effort is likely to be and what to inspect first. Run it with your IT lead and a process owner, and save the result to Excel or PDF for the steering group.
What drives upgrade effort
Business Central moved customisation from changing base objects to extensions written in AL. Code changed directly in NAV objects has to be rewritten or replaced by standard features. The count of custom objects, ISV add-ons without a Business Central version, and integrations that used direct SQL access are the three biggest cost drivers. Data volume and history affect conversion time more than complexity.
- Base object changes become extensions or events
- ISV add-ons need a supported Business Central version
- Direct SQL access is not available in SaaS
- Large databases lengthen conversion windows
Choosing the path
Typical paths are a technical upgrade of the existing database and code, a re-implementation on Business Central with selected data migrated, or a phased approach by company or module. Low scores usually favour re-implementation, because rebuilding on standard features is cheaper than porting years of base object changes. SaaS versus on-premises should be decided early, as it limits integration and customisation techniques.
Common mistakes
Underestimating testing, skipping a trial conversion, and assuming all add-ons exist in the cloud are the usual causes of overruns. Another is porting every old customisation without asking whether standard Business Central now covers it.
Frequently Asked Questions
Can I upgrade directly from any NAV version?
Not always. Older versions typically need an intermediate technical upgrade or a data migration approach. Check Microsoft's current upgrade path documentation for your exact version and choose with your partner.
Do my NAV customisations carry over?
Not automatically. Business Central uses extensions, so base object changes must be redone as extensions or replaced by standard functionality. Document what each change does before deciding.
Should I upgrade or re-implement?
If customisations are modest and data is clean, an upgrade can be efficient. With heavy base changes or old versions, re-implementing with selected data often costs less and gives a cleaner system.
Does this assessment give a price?
No. It scores readiness and highlights risk areas. Pricing needs an object inventory, a trial conversion and a defined scope from your implementation partner.
If your score points to a hard upgrade, Netray works alongside Business Central partners to review customisations and data before you commit.
Related Tools
Business Central Configuration Package Worksheet
Plan the tables, load sequence and expected error counts for Business Central RapidStart configuration packages before you import.
Developer ToolsBusiness Central AL Extension Skeleton Generator
Fill in publisher, prefix and ID range to get app.json, a table extension, a page extension, an event subscriber codeunit and a permission set.
Microsoft DynamicsBusiness Central Year-End Close Checklist
Work through preparation, subledger, inventory, closing and post-close steps for a clean Business Central fiscal year end.
Microsoft DynamicsBusiness Central API v2.0 URL Builder
Generate correct Business Central API v2.0 endpoints, OData query strings, the OAuth token request and a test call for SaaS or on-premises.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment