Magento to Shopify Migration Guide

A Magento to Shopify migration is a replatforming project involving data transformation, URL mapping, system re-integration, and SEO preservation. Migration timeline depends on catalog size and complexity, number of integrations, custom functionality requirements, B2B needs, and storefront design changes.

This guide covers why merchants leave Magento, what transfers during migration, what requires rebuilding, how to protect SEO rankings, and what a realistic project looks like. Platform-specific figures and dates are linked to their official sources.

Book a discovery call

Why merchants migrate from Magento to Shopify

Magento built its reputation on flexibility and self-hosted control. That flexibility requires ongoing infrastructure management, security patching, extension maintenance, and specialized developer expertise. For many ecommerce teams, the total cost of ownership and maintenance burden outweigh Magento’s customization advantages.

Adobe Commerce support timeline

Adobe has ended support for multiple Magento versions. Stores remaining on unsupported versions accumulate security risk and lose compatibility with payment processors and compliance requirements.

Check which version you’re on against Adobe’s Commerce Support Lifecycle policy to understand your support status. Migration off legacy versions becomes a matter of when, not if.

The Shopify Plus value proposition

Shopify Plus provides fully managed infrastructure, automatic security updates, and PCI compliance without dedicated DevOps resources.

Engineering effort shifts from platform maintenance to business growth. Development teams focus on product features, experimentation, and integrations rather than core infrastructure.

Shopify vs Shopify Plus for Magento migrations

Standard Shopify supports businesses up to moderate complexity. Shopify Plus provides additional capabilities essential for many Magento merchants.

Shopify Plus advantages:

• Custom checkout: Checkout Extensibility lets you add validation, upsells, custom fields, and B2B logic without fragility
• Advanced B2B: Unlimited company catalogs with company-specific pricing, deposits, and partial payments (all plans include foundational B2B with up to 3 catalogs since April 2026)
• Multi-store management: Operate multiple brands or regional stores with centralized administration
• Wholesale channels: Separate wholesale pricing, catalogs, and ordering experiences
• Higher API limits: GraphQL Admin API allows 1,000 points per second on Plus vs 200 on Advanced (source: Shopify API, verified October 2026)

When Shopify Plus makes sense:

• Operating multiple brands or regional storefronts
• B2B sales requiring advanced features (unlimited catalogs, deposits, company-specific pricing)
• Custom checkout requirements beyond basic customization
• Complex integrations with ERP, OMS, or PIM systems requiring higher API limits
• High-volume order processing

Read our comparison: Shopify vs Shopify Plus

What transfers during a Magento migration

Understanding what migrates cleanly versus what requires transformation prevents project delays and post-launch issues.

Products and catalog

Migrates with transformation:

• Product records with SKUs, titles, descriptions, and pricing
• Product images and media
• Product variants (Magento configurable products map to Shopify variants with constraints)
• Custom attributes (map to Shopify metafields)
• Inventory quantities and locations

Shopify constraints:

• Product variant limits require restructuring complex Magento configurable products
• Products with extensive option combinations may need splitting or metafield-based selection

Magento configurable products: These map to Shopify product variants. Simple products grouped under a configurable become variants. Complex configurations may need restructuring based on Shopify’s product model.

Customer data

Migrates:

• Customer records with names, emails, and addresses
• Customer tags and groupings
• Historical order associations

Cannot migrate:

• Customer passwords (due to different encryption methods)
• Magento customer group pricing structures (requires rebuilding with Shopify B2B or custom logic)

Customers receive account activation emails post-migration to set new passwords. Plan activation communication before launch.

Historical orders

Migrates:

• Order records with line items, pricing, and timestamps
• Customer associations
• Order status and fulfillment history

Limitations:

• Migrated orders are read-only in Shopify
• No payment capture, refund, or edit capability on historical orders
• Orders import after products and customers to preserve data relationships

Historical orders provide customer service continuity and warranty records rather than active order management.

CMS content

Requires manual recreation:

• About, Contact, and policy pages
• Content blocks and widgets
• Homepage sections
• Blog posts and articles

Magento CMS pages and Page Builder content have no direct Shopify equivalent. Content migrates by rebuilding in Shopify’s native page editor, Sanity CMS (for headless implementations), or page builder apps.

Audit existing content before migration. Pages with no traffic or business purpose need not transfer.

URLs and SEO metadata

Requires explicit mapping:

• Product URLs
• Category/collection URLs
• CMS page URLs
• Blog URLs
• Image URLs referenced externally

Magento and Shopify structure URLs differently. Magento often uses .html extensions and category paths (/category/product.html). Shopify uses fixed patterns: /products/handle, /collections/handle, /pages/handle, /blogs/handle.

Every indexed Magento URL requires a 301 redirect to its Shopify equivalent to preserve search rankings and backlink equity.

What needs rebuilding

Migration is not one-to-one transfer. These elements require implementation rather than import.

Custom functionality

Magento extensions and modules: Shopify does not run Magento extensions. Equivalent functionality comes from Shopify apps, custom development, or platform-native features.

Audit each Magento extension for business requirements. Many exist to work around Magento limitations rather than serve genuine needs. Shopify’s built-in features often handle what previously required extensions.

Custom checkout logic: Magento’s fully customizable checkout converts to Shopify Checkout Extensibility (Shopify Plus only). Address validation, custom fields, gift messages, and B2B terms rebuild as checkout extensions rather than template modifications.

Navigation and merchandising

Magento category trees: Magento’s hierarchical category structure does not transfer. Shopify collections are flat groups of products defined by manual selection or automated rules.

Recreate navigation by:

1. Mapping Magento categories to Shopify collections
2. Setting up collection rules based on product tags, types, vendors, or metafields for automation
3. Building menu navigation manually to show hierarchical structure
4. Adding breadcrumb logic if required

Faceted navigation: Magento’s layered navigation (filtering by attributes) maps to Shopify collection filters. Standard Shopify supports filtering by product tags, type, vendor, price, and metafields. Complex filtering may require search apps like Algolia or Searchspring.

Tier pricing and customer groups

Magento’s built-in tier pricing and customer group discounts do not map directly to Shopify.

Since April 2026, all Shopify plans include foundational B2B features: company accounts, up to 3 company catalogs, and basic wholesale ordering. Shopify Plus adds unlimited company catalogs with company-specific pricing, deposits, partial payments, and volume pricing rules.

B2B functionality requiring extensive customization may need custom development or service-layer pricing logic.

Integrations

ERP, OMS, PIM, and CRM connections: Magento integrations do not carry over. Each integration rebuilds using Shopify webhooks, REST Admin API, GraphQL Admin API, or integration platforms.

Common integrations:

• ERP systems (NetSuite, SAP, Microsoft Dynamics) for order, inventory, and financial sync
• Order management systems for fulfillment routing
• Product information management for catalog centralization
• CRM systems for customer data
• Marketing automation platforms
• Review and loyalty platforms

Plan integration rebuild during migration rather than post-launch.

Protecting SEO during migration

SEO preservation requires meticulous planning. Rushed URL mapping costs organic traffic and revenue.

URL redirect strategy

The requirement: Every indexed Magento URL must redirect to its Shopify equivalent with a 301 (permanent redirect) status.

URL inventory:

1. Export all product, category, CMS, and blog URLs from Magento
2. Pull URLs receiving impressions from Google Search Console
3. Identify revenue-generating landing pages from Google Analytics
4. Crawl the live Magento site to discover dynamically generated URLs
5. Document pagination, filter, and parameter-based URLs

URL mapping process:

1. Map product URLs: /category/product-name.html → /products/product-handle
2. Map category URLs: /category-name.html → /collections/collection-handle
3. Map CMS pages: /about-us.html → /pages/about-us
4. Map blog posts: /blog/post-name.html → /blogs/news/post-handle
5. Handle discontinued products: Redirect to parent collection or relevant alternative
6. Consolidate thin content: Redirect duplicates and low-value pages to stronger alternatives

Implementation:

• Shopify supports redirect management via admin CSV import
• Large redirect volumes may require edge-layer handling for headless builds or redirect apps

Testing:

• Validate redirects on staging before launch
• Crawl staging site to verify redirect coverage
• Test redirect chains (redirects pointing to other redirects) and eliminate them
• Confirm 301 status codes rather than 302 (temporary)

Pre-launch SEO checklist

☐ Complete 301 redirect map for all indexed URLs
☐ Preserve meta titles and descriptions from high-ranking pages
☐ Maintain URL structure for top-performing pages when possible
☐ Update XML sitemap and submit to Google Search Console
☐ Configure canonical URLs correctly (avoid trailing slashes)
☐ Test redirect implementation on staging environment
☐ Set up Google Search Console property for new Shopify domain
☐ Verify robots.txt allows crawling
☐ Implement structured data (Product, BreadcrumbList, FAQPage)
☐ Preserve image URLs or implement image redirects
☐ Update internal links throughout site content
☐ Verify hreflang tags for multi-language sites

Post-launch SEO monitoring

First 30 days:

• Monitor Google Search Console for crawl errors and 404s
• Track organic traffic and conversion compared to pre-migration baseline
• Verify search rankings for high-value keywords
• Check backlink resolution (external sites linking to old URLs)
• Monitor Core Web Vitals for performance regressions
• Review redirect coverage gaps and add missing redirects

Ongoing:

• Track indexed page count changes
• Monitor organic revenue attribution
• Review and optimize page load performance
• Update redirect map as new gaps surface

Headless Shopify with Sanity CMS

Headless architecture separates the storefront from Shopify’s backend commerce engine. This approach provides flexibility for content-rich experiences, multi-brand operations, and custom product interactions.

When headless makes sense:

• Operating multiple brands with shared content management
• Complex content operations requiring sophisticated editorial workflows
• Custom product configurators or visualization tools
• Unique buying experiences not achievable with Liquid templates
• Multi-channel content distribution (web, mobile app, in-store displays)

When headless adds unnecessary complexity:

• Standard product catalogs with straightforward merchandising
• Limited content team capacity for Studio-based workflows
• Budget constraints (headless costs more to build and maintain)
• Fast time-to-market requirements

Skai builds headless Shopify implementations with Sanity CMS for content management. We evaluate whether headless fits your operations during discovery and document the reasoning.

Headless Shopify case: We migrated Fjordfiesta from Craft Commerce to headless Shopify with Sanity CMS like-for-like, preserving their design and content while transitioning to a supported platform. The migration prioritized stability over immediate conversion optimization.

Read the Fjordfiesta case study

Learn more about headless Shopify architecture

Step-by-step migration plan

A structured sequence reduces risk and prevents data loss.

Phase 1: Discovery and planning

Audit current Magento environment:

• Document platform version (Magento 1, Magento 2, Adobe Commerce)
• Inventory products, variants, attributes, and categories
• List custom extensions and their business purposes
• Document integrations (ERP, OMS, PIM, CRM, email, reviews, subscriptions)
• Map customer groups and pricing structures
• Identify custom checkout modifications
• Review multi-store or multi-language configurations

Define migration scope:

• Decide what migrates, what rebuilds, and what retires
• Evaluate Shopify vs Shopify Plus requirements
• Assess headless vs native Shopify storefront
• Document success metrics and rollback criteria
• Assign project team roles and responsibilities

Phase 2: Data preparation

Clean and export data:

• Remove discontinued products and unused content
• Standardize SKUs, titles, and attribute values
• Ensure all product images have accessible URLs
• Deduplicate customer records
• Export products, customers, orders, and content in structured formats
• Map Magento attributes to Shopify metafields
• Resolve products exceeding variant limits

Create URL redirect map:

• Inventory all indexed URLs from Magento
• Pull URL data from Google Search Console
• Map each URL to Shopify equivalent
• Identify discontinued pages requiring parent-category redirects

Phase 3: Shopify setup

Configure staging store:

• Create non-public Shopify development store
• Configure business settings (tax, shipping, payments)
• Set up staff accounts and permissions
• Choose and install theme (or begin headless build)
• Install required apps for functionality gaps

Import data in sequence:

1. Products and variants (validate before proceeding)
2. Customers (link to existing products)
3. Historical orders (reference products and customers)

QA product catalog:

• Verify top-revenue SKUs for accuracy
• Test complex product configurations
• Validate inventory quantities
• Check images, pricing, and metafields
• Test collection rules and filtering

Phase 4: Storefront and functionality

Build storefront:

• Develop theme customizations or headless frontend
• Recreate CMS pages and content blocks
• Build navigation menus
• Implement product page features
• Configure collection pages and filtering
• Add blog content

Rebuild custom features:

• Implement checkout extensions for custom logic
• Configure B2B functionality if required
• Build custom product features (configurators, bundles)
• Add promotional and merchandising tools

Test checkout thoroughly:

• Successful orders across payment methods
• Failed payment handling
• Discount and gift card application
• Tax calculation across regions
• Shipping rate accuracy
• Email notifications

Phase 5: Integration and testing

Re-integrate systems:

• Connect ERP for order and inventory sync
• Wire OMS for fulfillment routing
• Link PIM for product data management
• Integrate CRM for customer records
• Connect email and SMS marketing platforms
• Add review and loyalty platforms

Test integrations:

• Order creation and sync to backend systems
• Inventory updates flowing to Shopify
• Customer data synchronization
• Error handling and retry logic
• Webhook reliability under load

Implement redirects:

• Upload redirect map to Shopify or configure server-level redirects
• Test redirect coverage by crawling staging site
• Verify 301 status codes
• Eliminate redirect chains

Phase 6: Launch and monitoring

Final preparation:

• Freeze content changes on Magento
• Run final delta migration for recent orders and customers
• Prepare customer communication about password resets
• Brief customer service team on new admin
• Schedule DNS cutover window

Launch sequence:

1. Make final Shopify store review
2. Update DNS to point domain to Shopify
3. Monitor DNS propagation (24-48 hours)
4. Verify SSL certificate activation
5. Test live checkout and payment processing
6. Confirm integration data flow

Post-launch monitoring (first 30 days):

• Track crawl errors and 404s in Search Console
• Monitor organic traffic and conversion rates
• Review checkout completion and cart abandonment
• Check integration data accuracy
• Verify email notifications
• Respond to customer service issues
• Fill redirect gaps as discovered

Migration risks and mitigation

Data loss or corruption

Risk: Incomplete data export, failed imports, or broken relationships between products, customers, and orders.

Mitigation:

• Export and validate all data before importing
• Test imports on staging environment first
• Reconcile record counts between Magento and Shopify
• Keep Magento database accessible for reference
• Document data transformation logic

SEO traffic loss

Risk: Missing or incorrect redirects cause 404 errors, losing search rankings and organic traffic.

Mitigation:

• Build comprehensive redirect map during planning
• Test redirects on staging before launch
• Monitor Search Console daily post-launch
• Add missing redirects immediately when gaps surface
• Track organic traffic against baseline

Integration failures

Risk: Orders, inventory, or customer data fails to sync between Shopify and backend systems.

Mitigation:

• Test integrations thoroughly pre-launch
• Implement error handling and retry logic
• Monitor integration queues and logs
• Have rollback plan for critical integration failures
• Keep Magento integrations functional during transition

Checkout and payment issues

Risk: Payment processing failures, tax miscalculation, or shipping errors lose revenue immediately.

Mitigation:

• Test all payment methods on staging
• Validate tax calculation across jurisdictions
• Verify shipping rates for various scenarios
• Test discount and gift card application
• Complete test orders end-to-end before launch

Customer confusion

Risk: Password resets, changed URLs, or different interfaces frustrate existing customers.

Mitigation:

• Communicate migration timeline and changes
• Provide clear password reset instructions
• Redirect all old URLs correctly
• Train customer service on new platform
• Monitor support tickets for migration-related issues

What drives migration timeline

Migration timeline depends on several factors:

Catalog complexity:

• Number of products and SKUs
• Variant structures requiring transformation
• Custom attributes mapping to metafields
• Product relationships and bundling logic

Integration scope:

• ERP systems for orders, inventory, and financial sync
• OMS for fulfillment routing
• PIM for product centralization
• CRM for customer data
• Marketing automation platforms

Custom functionality:

• Checkout customizations and validation
• B2B pricing and approval workflows
• Custom product features (configurators, visualizers)
• Unique merchandising requirements

Content and design:

• Number of CMS pages requiring rebuild
• Blog content migration
• Custom theme development vs adaptation
• Mobile and accessibility requirements

Data quality:

• Cleanup needed for inconsistent records
• Deduplication of customers and products
• Historical data validation

Small catalogs with standard requirements take less time than enterprise projects with extensive integrations, custom B2B functionality, and multi-brand operations.

Real migration examples

Like-for-like Craft Commerce to Shopify migration

Fjordfiesta manufactures Norwegian furniture including chairs, sofas, and tables. With Craft Commerce being phased out, they needed migration to a supported platform without disrupting their business.

We migrated Fjordfiesta like-for-like to headless Shopify with Sanity CMS. The migration preserved their design and content while transitioning the commerce foundation. Most of their sales come from B2B relationships, with separate B2B buying journeys planned for future development.

Read the Fjordfiesta case study

B2B migration with multi-store portal

Abate’s wholesale customers order across four Shopify stores and warehouses. We built a B2B portal connecting all four stores in one ordering experience.

B2B average order value increased 33% and sales increased 58% in the first year after migration.

Read the Abate case study

Frequently asked questions

How long does a Magento to Shopify migration take?

Migration timeline depends on catalog size and complexity, number of integrations, custom functionality requirements, B2B needs, and design changes. Small catalogs with standard requirements take less time than enterprise projects with extensive ERP/OMS integration, custom B2B functionality, and multi-brand operations. Timeline factors include data quality, content volume, and custom feature rebuilds.

Will I lose search rankings migrating from Magento to Shopify?

Not if planned correctly. A complete 301 redirect map from every Magento URL to its Shopify equivalent preserves search rankings and backlink equity. Monitor Google Search Console through migration, fill redirect gaps immediately, and track organic traffic against baseline. Poorly executed redirects cause ranking loss.

Can I migrate from Magento 1, Magento 2, or Adobe Commerce?

Yes. The migration process accommodates all versions with differences in risk and complexity. Magento 1 often carries more technical debt from older extensions and custom modifications. Adobe Commerce includes enterprise features like B2B, personalization, and multi-store operations requiring careful scoping to Shopify Plus equivalents.

What data transfers from Magento to Shopify?

Products, variants, customers, addresses, historical orders, and inventory migrate with transformation. Customer passwords cannot transfer due to encryption differences. Magento extensions, CMS content, and category trees require rebuilding. Custom attributes map to Shopify metafields. Tier pricing and customer group logic rebuilds using Shopify B2B or apps.

Do I need Shopify Plus for Magento migration?

Not always. Shopify Plus provides essential capabilities for many Magento merchants: custom checkout, advanced B2B with unlimited catalogs, multi-store management, and higher API limits. Standard Shopify suits businesses without these requirements. B2B sales requiring advanced features, operating multiple brands, or complex integrations typically justify Shopify Plus.

How do I handle products with many variants?

Shopify’s product model differs from Magento’s approach to configurable products. Complex variant structures may require splitting into multiple products, restructuring option hierarchies, or using metafield-based product selection with custom logic. Evaluate whether all variant combinations genuinely serve customers or exist due to previous platform flexibility.

Can you migrate my Magento store to Shopify?

We plan and execute migrations from various platforms with data transfer, system re-integration, and SEO preservation. We document what migrates, what rebuilds, and realistic timelines during discovery based on your specific requirements.

What happens to my Magento extensions?

Magento extensions do not run on Shopify. Each extension’s business requirement maps to Shopify apps, native features, or custom development. Many Magento extensions exist to work around platform limitations rather than serve genuine needs. Shopify’s built-in capabilities often replace what previously required extensions. Audit each extension’s purpose before assuming rebuild necessity.

How do I preserve my SEO investment?

Build a complete URL redirect map during planning. Every indexed product, category, CMS page, and blog URL requires a 301 redirect to its Shopify equivalent. Test redirects on staging before launch. Monitor Google Search Console for crawl errors. Add missing redirects immediately when gaps surface. Maintain meta titles and descriptions from high-ranking pages.

What about my integrations with ERP, OMS, and other systems?

Integrations rebuild using Shopify webhooks, REST Admin API, or GraphQL Admin API. Common integrations include ERP systems (NetSuite, SAP, Microsoft Dynamics), order management systems, product information management, CRM, marketing automation, and loyalty platforms. Plan integration rebuild during migration rather than post-launch to avoid operational disruption.

What would you like to migrate?

Book a 30-minute discovery call to discuss your Magento store, migration requirements, and realistic timeline. We’ll evaluate whether we’re the right team to help.

Book a call