Dynamics GP to Business Central: what Microsoft's migration tool moves, and what it doesn't

You've run Dynamics GP for fifteen years. It works, your team knows it, and the reports your board expects come out of it every month. But the end date is now on the calendar, and someone has told you Microsoft has a tool that "moves everything over" to Business Central.

It moves a lot. It doesn't move everything, and the parts it leaves to you are the parts that decide whether your first close in Business Central goes well.

The dates, briefly

Microsoft has set the end of support for Dynamics GP at December 31, 2029, with security updates available until April 30, 2031. That applies to current GP (version 18.x), which follows Microsoft's Modern Lifecycle Policy. (Microsoft's GP lifecycle page.)

Older versions are on a different clock. GP 2016's extended support ended in July 2026. GP 2018 and 2018 R2 run to January 2028 unless they've been patched up to version 18.5 or later, which moves them onto the Modern policy.

Three years sounds like plenty. In practice, a company that wants to go live at the start of a fiscal year, after budget approval, with a test cycle and a parallel close, has fewer good windows than it thinks. If you're on GP 2016 or older today, you're already past the end of extended support.

What Microsoft's tool actually moves

Microsoft's cloud migration tool supports GP 2015 and later. It replicates your GP data into Business Central online, table by table. According to Microsoft's documentation, it brings over:

  • Setup and master data: chart of accounts, customers, vendors, items, and their classes.
  • Open balances: outstanding receivables and payables, with the amount remaining.
  • General ledger summaries for open and historical years, back to the oldest year you choose.
  • Open purchase orders, inventory quantities, locations and lot/serial information.
  • Checkbooks, including unreconciled bank transactions.
  • Vendor 1099 data, from 2024 onward.
  • Optionally, a historical snapshot of GP detail (GL, receivables, payables, sales orders, receipts, inventory transactions) stored in separate history tables you can look up in Business Central.

That's a real head start. For a clean, single-company GP install with standard modules, the tool does much of the heavy lifting.

What it leaves to you

Here's where projects go sideways. None of these is a flaw in the tool. They're business decisions it can't make for you.

1. Your chart of accounts design. GP uses a segmented account string. Business Central uses a main account plus dimensions. The tool turns your main segment into the account number and your other segments into dimensions: you pick two as global dimensions, and the rest become shortcut dimensions. That's mechanically correct. Whether it's right is another question. If your GP segments grew over the years into a mix of department, location, entity and "project we stopped doing in 2014," you'll carry that into Business Central unless someone redesigns it first. Fixing it after go-live, with transactions posted, is far harder.

2. How much history you really need. The tool lets you choose how far back to bring summary history, and the snapshot can hold more detail. More isn't always better. Decide what auditors, tax and management reporting actually need from inside the new system, and keep GP (or an archive) read-only for the rest.

3. Anything that isn't standard GP. Third-party add-ons, custom tables, Excel and SQL reports that read GP directly, and integrations to payroll, banking or e-commerce aren't part of a standard GP migration. Each one needs a decision: replace it with standard Business Central, an AppSource app, a new integration, or retire it.

4. Cleanup GP has been hiding. Undeposited receipts aren't migrated, so they need to be deposited in GP first. Inactive customers, vendors and items can be excluded, and usually should be. Historical years come over open and need to be closed in Business Central. Duplicate vendors and customers come over just as they are.

5. Process, not data. Your AP approval, month-end checklist and reporting pack were built around GP screens and GP reports. Business Central does the same jobs differently. Migration moves data. It doesn't redesign how your team works.

A realistic example

A three-company distributor on GP 2018 R2 planned a "lift and shift" using the migration tool. The test migration ran in a weekend. Then the controller tried to produce the monthly management pack and found that two of the five GP account segments held the same information in different ways, a third had stopped being used in 2019, and every report relied on a SQL view nobody had documented. We paused for three weeks to redesign the dimensions and rebuild the reports in Business Central, then re-ran the migration. Go-live slipped one month and the first close took four days instead of the usual six.

The tool wasn't the problem. Treating the migration as a data copy rather than a finance redesign was.

How to plan it

A sensible order of work:

  1. Run Microsoft's migration assessment to see what's in your GP database and what the tool will and won't handle.
  2. Redesign the chart of accounts and dimensions on paper before any test migration. This is a finance decision; keep IT in the room but not in charge.
  3. List every add-on, report and integration, and decide replace, rebuild or retire for each.
  4. Clean up in GP: deposit receipts, deactivate dead records, merge duplicates.
  5. Run at least one full test migration into a sandbox, then run a real close on it. Microsoft warns against setting up cloud migration in a production environment in active use, because existing data in the target is overwritten.
  6. Pick a go-live date that isn't your busiest period, and plan a parallel month if your auditors expect one.

When you might not need much help

If you run one GP company, use mostly standard modules, have a tidy chart of accounts and few integrations, the migration tool and a focused implementation can get you there without a large project. Be wary of anyone who proposes the same scope for that company as for a multi-entity business with ten integrations.

If you have several companies, intercompany, add-ons or reporting your board relies on, the tool is where the project starts, not where it ends. See also our guide to multi-company, intercompany and consolidation in Business Central.

Moving off GP?

It's a chance to fix the chart of accounts and reporting you've worked around for years, if the decisions get made before the data moves. Cateran's Business Central implementation work starts with exactly that. Request a 30-minute call to talk through your GP setup and a realistic timeline.