SAP S/4HANA Migration Cutover Checklist
Cutover is the stretch between the last day in the old system and the first day in the new one. This checklist gives program managers and cutover leads a structured list of what must be agreed, frozen, loaded, validated and handed over for an S/4HANA go-live.
0 of 35 items complete
15 critical items still open - these are the highest-risk gaps.
Cutover planning (T minus 8 weeks to T minus 2 weeks)
Freeze and preparation
Technical conversion and data load
Validation and go-live decision
Hypercare handover
Critical items should be complete before the go or no-go decision. Anything open on a critical item needs a named owner and an agreed fallback.
Cutover runbook review
Send your runbook outline and rehearsal timings for a short written review of gaps. Optional.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through the five groups in order, from planning eight weeks out to handover after go-live. Tick items as they are confirmed, not as they are started. Items marked critical are those where a miss can force a rollback or a data integrity problem; treat them as gates. Use the checklist alongside, not instead of, a detailed runbook with minute-level tasks, because this list names the topics but not your project's task durations. Export the checked list to PDF for the go or no-go meeting.
- Tick only what is confirmed
- Treat critical items as gates
- Pair with a minute-level runbook
- Rehearse at least once with timings
Why cutover needs structure
S/4HANA conversion and data migration have long-running, strictly ordered steps, such as the downtime-heavy phases of a conversion tool or loads of dependent migration objects. A step that runs two hours over can consume the whole weekend buffer. The rehearsals matter most: they provide the actual durations that make the plan credible. A cutover plan built from estimates alone usually collapses on the first real run.
Reading progress
Count both total completion and critical completion. A project at 90 percent overall with two open critical items is not at 90 percent readiness. Before the go decision, every critical item should be done, or have an accepted risk with an owner. If the critical open list is longer than a handful the week before, consider moving the date rather than compressing validation.
Common mistakes
Teams often skip the rollback plan because it feels pessimistic, then discover at hour 30 that no one knows the decision point. Others forget to pause interfaces or to communicate the freeze to the business. Under-resourcing validation is the most costly mistake: finance and inventory reconciliations need subject experts present, not just consultants.
Frequently Asked Questions
How many rehearsals do I need?
Most programs run at least one full technical rehearsal and often two or three data migration mock loads. Each rehearsal should record actual durations and issues. The final one should be run as close as possible to the real timeline, with the same people.
What is a go or no-go criterion?
It is a pre-agreed, measurable condition for continuing, such as finance trial balance tying to the source, zero open severity-one defects, and key interfaces passing end-to-end tests. Agreeing these in advance prevents arguments at 3 a.m.
Should legacy ECC be switched off immediately?
Usually it is kept read-only for a defined period for reference, audit and reconciliation, and then archived or decommissioned according to a retention plan. Check legal and audit requirements before deciding the date.
Can I use this for greenfield and brownfield?
Yes, the structure applies to both. Brownfield programs lean on conversion tool steps, while greenfield programs lean more on migration cockpit loads. Add or remove items to match your approach.
If you want a second pair of eyes on your cutover runbook or rehearsal timings, we can review it with you. The checklist is free to use as is.
Related Tools
SAP Go-Live Hypercare Plan Template
A fill-in hypercare plan for the weeks after SAP go-live, with severity targets, war room schedule, exit criteria and approvals.
SAPSAP Data Migration Object Worksheet
An editable register of S/4HANA migration objects with record counts, cleansing progress, load method and mock load effort.
SAPECC to S/4HANA Readiness Assessment
A ten-question scorecard that tells you how ready your SAP ECC landscape is for an S/4HANA move and where to spend the next quarter.
SAPSAP Greenfield vs Brownfield Assessment
Ten questions that point toward brownfield conversion, selective data transition or greenfield re-implementation for your S/4HANA move.