# SAP S/4HANA Migration Cutover Checklist > Source: https://netray.co/tools/sap-s4hana-cutover-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A practical cutover checklist for S/4HANA go-live weekend, grouped from planning and freeze through validation and handover. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP program manager - Cutover manager - SAP Basis lead ## Tool **Kind:** checklist **Scoring Note:** 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. **Groups:** #### Cutover planning (T minus 8 weeks to T minus 2 weeks) **Items:** **Text:** Cutover runbook drafted with every task, owner, duration and dependency **Critical:** true **Text:** Go and no-go criteria agreed by business and IT sponsors **Critical:** true **Text:** Rollback decision point and fallback procedure documented and approved **Critical:** true Cutover calendar aligned with period-end close, payroll and customer shipping peaks Technical rehearsal (dress rehearsal) planned with timing capture Communication plan sent to users, customers and key suppliers Production support roster and war room staffing confirmed #### Freeze and preparation **Items:** **Text:** Code and configuration freeze in ECC enforced with change control **Critical:** true All open transports released and imported or consciously deferred Business freeze window communicated: posting, master data changes, new orders **Text:** Interfaces to external systems paused or queued with a restart plan **Critical:** true Background jobs reviewed, scheduled jobs suspended and documented **Text:** Final backup of source system taken and restore tested **Critical:** true Open item clean-up done: goods receipts, invoices, deliveries, production orders #### Technical conversion and data load **Items:** **Text:** Conversion or migration tool executed per rehearsed runbook **Critical:** true **Text:** Post-conversion checks run: consistency, DB, and system health **Critical:** true Migration cockpit objects loaded in dependency order, load results logged **Text:** Data reconciliation reports run against the agreed source totals **Critical:** true Authorizations, roles and Fiori launchpad content verified for key users Output devices, printers and forms tested Number ranges and open document numbering aligned to the cut-off **Text:** Interfaces re-pointed and connectivity tested end to end **Critical:** true #### Validation and go-live decision **Items:** **Text:** Smoke tests run per process: order to cash, procure to pay, record to report **Critical:** true **Text:** Finance trial balance and sub-ledger tie-out signed by controller **Critical:** true **Text:** Inventory valuation and quantity reconciled in key plants **Critical:** true Key batch jobs run once successfully, including MRP Business sign-off recorded for each process area **Text:** Go or no-go meeting held and decision documented **Critical:** true Users notified of go-live and new access details #### Hypercare handover **Items:** **Text:** War room live with incident triage, severity definitions and daily stand-ups **Critical:** true Monitoring in place for interfaces, jobs, performance and dumps Known-issue list published with workarounds Legacy ECC set to read-only and retention plan agreed Lessons-learned session scheduled within two weeks Hypercare exit criteria and end date confirmed with business ## Content **Intro:** 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. **Sections:** #### How to use the checklist **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How many rehearsals do I need? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap s4hana cutover checklist, sap cutover plan template, s4hana go live checklist, sap migration cutover runbook, sap go live weekend checklist, s4hana conversion cutover steps --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json