Week 9 of 12
Data migration and mock cutovers
On an S/4HANA move, the migrated data is itself a test object. Every mock load needs reconciliation: balances by company code, open items, stock quantities and values, master data counts. You will run these checks for every mock, the dress rehearsal and the real cutover, at 3 a.m., under pressure.
Data migration was named alongside testing as an underestimated phase in the Horváth study.
This week: agree tolerances and script the reconciliation
- Agree reconciliation tolerances with finance before Mock 1, per check: absolute and percentage.
- Script every check you can: GL balances, AR and AP open items, stock quantity and value, assets, Business Partner counts and links.
- Give each mock one goal: prove it runs, prove it reconciles, prove it fits the window, prove it on production-sized hardware.
- Record step timings in every mock. Anything over 20% of plan on the critical path gets an action before the next rehearsal.
Number of the week
30%
average schedule overrun on S/4HANA projects; underestimated testing and data migration were among the causes.
Source: Horváth study, via CIO.com (2025)Use this week
- Data Migration Reconciliation Checklist →
30 checks with source and target reports, numeric tolerances and a mock-by-mock comparison.
- Mock Cutover Rehearsal Tracker →
Goals and exit criteria per rehearsal, step timings and variance flags.
Next week: the cutover weekend and the go/no-go call. What evidence the room needs before anyone signs.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.