# Dynamics GP to Business Central Migration Checklist

> Source: https://netray.co/tools/gp-to-business-central-migration-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Thirty checks across scoping, data, add-ons, cutover and go-live for a GP to Business Central move.

## Category

erp-migration

## Erp

Microsoft Dynamics GP

## Audience

- ERP project manager
- Controller
- IT manager

## Tool

**Kind:** checklist

**Scoring Note:** Items marked critical block go-live if left open. Aim for every critical item done and at least 85 percent overall before cutover.

**Groups:**

#### Scope and decisions

**Items:**

**Text:** Confirm Business Central is the chosen target after a fit-gap against real process scripts

**Critical:** true

List every GP company database and decide which move, merge or close

**Text:** Decide how many years of transactions migrate versus archive

**Critical:** true

Inventory GP modules in use: GL, AP, AR, Inventory, SOP, POP, Payroll, Fixed Assets, Bank Rec

**Text:** Identify features with no Business Central equivalent and decide on extension, ISV or process change

**Critical:** true

Set a cutover date away from year end and quarter close

#### Data readiness

**Items:**

**Text:** Clean duplicate and inactive customers, vendors and items before extract

**Critical:** true

**Text:** Reconcile GP sub-ledgers (AR, AP, Inventory) to the general ledger and document differences

**Critical:** true

Map the GP segmented chart of accounts to the BC chart plus dimensions

Map payment terms, tax schedules, shipping methods and units of measure

Check for orphaned or unposted batches and clear them

Decide opening balance strategy: summary journals or open-item migration

#### Add-ons, reports and integrations

**Items:**

**Text:** Confirm each GP add-on has a Business Central replacement or is retired

**Critical:** true

List all SSRS, SmartList, Management Reporter and Excel reports and decide which to rebuild

**Text:** List every integration: EDI, bank files, e-commerce, payroll, CRM, scanners

**Critical:** true

Document SQL jobs, stored procedures and linked server queries that read GP tables

Plan replacements for custom Dexterity, VBA and Modifier forms

Prepare user security roles and map them to BC permission sets

#### Migration build and testing

**Items:**

**Text:** Run at least two full mock migrations and record load times

**Critical:** true

**Text:** Have finance sign off trial balance, AR aging, AP aging and inventory valuation after each mock

**Critical:** true

Test the key business flows end to end: quote to cash, procure to pay, month end

Test integrations against the BC sandbox, including error handling

Run user acceptance testing with named business owners

Record open defects with severity and decide which can go live with a workaround

#### Cutover and go-live

**Items:**

**Text:** Freeze GP transactions and complete final posting

**Critical:** true

**Text:** Take full SQL backups of every GP database and verify restore

**Critical:** true

Run the final migration and reconcile to the frozen GP balances

Make GP read-only or archive it for reference and audit

Train users and publish quick reference guides before go-live

Run a hypercare period through the first month end close

## Content

**Intro:** Moving from Dynamics GP to Business Central is mostly a data and process exercise, not a software install. This checklist covers the steps projects most often miss, with critical items flagged.

**Sections:**

#### How to use this checklist

**Body:** Work through the groups in order and tick items as they are truly finished, not merely started. Assign every unticked item an owner and a date. The scoring note tells you how many to complete before cutover, and the critical items are the ones that stop go-live. Export the PDF at each stage gate so the steering committee sees movement. It works for a first plan or as a final readiness review one week before cutover.

#### How the migration works in outline

**Body:** Microsoft provides a cloud migration approach for moving GP data into Business Central, which typically carries master data, balances and selected history. It does not carry your reports, custom code or add-ons, and it will not fix bad data. Many projects instead load with configuration packages or data entities when they need more control. Whichever method you choose, treat extract, transform and reconcile as three separate steps and have finance sign off each mock.

**Bullets:**

- Master data and opening balances move first
- Open documents need a clear policy
- History can move in summary or be archived
- Reports and customizations are rebuilt, not migrated

#### Reading the result

**Body:** If critical items remain open, do not set a go-live date. Typical blockers are unreconciled sub-ledgers, an add-on with no replacement and an integration nobody owns. A project with data and add-ons resolved but weak testing is a schedule risk, not a scope risk. If you finish above 85 percent with every critical item closed, you are in good shape to run the final mock and agree the cutover weekend.

#### Common mistakes

**Body:** The most frequent errors are migrating too much history, discovering reports built straight on GP SQL tables after the cutover, and planning go-live in the middle of a fiscal close. Another is underestimating training because the screens look familiar to Microsoft users. Business Central uses dimensions rather than account segments, a different posting model and different security, so user training is a real work item.

**Cta:** We can review your extract scripts and reconciliation logic, or help turn your GP SQL queries into a migration-ready inventory. Optional, and the checklist works without us.

**Faq:**

#### Does Business Central migrate GP history automatically?

**Answer:** Migration tooling can carry master data and balances, and in some setups selected history, but you decide the scope. Most projects migrate a limited period and keep the rest in a read-only archive for audit and lookups.

#### How long does a GP to Business Central migration take?

**Answer:** It depends on modules, add-ons and data quality. Small, standard companies can finish in a few months, while multi-company or heavily customized GP estates take considerably longer. Plan two or more mock loads regardless of size.

#### What happens to our GP reports?

**Answer:** Reports are not migrated. You rebuild them as Business Central reports, Power BI or Excel. Start by listing which reports are actually used, since many GP estates carry dozens of unused ones.

#### Should we archive GP or keep it running?

**Answer:** Most customers keep GP read-only for a defined retention period or move history to a queryable archive. Agree this with audit and tax advisers, and keep a verified SQL backup in either case.

## Search terms

gp to business central migration checklist, dynamics gp to business central, migrate gp to business central, gp data migration checklist, business central cloud migration tool gp, gp to d365 business central steps, gp migration project plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json