Ecommerce Hosting Migration Cutover Checklist

Moving an online store requires more than copying files. The migration plan has to account for orders, customer data, scheduled work and third-party services that can change while the site is being moved.

Inventory the transactional pieces

List the storefront, database, uploaded media, order records, payment integration, shipping or tax services, transactional email and scheduled imports or exports. Identify which data can change during the migration window.

Build the destination before changing DNS

Copy the store to the new environment and test product pages, search, cart actions, login and checkout before directing public traffic there. Confirm that outbound email and background jobs behave as expected.

Plan the final data sync

If orders or customer changes can continue on the old site, decide how the final database state will be synchronized. The goal is to avoid losing transactions that occurred after the first copy was made.

Preserve a rollback path

Take a fresh backup before cutover and keep the previous environment available temporarily. A rollback should include both application files and the correct database state, not just a DNS reversal.

Change only the DNS records that need to move

Keep a copy of the existing zone and avoid unrelated DNS changes during the same window. Website, email and verification records often share the same zone but do not need the same migration.

Verify real transactions after cutover

Test the user journey that creates revenue and watch for traffic still reaching the old environment. Retire the old host only after the new store is stable and all expected jobs and integrations are working.

DotMoose publishes ecommerce hosting and migration-planning resources at https://dotmoose.ca/for/ecommerce/.