What is a cutover in simple terms?

A cutover is the moment when you stop using the old system and start using the new one. In IT migrations, it's a planned window — often a weekend — during which data moves, the new system is validated, and users are switched over.

What is the difference between cutover and go-live?

Cutover is the transition process; go-live is the moment users start using the new system. The cutover window contains the go-live event but extends before and after it through preparation, validation, and hypercare.

What is a cutover plan?

A cutover plan is the runbook that sequences every activity, owner, dependency, and rollback trigger for the cutover window. It typically covers six phases: pre-cutover prep, dry run, T-1 readiness, the cutover window itself, validation, and hypercare.

Who is responsible for the cutover?

The cutover lead (or cutover program manager on large programs) owns end-to-end execution. They coordinate infrastructure, data migration, QA, and business stream leads, each of whom owns activities in their domain.

Learn

What is a cutover?

Definition of cutover in IT migrations: the controlled transition window during which an organization moves from one system to another, including data migration, validation, and go/no-go decisions.

May 15, 2026

Definition

A cutover is the controlled transition window during which an organization moves from an old system to a new one. In enterprise IT, cutovers happen during ERP migrations, platform replacements, data warehouse migrations, and large-scale system upgrades. The cutover window typically lasts hours to days and includes data migration, validation, the go-live moment itself, and the initial monitoring period.

A cutover is not a single event — it’s a phased operation with explicit gates between each phase.

The six phases of a cutover

Pre-cutover preparation — finalize plan, freeze source-system changes, communicate to users
Dry run / dress rehearsal — execute the full cutover sequence in non-production
T-1 readiness review — go/no-go decision before the cutover window opens
Cutover window — the actual transition: data migration, validation, go-live
Post-cutover validation — confirm the new system is operating correctly
Hypercare — intensive monitoring and rapid incident response (typically 2 weeks)

What makes cutovers hard

Irreversibility window. Once the source system is locked and final data is migrated, rolling back becomes expensive — sometimes impossible.
Compressed time. Most cutover windows are a weekend. Activities that take 8 hours in dry run can take 14 in production.
Coordinator load. A cutover lead is making 40+ go/no-go calls under fatigue. Decision quality degrades.
Hidden dependencies. Integrations, downstream systems, and reporting pipelines all assume the old system. Many of them surface only at cutover.

What good cutovers do differently

Rehearse twice. A mock cutover early, a full dress rehearsal at T-7. See the cutover rehearsal guide.
Pre-write rollback triggers. Don’t decide whether to roll back at 3 am during the cutover — decide at planning time what conditions force rollback.
Smaller, gated phases. Six phases with hard go/no-go gates beats one 400-row checklist.
RACI per activity, not per phase. Owners need to know exactly which tasks are theirs.

Generate a cutover plan

Generate a tailored cutover plan in 60 seconds with phases, RACI, dry-run schedule, and rollback triggers — sized to your migration.

Frequently asked questions

What is a cutover in simple terms?: A cutover is the moment when you stop using the old system and start using the new one. In IT migrations, it's a planned window — often a weekend — during which data moves, the new system is validated, and users are switched over.
What is the difference between cutover and go-live?: Cutover is the transition process; go-live is the moment users start using the new system. The cutover window contains the go-live event but extends before and after it through preparation, validation, and hypercare.
What is a cutover plan?: A cutover plan is the runbook that sequences every activity, owner, dependency, and rollback trigger for the cutover window. It typically covers six phases: pre-cutover prep, dry run, T-1 readiness, the cutover window itself, validation, and hypercare.
Who is responsible for the cutover?: The cutover lead (or cutover program manager on large programs) owns end-to-end execution. They coordinate infrastructure, data migration, QA, and business stream leads, each of whom owns activities in their domain.