Cutover vs go-live: where the line falls

Cutover is the transition process. Go-live is the moment users start using the new system. Go-live happens inside the cutover window — it is the cutover’s success criterion, not a separate event.

The two terms are often used interchangeably, especially in ERP and platform-migration vendor marketing. They are not the same.

Definitions

Cutover

A cutover is the controlled transition during which an organization moves from an old system to a new one. It is a phased operation — typically pre-cutover preparation, dry runs, the cutover window itself, validation, and hypercare. A cutover is an activity, scheduled over days or weeks. See what is a cutover for the full definition.

Go-live

A go-live is the moment within the cutover when the new system becomes operational for end users. It is an event, not a process. Go-live is typically marked by the final DNS cutover, load-balancer switch, or removal of the source-system lock — the technical action that puts users on the new system.

Where the line falls

If you draw a timeline of a typical cutover:

Phase	Time	Cutover?	Go-live?
Pre-cutover preparation	T-14 to T-2	✓	—
T-1 readiness review	T-1	✓	—
Source-system lock	T-0 start	✓	—
Data migration	T-0	✓	—
Validation	T-0	✓	—
Smoke tests	T-0	✓	—
DNS / load-balancer cutover	T-0	✓	← go-live moment
Users open new system	T-0 + minutes	✓	(post-event)
Post-cutover validation	T+0 to T+1	✓	—
Hypercare	T+1 to T+14	✓	—

The cutover spans the whole table. Go-live is one row.

Side-by-side comparison

	Cutover	Go-live
Type	Process	Event
Duration	Days to weeks	A moment (typically minutes)
Owner	Cutover lead / program manager	Cutover lead announces; infra executes
Artifact	Cutover plan / runbook	Announcement to users + status update
Outcome	Stable new system, source decommissioned	Users on new system
Failure mode	Plan executes but business cannot operate	Users cannot access the new system
Reversible?	Yes (rollback procedure)	Yes if caught quickly; harder once business transactions occur

Why the two get confused

Four reasons:

1. Smaller projects collapse them. A platform replacement with a 4-hour cutover window has so little time between source-lock and user-open that the cutover and the go-live feel like the same event. They are not, but the distinction has no practical value at that scale.
2. Vendor marketing prefers “go-live.” ERP and SaaS vendors talk about go-live dates because that is what business sponsors track. The full cutover plan is treated as an integrator concern, not a sponsor concern.
3. “Go-live date” is a colloquial shorthand. When someone asks “what’s the go-live date?” they often mean “when does the cutover window start?” That conflates the two cleanly enough that the precise distinction rarely surfaces.
4. Hypercare is treated as separate. Many teams talk about “go-live and then hypercare” as if hypercare were a separate phase. It is not — hypercare is part of the cutover, and the cutover is not complete until hypercare ends.

When to use which term

Use cutover when:

• Talking about the plan, the runbook, or the sequence
• Discussing rehearsals, dry runs, dress rehearsals
• Reporting on activities, owners, RACI
• Setting up the war room, comms channels, on-call rotation
• Describing rollback procedures or trigger conditions
• Tracking the hypercare period

Use go-live when:

• Communicating to end users about when the new system is available
• Setting expectations with business sponsors
• Coordinating cross-team timing (“be ready by go-live”)
• Marking the success of the cutover

In integrator-internal conversation, default to cutover — it is the more precise term and avoids ambiguity. In business-facing communication, go-live is usually clearer because it answers the question users actually care about: when can I start using the new system?

Concrete examples

Scenario 1 — SAP S/4HANA migration. The cutover plan covers six weeks: T-30 to T+14. The cutover window itself is a 56-hour weekend, Friday 18:00 to Monday 02:00. Go-live is Monday 02:00 — the moment SAP transactions begin in the new system. Hypercare runs Monday 02:00 to two weeks later.

Scenario 2 — Salesforce migration. The cutover plan covers two weeks. The cutover window is a 12-hour Saturday. Go-live is Saturday 18:00 — the moment users are redirected from the legacy CRM to Salesforce.

Scenario 3 — Small platform replacement. The cutover plan covers three days. The cutover window is four hours overnight. Go-live is the moment DNS propagates and users hit the new platform. In this case the cutover and the go-live are so close in time that the distinction has little operational value — though the cutover plan still exists and still has phases.

Adjacent terms

A few terms that get pulled into this conversation:

• Deployment — the act of pushing code or configuration to an environment. A cutover may include a deployment, but it is much broader.
• Release — making new functionality available. A release often does not require a cutover (e.g., a feature flag flip).
• Launch — typically used for new products. A launch may include a cutover (if migrating from a beta or a prior platform), but the term is marketing-led, not operationally precise.
• Migration — moving data or workload from one system to another. Migration is one part of a cutover (the data step), not the whole thing.
• Hypercare — the intensive post-cutover support period. Part of the cutover, not separate from it.

What happens after go-live?

Go-live is the visible moment, but the cutover continues:

1. Post-cutover validation. Confirm the new system is operating correctly under real user load. Reconcile any final data discrepancies.
2. Hypercare. Intensive monitoring and rapid incident response, typically for two weeks. Bug-fix turnaround is measured in hours, not days.
3. Transition to standard support. At the end of hypercare, the system moves from the cutover team to the steady-state support team.
4. Source-system decommissioning. Once the new system has demonstrated stability, the source system is decommissioned per a documented plan.
5. Lessons-learned retrospective. The cutover team captures what went well, what didn’t, and what the next cutover should do differently.

The cutover is not complete at go-live. It is complete at the end of hypercare.

Generate your cutover plan

The free cutover plan template generator produces a phased plan that explicitly distinguishes the cutover window from the go-live moment, with timing for hypercare and a decommissioning gate.

Related

• What is a cutover? — full definition and scope
• Cutover phases breakdown — the six phases of a cutover, in detail
• Cutover rehearsal: the complete guide — how to rehearse the cutover before the real window
• Cutover activities & responsibilities — RACI patterns for cutover programs