ERP Solutions

Navision to Business Central migration: should you upgrade?

Moving from Navision to Business Central is not automatically the best choice. Compare keeping NAV temporarily, full migration, targeted data reimplementation and, if needed, ERP replacement. C/AL custom code, historical transactions, integrations and future processes determine the actual work and risk.
By
PlanAxion
•
Published
October 19, 2026
Reading time
7
min read
Updated
October 19, 2026
image of an innovation lab (for an AI developer tools business)
Key takeaways
  • Compare keeping NAV, migrating to Business Central and replacing the ERP.
  • Assess C/AL code, historical data and integrations.
  • Require comparable business proof and project quotes.

An organization may have relied on Dynamics NAV for years while its operations, integrations and controls have changed. Still, moving automatically to Business Central is not always the right decision. Choose the system that fits your future business first, then decide how to move the data and applications.

Should you keep Navision, migrate to Business Central or replace the ERP?

  1. Keep NAV temporarily. This can make sense when operations are well served and you have a defined support, risk and replacement plan. Without a plan, it may simply defer cost and risk.
  2. Move to Business Central. Consider this when the product remains a good fit and the data, integrations and necessary customizations can justify the migration. Compare a fuller migration with a targeted reimplementation.
  3. Compare other ERP systems. If manufacturing, distribution, multi-entity finance or integration requirements have materially changed, NAV's successor is not automatically the best system. An independent ERP selection helps evaluate alternatives before committing.

The real question: which option will support critical processes with manageable customizations, risks and future costs?

Full migration or targeted reimplementation: what does Microsoft support?

Full migration: the goal is to preserve data and legacy functions that are still useful. Microsoft documents upgrading from Dynamics NAV to Business Central on-premises before moving online. Relevant migration paths require C/AL customizations to be converted into AL extensions. Custom-table data needs careful handling.

Targeted reimplementation: Microsoft also documents a Business Central 14 reimplementation approach that carries essential business data such as master records, setup and opening balances, rather than automatically moving the full transaction history and legacy customizations. Plan separately for historical lookup and retention.

The supported intermediate versions depend on your starting point. Review Microsoft's NAV to Business Central online migration guide and its supported upgrade paths before approving a technical plan.

Six checks before requesting a migration quote

  1. Version and environment. Document NAV release, database, environments, support contracts and operational constraints.
  2. Customizations. Inventory modified C/AL objects, reports, automation and dependencies. Classify each as standard, configuration, extension, third-party solution or retirement.
  3. Data and history. Separate active records, balances, posted history and material needed for audits or reporting. Define what will migrate and what remains archived.
  4. Integrations. Test banking, EDI, warehousing, production, ecommerce, payroll and reporting. Existing NAV integrations may need a new design.
  5. Business proof. Require real demonstrations of a financial close, inventory correction, rush order and data exchange with realistic company data.
  6. Internal capacity. Finance, process owners, IT and data validators must have time allocated. Their workload belongs in the total cost.

How should you compare the choices?

Weight these criteria, then demand comparable evidence for each option: process fit, custom code to retain, historical access, five-year cost, transition risk and internal capacity.

A low licence price can lead to costly extensions, maintenance or training. A full replacement can create a larger change-management burden. The decision needs a documented comparison, not a generic software ranking.

How much does a Navision-to-Business Central migration cost?

There is no universal public price. The budget depends on NAV version, C/AL customizations, integration complexity, data condition, testing and support. Request separate estimates for licensing, technical upgrades, code conversion, data migration, integrations, user acceptance, training, launch, stabilization and internal effort.

Microsoft publishes Canadian prices for Business Central Essentials and Premium. Those are licence rates, not project quotes. Also compare Business Central and Dynamics 365 Finance if financial complexity is an important factor.

Common Navision migration mistakes

  • Recreating every customization. Some old functions may now be covered by standard features or no longer serve a valid need.
  • Delaying decisions about history. The migration path affects what historical transactions and records remain accessible.
  • Confusing technical success with business acceptance. Loaded data does not prove that financial controls, inventory and integrations work.
  • Comparing different proposals. Partners must identify the same scope, exclusions, data, integrations and client responsibilities.

FAQ: Dynamics NAV to Business Central migration

Is Business Central simply Navision under a new name?

Business Central is the successor to Dynamics NAV, but migration involves changes in versions, application platform and customization handling. It is not merely a rename.

Can you migrate directly from NAV to Business Central online?

Microsoft documents an initial upgrade to Business Central on-premises followed by cloud migration. Intermediate versions depend on the starting release and customizations.

Do you have to preserve custom C/AL code?

No. First test whether standard Business Central meets the business need. Customizations that remain necessary may need conversion to AL extensions and validation.

What happens to historical transactions?

Full migration and targeted reimplementation serve different purposes. Decide which information must be migrated, retained and accessible before choosing a path.

When should you choose a different ERP?

When critical requirements remain unsupported or the custom work needed outweighs the expected benefits. Compare multiple systems on the same business scenarios.

Before signing a migration proposal

Document the current NAV environment, essential customizations, historical data and acceptance tests. PlanAxion independently advises clients on ERP scoping and evaluation, without reselling software licences.

← All insights
Share

Related articles

Structured comparison of ERP solutions with a criteria grid for evaluating a demonstration.

How to evaluate an ERP demo: 12 criteria before choosing

An ERP demonstration should not be a presentation controlled solely by the vendor. To properly compare multiple solutions, the company must mandate the same scenarios, test the exceptions that truly matter to its operations, and require proof for critical capabilities. This guide proposes 12 criteria to structure the evaluation: scenarios, exceptions, standard versus development, number of steps, data, integrations, integrator quality, evidence, immediate scoring, weighting, and gap management. It also provides 25 questions to ask during the sessions and explains why a demo should never be used in isolation to select an ERP. The goal is to transform a sales presentation into a comparable, documented validation exercise that is integrated into an independent, client-side ERP selection process.
how-to-evaluate-erp-demo
ERP contract reviewed during the assessment of critical clauses before signing.

Which clauses to check in an ERP contract? 12 points before signing

An ERP contract should do more than just confirm a price and a timeline. It must explicitly define scope, deliverables, acceptance criteria, responsibilities, change management, data, integrations, support, exit rights, and commercial terms. This guide outlines 12 clauses to examine before signing with an ERP vendor or integrator. The goal is to identify areas where a contract might silently shift risk to the client: vague assumptions, uncosted exclusions, change order billing, imprecise migration, weak service level agreements, price hikes, vendor lock-in, or the absence of a transition plan. PlanAxion addresses these points from the client side as part of an independent ERP selection. This content supports business, operational, and IT analysis; it does not replace the advice of qualified legal counsel.
erp-contract-clauses
Two ERP proposals and a comparison matrix analyzed before selecting a solution.

How to Compare ERP Proposals: 10 Criteria Before Choosing

Two ERP proposals can show very different prices while covering scopes, assumptions, and responsibilities that are not at all equivalent. This guide shows how to normalize offers before comparing the amounts: functional scope, exclusions, proposed team, effort required from the client, migration, integrations, total five-year cost, and commercial terms. It also explains why the ERP solution and the integrator must be evaluated separately, how to handle items yet to be confirmed, and how to add evidence and risk to a weighted grid. The goal is not to produce an automatic winner, but a decision that management can defend: understanding what is actually included, where the trade-offs are, and which gaps must be closed before negotiation or signing. The method is part of an independent ERP selection process conducted on the client side.
compare-erp-proposals
Steering committee reviewing an ERP schedule with slipped milestones in a Montreal office

Delayed ERP project: what to do before increasing the budget?

An ERP delay is a symptom, not a fatality. Gartner predicts that more than 70% of ERP initiatives will miss their objectives by 2027. This guide provides the seven signals to watch for, four decision options, and the methodology for an independent three-week diagnostic.
late-erp-project-what-to-do