What is a cutover strategy in an SAP implementation?

A cutover strategy is the detailed, sequenced plan for the actual transition from an old system to the new one — covering final data migration, system configuration freeze, user access transition, and the exact sequence of technical and business activities that must happen, typically within a tightly constrained window, to move live operations from the old environment to the new one with minimal disruption.

flowchart LR
    A[Pre-cutover: final data extract, freeze changes] --> B[Cutover weekend: migrate, validate, configure]
    B --> C[Go-Live: users begin operating on new system]
    C --> D[Hypercare: intensive post-go-live support]

Because most cutovers happen during a narrow window (often a weekend, to minimize business disruption), the plan needs extreme specificity — exact timings, clear ownership of each task, defined go/no-go decision points, and rehearsed contingency plans — rather than a high-level plan that assumes everything will proceed smoothly on the first attempt.