EN
Insight

The cutover runbook: making the cutover weekend predictable

A cutover weekend becomes predictable when everyone knows in advance who does what and when, how success is measured, and how to roll back. The cutover runbook, called the cutover plan in many projects, records exactly that. Its time windows come from a dress rehearsal with measured run times.

Martin Hörnig5 min read

In brief
  • Every line of the runbook has an owner, a time window, a dependency, and a checkpoint.
  • The steering committee approves the go/no-go criteria and the fallback plan before the weekend begins.
  • The dress rehearsal with production volumes provides the run times. Without it, every time window is a guess.
  • Many gaps lie outside data migration, for example in interfaces, authorizations, forms, and background jobs.

What the runbook does

Cutover is the move from the legacy system to the new one. The legacy system is closed for postings, the data is transferred and reconciled, and then the go/no-go decision is made. This usually happens over a weekend, often at a month-end or quarter-end.

The runbook is a list worked through line by line, with time, result, and sign-off. Anyone with a question at three in the morning finds the answer in the line.

We provided interim overall project leadership for an SAP S/4HANA implementation at an industrial company. In that role, we were also responsible for cutover management, including the test migrations (mock migrations).

What goes into every line

ColumnContentWhy
Number and taskShort and unambiguous, one result per lineEvery follow-up question refers to one line
OwnerA named person with a backupUnclear ownership costs hours at night
Time windowStart and duration, planned and actualDeviations show up at once
DependencyWhich lines must be complete firstThe sequence of migration objects is not arbitrary
CheckpointHow the result is checked and who signs offWithout sign-off, the next line does not start
Point of no returnFlags the lines after which going back costs moreThe steering committee knows how long it can still decide freely
StatusOpen, in progress, done, issueOne shared picture of the situation at a glance

The runbook also includes a contact list with availability for the whole weekend, fixed status meetings, and an escalation path. A communication plan for business units, customers, and suppliers completes it.

The sequence up to the first business day

The exact timings depend on your project; the order stays the same.

TimingWhat happens
6 to 8 weeks beforeDress rehearsal with production volumes and measured run times, then revision of the runbook
4 weeks beforeThe steering committee approves the runbook, the go/no-go criteria, and the fallback plan; customers and suppliers are informed
2 weeks beforeMaster data freeze: changes to material, supplier, and customer masters only with approval
The week beforePre-load of the frozen master data, checked by key users
Last business day in the legacy systemClose open transactions, reconcile stock, stop background jobs, and lock the legacy system for postings
Cutover weekendTransfer transaction data in a fixed order, reconcile, spot checks by key users, go/no-go
First business dayStart of hypercare: ramp-up with extra support and a daily status meeting

The order of the objects follows their dependencies. Purchasing info records need suppliers and materials, stock needs storage locations and valuation data, and open purchase orders need suppliers, materials, and conditions. Define the right tool for each object before the first test migration.

In a system conversion, the weekend looks different technically, because the existing system is converted rather than a new one loaded. The principle of the runbook still applies.

Go/no-go criteria that hold up

The decision on Sunday is easier if the criteria are measurable and were approved beforehand. Criteria like these have worked well.

  • Stock quantities and values per plant and storage location within the agreed tolerance
  • Open purchase orders complete by number and value, spot checks done
  • Asset values per depreciation area reconciled with asset accounting
  • Critical interfaces tested, for example to banks, carriers, and warehouse systems
  • Key users can log on and post their most important transactions
  • Fallback plan checked and the point of no return not yet passed

Who decides, and at what time, is also fixed in advance. A no-go is not a failure. It protects the company from a Monday on which nothing is right.

The fallback plan

If the criteria are not met, you need a prepared way back. The fallback plan describes how long a fallback remains possible, who triggers it, and which steps follow. These include unlocking the legacy system, switching interfaces back, informing everyone involved, and setting a new date.

The point of no return usually comes when the new system first has an effect outside the company. Examples are the first purchase order sent to a supplier or the first payment. After that, transactions would have to be unwound twice: in the system and with the supplier or bank. If you have not prepared the fallback plan, you have no real choice on Sunday.

The dress rehearsal counts more than any single test

In the dress rehearsal, the runbook runs once from start to finish, with production volumes and in a production-like environment. This shows whether the time windows are long enough. If the stock load takes three hours instead of one, everything after it shifts.

Measure every line, including reconciliations, sign-offs, and waiting times. They often take longer than expected. After the dress rehearsal, the runbook is revised with the measured times, and only then is the date set.

Typical gaps in the runbook

Many problems on the cutover weekend have nothing to do with data migration. Check your runbook for these points.

  • Stop interfaces in the legacy system and start them in the new system at the right time
  • Switch off background jobs in the legacy system so that nothing posts after the lock
  • Test key user authorizations before the first business day
  • Print or send output forms such as purchase orders, delivery notes, and invoices once under real conditions
  • Set number ranges in the new system so they do not collide with legacy documents
  • Inform suppliers and customers about pauses in deliveries and orders
  • Staff hypercare, with clear contacts for the first days

How we help

We draw up cutover runbooks, plan the dress rehearsal, and support the cutover weekend through hypercare. We do this as part of your SAP S/4HANA transformation or in interim project management.

Initial call: 30 minutes, free of charge.

Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.

Initial call Call