The complete Shopify migration guide.
Everything we know about replatforming to Shopify after running 2,000-plus migrations. Honest scope, real costs, the decisions that actually move the needle.
Eight workstreams. Six to 24 weeks. One redirect map.
A Shopify migration is eight workstreams running in parallel: discovery, data, theme, apps, integrations, SEO preservation, launch, and 90-day recovery. Costs run USD 12K to 250K and timelines six to 24 weeks, both driven by data complexity and integration depth. The single highest-leverage artifact is the 301 redirect map; the single biggest source of budget overrun is skipped discovery. Pick the agency that runs a paid 2-week discovery before quoting; everyone else is guessing. Published by Prasun Anand.
When does Shopify actually beat your current platform?
Shopify wins when your team is spending more than one engineer-week per month on platform maintenance instead of revenue work. That is the cleanest decision rule we use. If your current Magento or WooCommerce or BigCommerce stack has eaten an engineering hire because someone has to keep the lights on, the total cost of ownership math has already flipped against it.
The four genuine triggers we see across the 2,000-plus migrations we have run: infrastructure cost growing faster than revenue (Magento + AWS + DevOps regularly hits USD 8K-plus per month for stores that would pay USD 300 to 2,000 on Shopify Plus); checkout conversion gap of three percentage points or more (Shopify Plus checkout regularly converts three to seven points higher than self-hosted alternatives because of Shop Pay and the platform's checkout investment); integration brittleness (every native Shopify app has a maintained version; legacy plugin ecosystems on Magento + WooCommerce drift out of compatibility constantly); and team velocity collapse (the team can no longer ship a homepage variant without a senior engineer because the platform's templating model requires it).
The four scenarios where you should NOT migrate: catalog with 50-plus pricing tiers and contract pricing per buyer (Shopify Plus B2B has improved but still loses to dedicated B2B platforms for the most complex cases); product model that depends on truly infinite variants or shared-inventory bundles (Shopify caps variants at 100 per product and treats bundles as separate SKUs); team that just rebuilt the current platform within the last 18 months (the sunk-cost trap is real and migration is a 6 to 18 month payback at best); regulatory constraint requiring on-prem hosting (Shopify is SaaS — no debate).
Read the deeper signal-by-signal breakdown in When to hire a Shopify Plus agency and the platform comparison in Shopify vs WordPress.
What does a real discovery phase include?
Discovery is two weeks, costs USD 4K to 8K, and prices everything that comes after. Skipping it is the most common reason migrations blow budgets by 30 to 60 percent. The deliverable is a fixed-price proposal with a signed-off scope document; without that artifact, you are paying time-and-materials and the agency is guessing.
Six artifacts ship out of a real discovery sprint: full URL inventory exported from Google Search Console covering every URL with non-zero impressions in the trailing 12 months (this is the input to the redirect map); top 500 ranking keywords with landing-page mapping so on-page elements get carried forward verbatim during rebuild; plugin and app audit classifying each as keep / replace / drop with a Shopify equivalent named per row; custom field inventory mapping every Magento product attribute or WooCommerce custom meta to a planned Shopify metafield; integration map covering ERP, 3PL, accounting, tax, shipping, payment, email, reviews, search, and any custom internal services with a wiring strategy per system; brand-system review deciding whether the rebuild adapts the existing design or takes a fresh design pass.
The discovery phase also runs a red-flag pass: legacy custom code with no documentation, integrations that depend on deprecated APIs, custom features that Shopify cannot replicate without code, data quality issues that will fight every later step. Surfacing these early is the difference between a 14-week project and a 14-week project that turns into 22 weeks because of a single cataloging quirk nobody noticed.
Brands that try to skip discovery save USD 4K to 8K and spend USD 20K to 80K downstream — the math is almost mechanical. We do not start any migration without one. The signed scope document protects both sides.
How does data actually move across?
Data migration is one to three weeks of work with three layers: products and variants, customers and order history, and custom metafields. The tooling depends on source platform but the failure modes are universal — bad mapping, lost custom data, broken images, and orphaned records that nobody catches until launch.
Tooling we use most often: Matrixify for products + customers + orders bulk import (handles most of the heavy lifting on Shopify's side), platform-specific exporters on the source side (Magento Mage::ImportExport, WooCommerce CSV Importer, BigCommerce data export), and the Shopify Admin GraphQL API for anything custom. Custom Magento attributes mapping to Shopify metafields is where most projects burn time — the relationship is not always one-to-one and decisions about which attributes become metafields versus product variants versus tags need to be made deliberately.
Order history migration is the second-biggest source of pain. Shopify's order import is robust but the historical orders come in as fulfilled archives — they cannot be modified, refunded, or used for ongoing customer service. For most brands this is fine; the customer list, lifetime value calculations, and reorder-flow attribution land correctly. For brands that need full operational continuity on historical orders (B2B with frequent reorders, subscription brands with active subscription records), we usually run a parallel period where the legacy platform stays read-only for support purposes for 30 to 60 days while the new store handles all new orders.
For deep treatment of the Magento-specific path, see Magento to Shopify migration cost; for WooCommerce, the step-by-step is in WooCommerce to Shopify checklist; the BigCommerce path is documented in BigCommerce to Shopify migration guide.
Custom theme or adapt the existing design?
The choice splits the project's budget by roughly two-to-one. Adaptation runs three to four weeks and lands the existing design on a Shopify-native theme base. Custom rebuild runs eight to 12 weeks and produces a theme designed specifically for the catalog, the brand, and the conversion path.
For brands whose current site converts well, adaptation is usually right. The best Shopify theme bases for adaptation in 2026 are Dawn (Shopify's official OS 2.0 reference theme — free, well-maintained, fast), Impulse, Prestige, and Stiletto. Each has its strengths; the choice depends on category. Fashion-forward DTC tends to land on Impulse or Prestige; performance-first commodity goods land on Dawn.
Custom theme work is justified when the brand has invested in distinctive design language that template themes cannot represent without compromising it, or when the catalog has unusual structure (configurable products, complex variants, made-to-order workflows) that a generic theme handles awkwardly. We work in Liquid, sections + blocks for OS 2.0 flexibility, and Shopify Functions for cart and checkout customization. The depth of OS 2.0's templating model is covered in Shopify Online Store 2.0 explained.
App replacement runs in parallel with theme work. The five apps that almost every migration installs: Klaviyo for email + SMS (replaces Mailchimp, ESP-X, internal tools), a reviews app (Judge.me for cost-sensitive brands, Yotpo for enterprise), a subscription app where applicable (Recharge, Skio, Loop), a search and merchandising app (Boost, Searchspring), and a customer support tool (Gorgias for the Shopify-native experience). Each of these has been covered in depth in our journal — see the related links in §08.
Why does SEO survive some migrations and not others?
Every migration that loses 30-plus percent of organic traffic for six months did one of three things: shipped without a complete 301 redirect map, rewrote on-page elements during the rebuild instead of preserving them, or changed URL structure without one-to-one mapping. Done right, you should see a small two to four week impressions dip followed by full recovery by week eight.
The 301 redirect map is the single highest-leverage SEO artifact in the project. It maps every old URL with non-zero historical impressions or backlinks to its new home. The map is built in week 9 of a typical 14-week migration, tested against the staging site, and deployed live at minute zero of DNS cutover. Cheap migrations skip URLs that look unimportant — that page with 12 backlinks from authoritative sites you forgot existed becomes a 404 and the link equity dies.
On-page preservation runs as the rebuild proceeds. As each template is built, the title tags, meta descriptions, H1s, and on-page content for ranking pages are carried forward verbatim from the source. Rewrites only happen when there is a measurable reason — a page that ranks position 12 with a weak title is a candidate for a rewrite during migration; a page ranking position three with a great title is preserved exactly. The sequencing matters: rewrite before launch and the migration absorbs the volatility; rewrite three months after migration and you can attribute any rank movement directly to the on-page change.
Structured data carries forward too. Product schema, Review schema (only when sourced from third-party platforms with proper attribution per Google Search Central guidance), Organization schema, BreadcrumbList. The schema gets validated against Rich Results Test on staging before launch. The full redirect playbook is in Shopify 301 redirect best practices.
What does launch week actually look like?
Launch is Tuesday morning. Never Friday. Never the week before BFCM. Never during a holiday cluster. Tuesday because you have four full working days to triage anything that surfaces before the weekend and a fresh team on Monday for the first follow-up cycle. The 90-day recovery period after launch is where SEO either recovers or does not.
Launch checklist: redirects deployed at minute zero, sitemap submitted to GSC and Bing Webmaster Tools, Core Web Vitals baseline captured, GA4 + Meta Pixel + any other tracking validated end-to-end with a real test order, war-room Slack channel active for 48 hours with the agency team monitoring real traffic. Rollback plan documented and tested before launch — the only acceptable rollback is a tested one.
The first 90 days post-launch run on a defined cadence. Week 1: daily rank monitoring, daily 404 log review, daily customer-report triage. Week 2-4: trend watching on GSC impressions and position; small redirect tuning for URLs that missed the original map. Week 5-12: monthly written status covering rank trajectory, conversion rate vs old site, revenue continuity, outstanding issues. Day 90: formal recovery report closes the project or transitions to retainer.
The full week-by-week breakdown of the entire project is in Shopify migration timeline; the recovery-period detail is documented per phase there too.
Seven answers.
What does a complete Shopify migration include?
Eight workstreams. Discovery (URL inventory, ranking export, custom-field audit, integration map). Data migration (products, customers, orders, custom metafields). Theme rebuild (or design adaptation if budget is tight). App replacement (every legacy plugin gets a Shopify equivalent or custom build). Integration wiring (ERP, 3PL, accounting, payment, tax). SEO preservation (301 map, on-page carry-forward, GSC monitoring). Launch operations (DNS cutover, war-room monitoring, rollback plan). 90-day recovery (rank tracking, conversion comparison, traffic continuity). Skipping any one of these is where migrations fail.
How much does a Shopify migration cost?
Range is wide because scope varies dramatically. Small catalog (under 200 SKUs) with design-as-is adaptation and standard integrations: USD 12K to 30K. Mid-market (200 to 5,000 SKUs) with custom theme and 3 to 5 integrations: USD 30K to 85K. Enterprise Shopify Plus migration with 5,000-plus SKUs, custom checkout, B2B, multi-store, ERP, 3PL: USD 85K to 250K. The two cost drivers are data complexity (custom fields, subscription history, configurable products) and integration depth. A 2-week discovery phase prices both before any build commits.
Will my SEO survive a Shopify migration?
Yes if redirects, on-page carry-forward, and structure preservation are done before launch. Most migrations that lose SEO did one of three things: shipped with broken or missing 301 redirects, rewrote title tags and meta descriptions during the rebuild instead of preserving them, or changed URL structure without a one-to-one map. Done correctly, you should expect a small two to four week dip in impressions followed by full recovery by week eight. Done badly, you can lose 30 to 60 percent of organic traffic for six months while you debug.
Should I use Shopify or Shopify Plus?
Plus is for stores hitting USD 1M-plus annual revenue, doing custom checkout work, running multi-store, or needing API throughput beyond the standard tier. Below that revenue, the Plus features rarely pay for themselves — basic Shopify covers 90 percent of DTC needs at one-third the cost. Common Plus triggers: custom B2B with company accounts and tiered pricing, checkout extensibility for custom upsells or compliance fields, multi-store for international operations, scripts API for cart logic, and dedicated launch engineering support.
When should I NOT migrate to Shopify?
Three honest scenarios. One, if you sell heavily customized B2B with 50-plus pricing tiers, contract pricing per buyer, or require approval workflows that span days — Shopify Plus B2B handles a lot of this in 2026 but the custom B2B platforms (BigCommerce B2B Edition, Magento with B2B, custom platforms) still beat it for the most complex cases. Two, if your business depends on cataloging logic that Shopify's product model can't represent (truly configurable products with infinite variants, product bundles with shared inventory across SKUs). Three, if your current platform is fine and you're being talked into a migration for political reasons rather than commercial ones — that migration usually costs more than it returns.
How long does a complete Shopify migration take?
Six to 24 weeks depending on scope. Small catalog migration: 6 to 8 weeks. Mid-market with custom theme and 3 to 5 integrations: 10 to 14 weeks. Enterprise Plus migration with B2B, custom checkout, multi-store, ERP integration: 16 to 24 weeks. The discovery phase prices the bucket. Compressing the timeline below the bucket floor usually means parallelizing work that should be sequential, which surfaces as broken redirects, missed data, or a customer-facing bug visible after launch. The right schedule is the one that does not skip QA.
What is the biggest mistake brands make during Shopify migration?
Skipping discovery. Teams that go straight from agency selection into theme work miss between 15 and 40 percent of the actual scope, which surfaces as either a 30 to 60 percent budget overrun or a launch slip of one to three months. The discovery phase costs USD 4K to 8K and saves between USD 20K and 80K downstream. Second-biggest mistake: cheap on the redirect map. The map is the single highest-leverage SEO artifact in the project; budgeting one day for it instead of the three to five it actually requires costs months of recovery work after launch.
Discovery first. Build second.
More from Saanvi.
Senior Shopify Engineer · B2B · Delhi · 3 posts on the site
Published .