Migrating from WooCommerce/Magento to Shopify Plus: A Technical Playbook

We have migrated over 150 stores from WooCommerce and Magento to Shopify Plus. Every migration has taught us something new about what can go wrong -- and most of those lessons are not documented anywhere else.

This is the playbook we wish existed when we started doing migrations. It covers the complete process from initial audit to post-launch monitoring, including the ugly parts that other guides skip: data that will not transfer cleanly, SEO rankings that can (and will) dip temporarily, subscription migrations that keep you up at night, and the payment gateway cutover window where two systems need to run simultaneously.

For platform-specific deep-dives, see our dedicated migration pages: WooCommerce to Shopify and Magento to Shopify.

The Complete Migration Timeline

Here is the timeline we follow for a mid-complexity migration (5,000-20,000 products, 10,000-50,000 customers):

Step 1: Data Mapping -- What Transfers and What Does Not

The first and most important step is understanding exactly what data can migrate cleanly, what needs transformation, and what will be lost.

Data that transfers cleanly

• Products: Title, description, images, variants, prices, SKUs, inventory quantities, weight
• Customers: Name, email, addresses, order history association
• Orders: Order details, line items, fulfillment status, payment status (as historical records)
• Blog posts: Title, content, author, publish date, featured image
• Pages: Static page content (HTML preserved)

Data that needs transformation

• Product categories/collections: WooCommerce categories and Magento categories have different hierarchies than Shopify collections. Manual mapping required.
• Product attributes: WooCommerce/Magento custom attributes become Shopify metafields. Requires metafield definition setup.
• Customer groups/tiers: Map to Shopify customer tags or B2B company accounts.
• Discount/coupon rules: Complex Magento cart price rules and WooCommerce coupon logic need to be rebuilt in Shopify's discount system or Shopify Scripts.
• URL structure: Complete restructuring required (covered in SEO section below).

Data that is lost

• Customer passwords: Cannot migrate password hashes between platforms. Customers must reset passwords.
• Saved payment methods: Tokenized payment data is gateway-specific and non-transferable.
• Wishlist data: No native Shopify equivalent. Requires a third-party app to rebuild.
• Product reviews: Exportable from most review plugins, but must be imported into a Shopify review app (Judge.me supports CSV import).
• Advanced tax rules: Magento's complex tax rule engine does not map to Shopify's tax system. Must be reconfigured.

Pro Tip: Always run a test migration first. Import data into a Shopify development store, validate every field, and identify gaps before touching production data. We run 2-3 test migrations before the final cutover.

Step 2: URL Redirects and SEO Preservation

This is the step that determines whether your migration preserves your organic traffic or destroys it. URL structure changes are the single biggest SEO risk in any migration.

URL structure differences

Our redirect process

1. Crawl the source site using Screaming Frog or Sitebulb. Export all URLs with status codes, meta titles, and canonical tags.
2. Map every URL from source to Shopify equivalent. Automate with a script for products and collections; manually map pages and blog posts.
3. Prioritize by traffic -- sort URLs by organic sessions (from Google Search Console data). The top 100 pages typically account for 80% of organic traffic.
4. Implement 301 redirects in Shopify. For stores under 1,000 redirects, use the Shopify admin. For larger volumes, use the Shopify API or a redirect app.
5. Handle edge cases: paginated URLs (/page/2/), filtered URLs (?color=blue), and trailing slashes all need explicit handling.

# Sample redirect CSV for Shopify import
# /old-path, /new-path
/product/blue-cotton-shirt/,/products/blue-cotton-shirt
/product-category/mens-shirts/,/collections/mens-shirts
/about-us/,/pages/about-us
/blog/how-to-style-shirts/,/blogs/news/how-to-style-shirts
/shop/,/collections/all
/cart/,/cart
/my-account/,/account

SEO preservation beyond redirects

• Migrate meta titles and descriptions -- do not let Shopify auto-generate them. Port exact meta data from the source.
• Preserve structured data -- product schema, breadcrumb schema, FAQ schema. Rebuild in the Shopify theme.
• Submit new sitemap to Google Search Console immediately after launch.
• Monitor 404s daily for the first 30 days using Screaming Frog and Search Console's Coverage report.
• Set realistic expectations: even with perfect redirects, expect a 10-20% organic traffic dip for 2-6 weeks. It recovers.

Step 3: Payment Gateway Cutover

The payment gateway switch is the highest-risk moment of the migration. Here is how to handle it safely:

1. Set up Shopify Payments (or your chosen gateway) on the Shopify store 2-3 weeks before launch. Complete all verification and test transactions.
2. Run both gateways simultaneously for a brief window. Keep the old store processing orders until DNS fully propagates (24-48 hours).
3. Migrate active subscriptions before cutting over (see next section).
4. Communicate to customers about saved payment method resets. Prepare a post-launch email campaign for password resets and payment re-entry.
5. Monitor failed transactions closely for the first 72 hours. Payment declines often spike during gateway transitions.

Step 4: Subscription Migration

Subscription migration is the most technically complex part of any migration. Here is why it is difficult and how we handle it:

Why subscriptions are hard to migrate

• Payment tokens are non-transferable. Each payment processor generates unique tokens for stored cards. You cannot move a Stripe token from WooCommerce to Shopify Payments.
• Billing schedules must be recreated. Each subscriber's next billing date, interval, and product selections need to be replicated exactly.
• Dunning and retry logic differs. WooCommerce Subscriptions and Recharge handle failed payment retries differently. Customized retry schedules need to be rebuilt.

Our subscription migration process

1. Export all active subscriptions from the source platform (subscriber email, product, variant, price, interval, next billing date, payment method last 4 digits).
2. Set up Recharge (or chosen subscription app) on Shopify with matching product configurations.
3. Import subscribers into Recharge using their bulk import API. Subscriptions are created in a "paused" state initially.
4. Communicate with subscribers: Send an email explaining the migration, asking them to update their payment method on the new store. Offer a discount or incentive for updating within 7 days.
5. Activate subscriptions as customers update payment methods. Monitor activation rates daily.
6. Handle holdouts: For subscribers who do not update within 14 days, send a final reminder. Consider manually reaching out to high-value subscribers.

Expect 15-25% subscriber churn during migration. This is normal. Some subscribers use the disruption as a natural exit point. The key is minimizing involuntary churn (payment failures) through proactive communication and a smooth update flow.

What Breaks: The Section Nobody Writes About

This is the part of the migration playbook that most agencies leave out. Here is what will break or behave unexpectedly, no matter how carefully you plan:

1. Custom functionality gaps

WooCommerce and Magento have extensive plugin/extension ecosystems with functionality that may not have a Shopify equivalent. Common gaps:

• Complex product configurators -- WooCommerce Composite Products and Magento Configurable Products with custom options. Shopify's variant system is more limited. Requires a custom app or third-party configurator.
• Advanced shipping rules -- Per-product shipping classes, dimensional weight calculations, multi-origin shipping. Shopify's native shipping is simpler; may need Shopify Scripts or a shipping app.
• Customer-specific pricing -- Magento's Tier Pricing and WooCommerce's dynamic pricing plugins. On Shopify, this requires Shopify Plus B2B features or a custom app.

2. Template/theme differences

• WooCommerce shortcodes will not render. Any page using [woocommerce_cart], [products], or custom shortcodes needs to be rebuilt as Shopify sections.
• Magento CMS blocks and widgets do not transfer. All dynamic content blocks must be recreated as Shopify sections or metafield-driven content.
• Custom post types (WooCommerce) have no Shopify equivalent. Recipes, lookbooks, and custom content types need to be rebuilt as Shopify pages with metafields or a headless CMS.

3. Third-party integration disruptions

• ERP integrations need to be reconfigured. NetSuite, SAP, and QuickBooks connectors are platform-specific. Budget 2-4 weeks for ERP reconnection.
• Email marketing automations break. Klaviyo flows triggered by WooCommerce events need to be rewired to Shopify events. All automations need retesting.
• Analytics continuity is lost. Google Analytics 4 property stays the same, but historical data will show a gap at the migration point. Set up comparison annotations.

4. Staff workflow changes

• Order management is different. Staff accustomed to WooCommerce's order screen need training on Shopify's order management.
• Content editing workflow changes. Shopify's theme editor is different from WordPress's Gutenberg or Magento's Page Builder. Plan training sessions.
• Reporting differences. Shopify's native reports differ from WooCommerce's WP Admin reports and Magento's BI. Staff may need time to adapt.

Step 5: Staff Training and Documentation

The migration is not done when the code goes live. Your team needs to be able to operate confidently on the new platform. We provide:

• Admin walkthrough (2 hours): Products, orders, customers, discounts, reports, settings
• Theme editor training (1 hour): How to edit sections, update content, manage navigation
• App-specific training (1-2 hours): Klaviyo, Recharge, and any other critical apps
• Documentation package: Written SOPs for common tasks (adding products, creating discounts, editing pages, managing blog posts)
• Emergency runbook: What to do if something breaks, who to contact, how to roll back if needed

Post-Launch: What to Monitor

The first 30 days post-migration are critical. Here is our monitoring checklist:

Final Thoughts

Migration is not a one-day event -- it is a multi-month project that requires technical precision, clear communication, and experienced hands at the controls. The cost of a botched migration (lost SEO rankings, broken checkout, subscriber churn) far exceeds the cost of doing it right.

If you are considering a migration from WooCommerce or Magento to Shopify Plus, here are the three things to get right:

1. Invest in a thorough audit before you write a single line of code. Understand exactly what you are migrating, what will change, and what will break.
2. Prioritize SEO preservation as the number-one technical concern. Redirect mapping is tedious but essential. Every missed redirect is lost revenue.
3. Communicate proactively with customers, especially subscription customers. The migration should be invisible to most shoppers, but subscribers need a heads-up.

For more details on platform-specific migration paths, explore our dedicated guides: WooCommerce to Shopify Migration and Magento to Shopify Migration.