Cutover
A cutover is the time-boxed switch from an old system to its replacement: the old system is frozen, a final data load runs across, users and integrations move to the new system, the result is checked against agreed criteria, and a rehearsed rollback point stays ready if that check fails.
Submit a project Plan a legacy data migrationReviewed by Huy Nguyen (David), CEO · Updated 27 Oct 2026 · 4 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while planning a move to a replacement system.
Why does a cutover matter?
A cutover is the one part of a migration where the old and new systems trade places in front of real users, so the risk a project carried for months is concentrated into a short window. OutsourcingVN is operated by Netbase JSC, and Microsoft's implementation guidance says that during cutover "you can't use your old system or your new one," which is why its plan, its rehearsal and its rollback point are written down in advance rather than improvised on the day. A cutover planned this way turns a go/no-go call into a decision made against agreed criteria, not a guess made under pressure.
What is an example of a cutover in practice?
A retailer replacing its order-management system picks a quiet evening for the switch. First, the old system stops accepting new orders so its data stands still. The final batch of orders, customers and inventory levels is loaded into the new system, and support staff and the warehouse scanners are pointed at it. A short list of checks runs next — can a test order be placed, does stock match, do the integrations with the courier and the accounting system still fire — and only once those checks pass does the team confirm the new system takes live traffic. The rollback point, agreed before the evening started, is the moment after which reversing the switch would mean carrying new orders back to the old system rather than simply pointing traffic back.
What are the common misreadings of a cutover?
A cutover is not the same as data migration: moving records with their meaning intact is the data-migration work that usually finishes before a cutover begins, and the data migration entry covers that separately. A cutover is also not a routine release: a release ships a change to a system that keeps running, while a cutover retires one system in favour of another. Nor is a cutover the same as "go-live": Microsoft's guidance places cutover as the last step before go-live, and AWS's migration guidance lists its phases, from an ingestion freeze to final testing. A big-bang cutover (AWS calls it all-at-once: the whole solution moves at once) and a phased cutover (parts move over a defined period) are variants of this one idea, not separate concepts.
Plan the next step for your project
Common questions
Not always; AWS's guidance says a phased cutover typically needs less downtime than an all-at-once one, while locking the source database to keep data consistent may require a larger downtime window.
The people accountable for the agreed checks, at an agreed go/no-go point; Microsoft's guidance calls this the go/no-go decision and asks for stakeholder sign-off at a go/no-go meeting.
Which decisions does a cutover affect?
Planning everything that has to be true before a cutover can start — what data moves, in what shape, and how its accuracy is checked — is the subject of legacy data migration planning. A platform move such as the WooCommerce to Magento migration guide plans its own cutover inside a wider replatforming project, including the rehearsal and the rollback point specific to that move. When you know which system you would retire and which one would take over, describe it and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.