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

Lesson 2 of 5

The cutover runbook

11 min

The runbook (also called the cutover plan) lists every task needed to move from the legacy system to live operation, with its owner, timing, dependencies and proof of completion. SAP's own cutover guidance describes the plan as the tasks required before go-live along with timelines, responsibilities, resources and contingency. A good runbook is precise enough that a tired person at 03:00 on Sunday can execute their step without asking anyone what it means.

Three sections

Pre-cutoverWeeks before the window: static master data loads, user provisioning, transports, open-item cleanup, communications
Cutover windowFrom transaction freeze to business release: conversion, loads, reconciliation, technical checks, verification, go/no-go
Post-cutoverAfter release: first transactions monitored, catch-up postings, legacy decommissioning steps, hypercare start
Runbook sections. Moving work out of the window into pre-cutover is the cheapest way to create time.
The Sign-Off Table · thesignofftable.com/academy/sap-pmo-301

Anatomy of a runbook task

Each task is a row with the same fields. The discipline of filling every field is what turns a to-do list into a plan you can run against the clock.

FieldExample (Contoso task C-214)
ID and nameC-214 Load open purchase orders for supplier Lakeside Components
Owner and backupData migration specialist; backup named
System and clientProduction, client as defined for go-live
PredecessorsC-198 Business partners validated; C-205 Products validated
Planned start, durationSaturday 04:25, 135 minutes (from Mock 2 actual)
InstructionsLink to the work instruction, including the selection and expected record count
VerificationRecord count matches extract; sample of 20 checked by purchasing key user
EvidenceLoad log and signed count stored in the cutover folder
Status and actualsNot started, running, done, failed; actual start and end

Fields of a runbook task. Durations come from rehearsal actuals, not from estimates.

Dependencies and the critical path

Tasks depend on each other: business partners before open orders, products before stock, G/L balances before open items can be reconciled. Chain them, then find the critical path: the longest sequence of dependent tasks, which sets the minimum duration of the cutover. The time between the end of the critical path and the end of the window is your float, or contingency. After Mock 2, Contoso's cutover fitted the 60-hour window with only 1.5 hours of float, which was far too thin for a real weekend.

  1. Legacy lockedFriday 18:00; final backup taken
  2. Technical conversionSystem converted; technical checks
  3. Master data validatedBusiness partners, products checked by owners
  4. Open items and stockLoaded or converted, then reconciled
  5. Finance reconciliationDan signs balances before go/no-go 1
  6. VerificationProduction verification tests by Priya's team
  7. Business releaseUsers unlocked Monday 06:00
Contoso's critical path in simplified form. A delay to any step delays everything after it.
The Sign-Off Table · thesignofftable.com/academy/sap-pmo-301

Ways to create float

  • Move static work out of the window. Load master data that rarely changes in pre-cutover and control changes to it.
  • Parallelize. Run independent tasks side by side, for example stock reconciliation per plant.
  • Shorten validation without weakening it. Prepare reports and expected totals in advance so business checks start the moment a load ends.
  • Remove waits. Many overruns come from people waiting for a call, a password or an approval, not from the work itself.

Luis moved product and bill of material checks into pre-cutover and split stock reconciliation by plant, which gave the dress rehearsal four hours of contingency.

Business and communication tasks belong in the runbook

Business tasks are not a side list. The legacy period close, the stock count at the Chicago warehouse, Dan's reconciliation sign-off, Maria's first sales order for Great Lakes Fleet Services, and the go-live message to users are runbook tasks with owners and times like any other. So are the checkpoint calls, the go/no-go meetings and the messages to executives.

  1. Go-live minus 8 weeksRunbook draft 1All tasks listed; owners named; first durations estimated
  2. Mock 1First timed runDurations measured; sequence gaps found
  3. Mock 2Runbook draft 2Fixed sequence; full volumes; fallback tested
  4. Dress rehearsalRunbook finalExecuted as written; changes after this need approval
  5. Cutover weekendRunbook liveEvery task tracked with actual start and end
The runbook matures through the rehearsals. After the dress rehearsal it is under change control.
The Sign-Off Table · thesignofftable.com/academy/sap-pmo-301

Where should the runbook live? Many programs keep it in a dedicated workbook; some track cutover tasks as project tasks in SAP Cloud ALM alongside the rest of the project. The tool matters less than having one master version, under change control after the dress rehearsal, that everyone executes from.

What would you do?

In the dress rehearsal, the task "Run open sales order report for validation" has no owner because the analyst who used to run it left the company. What should Luis do?

Key points
  • The runbook lists every task with owner, backup, timing, dependencies, instructions, verification and evidence.
  • Durations come from rehearsal actuals; the critical path and float show whether the plan fits.
  • Create float by moving static work out of the window, parallelizing and removing waits.
  • Business, checkpoint and communication tasks are runbook tasks like any other.

Check your understanding · not graded

Lesson check

  1. 1. What should a runbook task specify?

  2. 2. What is the critical path of a cutover?

  3. 3. Where should runbook task durations come from?

  4. 4. Which change usually creates the most float cheaply?