Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 5 of 5

Integrating migration with cutover

9 min

Data migration is the longest single stream of go-live weekend, but it is not the only one. The cutover plan coordinates technical steps (transports, system settings, interfaces, users), business steps (freezes, stock counts, communication) and data steps. In SAP Activate, cutover is planned during Realize and executed in Deploy. The migration runbook must fit into that plan, with clear hand-offs in both directions.

Business cutoverFreezes, last shipments and postings, stock count, customer and supplier communication
Data migrationDelta and open item loads, reconciliation, owner validation
Technical cutoverFinal transports imported, system and client settings, users and roles, interfaces stopped and restarted, jobs scheduled
GovernanceGo/no-go checkpoints, issue triage, escalation to Grace and the steering committee
The streams of a cutover plan. Migration depends on the technical stream and feeds the business stream.
The Sign-Off Table · thesignofftable.com/academy/sap-dmg-304

Hand-offs that must be explicit

FromToHand-offWhy it matters
Technical cutoverMigrationAll configuration transports imported and verified in productionLoads fail or post wrongly against missing configuration
Business cutoverMigrationTransactional freeze confirmed; last legacy ERP postings completeOpen items extracted too early miss the last postings
Business cutoverMigrationPhysical stock count resultsInventory balances must reflect counted stock in plant 1910 Monterrey
MigrationFinanceOpen items and balances loaded and reconciledDan signs the opening balance sheet for company code 1910
MigrationTechnical cutoverLoads complete; interfaces may restartInterfaces sending documents too early create duplicates

Typical hand-offs between streams. Each is a runbook step with an owner on both sides.

Go-live weekend for data

  1. Fri 6 p.m.Freeze and lockLegacy ERP locked for postings; its interfaces stopped; stock count starts in Monterrey
  2. Fri 8 p.m.ExtractOpen items, stock and balances extracted after the last postings
  3. Sat 2 a.m.Delta and open documentsMaster data delta, open purchase and sales orders
  4. Sat 2 p.m.Checkpoint 2Order and stock reconciliation; go or stop for finance loads
  5. Sun 6 a.m.Finance loadsInventory values, AR, AP and G/L balances; clearing accounts net to zero
  6. Sun 2 p.m.Final go/no-goOwner sign-offs; Grace and the steering committee decide
A simplified data view of the go-live weekend for company code 1910. Times are illustrative and come from the dress rehearsal.
The Sign-Off Table · thesignofftable.com/academy/sap-dmg-304

Checkpoints and the point of no return

Go/no-go checkpoints are planned moments where named people decide, on agreed criteria, whether to continue. They belong in both the cutover plan and the migration runbook. The most important is the point of no return: the last moment at which the program can still fall back to the old system without losing business data. After users start posting in SAP S/4HANA, falling back means re-entering or reversing real business, so the fallback plan is usually viable only up to that point.

  1. Are all loads complete with error rates within thresholds?Yes → next question · No → fix and rerun if time allows, else escalate
  2. Do reconciliations match, with every difference explained and accepted by the owner?Yes → next question · No → stop; owner and Luis decide on correction or fallback
  3. Have the data owners signed off their objects?Yes → next question · No → no go
  4. Is there still enough time before the point of no return?Yes → go · No → invoke the fallback plan as agreed
A data go/no-go checkpoint. The criteria are agreed before the weekend, not during it.
The Sign-Off Table · thesignofftable.com/academy/sap-dmg-304

Rehearse the whole cutover

The dress rehearsal should run the full cutover plan, not only the migration runbook, so that the hand-offs between streams are tested too. Typical findings are timing gaps at hand-offs, interfaces that restart on their own, and checkpoints that cannot be held because a decision-maker is not on shift. Each finding is fixed in both documents.

What would you do?

At the Sunday checkpoint of the Alternadores del Norte load, open receivables differ from the legacy ERP by MXN 3,800 across two customers. The point of no return is in six hours. What should happen?

Key points
  • The migration runbook is one stream of the cutover plan, alongside technical, business and governance streams.
  • Make every cross-stream hand-off an explicit, owned step.
  • Hold go/no-go checkpoints on pre-agreed criteria; know the point of no return.
  • Data owners sign their objects before users post; the dress rehearsal tests the full cutover plan.

Check your understanding · not graded

Lesson check

  1. 1. What is the point of no return in cutover?

  2. 2. Which hand-off must precede loading inventory balances?

  3. 3. Why should interfaces restart only after loads complete?

  4. 4. In SAP Activate, when is cutover executed?