Week 4 of 8

Data migration and mock loads

In Finance and Operations, the data management framework loads data through data entities and staging tables, in the sequence you set. Most load failures are sequencing or staging errors that nobody reviewed. In Business Central, the GP cloud migration brings balances, open items and history across, but historical years arrive open and must be closed.

Each mock load is a test with expected results. Counts, balances and open items have to reconcile to the source within an agreed tolerance, every time, including at 3 a.m. on cutover weekend.

This week: agree tolerances and track every entity in every mock

List every data entity (or GP migration area) in load order, with its execution unit and sequence, and the source extract it comes from.
Agree reconciliation checks and tolerances with finance before Mock 1: trial balance by legal entity, open AR and AP, inventory quantity and value, master data counts.
After every load, review staging errors and the execution log. A record skipped is a record you still owe.
Record load duration per entity in every mock. That is your cutover runbook timing.

Number of the week

Open

is how GP historical years arrive in Business Central after cloud migration. They must be reviewed and closed in Business Central.

Source: Microsoft Learn, Migrate Dynamics GP data to the cloud

Use this week

Dynamics 365 Data Migration Validation Tracker →
Entity load log with staging errors and timings, plus reconciliation checks with tolerances, mock by mock.
Mock Cutover Rehearsal Tracker →
A goal for each rehearsal and step timings against plan.

Next week: security roles and segregation of duties, and the check Dynamics 365 does not run for you.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.