In short: Replatform in phases: audit your URLs, integrations and catalog first, migrate data in order (products, customers, orders), build the redirect map in parallel with the theme, test checkout and integrations on staging, then cut over in a low-traffic window and keep the old platform warm for two weeks. WooCommerce and BigCommerce moves usually take 8 to 14 weeks; larger Magento builds take longer.
Ready to move to Shopify but not sure where to start?
Replatforming is one of the highest-leverage decisions you'll make for your ecommerce business. It's also one of the easiest to get wrong.
A botched migration can cost you a large share of your organic traffic, break integrations you depend on for revenue, and take the better part of a year to fully recover. We've seen it happen to brands that moved fast and skipped the fundamentals.
This guide covers the full process, from the pre-migration audit through to post-launch stabilization. We also break down the specific risks for the three most common source platforms: WooCommerce, Magento/Adobe Commerce, and BigCommerce.
The one rule that applies to every migration: migrate once, properly. The cost of doing it right is always less than the cost of fixing a bad one.
What this guide covers:
- The universal migration process (all platforms)
- Platform-specific risks and timelines
- SEO continuity: the single biggest failure mode
- Data migration sequence and what doesn't transfer
- Cutover, rollback, and the first 30 days post-launch
Why Brands Replatform to Shopify
Before you plan a migration, it's worth being clear on what you're actually solving for.
The most common reasons we hear from brands:
- Maintenance tax. Your current platform requires ongoing developer time just to stay stable. Plugins conflict. Updates break things. You're paying to stand still.
- Performance ceiling. Page speed is suffering. Core Web Vitals are failing. Your platform's architecture is working against you.
- Missing B2B or international capability. You need net terms, company accounts, multi-currency, or market-specific pricing, and your current platform can't do it cleanly.
- Checkout limitations. You can't customize the checkout experience without expensive custom development or workarounds.
- Total cost of ownership. The three-year TCO on Magento or a self-hosted WooCommerce setup often dwarfs Shopify's all-in cost once you factor in hosting, security, development, and plugin fees.
Don't treat this as a cost-cutting exercise.
The real ROI of a Shopify migration comes from four places: lower platform overhead, higher conversion rates, unlocked revenue channels (B2B, international), and a smaller ongoing engineering load. If you're only optimizing for the platform invoice, you're leaving most of the value on the table.
The Universal Migration Process
Regardless of which platform you're leaving, the migration follows the same core sequence. Skip a phase and you'll pay for it later.
Phase 1: Discovery and Audit (Weeks 1-2)
This is the phase most brands underinvest in. Two weeks of senior strategy work before you write a single line of code will save you months of rework.
What to do:
- Crawl your current site with a tool like Screaming Frog and export every indexed URL with its traffic, rankings, and backlink count.
- Inventory every integration: ERP, 3PL, ESP, subscriptions, loyalty, review apps. For each one, document the business owner, the job it does, and the monthly cost.
- Audit your product catalog for taxonomy issues, inconsistent data, and variant structures that won't map cleanly to Shopify's model.
- Benchmark your current conversion rate, average order value, page speed, and Core Web Vitals. You need a baseline to measure against post-launch.
Sort your integrations into three buckets: Keep (has a Shopify equivalent), Replace (Shopify does this natively), and Cut (no longer needed). Most brands find apps and plugins they can cut during this exercise. Our guide to auditing your app stack by margin shows how to decide.
Phase 2: Data Migration (Weeks 3-6)
Shopify's own Store Migration app moves products and customers from a handful of platforms, including WooCommerce. For Magento and BigCommerce, and for orders, gift cards, blogs and pages, you'll need a third-party migration tool such as Matrixify, LitExtension or Cart2Cart.
What a migration tool can move:
- Products, variants, and images
- Customer records and order history
- Gift cards (confirm during discovery that your tool and Shopify plan support importing existing codes and balances)
- Blog posts and static pages
What doesn't transfer via standard export:
- Themes and custom code (rebuild from scratch)
- Platform extensions and plugins
- Stored payment credentials (requires a specialist PCI-compliant process)
- Subscription data (requires coordination with your subscription app)
The sequence matters. Import products first, then customers, then historical orders. Don't start building your theme until the catalog is in and verified.
Phase 3: Build and Integrations (Weeks 4-10)
Your new Shopify store gets built in parallel with data migration.
For most brands, we recommend Shopify's free Horizon theme as the starting point. It uses the latest block-based architecture, performs well out of the box, and reduces your reliance on third-party apps. Our Nc'nean case study shows what moving an older theme to Horizon did for page speed.
Custom integrations, Shopify Functions, and Shopify Flow automations get built during this phase. If you're on Shopify Plus, this is also when you configure checkout customizations. If you sell wholesale, this is when B2B catalogs, company accounts and payment terms get set up (see our Shopify B2B development service).
Phase 4: SEO and Redirect Mapping (Weeks 5-8, runs in parallel)
SEO is the headline risk of any migration. Handle it in parallel with the build, not as an afterthought.
Build a 1:1 redirect map: one spreadsheet row per old URL, pointing to its exact new Shopify equivalent. Every URL that has traffic or backlinks needs a destination.
The URL changes you'll deal with on each platform:
| Source Platform | What changes | Biggest SEO risk |
|---|---|---|
| WooCommerce | /product/ becomes /products/, /product-category/ becomes /collections/ | Blog posts and custom pages missed in the redirect map |
| Magento/Adobe Commerce | .html endings removed, nested category paths flattened, filter URLs disappear | Very large URL counts including indexed filter pages |
| BigCommerce | Products move under /products/, category paths change | Page titles and meta descriptions not carried over for every page type |
Import redirects via CSV into Shopify's URL Redirects table before DNS cutover. Avoid redirect chains: old to new in one hop, never two.
Check the limit before you build the map. Shopify allows up to 100,000 URL redirects on standard plans and up to 20 million on Shopify Plus (Shopify Help Center). A very large catalog with years of indexed filter URLs can hit the standard limit, so prioritize the URLs that carry traffic and backlinks.
Phase 5: QA and Testing (Weeks 9-11)
NEVER skip this phase.
Test every critical journey on a staging store before you touch the live domain:
- Full checkout with each payment method, each shipping rate, discount codes, logged-in and guest sessions
- Deliberately failed transactions (to confirm error handling works)
- Every integration: verify orders flow to your ERP, fulfillment triggers your 3PL, emails fire from your ESP
- All 301 redirects (crawl staging with Screaming Frog and confirm every old URL returns a single 301 to a live page)
- Mobile and desktop on multiple devices
Phase 6: Cutover
Schedule your cutover window during your lowest traffic period. For most US stores that's 2-6am on a Tuesday.
The cutover sequence:
- Freeze the old platform at T-14 days (no new content, no new products, no new code)
- Run a final data sync rehearsal at T-7 days and time it
- At T-3 days, check that every ad and email landing URL is in the redirect map
- On cutover: deactivate test mode on Shopify Payments, switch your primary domain, point DNS records at Shopify, remove the password page
- Run the delta migration: sync every order, customer and gift card balance created on the old store since your data cutoff, so nothing is missing on day one
- Deactivate checkout on the old store while DNS propagates (so no orders land somewhere you'll have to reconcile)
- Submit your sitemap to Google once the site is live
Reduce your DNS TTL to 300 about a week before cutover to ensure fast propagation.
Phase 7: Post-Launch Stabilization (Days 1-60)
Keep the old platform warm for at least 14 days after launch. If something catastrophic surfaces in the first 48 hours, you need the ability to revert.
Week 1: Validate every 301 redirect. Resolve 404s as they surface. Confirm orders are flowing, payments are processing, and analytics are tracking.
Weeks 2-4: Compare conversion rate, load time, and AOV against your pre-migration baseline. Catch regressions in days, not weeks.
Days 30-60: Ship the phase-2 items you deferred from launch scope.
Platform-Specific Migration Guides
The universal process above applies to every migration. What changes is the shape of the risk, the size of the data problem, and the realistic timeline. Here's what to expect from each platform.
WooCommerce to Shopify
This is one of the most common migrations we see.
WooCommerce brands hit a ceiling that's almost always the same: plugin fragility, performance degradation, and the compounding cost of maintaining a self-hosted stack. The migration budget you'd spend in one shot is often less than two years of WooCommerce maintenance.
The headline challenge: data quality.
WooCommerce stores accumulate years of inconsistent product taxonomy, custom meta keys, and plugin-specific database tables. Before you estimate a build timeline, plan a 4-week data audit. You'll find product data that won't map cleanly to Shopify's variant model, customer records with gaps, and order history that needs cleaning before import.
WooCommerce-specific gotchas:
- URL structure changes significantly. /product/your-product becomes /products/your-product, and /product-category/your-category becomes /collections/your-category. Your blog moves from /your-post or /blog/your-post to /blogs/news/your-post. Every one of these needs a redirect.
- Plugin replacement audit. List every active plugin and map it to a Shopify equivalent. Many WooCommerce plugins have direct Shopify app equivalents. Others are replaced by Shopify's native functionality (abandoned cart, basic discounts, email notifications). Resist replacing every plugin with an app: that path leads to app bloat, a slower store and growing monthly costs.
- Subscription data. If you run subscriptions through WooCommerce Subscriptions, coordinate the migration with your new Shopify subscription app vendor before you start. This is not a standard CSV import.
For custom functionality, decide the approach item by item:
| Functionality | Recommended approach on Shopify |
|---|---|
| Custom or wholesale pricing rules | Shopify B2B catalogs and quantity price breaks, or Shopify Functions delivered through an app |
| Subscription products | Shopify Subscriptions or a subscription app such as Recharge |
| Product configurators | Line item properties for simple options, or a custom app for complex ones |
| Loyalty programs | A loyalty app such as Yotpo or Smile.io |
| Custom checkout fields | Checkout UI extensions (Shopify Plus for the information, shipping and payment steps) |
Realistic timeline: 8-12 weeks for an established DTC brand with a clean catalog. Add 2-4 weeks if you're also redesigning or have a complex integration stack.
Magento / Adobe Commerce to Shopify Plus
This is the most expensive migration to do correctly. It's also usually the most economically rational.
The three-year TCO difference between a maintained Magento/Adobe Commerce setup and Shopify Plus is dramatic, and the engineering team you need post-migration is meaningfully smaller. We break down the cost and admin differences in Magento vs Shopify for mid-market merchants.
The headline challenge: catalog complexity and URL structure.
Magento's configurable product model doesn't map directly to Shopify's variant model. If you have products with many configurable options (size, color, material, finish), you'll need to make deliberate decisions about how they translate. Some combinations become variants; others become separate products or use Shopify's line item properties for customization.
URL structure is the other major risk. Magento stores often have years of indexed URLs including .html endings, nested category paths, and layered-navigation filter pages that generated thousands of indexed URLs. Every one of those needs to be mapped.
Magento-specific gotchas:
- Custom modules. List every custom Magento module and evaluate it against Shopify's native capabilities, Shopify Functions, Shopify Flow, and the app ecosystem. Most can be replaced. Some require custom development.
- Multi-store setups. If you're running multiple storefronts from a single Magento instance, your Shopify architecture decision (multiple stores vs. Shopify Markets) needs to be made before the build starts, not during it. Shopify Markets handles currency, language and pricing per region from a single store, which is the cleaner answer for most brands. Brands with genuinely distinct catalogs or business units are better served by separate stores. Our guide to enterprise migrations vs. multi-brand architecture covers that decision.
- Filter/faceted navigation URLs. Magento's layered navigation generates URLs like /category?color=blue&size=medium that often get indexed. These disappear on Shopify. Map the high-traffic ones to their collection equivalents.
- B2B customer groups. Magento's customer group pricing needs to be rebuilt as Shopify B2B catalogs and company accounts. These have been available on every plan from Basic up since April 2026; Plus adds more catalogs and options such as deposits.
Realistic timeline: 14-22 weeks for a larger or more complex Magento build. A mid-market store with a standard catalog and few custom modules can land closer to 8-16 weeks. The range is wide because catalog complexity, multi-store setup, and custom module count vary enormously. Budget for the longer end if you have a large catalog or significant custom development on the current platform.
BigCommerce to Shopify
This is often the smoothest migration of the three.
BigCommerce's APIs are clean, and the product/customer/order data shapes map closely to Shopify's. Skullcandy moved from BigCommerce to Shopify in 90 days. That's achievable for a well-scoped project. In research Shopify commissioned from an independent consulting firm, Shopify implementations were 10% faster and 4.4 times more likely to stay on budget than comparable BigCommerce implementations.
The headline challenge: B2B pricing and theme logic.
If you're using BigCommerce's customer groups for B2B pricing or wholesale, that logic needs to be rebuilt in Shopify. BigCommerce's Stencil theme framework also has its own conventions, so any custom theme work doesn't transfer and needs to be rebuilt from scratch in Shopify's Liquid.
BigCommerce-specific gotchas:
- Product options vs. variants. BigCommerce product options don't map directly to Shopify's variant format. Products with many option combinations may need to be restructured. Custom fields may need to be remapped to Shopify metafields, sometimes requiring manual CSV work.
- Categories vs. collections. BigCommerce categories don't translate one-to-one into Shopify collections. You'll need to rebuild your collection structure and map the old category URLs to new collection URLs.
- Page titles and meta descriptions. Check that these come across for every page type, especially categories and web pages. Export them before you start so you aren't rebuilding your SEO metadata from scratch.
- B2B price lists. BigCommerce's price list system needs to be rebuilt as Shopify B2B catalogs, or through a B2B app if your pricing logic goes beyond what catalogs support.
Realistic timeline: 8-14 weeks. This is the shortest range of the three platforms, assuming a standard DTC catalog without heavy B2B complexity.
Shopify vs. Shopify Plus: Which Do You Need?
Don't make this decision based on price alone.
Shopify Plus starts at $2,300/month. For many brands, it's not necessary. For others, it's non-negotiable. The real question is whether you need what Plus actually unlocks.
You need Shopify Plus if:
- You need to customize the information, shipping, and payment steps of checkout (checkout UI extensions on those steps require Plus)
- You're running B2B at scale, with more price catalogs than other plans allow or features such as deposits
- You're selling across many markets with per-market pricing, themes, or domains
- You need Plus-only capabilities such as expansion stores, custom Shopify Functions apps, or higher API limits
Standard Shopify is fine if:
- You're a single-market DTC brand with a straightforward checkout
- Your integration complexity is moderate (most apps work on all Shopify plans)
- Your B2B needs are simple: company accounts, net terms, and a few price lists, which every plan from Basic up now supports
Make this call before you start the build. The architecture decisions that follow depend on it. For a deeper comparison, see our guide on Shopify vs. Magento vs. BigCommerce.
The Most Common Migration Mistakes
These aren't hypothetical. They're the patterns we see most often when brands come to us after a migration that didn't go well.
- Skipping the pre-migration data audit. You can't estimate a migration timeline without knowing the state of your data. WooCommerce stores especially accumulate years of inconsistency. Discover this before the build starts, not during it.
- Treating SEO redirects as an afterthought. The redirect map should be built in parallel with the theme, not the week before launch. Brands that rush this step can lose a large share of their organic traffic and spend months clawing it back.
- Migrating and redesigning at the same time without a clear scope. Doing both is fine. But they need to be scoped separately, with a clear decision on what's in scope for launch and what's phase 2. Scope creep during a migration is the most common reason projects go over budget and over time.
- Not testing payment flows on staging. Your checkout is your revenue. Test every payment method, every shipping rate, every discount code, and deliberately failed transactions before you touch the live domain.
- Cutting the old platform off too soon. Keep your old platform live and accessible for at least 14 days post-launch. If something goes wrong in the first 48 hours, you need a rollback option. The cost of keeping it warm for two weeks is trivial compared to the cost of a botched launch with no recovery path.
- No post-launch monitoring plan. Assign someone to watch conversion rate, 404 errors, and organic traffic daily for the first two weeks. Problems caught in days are recoverable. Problems caught in weeks are expensive.
For the B2B, ERP and post-launch side of a migration in more depth, see 10 things Shopify developers actually get right.
Migration Timeline Summary
Here's a realistic timeline range for each migration type, based on a standard DTC brand with a moderately complex integration stack.
| Source Platform | Typical Timeline | Key Variable |
|---|---|---|
| WooCommerce to Shopify | 8-12 weeks | Data quality and catalog size |
| BigCommerce to Shopify | 8-14 weeks | B2B complexity and custom theme work |
| Magento/Adobe Commerce to Shopify Plus | 14-22 weeks for larger builds (8-16 for a standard mid-market catalog) | Custom modules, multi-store setup, URL volume |
Add 2-4 weeks to any of these if you're also doing a full redesign.
These timelines assume a properly scoped project. Brands that skip the discovery phase or underestimate data complexity routinely run well over these estimates.
Ready to Migrate?
We've migrated brands from WooCommerce, Magento, and BigCommerce to Shopify and Shopify Plus through our Shopify website development service. We scope it properly, we handle the SEO, and we don't disappear after launch.
If you're planning a migration or trying to figure out what it would actually involve for your store, email us at hello@kirkbyconsulting.com or book a free discovery call.
Frequently asked questions
How long does it take to migrate to Shopify?
What is the biggest risk in a Shopify migration?
Can all data be moved from WooCommerce, Magento, or BigCommerce to Shopify?
Do I need Shopify Plus for a migration?
Should I redesign the site during the migration?
Sources
- Migrating to Shopify (Shopify Help Center)
- Store Migration app (Shopify App Store)
- URL redirects (Shopify Help Center)
- Shopify B2B (Shopify Help Center)
- Checkout extensibility (Shopify Help Center)
- Shopify Plus pricing (Shopify)
- Skullcandy case study (Shopify)
- Time to value research (Shopify)
Spotted something wrong or out of date? Email hello@kirkbyconsulting.com with the details and we will correct it.