# SAP Cutover Runbook Timing Worksheet > Source: https://netray.co/tools/sap-cutover-runbook-timing-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Build the hour-by-hour cutover runbook with task owners, durations and buffers, and total the business downtime. Exports to Excel. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP cutover manager - Basis lead - SAP program manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Seq **Key:** seq **Type:** number **Format:** integer #### Task **Key:** task **Type:** text #### Stream **Key:** stream **Type:** select **Options:** - Basis - Data migration - Finance - Logistics - Interfaces - Security - Business sign-off #### Owner **Key:** owner **Type:** text #### Planned duration **Key:** mins **Type:** number **Unit:** min #### Buffer **Key:** buffer **Type:** number **Unit:** % #### Duration with buffer **Key:** total **Type:** number **Expr:** mins * (1 + buffer / 100) **Format:** minutes #### Business downtime? **Key:** downtime **Type:** select **Options:** - Yes - No #### Last rehearsal result **Key:** rehearsal **Type:** select **Options:** - Not run - Passed - Passed with issues - Failed **Rows:** **Seq:** 1 **Task:** Lock users and stop batch scheduling **Stream:** Basis **Owner:** Basis lead **Mins:** 30 **Buffer:** 10 **Downtime:** Yes **Rehearsal:** Passed **Seq:** 2 **Task:** Final delta extract from legacy **Stream:** Data migration **Owner:** Data lead **Mins:** 180 **Buffer:** 25 **Downtime:** Yes **Rehearsal:** Passed with issues **Seq:** 3 **Task:** Load open items and balances **Stream:** Finance **Owner:** Finance lead **Mins:** 120 **Buffer:** 20 **Downtime:** Yes **Rehearsal:** Passed **Seq:** 4 **Task:** Reconcile stock and open orders **Stream:** Logistics **Owner:** Supply chain lead **Mins:** 150 **Buffer:** 25 **Downtime:** Yes **Rehearsal:** Not run **Seq:** 5 **Task:** Switch interfaces to new endpoints **Stream:** Interfaces **Owner:** Integration lead **Mins:** 90 **Buffer:** 30 **Downtime:** Yes **Rehearsal:** Passed with issues **Seq:** 6 **Task:** Go / no-go confirmation **Stream:** Business sign-off **Owner:** Program manager **Mins:** 30 **Buffer:** 0 **Downtime:** Yes **Rehearsal:** Passed **Totals:** #### Total planned minutes **Key:** mins **Agg:** sum **Format:** minutes #### Total with buffer **Key:** total **Agg:** sum **Format:** minutes **Summary:** #### Total sequential hours with buffer **Key:** hours **Expr:** sum_total / 60 **Format:** hours #### Average task length **Key:** avg_task **Expr:** sum_total / count **Format:** minutes **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use it **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** Netray can help automate reconciliation checks during cutover by comparing legacy and new system figures directly from the databases. **Faq:** #### How long is a typical SAP cutover? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** Use the Seq column to order tasks and compute the critical path separately. The sequential total is a conservative upper bound. ## Search terms sap cutover plan template excel, sap cutover runbook, s4hana cutover timing, sap go live runbook template, sap downtime estimate worksheet, sap cutover task list --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json