01 · What loads, and in what order
The migration-object catalogue.
You cannot load an open invoice before the customer exists. Every object has a type and a load sequence — master data first, then the transactional open items that reference it. Filter the catalogue below.
| Seq | Object | Type | Load method | Validation |
|---|
Org structure & config travel by transport, not the Migration Cockpit — they are the container everything else loads into.
02 · The cutover window
Run the cutover.
A cutover is a countdown: freeze legacy, extract, load, reconcile, decide, open. Press Run cutover to walk the T-minus sequence, or step it yourself.
9 phases · T-7 to T+1 hypercare
03 · The decision gate
Go / no-go: every box, or you don’t go.
Cutover ends at a gate. These are the criteria I’d hold the line on — tick each as it clears; the verdict flips to GO only when they all do.
NO-GO
0 / 6 criteria cleared
ABOUT THIS RUNBOOK
The migration objects, load sequence and cutover phases are the standard SAP mechanism; the go/no-go criteria are the ones I hold to. I’ve run this cutover discipline for real on four XeerSoft Cloud ERP go-lives — freeze, migrate, reconcile, decide, hypercare — and this is how I’d carry it onto an SAP programme. It is a methodology artifact, not a delivered SAP migration.
See the delivered go-lives behind it →