Dynamics GP to Business Central: A Data Migration and Cutover Checklist

Illustration of business data moving from an on-premises ERP system to a connected cloud platform

Moving from Dynamics GP to Business Central starts with a business question: what must your team be able to do on the first day in the new system?

Finance needs reliable balances. Sales needs access to customers and orders. Operations needs accurate stock information. Everyone needs confidence that essential processes will continue working.

A successful Dynamics GP to Business Central migration depends on decisions made well before go-live. This checklist helps finance leaders, IT teams and Microsoft partners plan the data, integrations, testing and cutover activities that matter.

1. Assess your current Dynamics GP environment

Before choosing a migration approach, document how your organisation uses Microsoft Dynamics GP.

Your assessment should identify:

  • The GP version, companies and databases in use.

  • Active modules, add-ons and customisations.

  • Connections to banking, payroll, CRM, warehouse and e-commerce systems.

  • Reports and spreadsheets used for daily operations and financial reporting.

  • Approval processes, user roles and access requirements.

  • Business-critical activities that cannot be interrupted.

Assign an owner to each area. A finance report that appears straightforward may depend on custom fields, an external database or a spreadsheet maintained by one person.

Checklist outcome: an agreed inventory of systems, processes and dependencies.

2. Confirm the migration route and local requirements

The right migration route depends on your GP environment, target Business Central localisation and business requirements.

For South African organisations, confirm how the proposed solution will handle VAT, banking formats, currencies and any country-specific extensions.

Do not assume every Microsoft migration tool applies to every market. Microsoft currently lists its assisted GP cloud migration setup as supported for the United States, Canada and United Kingdom. Your implementation partner should confirm the appropriate route for your environment and localisation before committing to tools or timelines. Microsoft migration guidance

Use this stage to establish whether Dynamics 365 Business Central fits your processes as standard, needs extensions or requires changes to how work is performed.

Checklist outcome: a documented migration approach with local requirements and responsibilities confirmed.

3. Decide what data to migrate and what to retain

Not all historical information needs to become live operational data in the new system.

Create a data plan covering three categories:

Data categoryPlanning decision
Master dataWhich customers, suppliers, items and accounts remain relevant?
Operational dataWhich balances, unpaid invoices, orders and stock records must be available at go-live?
Historical informationWhat must remain searchable for reporting, audit and customer enquiries?

Specify the required history by company and data type. Also decide how users will access information that remains outside Business Central.

Where Microsoft’s supported GP migration tools are applicable, selected historical transactions can be available through GP historical snapshot tables. These should not be confused with ordinary Business Central transactions. Confirm coverage and reporting access during design. Microsoft’s GP data migration reference

Checklist outcome: a signed-off data scope, including historical access and retention arrangements.

4. Clean and map your data

Migration is an opportunity to address records and structures that have become difficult to maintain.

Review duplicate customers and suppliers, inactive items, inconsistent contact details and unresolved balances. Agree which records can be excluded and who approves those decisions.

Next, document how GP information will map into Business Central. Review:

  • General ledger accounts and reporting dimensions.

  • Customer, supplier and item identifiers.

  • Posting groups and tax settings.

  • Units of measure.

  • Locations and inventory structures.

  • Payment terms and currencies.

Test the mapping with real examples. Can finance still produce a departmental profit-and-loss report? Can operations identify stock by location? Can a user trace a supplier balance back to supporting records?

Checklist outcome: approved mapping rules and a clean migration dataset.

5. Review customisations and rebuild integrations

An ERP migration involves more than transferring database records.

Assess each GP customisation and add-on against a specific business requirement. Decide whether standard Business Central functionality can meet the need, whether an extension is appropriate or whether the process should change.

For every integration, record:

  • What information moves between systems.

  • Which system owns each record.

  • How frequently information must synchronise.

  • How errors and duplicates will be detected.

  • Who will resolve failed transactions.

  • How the connection will be tested and monitored.

For example, an online order arriving in Business Central is only part of the test. Confirm that stock, tax, customer details, fulfilment and invoice information remain correct throughout the process.

Checklist outcome: an integration register with owners, test cases and recovery procedures.

6. Run a trial migration and reconcile the results

Complete a trial migration before the production cutover.

Finance and operations should compare agreed source reports with the corresponding Business Central results. Depending on scope, reconciliation should cover:

  • Trial balances by company and currency.

  • Customer and supplier balances.

  • Aged receivables and payables.

  • Inventory quantities and valuation.

  • Bank balances and outstanding items.

  • Open sales and purchase documents.

Investigate differences and record their resolution. Matching record counts alone does not establish that financial values and business relationships are correct.

Where available for the chosen migration route, automated validation can support these checks. It should sit alongside business-led reconciliation and approval.

Checklist outcome: documented reconciliation results, with discrepancies resolved or explicitly accepted.

7. Test complete workflows and prepare users

User acceptance testing should follow real work from beginning to end.

Ask users to process a sales order through invoicing, receive goods against a purchase order, apply a customer payment and run month-end reports. Include exceptions such as credit notes, partial deliveries and approval rejections.

Test access as well as functionality. Users need enough permission to perform their roles while maintaining appropriate financial controls.

Training should use these same practical scenarios. Prepare short role-specific guides and identify internal users who can support colleagues after go-live.

Checklist outcome: approved business workflows and users prepared for their daily tasks.

8. Build and rehearse the cutover plan

Cutover is the controlled transition from GP to Business Central.

Your plan should specify the sequence, owner and expected duration of each activity:

  1. Complete agreed processing in GP.

  2. Pause relevant integrations and data entry.

  3. Take and verify backups.

  4. Capture final source reports.

  5. Run the final data migration.

  6. Reconcile balances and open documents.

  7. Test critical workflows and connections.

  8. Obtain approval to begin processing in Business Central.

  9. Communicate access and support arrangements to users.

Define go/no-go criteria before the cutover starts. State who can approve go-live, what would trigger a delay and how the business would resume operations if the transition cannot proceed.

Any rollback approach must address transactions already entered into Business Central, otherwise records could be duplicated or lost between systems.

Checklist outcome: a rehearsed cutover plan with clear decision points and recovery arrangements.

9. Support the first reporting cycle

Go-live is the start of a new operating routine.

Provide a clear support channel, maintain an issue log and review urgent problems daily during the initial period. Monitor integrations, payment processing, stock movements and reporting.

Plan additional support for the first month-end close. This is when finance can confirm that balances, reporting structures and controls work together under normal operating conditions.

Keep historical GP information accessible through the agreed retention approach, with suitable access controls.

Checklist outcome: stable operations and a completed first reporting cycle.

Frequently asked questions

Will all Dynamics GP history transfer into Business Central?
Do not assume it will. Coverage depends on the migration route, configuration and data type. Agree which information becomes operational data, which is available as historical reference and which remains in a separate archive.

How long does a GP to Business Central migration take?
The timeline depends on company count, data quality, customisations, integrations and testing requirements. Establish a realistic schedule after discovery and use trial migrations to validate the cutover window.

Can we continue using GP during the project?
Plan to keep GP as the operational system during preparation and testing, with a defined point at which processing stops for final migration. Agree the transition process with your implementation partner.

What is the most important go-live check?
Confirm that critical balances reconcile and essential workflows pass business testing. A completed data transfer alone is not sufficient approval to go live.

Plan your next step with 4Sight Dynamics Africa

A well-prepared migration gives your team clear answers about data, responsibilities and business continuity before the transition begins.

Whether you are reviewing your own GP environment or helping a customer plan their move, contact 4Sight Channel Partner to discuss your requirements and the next steps towards Business Central.



Leave a Reply

Your email address will not be published. Required fields are marked *