SAP Cutover Runbook Timing Worksheet
The cutover runbook decides whether a go-live fits the weekend. This worksheet lets you list every task with an owner, a duration and a buffer, so you can see the total downtime and where it needs to shrink.
| Seq | Task | Stream | Owner | Planned duration (min) | Buffer (%) | Duration with buffer | Business downtime? | Last rehearsal result | |
|---|---|---|---|---|---|---|---|---|---|
33 min | |||||||||
225 min | |||||||||
144 min | |||||||||
187.5 min | |||||||||
117 min | |||||||||
30 min |
Totals assume tasks run one after another. If streams run in parallel, the critical path is shorter, so mark the sequence carefully and compute the path in your plan. Use rehearsal timings, not estimates, once available.
Cutover reconciliation help
Learn how to automate legacy versus new balance checks during cutover. Optional.
Optional. The tool and every export work without this. No spam.
How to use it
List tasks in execution order, give each one an owner, and enter the planned duration from your last rehearsal. Add a buffer based on how reliable that task is: a database restore may need 10 percent, a data load with reconciliation may need 25 percent or more. Mark which tasks fall inside business downtime. Export to Excel for the cutover command center.
- One owner per task, with a named backup
- Use measured rehearsal times
- Include business sign-off steps as tasks
- Add rollback decision points
The arithmetic
Duration with buffer equals planned minutes times one plus the buffer percent. The summary converts the sum to hours. Because the sheet adds tasks in sequence, it gives an upper bound when streams can run in parallel. For the real critical path, find the longest chain of dependent tasks in your plan and compare it with the available window.
Rehearsals and the downtime window
Plan at least two full dress rehearsals for an S/4HANA conversion or migration, and capture timings for each step. Technical steps such as the downtime-optimized conversion, data load cycles and interface switching often dominate. If the total exceeds the agreed window, shorten the longest tasks first, for example by moving master data loads before the freeze.
Common mistakes
Teams forget time for reconciliation, approvals and handovers between streams. They also reuse optimistic durations from a small test dataset. Always keep a go or no-go point before the irreversible step, with a tested rollback plan.
Frequently Asked Questions
How long is a typical SAP cutover?
It varies widely with data volume and approach. Some conversions fit into a long weekend, others need extended windows. Your rehearsals are the only reliable guide for your landscape.
How much buffer should I add?
Base it on rehearsal variance. Stable steps need little, while data loads and interface switches usually need 20 to 30 percent. Re-estimate after every rehearsal.
Does this replace a project plan tool?
No. It is a focused timing sheet. Many teams keep the detailed plan in a tool and use this sheet to check the total downtime quickly.
What about parallel tasks?
Use the Seq column to order tasks and compute the critical path separately. The sequential total is a conservative upper bound.
Netray can help automate reconciliation checks during cutover by comparing legacy and new system figures directly from the databases.
Related Tools
SAP Migration RAID Log Worksheet
Log risks, assumptions, issues and dependencies for an SAP migration with automatic risk scores. Exports to Excel.
SAPSAP Business Partner CVI Conversion Worksheet
Plan customer and vendor master conversion to Business Partner with record counts, error rates and cleanup effort per company code or account group.
SAPSAP S/4HANA Test Scenario Tracker
Track integration and user acceptance test scenarios with pass rates and open defects per process area. Exports to Excel.
SAPSAP S/4HANA Steering Committee Status Report Template
A one-page monthly status report for SAP S/4HANA steering committees: RAG by workstream, milestones, top risks and decisions needed.