Lesson 1 of 5
Cutover strategy
11 min
Cutover is the controlled move from the old way of running the business to the new one: the technical steps that bring the production system into its final state, the data that moves into it, and the business steps that stop work in the legacy system and start it in SAP S/4HANA. In SAP Activate, cutover is executed in the Deploy phase, after integration testing and user acceptance testing are complete, but it is designed much earlier. The strategy decides what moves, when, and in what order. Everything else in this course follows from it.
Four kinds of work in one cutover
Big bang, phased or parallel
The first strategic choice is how much changes at once. In a big bang, all in-scope companies, plants and processes move on one weekend. In a phased cutover, they move in waves, by site, company code, region or process. A parallel run, where old and new systems both process the same transactions for a period, is rare in SAP programs because it doubles the business workload and creates two sets of truth to reconcile.
| Big bang | Phased | Parallel run | |
|---|---|---|---|
| What moves | Everything in scope at once | Waves by site, entity or process | Both systems run the same work for a period |
| Main benefit | One cutover; no temporary interfaces | Smaller blast radius; lessons carried to later waves | Direct comparison of results |
| Main cost | Highest single-event risk | Temporary interfaces and longer program | Double data entry and reconciliation effort |
| Fits when | Processes are tightly integrated across sites | Sites or entities are loosely coupled | Rarely; sometimes for a narrow calculation such as payroll |
A system conversion is big bang for the system by nature: the whole ECC database is converted at once. You can still phase the business change, for example switching on new functions after go-live, but the technical cutover happens in one window.
Contoso's choice
Contoso converts its ECC 6.0 EHP 8 system to SAP S/4HANA in one weekend. Plants 1710 Detroit and 1720 Chicago share stock, a single company code 1710 and common customers, so moving one plant without the other would have required temporary interfaces for stock transfers and sales. Contoso Parts Distribution LLC, company code 1810 with plant 1810 Toledo, sits in the same ECC system and converts with it. Luis, the cutover manager, therefore plans a big bang with one cutover window.
Timing
The second choice is when. Cutover weekends are usually chosen to start just after a period-end close in the legacy system, so opening balances are clean and the new system starts a fresh period. Avoid quarter-end and year-end, peak shipping weeks and public holidays when key people are away. Then size the downtime window: how long the business can be without a system. For Contoso that is 60 hours, from Friday 18:00 to Monday 06:00, set by the first shift at the Detroit plant.
- Does the date fall just after a legacy period-end close?Yes → clean opening balances · No → plan extra reconciliation for a mid-period start
- Is it clear of quarter-end, year-end and peak season?Yes → continue · No → move the date; finance and logistics cannot absorb both
- Are the key people available, with backups?Yes → continue · No → check vacation calendars and holidays before committing
- Does the measured cutover duration fit the downtime window with contingency?Yes → confirm the date · No → shorten the cutover or negotiate a longer window
Freezes
A cutover strategy also sets the freezes that protect the move. A change freeze stops new configuration and code, apart from approved fixes, so what goes live is what was tested. A master data freeze or controlled change window stops uncontrolled changes to customers, suppliers and products while they are being moved. A transaction freeze (the business blackout) stops postings in the legacy system once the final data is taken. Each freeze needs a start date, an owner and an exception process.
- Go-live minus 4 weeksChange freezeOnly approved go-live fixes move to production
- Go-live minus 2 weeksMaster data controlChanges logged and replayed into the new system
- Friday beforeLegacy period closeFinal postings and close in ECC
- Friday 18:00Transaction freezeLegacy locked; window starts
- Monday 06:00Business releaseUsers start in SAP S/4HANA; hypercare begins
In SAP S/4HANA Cloud Private Edition under RISE, some technical tasks in the window, such as system operations and backups, are performed by SAP according to the contract's roles and responsibilities. Check that document and put SAP's tasks in your plan with named contacts. In Public Edition the technical cutover is much smaller, because SAP provides the system, but the data, business and organizational layers remain yours.
What would you do?
Contoso's sales director asks Luis to move go-live one week later so that it falls on the last weekend of the quarter, after a big promotional push. What should Luis recommend?
- Cutover has technical, data, business and organizational layers; the strategy covers all four.
- Big bang, phased and parallel run trade single-event risk against duration and duplicated effort.
- Pick a date just after a legacy period close, clear of quarter-end, peaks and holidays.
- Freezes protect what was tested: change, master data and transaction freezes, each with an owner.
Check your understanding · not graded
Lesson check
1. In which SAP Activate phase is the production cutover executed?
2. Why is a parallel run rare in SAP programs?
3. What is the purpose of a change freeze before cutover?
4. Why does Contoso's system conversion lead to a big bang technical cutover?