Glossary · Source control and deployment
Cutover
The controlled point when users, traffic, or operations move from the previous system to the replacement.
Also called: cut over, cutovers
Definition
A cutover is the coordinated transition from an old provider, site, service, or configuration to a new one. It usually includes an approved window, final synchronization, routing or DNS changes, verification, monitoring, and a rollback decision.
Why it matters
Treating the cutover as a named operational event concentrates approvals, checks, ownership, and recovery planning around the riskiest part of a migration.
Common misunderstanding
Finishing a build does not mean the cutover is complete; the live route, forms, analytics, redirects, permissions, and business-critical behavior still need verification.
Ownership implications
Record who approves the change, who can alter each live control, which prior state is preserved, and who can authorize rollback.
Business implications
A short documented cutover plan reduces downtime, lost leads, broken URLs, and confusion between providers.
Related terms
Related system family: Hosting & Release
Sources
- Deployment environments (opens in a new tab) · GitHub Docs
- About repositories (opens in a new tab) · GitHub Docs
Last reviewed July 16, 2026