When an SAP S/4HANA cutover begins, transactions stop in the legacy ERP before they start in S/4HANA. For a manufacturer, every hour of that window is production that either stops or runs on contingency procedures, with a backlog to post once the new system opens. A rehearsal must show that the plant can stop, migrate, validate, and restart within its window and still recover a usable operation before the next shift if the run falls behind.
An SAP S/4HANA cutover plan is the runbook for that switch. SAP’s S/4HANA Regional Implementation Group describes it as every task that must be performed before go-live, simulated in advance to document sequence and timing, then validated with the business. In SAP Activate, the team plans cutover in the Realize phase and executes it in Deploy.
How much a rehearsal can prove depends on how many times the team has worked through the cutover’s content (the data, workflows, and handoffs it depends on) before the real weekend, and that depends on when a working S/4HANA system with the company’s own data first exists. The checks below are written for a new implementation, where data is extracted from legacy systems and loaded into S/4HANA. A system conversion uses different technical tooling, but the business checks apply to both.
Measure the interruption as well as the migration
The rehearsal scorecard should also record which production activities must stop and which can continue under approved contingency procedures. It should show whether production orders, material movements, and work in progress stay traceable across the transition; how long the plant can absorb the outage before it reaches the next shift; and how much backlog must be posted in S/4HANA when processing resumes.
None of these has a universal threshold. Operations sets the acceptable interruption and restart conditions before the rehearsal, and the rehearsal reports against them.
Decide in advance how to record manual work done during the outage, and who posts it in S/4HANA once the system opens. The rehearsal should time that posting too.
Six things a good rehearsal tests
SAP calls this event the cutover simulation or dress rehearsal, and its project cutover guidance gives it one job: to test all aspects of the cutover before the production cutover. For an S/4HANA program, that comes down to six checks.
1. The full elapsed time
Time the whole sequence: legacy system freeze, extraction, transformation, loading into S/4HANA, reconciliation, interface activation, business validation, and release to users, with the handoffs between them. Data load runtime is one line in that sequence.
SAP’s cutover guidance schedules the go/no-go decision early enough to allow a restore back to the legacy systems and processes without disrupting operations. The rehearsal is where you learn whether your timings leave that room. If the sequence finishes with no time to investigate a problem, decide, and execute the recovery path, the plan does not fit the window.
2. Data at production volume and complexity
Run with production-representative data and the migration tooling you will use on the night. SAP Activate asks the test strategy to state when and where the team runs data migration tests and with what data, and lists load testing as its own test type. A small, clean extract can confirm the load objects run. It cannot show whether full volume finishes on time.
For a manufacturer, check open production orders and their status, inventory quantities and storage locations with their batch or serial number records, work-in-progress and open transactions, open purchase orders and deliveries in transit, and the master data relationships the first production shift depends on. Records that load but cannot be used by that shift count as a failed test.
3. Business restart
A successful logon and green technical checks show the system is up. SAP Activate separates the final business acceptance from the user acceptance testing done during sprints: before go-live, extensive, functional, end-to-end testing is performed on migrated business data.
For a plant, follow one representative order through what the next shift needs: release the production order, issue material, post the confirmation, then check the resulting inventory and order status. Include the plant-floor connections that the order touches, such as the interface to a manufacturing execution system (MES), label printing, warehouse movements, and quality inspections. Operations defines the workflows and expected results before the rehearsal starts.
4. People, handoffs and decision authority
SAP advises using the same cutover team and resources in the production cutover as in the simulation. Run tasks on the real clock: a step scheduled for 3 a.m. needs its owner ready at 3 a.m.
Every task owner should be able to answer four questions: what event authorizes the task to start, what evidence shows it is complete, who receives the handoff, and who can resolve an exception or stop the sequence. A runbook whose owners can answer those is one the team can execute.
5. Rollback, triggered by a failure
SAP calls for business continuity plans to be defined in detail and tested before the production cutover. Run the rollback in the rehearsal, ideally from a planned failure, and verify the backup it depends on.
The scenario should define what condition requires rollback, the point of no return after which restoring to the legacy system is off the table, and what happens to transactions posted in S/4HANA after the system opened. The third needs its own section in the plan, because restoring the legacy system does not account for that activity.
6. What the rehearsal cannot prove
A rehearsal system can differ from production in data volume, interface endpoints, authentication, and network configuration, and some steps cannot be exercised safely at all. Write those differences down, assess the risk of each untested activity, and carry them into the go/no-go decision. The report should separate what was tested successfully from what is assumed to work.
What the go/no-go meeting should receive
SAP Activate sets the bar: before the go/no-go decision, the team analyzes and fixes every issue found in the dress rehearsal, and estimates and manages the go-live risk level. The rehearsal report should give the steering committee six things.
| Deliverable | What it establishes |
| Actual timings and dependencies | Whether the complete sequence fits the cutover window |
| Data and business-validation results | Whether S/4HANA supports the required restart workflows on migrated data |
| Defects, owners and retest results | Whether rehearsal issues have been fixed |
| Recovery timing and decision cutoff | Whether a restore to the legacy system remains executable |
| Environment differences and untested steps | Which risks remain outside the rehearsal’s evidence |
| Explicit go/no-go criteria | What must be true before the business accepts the transition |
Fixing every issue and retesting it assumes the SAP S/4HANA cutover plan leaves time for another run.
Rehearse the content before the dress rehearsal
SAP’s cutover guidance places the cutover simulation after the solution build and testing cycles. When the working system arrives late in a program, the first chance to exercise the cutover content on it arrives too. LeapGreat calls the usual sequence backloaded waterfall and proposes a parallelized SAP Activate.
LeapGreat’s FrontLoad approach starts the program with a working S/4HANA development system, configured by automation in week two and populated with the customer’s business data and configurations. From week three, the Digital Twin connects processes, roles, data, decisions, transactions, documentation, and tests to that system. The program then runs three integration cycles that refine, test, and deploy it before cutover.
The dress rehearsal itself still needs production volume, the real migration tooling, and the production cutover team. It can exercise the content it checks much earlier. The company can work through production order relationships, the first-shift workflow, and own data from the first weeks. Because the Digital Twin keeps tests and documentation connected to the working system, the business can test the workflows it signs off on in the dress rehearsal in each of the three integration cycles.
LeapGreat states that FrontLoad does not remove design, testing, business decisions, or implementation discipline. The program remains responsible for the cutover plan, rollback scenario, and go/no-go criteria. Starting with a working S/4HANA system means data and workflow problems can surface in the first weeks, while you still have time to fix them before the dress rehearsal.
Check your S/4HANA program risk
See where your S/4HANA program’s risk sits before the cutover plan is locked. Get Your S/4 Transformation Risk Scorecard.
