Checklist

NAV and GP upgrade readiness checklist

What has to be true of your current system before a Business Central migration can start, which of the two upgrade routes fits, and the preparation each product needs. The same briefing we give in a discovery call.

For Finance and IT leads weighing a move off Dynamics NAV or GP

There is no single upgrade path. There are two, and the right one depends on how heavily customised your environment is and whether you want to preserve your current processes or take the opportunity to redesign them. This applies equally to NAV and GP.

Before you start: what has to be true of your current system

  • The technical prerequisites. Your source database must be on SQL Server 2016 or later with a compatibility level of 130 or higher. Older environments need a database upgrade before migration can begin. Data movement itself is handled by Azure Data Factory, running as part of the Business Central online service.
  • Your live system stays live. While replication runs, the online environment is configured with read-only access so your team can preview and validate data without creating conflicts. Your existing system remains the system of record until you explicitly cut over. There is no period where the business is without a working ERP.
  • Customisations must match the online schema. Custom fields, tables and ISV add-ons need to exist as extensions matching Business Central online's schema. Anything that doesn't match will fail to replicate, sometimes without an obvious error. We inventory this at assessment rather than discovering it mid-migration.
  • How much history to carry. Every additional year of transactional history lengthens replication and increases the reconciliation burden. Most organisations bring forward two to three years of active history and archive the remainder in an accessible form for audit and reporting. Moving everything by default is the most common avoidable cost in these projects.

If you are on Dynamics NAV

NAV does not migrate directly to the cloud. Microsoft's cloud migration tool supports Business Central on-premises and Dynamics GP 2015 or later as sources. Dynamics NAV is not a supported source. A NAV environment has to be upgraded to Business Central on-premises first, and only then migrated to Business Central online.

For most NAV environments that intermediate step is Business Central version 14, the last release supporting both the legacy C/AL development environment and modern AL. It is the bridge between the way your system was written and the way Business Central online expects it to be written, and it is the single most commonly underestimated element of a NAV project.

We scope this explicitly in the assessment, because a timeline that ignores it is not a timeline.

If you are on Dynamics GP

GP migrates directly, from GP 2015 or later. Older GP versions need an intermediate GP upgrade before the migration tool will run at all.

There is a preparation list to work through first.

  • All batches posted.
  • Sub-ledgers reconciled to the general ledger.
  • The main account segment defined in General Ledger Setup.
  • Activity tracking enabled across all companies.
  • Check links run to clear errant data.
  • Item codes brought within Business Central's twenty-character limit.
  • Default posting accounts configured.
  • Periods closed up to the open fiscal year.

Which of the two routes fits

Route A: Technical upgrade

  • Moves your existing data, chart of accounts and configuration across into Business Central largely as they stand
  • Preserves what already works and keeps disruption to a minimum
  • Best suited to lightly customised environments on recent versions
  • Custom code still has to be converted to the modern extension model, and this is almost always the largest variable in both timeline and cost
  • Carries forward any accumulated workarounds along with the good parts

Route B: Reimplementation

  • Rebuilds the system around how the business runs today rather than how it ran when the original configuration was written
  • Master records, opening balances and open transactions migrate across; older history is archived separately for audit and reference
  • Best suited to heavily customised environments, older versions, or businesses that have simply outgrown their original design
  • Clears accumulated technical debt instead of paying to move it
  • Requires more of your team's time, and delivers correspondingly more
The two routes compared
Technical upgradeReimplementation
Historical dataMigrated in fullCore data migrated, history archived
CustomisationsConverted to extensionsRebuilt only where still justified
Process redesignMinimalSubstantial opportunity
Best suited toLight customisation, recent versionsHeavy customisation, older versions
Business time requiredLowerHigher
The two routes compared

What we will tell you

We will tell you which one we think fits after the assessment, with the trade-offs written down. If a technical upgrade is genuinely the better answer for you, we will say so: it is the smaller engagement.

Prints as a clean document — no navigation, no calls to action.

Next step

You have the checklist. We will run it against your system.

A health check turns these questions into written answers about your environment — what carries over, what is now standard functionality, and what genuinely has to be rebuilt. You keep the assessment either way.

Newsletter

One email a month. No filler.

Stay ahead with Microsoft Business Applications.
Insights, implementation advice and practical ideas to help your business get more from Microsoft technology.

By subscribing, you acknowledge MicroCloud 360’s Privacy Policy.