Skip to main content

ERP Migration to Dynamics 365 Business Central

ERP migration to Business Central is the process of moving your master data, transaction history and opening balances off a legacy system such as Dynamics NAV, GP, Sage, SAP or QuickBooks and into Dynamics 365 Business Central, with balances reconciled and signed off by your finance team before you go live.

Migration is the part of an ERP project where confidence is either earned or lost. If the trial balance does not agree on day one, nobody trusts the new system, and the informal spreadsheets come straight back.

So we rehearse. Every migration runs into a sandbox at least twice before the live cutover, and your finance team signs off the reconciliation each time.

What ERP Migration to Business Central includes

Source system assessment

What exists, what is still used, and what should be left behind. Migrating a decade of dormant records costs money and slows the system permanently.

Data cleansing

Duplicate customers, obsolete items and orphaned records dealt with before migration rather than carried across and multiplied.

Field mapping

A documented mapping from every source field to its Business Central destination, including the transformations and defaults applied.

Opening balance reconciliation

Trial balance, aged receivables, aged payables, inventory valuation and fixed asset registers reconciled line by line and signed off by your accountants.

Historical data strategy

A decision on how much transaction history moves into Business Central and how much stays queryable in an archive, balancing audit needs against performance.

Rehearsed cutover

A timed dry run with a documented rollback point, so the live weekend follows a script that has already been executed successfully.

Certified for erp migration to business central

The Microsoft certifications our team holds for this work.

  • Microsoft Certified AssociateMB-800Dynamics 365 Business Central Functional Consultant AssociateAssociate
  • Microsoft Certified AssociateDP-203Azure Data Engineer AssociateAssociate
  • Microsoft Certified FundamentalsDP-900Azure Data FundamentalsFundamentals

How the engagement runs

  1. Assess

    We profile the source data and report what is clean, what is not and what should be retired.

  2. Map and cleanse

    Mapping is documented and cleansing happens in the source system where possible, so it benefits everyone.

  3. Trial migration

    A full run into a sandbox, followed by reconciliation against your source reports.

  4. Rehearse

    A second timed run to prove the runbook and establish exactly how long cutover takes.

  5. Cutover

    The live run, executed against the rehearsed script with finance sign off before you transact.

What you end up with

Opening balances that agree with your legacy system on day one

A cutover with a known duration and a rollback point

Legacy clutter retired rather than carried forward

An audit trail of every transformation applied

Who this is for

Businesses on Dynamics NAV or GP approaching end of support, companies that have outgrown QuickBooks or Sage, and groups consolidating several legacy systems onto one platform.

ERP Migration to Business Central questions

Usually open items plus two to three years of closed history. Beyond that the value drops sharply while the storage cost and query performance impact continue to rise. Older history is better kept in a read only archive that remains available for audit.

Yes, and it is one of the most common migrations we run. NAV to Business Central benefits from a shared lineage in the data model, but customisations written as C/AL objects do not carry across and have to be rebuilt as AL extensions or replaced with standard functionality.

For most mid sized businesses the technical migration runs four to twelve hours. We know the number precisely before the live run because the rehearsal is timed, which is the point of rehearsing rather than estimating.

That is exactly why the trial run happens weeks before cutover. Discrepancies found in a sandbox are a scheduling matter. Discrepancies found on the live weekend are a crisis. In practice most differences trace back to rounding rules, cutoff dates or source data that was already wrong.

Book a free consultation

Thirty minutes with a senior engineer, not a salesperson. Bring the system you are stuck on and you will leave with a written summary of your options and a rough scope, whether or not you go on to work with ForgeSolutionz.

Schedule now