Cutover Weekend Playbook
As of 2026-10-04
Treat cutover like a flight checklist: an hour-by-hour runbook (task · owner · duration · success criterion · rollback), rehearsed in a full dry-run. Reconciliation is the heart — formal tie-out of row counts + key-figure totals new-vs-legacy, with tolerances agreed in advance with finance (GL zero-variance). Go/no-go gates with named decision-makers, decided before the weekend, not under pressure. A real, tested rollback with an explicit signed point-of-no-return. Roles: cutover manager · technical leads · business validators · comms owner. Hypercare (2-4 weeks, legacy read-only) follows, exited by a gate. A clean cutover books the next three engagements.
What you will learn
- Work through a realistic scenario: Logistics company, core finance + operations cutover to BDC over a 3-day weekend, board-visible go-live, hard Monday-morning reporting deadline.
- Recognize and avoid the anti-pattern: No rehearsed dry-run — Step timings wrong; the weekend overruns and gates cascade.
- Apply the module's core decision: Runbook readiness — choose Hour-by-hour runbook rehearsed against a copy env, not First execution being the live weekend.
- Track mastery with the KPI: Dry-run completed (target: ≥ 1 full dry-run before go-live; red flag: Live weekend is the first end-to-end run).
Module overview
The cutover weekend is the few-dozen hours where months of migration work either lands cleanly or unravels in public. A senior consultant treats it like a flight checklist: every task scripted, every owner named, every go/no-go gate pre-agreed, and a rollback path that actually works. Improvisation at cutover is how trust dies.
The runbook is the deliverable. Long before the weekend, you write an hour-by-hour runbook: each task with a start time, duration, owner, dependency, success criterion, and explicit rollback action. The runbook is rehearsed in at least one full dry-run against a copy environment — the dry-run is where you discover the step that takes 4 hours instead of the 30 minutes you assumed. A cutover without a rehearsed runbook is a gamble, not a plan.
Prerequisites
- Intermediate hands-on experience on SAP analytics projects
- Review core concepts first: C035, C033, C032
Outcomes
- Work through a realistic scenario: Logistics company, core finance + operations cutover to BDC over a 3-day weekend, board-visible go-live, hard Monday-morning reporting deadline.
- Recognize and avoid the anti-pattern: No rehearsed dry-run — Step timings wrong; the weekend overruns and gates cascade.
- Apply the module's core decision: Runbook readiness — choose Hour-by-hour runbook rehearsed against a copy env, not First execution being the live weekend.
- Track mastery with the KPI: Dry-run completed (target: ≥ 1 full dry-run before go-live; red flag: Live weekend is the first end-to-end run).
Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.