Guide

NAV/Navision to Business Central migration guide

Practical migration guide for NAV/Navision to Business Central covering assessment, upgrade vs reimplementation, data strategy, testing, and cutover planning.

NAV to Business Central migration is often framed as a technical upgrade, but for most mid-market companies it is a business transformation decision. The core question is whether to preserve legacy customizations and workarounds or use the migration to redesign finance and operations processes.

This guide helps ERP program leaders, finance teams, and IT stakeholders plan a migration that balances risk, speed, and long-term maintainability. It is especially useful for organizations with older NAV versions, custom objects, third-party add-ons, or inconsistent data quality.

The most important early decision is whether to pursue an upgrade-led path or a reimplementation-led migration. Delaying that decision usually creates major surprises in budget, timeline, and stakeholder expectations later in the project.

Start by assessing your current NAV estate: version, customizations, add-ons, integrations, reports, and known process pain points. This assessment should identify what is business-critical, what is technical debt, and what can be retired instead of migrated.

Next, evaluate whether your current processes are worth carrying forward. If users rely heavily on spreadsheets, manual workarounds, or unsupported customizations, a reimplementation-led migration may produce a better long-term result even if the short-term effort is higher.

Data migration should be treated as a formal workstream with business owners, not a late technical task. Define data ownership, mapping rules, historical data strategy, and reconciliation criteria early so finance and operations leaders can sign off before cutover.

Review legacy customizations and extensions one by one. For each item, decide whether to keep it, replace it with standard Business Central functionality, use an add-on, or retire it entirely. This step is critical for reducing future support and upgrade burden.

Testing should reflect real business scenarios, not isolated module checks. Run end-to-end flows such as quote-to-cash, procure-to-pay, period close, inventory adjustments, and any industry-specific processes that are essential to go-live success.

Plan cutover and hypercare as part of the migration design, not as an afterthought. A strong cutover plan includes decision checkpoints, responsibilities, reconciliation tasks, issue triage, and clear criteria for exiting hypercare.

Finally, choose an implementation partner with proven NAV-to-Business-Central migration experience, not just general ERP credentials. Migration quality depends heavily on how well the partner handles data, customizations, testing discipline, and scope control.