Timing depends on catalog and attribute complexity, B2B, websites and markets, extensions, integrations, storefront scope, data quality, security review, testing, and launch constraints. Enterprise migrations need discovery, repeatable rehearsals, reconciliation, operational acceptance, controlled cutover, and stabilization.
Let architecture and operational proof shape the schedule
The longest dependency may be an ERP connection, a B2B decision, a catalog transformation, or regional ownership rather than the storefront build. Identify those uncertainties during discovery and give each a decision owner. An early proof of the hardest workflow is more useful than a detailed schedule built on untested assumptions.
Plan repeatable migration rehearsals and reserve time to resolve the exceptions they expose. Include finance, customer service, fulfilment, and commercial approval in the launch criteria. The final window should cover data changes since the rehearsal, order handling, domains, monitoring, and the decision to proceed or pause if a critical check fails.
What to check before deciding
- Resolve architecture and integration ownership before fixing scope.
- Test complex catalog and B2B cases early.
- Schedule repeated data reconciliation and operational acceptance.
- Agree final-delta handling, launch authority, and stabilisation support.
