How long does a NAV to Business Central upgrade take? - Austral Dynamics
02 9763 2040 Enquire Now

In Austral Dynamics’ experience, a NAV to Business Central upgrade typically takes 2 to 6 months. Where your project lands in that range depends mainly on how much custom code you have, how much data and history you bring across, how many companies and integrations are involved, and which NAV version you start from. That range is our typical experience, not a quote. The real figure for your system comes from an assessment.

What are the phases of a NAV to Business Central upgrade?

Microsoft describes six high-level phases for moving from NAV to Business Central online. If you are staying on-premises, the first two are the core of the work.

  1. Preparation. Assess your current state, set scope, validate prerequisites and clean the data.
  2. Business Central upgrade. Upgrade NAV to a supported Business Central on-premises version, converting C/AL customisations to AL extensions along the way.
  3. Cloud migration setup. Connect the on-premises database to the online tenant and choose companies.
  4. Data replication. Run initial and delta replications, then validate the results.
  5. Data upgrade and completion. Run the final data upgrade and make the new environment your primary system.
  6. Post-migration follow-up. Enable users, reconnect integrations and monitor performance.

Microsoft also recommends at least one dry run in a sandbox before the production cutover, so you can find problems and measure timing before it counts.

What makes an upgrade take longer?

Five things stretch a project most often.

Customisations

Microsoft requires C/AL customisations to be converted to AL extensions, and data in tables with code customisations cannot be carried forward unless they are. A lightly customised system converts quickly. A heavily customised one does not. On one multi-entity upgrade we rebuilt hundreds of custom objects as upgrade-safe extensions rather than lifting them across.

Data volume and history

Large transaction and log tables take longer to process and validate. Microsoft advises archiving obsolete history and shrinking oversized tables before you start.

Integrations

Every EDI feed, field service tool or banking link has to be reconnected and tested. Each one adds testing time.

Reports and layouts

Custom reports, and any local tax or regulatory logic, have to be converted so they work with Business Central.

Companies and NAV version

More companies means more validation, and Microsoft suggests designing company batches early. Your starting version matters too. NAV versions before 14 cannot migrate straight to the cloud and must first upgrade to Business Central on-premises version 14. Older versions have more steps to get there.

Can we shorten the timeline?

Sometimes, yes. These are the levers worth looking at:

  • Reimplementation. After reaching version 14, Microsoft’s reimplementation tool moves essential data only (master data, balances, setup). It avoids extension conversion, but historical transactions and legacy customisations are not carried forward.
  • Archive history. Less data to move means less to process and check.
  • Cut unused customisations. Code nobody uses should not be converted.
  • Dry run early. A sandbox run surfaces the slow parts while there is still time to deal with them.

Each of these trades something away, so decide with your finance and operations leads, not just IT. Our upgrades page explains how we approach the work.

Does the NAV 2018 deadline change the timing?

It sets the latest date you can plan around. Microsoft lists extended support for Dynamics NAV 2018 as ending in January 2028, and each NAV version has its own dates. Because the typical range is 2 to 6 months, and the first step is only an assessment, starting well ahead of the deadline leaves room for a dry run and for surprises. Our article on NAV 2018 end of support covers the dates in more detail.

How do we get a firm timeline?

Through an upgrade assessment. We look at your NAV version, the amount and condition of custom code, data volumes, integrations, reports and the number of companies. Those are the same factors that drive the timeline, so the assessment is where the 2 to 6 month range turns into a plan for your business. We have 100+ NAV and Business Central customers, and 50+ have upgraded with us. Austral Dynamics is a Sydney-based Microsoft Solutions Partner for Business Applications with more than 19 years of experience.

Questions people ask

Is 2 to 6 months a guarantee?

No. It is the range we typically see. Your own timeline depends on the factors above and is confirmed through an assessment.

Do we have to convert all our customisations?

For a full migration, yes. Microsoft requires C/AL code to be converted to AL extensions. The reimplementation option avoids this, at the cost of leaving historical transactions and legacy customisations behind.

Should we do a dry run?

Yes. Microsoft recommends at least one dry run in a sandbox before the production cutover, to find issues and measure timing.

Book an upgrade assessment

If you are an IT manager weighing up an upgrade, the quickest way to a real timeline is an assessment of your system. Book an upgrade assessment and we will take it from there.

Sources