Comparison

NAV technical upgrade vs full reimplementation

A decision framework for legacy NAV customers modernising to Business Central.

Assess business process change requirements before deciding technical strategy.

Hidden legacy complexity can make reimplementation the lower-risk option in practice.

Pilot data migration and extension conversion on a representative subset first.

What to compare first

• This comparison should start with business intent, not technical preference. If the business wants a cleaner process model, master data reset, or control redesign, a full reimplementation may be the more honest path even if the technical team prefers an upgrade.
• Run an inventory of customisations, reports, integrations, and manual workarounds. That inventory determines whether the legacy estate is still manageable or whether it is carrying too much hidden complexity.
• Evaluate the cost of preserving old design decisions. A technical upgrade can appear safer but may preserve poor process, obsolete controls, and hard-to-support extension logic.
• Ask what the business will gain after go-live in each path. If the answer is only “same process on newer technology”, that may not justify the delivery effort.

Questions to ask before shortlisting

• A strong shortlist decision should test Technical Upgrade and Reimplementation against the same operating scenarios, governance expectations, and implementation constraints.
• The product that looks better in a demo can still be the worse choice once partner capability, data migration effort, and operating discipline are considered.
• Before final selection, ask each vendor or partner to walk through your target state processes, key reporting requirements, and the top three reasons the implementation could go off track.