SAP Cutover Planning: From Dress Rehearsal to Successful Go-Live

The cutover – the switch from the legacy system to the new SAP system – is the most critical moment of an SAP project. Weeks or months of preparation culminate in a window of just a few days where errors can have severe consequences. Systematic cutover planning is the key to success.

What Is a Cutover?

The cutover encompasses all activities required for switching from the old to the new system environment: data migration, technical switchover, user activation, interface activation and organisational preparations. A typical cutover lasts one to five days depending on complexity – often over a weekend to minimise business impact.

Creating the Cutover Calendar

The cutover calendar is the central planning document. It contains all activities in chronological order with: activity description and expected duration, responsible person and deputy, predecessor activities (dependencies), success criteria (definition of done) and fallback action in case of failure. Create the calendar early (T-12 weeks) and refine it iteratively. Every activity should have a clear owner and maximum duration.

Dress Rehearsals: Practice, Practice, Practice

Dress rehearsals are trial switchovers that simulate the cutover under conditions as realistic as possible. Plan at least two rehearsals: the first rehearsal (T-8 weeks) identifies missing activities, incorrect time estimates and dependencies. The second rehearsal (T-4 weeks) validates corrections and measures actual throughput time. Optional: a third rehearsal (T-2 weeks) as final validation if the first two revealed significant issues. Document the results of each rehearsal with lessons learned and changes to the cutover calendar.

Data Migration During Cutover

Data migration is often the most time-critical part of the cutover. Plan for: pre-migration (master data that can be migrated in advance), delta migration (transactional data that can only be migrated during the cutover window) and validation (automated checks after migration). Define quality criteria for migrated data and test these in rehearsals. A data migration error is the most common reason for cutover delays.

Fallback and Rollback Scenarios

What happens if the cutover fails? Define a clear fallback scenario: establish the point of no return (from when is going back no longer possible?), document the fallback procedure (how is the switch back to the legacy system executed?), create a communication plan for the fallback case and test the fallback in a rehearsal. The go/no-go decision should be made based on defined criteria – not on gut feeling.

Hypercare Planning

The first 2–4 weeks after go-live (hypercare phase) require heightened attention: reinforced support staffing, dedicated contacts for each business department, daily status meetings, fast track for critical bug fixes and performance monitoring at higher frequency. Plan hypercare resources early – the best project staff are needed most after go-live.

Conclusion

A successful cutover is the result of thorough planning, realistic dress rehearsals and clear responsibilities. Invest the time in preparation – nothing should need to be improvised on the cutover weekend itself.

Get in touch →

Related Articles

Need support with this topic?

We help you with implementation – from analysis to go-live.

Get in touch

← All articles