The safest way to migrate from Magento to Shopify without downtime is to build the Shopify store in parallel, run at least one full dry run, then finish with a delta migration and a short, planned cutover with your 301 redirects ready. At Futur Media, a UK Shopify agency that specialises in replatforming, "zero downtime" means your storefront never goes offline and checkout pauses for minutes, not hours. The real risks are orders placed during DNS propagation, missing redirects and tax totals that don't reconcile.
This is the exact sequence we use on our own Magento 2 to Shopify migrations, including a live project moving more than 55,000 orders. If you'd rather have it handled for you, see our Shopify migration service.
What does "without downtime" actually mean for a Magento migration?
Zero downtime in a Magento to Shopify migration means the storefront stays online throughout, while order capture pauses only for a short, planned window. No honest migration plan promises a cutover with no pause at all, and Shopify's own enterprise migration guidance says to plan for some downtime during the final switch.
Split "downtime" into three separate risks, because each has a different fix:
| Risk | What it means | Can you avoid it? |
|---|---|---|
| Storefront availability | Shoppers see an error page or a blank site | Yes. Keep Magento live until Shopify is verified. |
| Order capture | Shoppers can't check out for a short period | Minimise it with a short freeze in your lowest-traffic window. |
| SEO | Rankings and organic traffic dip after launch | Reduce it with redirects and checks. Nobody can promise zero movement. |
The commercial goal is simple: no lost orders, no broken checkout, and organic revenue held close to your baseline.
The safe Magento to Shopify migration sequence at a glance
There are six steps. Magento keeps trading until step 5.
- Build and stage the Shopify store in parallel, away from your live site.
- Audit and map your data before you import anything.
- Run a base migration and dry runs until every reconciliation check passes.
- Run a delta migration to catch everything that changed on Magento since the base import.
- Cut over in a quiet window: pause Magento checkout, run the final delta, point DNS at Shopify.
- Verify and monitor redirects, orders and organic traffic for 14 days.
How that maps to a calendar:
| When | What happens | What keeps running |
|---|---|---|
| 4 weeks before | Development store build, data audit, attribute mapping | Magento trades as normal |
| 3 to 2 weeks before | Base migration, first dry run, reconciliation | Magento trades as normal |
| 1 week before | Second dry run, test orders, redirect file tested | Magento trades as normal |
| 48 to 24 hours before | Lower DNS TTL, confirm SSL, stage redirects, agree rollback plan | Magento trades as normal |
| Cutover | Pause Magento checkout, final delta, DNS switch, redirect import | Storefront stays up; checkout paused briefly |
| Day 1 after | 404 crawl, order and payment checks | Shopify trades |
| Day 14 after | Compare organic traffic and conversion with baseline | Shopify trades |
TTL (time to live) tells the internet how long to cache your DNS record. A lower TTL means a faster switch.
Phase 1: How do you build and stage the Shopify store in parallel?
Build the new store on a Shopify development store or its myshopify.com address, and never touch your live Magento database during setup. Customers keep buying on Magento while you configure the theme, apps, tax, shipping and payments on Shopify.
Audit and prune your data. Remove dead SKUs, customer accounts that haven't ordered in years and Magento attributes you never use. Smaller imports run faster and reconcile more easily. Decide your lawful basis for moving customer records under UK GDPR before you export anything.
Map your data structures. Magento and Shopify model products differently, so write the mapping down before any import runs:
- Magento configurable products become Shopify products with variants.
- Customer group and tier pricing map to Shopify B2B catalogues or Markets where your plan supports them, or to a custom build.
- Custom attributes map to metafields and metaobjects.
Check the variant limits. Shopify raised the limit to 2,048 variants per product in 2025, with up to three options per product. Some guides still quote the old 100-variant limit, so ignore them, and test your theme and apps, which may set their own limits.
UK setup: configure VAT in GBP, Royal Mail and DPD shipping rates, and payment methods (Shopify Payments, PayPal, Klarna, Clearpay) in this phase, not after launch.
Phase 2: How do you run the base migration and dry runs?
Import in this order: products, then customers, then orders. Orders reference products and customers, so the order matters. Treat the first import as a rehearsal, because no tool or script gets it right first time.
Choose your method on complexity, not price alone:
| Option | Best for | Reruns and deltas | Watch out for |
|---|---|---|---|
| Matrixify | Catalogues managed through spreadsheet-style imports | Yes. Supports repeat imports and merging updates into existing records | Needs careful field mapping. Our first choice when the mapping is clean |
| Cart2Cart / LitExtension | Simple stores wanting an automated transfer | Check their recent-data options before relying on them | Custom attributes and logic need a manual reconciliation pass |
| Custom API scripts | Custom attributes, B2B pricing or ERP links | Yes. You control the logic and rerun by date or order ID | Takes development time |
What should you reconcile after each dry run?
Reconcile everything that touches revenue, and check it against Magento, not against what the import tool reports:
| Check | Pass condition |
|---|---|
| Product and SKU counts | Counts match, with intended exclusions listed |
| Top 20 SKUs by revenue | Price, stock, images and variants all correct |
| Category sample | 10 to 15 products per category, no missing options or images |
| Customer counts | Counts match, with marketing consent preserved |
| Order counts and totals | Totals by month match to the penny |
| VAT totals | GBP tax totals match on a sample period |
| Inventory | Stock by SKU and location matches at export time |
| Metafields and metaobjects | Values populated, formatted and linked correctly |
Then test end to end: place test orders, apply discount codes, check ERP or warehouse syncs and trigger every email notification.
Historical orders arrive in Shopify as reference records. You can't edit them, and they don't feed Shopify's financial reports or inventory, so brief your customer service team before launch.
Phase 3: What is a delta migration and why does it make zero downtime possible?
A delta migration copies only the orders, customers and inventory changes that happened on Magento after your base migration. It is how you avoid downtime. Magento keeps taking orders while you build Shopify, so the base copy is out of date by launch day. The delta brings Shopify level without a second full import.
- Freeze non-essential changes on Magento. Stop large catalogue updates and content publishing during the freeze, but keep trading.
- Run the delta sync. Pull new orders, updated stock and new customer accounts since the base migration.
- Verify the delta. Check for duplicates and missed transactions by comparing Magento order IDs against Shopify.
Rehearse the delta at least once before launch, and time it. That duration decides how long your checkout pause lasts.
Worked example: London Arrangements (Magento 2 to Shopify)
London Arrangements is a UK sheet music publisher selling physical and digital products. Futur Media is moving the store from Magento 2 to Shopify using exactly this sequence:
- 55,000+ historical orders, plus products and customer accounts, migrated with Matrixify while Magento kept trading.
- More than 2,000 metaobjects created and verified, so every product's digital files and track previews resolve to the right file and label.
- Repeatable imports: data is imported with merge updates, so any batch can be rerun or topped up with a delta without creating duplicates.
- A bespoke downloads locker so customers can re-download past digital purchases, plus custom automations to deliver files after checkout.
The biggest lesson: on a catalogue with complex product data, the work is in the mapping and verification, not the import itself. We'll add launch-day and post-launch SEO results here once the store is live.
Phase 4: How do you run the cutover window and DNS switch?
Schedule the cutover for your lowest-traffic window. Checkout pauses on Magento, the final delta runs, then DNS points to Shopify. DNS propagation typically takes minutes to a few hours, and up to 48 hours at the outer limit.
- 24 to 48 hours before: lower your DNS TTL.
- Before cutover: confirm SSL is provisioned, redirects are staged and a rollback plan is agreed.
- Cutover: put Magento into maintenance mode or disable checkout, so no new order can slip in.
- Final delta: run it once checkout is paused.
- DNS switch: point your domain at Shopify.
- Verify: place a live test order and confirm payment, email and fulfilment all work.
Where do orders land during DNS propagation?
For a short time, the same domain can resolve to either platform, so a shopper on the old DNS record could still place an order on Magento that misses your final delta. Prevent it three ways: disable Magento checkout before the final delta, keep the TTL low, and compare Magento order IDs against Shopify afterwards to catch strays. That's why we tell clients the checkout pause is real, small and planned.
Choose your date carefully. Where you can, avoid cutting over in the busiest weeks of your trading year, such as Black Friday to Christmas for most retailers. If you must launch near a peak, rehearse the delta more than once and pick the quietest day and hour your analytics can find.
How do you keep your SEO with 301 redirects?
A 301 redirect permanently sends visitors and search engines from an old URL to its new equivalent. Build your redirect map from four sources: the Magento URL rewrite table, Google Search Console, your analytics and a backlink report. Cover your highest-traffic and highest-revenue URLs first.
- Map to Shopify's URL structures: /products/, /collections/ and /pages/.
- Use 301s, not 302s.
- Avoid redirect chains and loops.
- Spot-check 20 to 30 redirects before and after launch.
Timing: prepare and test your redirect file before launch, then import and verify it as soon as your domain connects, because redirects only fire for requests that reach Shopify.
Expect a small dip. A 5 to 10% drop in organic traffic in the first week is common; a sustained drop of more than 20% needs investigating. Our guide to migrating without losing SEO rankings covers this in more detail.
What won't transfer from Magento to Shopify?
| Item | What happens | What to do |
|---|---|---|
| Customer passwords | Can't be exported or imported | Send account activation emails |
| CMS blocks and pages | Don't map cleanly | Rebuild as Shopify pages, sections or metaobjects |
| Grouped and bundled products | Different product model | Rebuild with variants, a bundles app or custom logic |
| Layered navigation | Magento-specific | Rebuild with Shopify's filtering |
| Tax and shipping rules | Configured separately | Rebuild and test on the staging store |
| Reviews and store credit | Depend on your apps | Check the migration path for each one |
Send account activation emails at a sensible time after launch, written as a service message about the customer's account rather than a marketing email. That matters under UK GDPR and PECR.
What should you check in the first 14 days after launch?
- First 24 hours: crawl for 404s, confirm redirects, check payments, order emails and fulfilment.
- Days 2 to 7: watch Search Console for crawl errors and coverage issues, and compare organic sessions and conversion rate with your baseline.
- Days 8 to 14: fix remaining 404s, review your weakest redirected URLs and check checkout completion rate.
Set your investigation threshold before launch, so you know when a dip is normal and when it needs action.
Common mistakes that cause downtime
| Mistake | Why it hurts | Fix |
|---|---|---|
| One bulk import, no dry run | Errors show up live | Run at least one full dry run and reconcile |
| Skipping the delta | Orders placed during the build are lost | Run a delta after the freeze |
| Leaving TTL high | DNS takes longer to switch | Lower it 24 to 48 hours before |
| Untested redirects | Rankings and bookmarks break | Test on staging, verify after the DNS switch |
| Launching into your peak | No margin for error | Pick a quiet window and rehearse |
When should you bring in a Shopify migration specialist?
Bring in a specialist when mistakes are expensive: large catalogues, custom Magento logic, B2B pricing, digital products, ERP or warehouse integrations, or revenue that can't absorb a failed launch night.
Futur Media is a UK Shopify agency that handles complex replatforms from Magento, WooCommerce and BigCommerce, including Shopify Plus builds. You work directly with the people doing the migration, from data mapping to launch night and the 14 days after. We don't guarantee rankings or revenue, because nobody honestly can, but we do rehearse every step before it touches your live store.
Migrations start from £2,500, and complex or Shopify Plus replatforms from £15,000. See our pricing page, our Shopify Plus work, or read how we handle complex platform migrations.
Planning a Magento move? Get in touch and we'll review your store and cutover plan before you commit to a date.



%201.avif)

