Shopify Plus Migration Masterclass: replatform without losing revenue

Why brands replatform to Shopify Plus

Replatforming is the most expensive thing a $5M–$50M DTC brand will do in a five-year stretch. Done right, it unlocks 18–30 months of compounding velocity. Done badly, it kills SEO traffic for two quarters and the team never recovers.

The brands we move to Plus usually share three signals: their current platform is taxing engineering velocity (every release ships behind a feature flag because the system is fragile), checkout is a known revenue leak the team can't fix in the current platform, and the merchandising team wants ownership of changes without filing a ticket.

If you have only one of those, optimize what you've got. If you have all three, this guide is for you.

The four migration shapes we run

Not every migration looks the same. Mapping yours to one of these four shapes determines budget, timeline, and risk surface.

Shape 1 — Magento / Adobe Commerce → Plus

Usually a 14–22 week build. The hard parts: catalog complexity (configurable products → variant models), multi-store hierarchies, and decades of URL structure. SEO is the headline risk.

Shape 2 — BigCommerce → Plus

Often the smoothest. APIs are clean and product/customer/order shapes map closely. 8–14 weeks. The hard parts: B2B price lists, customer groups, and any Stencil-specific theme logic.

Shape 3 — WooCommerce → Plus

Data is the headline. WooCommerce stores accumulate a decade of meta keys, plugin tables and inconsistent product taxonomy. Plan a 4-week data audit before estimating the build.

Shape 4 — Custom stack (Rails, Node, headless CMS) → Plus or Hydrogen

These are the most expensive. The team usually has strong opinions and the migration needs to preserve a specific editorial or personalization layer. We almost always end up on Hydrogen + Plus rather than Liquid.

URL & SEO strategy: the 301 plan that preserves rankings

Every migration we audit that lost organic traffic lost it at the URL layer. Shopify forces specific URL patterns (/products/, /collections/) that almost certainly don't match your current site. If you don't plan for it, organic traffic drops 30–60% in the first 30 days.

The non-negotiables

• Crawl your current site with Screaming Frog and export every indexed URL with its rank, traffic, and backlink count.
• Build a 1:1 mapping spreadsheet from old URL → new Shopify URL. Every URL with traffic or backlinks must have a target.
• Implement redirects in Shopify's URL Redirects table (or Cloudflare Workers in front of it) before DNS cutover.
• Avoid redirect chains. Old → new in one hop, never two.

Things that bite

Faceted collection URLs, blog tag pages, internationalized URLs and search result pages all need policy. Decide which to redirect, which to canonical, and which to let 404. Document it before the cutover, not after.

Data migration — products, customers, orders, subscriptions

The migration spreadsheet has more rows than the build does. We typically move 6 data shapes and each one has gotchas.

Products & variants

Shopify caps variants at 100 per product. If you have configurable products that explode beyond that, you'll need bundles, metafields, or product splits. Decide before the build.

Customers

Password hashes don't transfer. Plan a password reset flow with email warmup so you don't trigger spam filters with a million reset emails on day one.

Orders

Historical orders can be imported via the Bulk Operations API for reference. But you usually don't want refunds, returns or subscription renewals running against the imported records — keep historicals read-only.

Subscriptions

Recharge, Skio and Stay AI all have migration paths but each requires a vault re-tokenization. Schedule with your processor 6 weeks ahead.

Metafields & custom data

This is where the slow week disappears. Custom data on the old platform rarely has a clean Shopify equivalent. Map it to metafields with namespaces you control, not the app's namespace.

App and integrations inventory: cut, replace, keep

Every store we migrate has at least one app that exists because someone, 4 years ago, needed something for one campaign. The migration is the right moment to cut.

The audit

List every app, every webhook, and every API consumer. For each, capture the business owner, the underlying job-to-be-done, and the monthly cost. Then sort into three columns: Keep (essential, has Shopify equivalent), Replace (Shopify has a native or better option), Cut (no longer needed).

Common cuts

Custom recommendation engines (Shopify has Search & Discovery), legacy review apps (consolidate to one), legacy CRO tools that don't support new checkout. Most stores cut 20–30% of their app stack at migration.

Common keeps

Klaviyo, Gorgias, the subscription processor, and the ERP/3PL integration. Plan these connections during the build, not after.

The cutover — staging, freeze windows, DNS, rollback

Cutover is the only step the executive team will remember. Plan it like a launch, not a deploy.

Timeline

• T-14 days: feature freeze on the old platform. No new content, no new products, no new code.
• T-7 days: final data sync rehearsal. Time it. Document every step.
• T-3 days: marketing pause on paid traffic to high-traffic landing pages.
• T-0: cutover window in lowest traffic period (usually 2–6am store time on Tuesday).
• T+24h: 24-hour war room. Engineering, marketing, support and the agency on shared Slack.

Rollback

Keep the old platform warm for 14 days. Set TTLs low. If something catastrophic surfaces in the first 48 hours, you want to be able to revert.

Post-launch: monitoring, performance, the 30/60/90

The brands that come out of replatform happy aren't the ones that nailed launch day — they're the ones that nailed week 4.

Days 0–30

Monitor everything. Track conversion rate, AOV, revenue per session, organic traffic and Core Web Vitals against the pre-launch baseline. Catch regressions in days, not weeks.

Days 30–60

Ship the items you knowingly punted from launch scope. Most stores have a list of 8–15 "phase 2" items. Convert that into a 60-day backlog.

Days 60–90

Start the optimization layer. Now that you're on Plus, you have access to Functions, Markets and checkout extensibility. Ship one win per area in the first quarter post-launch.

What a Shopify Plus migration actually costs

There are no clean answers, but there are ranges. Treat anyone who quotes you without a discovery as a vendor, not a partner.

Build cost

Most BigCommerce → Plus migrations land in $45k–$120k. Magento and custom-stack migrations run $90k–$300k+. Hydrogen builds add 30–60% on top.

Internal cost

Plan 0.5–1.0 FTE from the brand side for the duration: someone who can answer questions inside the same business day. Migrations slow down when the brand-side answers take a week.

Time cost

Plan 12–24 weeks end to end. Plan another 8 weeks of stabilization. Don't book a brand relaunch the same week as the platform launch — your team will be exhausted and you want one variable changing at a time.