eCommerce Migration Checklist: Move With No Downtime
eCommerce migration checklist for moving to Shopify with no downtime: audit, data freeze, parallel build, test orders, DNS switch, rollback plan and monitoring.
Author: Mousa Alhelo · Published · 6 min read
An eCommerce migration checklist that avoids losses rests on one principle: the old store keeps selling until the new store proves it is ready with real orders. Between start and finish there are seven phases: audit, data freeze, parallel build, test orders, a DNS switch window, a rollback plan and post-launch monitoring. This is the checklist we use on every migration to Shopify.
Phase one: audit and scope
Before any technical work, we write a short document answering specific questions, because most losses in migration projects come from assumptions nobody wrote down:
- What moves? Active products only or the whole catalog? How many years of orders? All customers or those who bought within a set period?
- What does daily selling depend on? Payment gateways, couriers, the accounting system or ERP, tax invoicing, apps.
- Where does traffic come from? The top 100 pages in Search Console and the active campaigns on Meta and Google.
- Who owns each decision? One person approves the data freeze and one person approves the switch.
Baseline numbers are recorded before the move (daily orders, conversion rate, organic traffic) because they are the reference against which the migration’s outcome is measured.
Phase two: the data freeze
The data freeze is an agreed date after which no edits are made to products, prices, images or content in the old store. After it, one final export is taken and moved to Shopify. What is not frozen: new orders and customers, which keep flowing into the old store and are moved as a final batch during the switch window.
| Frozen | Not frozen |
|---|---|
| Products, options and images | New orders |
| Prices and compare-at prices | New customer registrations |
| Collections, pages and blog posts | Quantities (synced at the end) |
| Discount codes | Customer service messages |
A practical rule: do not freeze data until the new store is ready to receive it within days, otherwise the freeze drags on and disrupts the business.
Phase three: the parallel build
The Shopify store is built on a password-protected temporary address, the cleaned catalog is imported, and everything that cannot be imported is completed: theme, menus, policy pages, payments, shipping, taxes, apps replacing old plugins, and tracking. The URL map and 301 redirects described in keep SEO rankings when migrating to Shopify are built in this phase too.
Tracking is installed now, not after launch: Meta Pixel with the Conversions API, GA4, Google Ads conversion tracking and Merchant Center. The detailed steps are in Meta Pixel and Conversions API setup for Shopify.
Phase four: test orders
No domain is switched before this list passes completely:
- A real order through every payment method (card, cash on delivery, any local gateway), then refunded.
- An order from mobile and from desktop, in Arabic and English if the store is bilingual.
- Confirmation that the order appeared in the Shopify admin and reached the accounting or shipping system if connected.
- Confirmation that the test order appeared in Pixel and GA4 events with the correct value.
- The order confirmation arrived by email and by WhatsApp if enabled.
- A review of a 50-product sample: images, prices, options, quantities, descriptions.
- A check of the top 100 redirects on the temporary address.
The full pre-launch checklist, whether for a migration or a new store, is in the Shopify store launch checklist.
Phase five: the DNS switch window
We choose the time with the least traffic, usually a mid-week night away from peak seasons. The sequence inside the window:
| Step | Approximate timing | Note |
|---|---|---|
| Put the old store into maintenance mode | Minute 0 | Clear message for visitors |
| Export the final batch of orders and customers | First 30 to 60 minutes | Everything since the last transfer |
| Import into Shopify and sync quantities | Immediately after | Verify counts |
| Change DNS records to Shopify | After the import completes | Propagation can take time |
| Verify SSL and the primary domain | After propagation | Remove password protection |
| Place a real order on the live domain | As soon as confirmed | With a real payment |
| Submit the sitemap in Search Console | Same hour | And request indexing of top pages |
Lowering the DNS TTL a day before the window makes propagation faster and shortens the maintenance period.
Phase six: the rollback plan
A rollback plan is not a sign that failure is expected; it is the condition for staying calm during the switch. It has three parts: the old store keeps running on a temporary address and is not shut down for weeks, a copy of the old DNS records is saved so they can be restored within minutes, and a written procedure exists for manually moving any orders that reached the new store if we have to go back. We define in advance what triggers a rollback (such as payment failing on every method) and what gets fixed in place (such as a missing image).
Phase seven: post-launch monitoring
For the first two weeks we monitor daily:
- Orders: the count against the pre-migration baseline, and the share of failed payments.
- Tracking: Pixel and GA4 purchases matched against Shopify orders.
- SEO: 404 errors in Search Console, redirects working, indexing progress.
- Campaigns: ads continuing on the new URLs and the catalog refreshing in Merchant Center.
- Customers: login complaints (because passwords do not transfer) and activation emails.
After two weeks, monitoring moves to weekly until day 90, when the numbers are compared with the baseline and the project is formally closed.
From our experience
Every migration we run through our Shopify migration service follows a written plan, a data freeze and a monitoring period after launch. For Luliz the challenge was a slow, expensive-to-maintain Magento store with thousands of products and an order history that had to be preserved; with the same plan (freeze, transfer of products, customers and orders, 301 redirects, reconnecting Merchant Center, GA4 and the Pixel) the move was completed in summer 2025 with no lost products or rankings, and campaigns running profitably since launch. The Magento specifics are in migrate Magento to Shopify.
Conclusion
A store migration without losses is not luck but order: a written audit, a dated data freeze, a parallel build with tracking ready, test orders with real payments, a quiet switch window, a ready rollback plan, and daily then weekly monitoring until day 90. With this checklist, selling never stops and the new store comes out stronger than the old one.
Send us your store link on WhatsApp and we will send you an estimate of the plan’s phases and timeline based on your catalog size.
Want this applied to your store?
E-SAFQA builds and runs Shopify stores and their ads. Message us on WhatsApp for a free audit.
Frequently asked questions
What does a data freeze mean in a store migration?
It is an agreed date after which no edits are made to products, prices or content in the old store, so a single final version is transferred to the new store without reconciling differences by hand.
Does selling stop during a store migration?
Not if the new store is built in parallel. The old store keeps taking orders until the switch window, and the final batch of orders and customers is moved during that window.
When is the best time to switch the domain to the new store?
A quiet time with the fewest visitors, usually a mid-week night away from seasons like Ramadan and White Friday, with the team on standby for a few hours after the switch.
What if a serious problem appears after the switch?
DNS records are pointed back to the old store, which is still running on a temporary address, and any orders that reached the new store are moved manually. That is why the old store is not shut down for weeks.