Migration Cutover

Cutover is the live launch window of a migration. It coordinates the final data sync, storefront switch and connected systems. Agree which system owns each record after launch; an ERP may remain the source of truth for inventory or other data.

A typical cutover runs 4 to 12 hours, with the actual sequence agreed and rehearsed for the project. Control writes on the old store, reconcile the final data delta, switch the required domains and endpoints, verify redirects and test checkout. Configure and test payment providers before launch where possible; confirm what needs a production check during the window.

Choose the launch window from the store’s traffic, order patterns and available support team. It may be overnight or on a Sunday morning, but neither is always the quietest time. A planned holding-page window of 1 to 2 hours may be part of the runbook; the necessary interruption depends on the architecture and rehearsal results.

Risks include DNS changes taking longer than planned, payment credentials or tokens needing provider-supported migration, gaps in the redirect map and integrations still using old endpoints. Review TTL and provider requirements in advance. Google has no fixed one-week deadline for finding redirect issues or changing rankings; monitor errors and search performance after launch.

The cutover plan is rehearsed at least twice on staging before go-live. If it hasn't been rehearsed end-to-end, it's not ready.

Frequently asked questions

How long does a migration cutover take?

A typical planned window is 4 to 12 hours. Confirm the estimate through rehearsal and schedule around actual traffic and team availability. The cutover window is not necessarily the same as customer-facing downtime.

What happens during a Shopify cutover?

Follow the rehearsed runbook: control source writes, sync and reconcile final data, switch required domains and endpoints, verify redirects and perform live payment and checkout checks. Define field ownership, monitoring and the recovery decision before reopening normal operations.

What are the most common cutover failures?

DNS changes, unreconciled data, payment migration or configuration issues, missing redirects and integrations still using old endpoints can disrupt launch. Rehearse the sequence, confirm provider requirements and assign owners for monitoring and recovery.

Related terms: 301 Redirect Map, Migration Sandbox, Customer Account Migration. For hands-on help, see how Flux runs Shopify Plus migrations.

Shopify Plus development and AI search

We build Shopify Plus stores that customers and AI shopping agents can find, compare and buy from. 210+ stores since 2012.

Chosen by Shopify Plus brands worldwide.