How to Migrate from Magento to Shopify Plus

ReplatformingUpdated 12 min read

In short: A Magento to Shopify Plus migration runs in six phases: audit what exists, map Magento data and workflows to Shopify, build integrations in parallel, migrate and validate data in the right order, protect SEO with redirects, then run a controlled cutover. Decide what to migrate, rebuild, replace or retire before development starts.

A Magento to Shopify Plus migration is not a CSV upload. For a serious DTC or B2B brand, it is a business-critical rebuild involving product data, customer accounts, custom pricing, ERP connections, SEO, checkout behavior and the processes your operations team uses every day.

Get the migration right and you leave Magento with a simpler operating model and a store your team can actually manage. Get it wrong and you create months of cleanup, lost organic traffic, broken integrations and frustrated customers.

Best for: Mid-market and enterprise DTC or B2B brands moving from Magento or Adobe Commerce to Shopify Plus with complex catalogs, configurable products, wholesale pricing, ERP or 3PL integrations, or multi-store requirements.

This guide explains how to plan a Magento to Shopify Plus migration without treating your ecommerce platform like a data-export project. If you are moving from WooCommerce or BigCommerce, or want the general process, start with our Shopify migration guide.

The short answer

A successful Magento to Shopify Plus migration has six phases:

  1. Audit what exists and decide what should not move.
  2. Map Magento data and workflows to Shopify's operating model.
  3. Build the new storefront and integrations in parallel.
  4. Migrate and validate products, customers, orders, content and B2B data.
  5. Protect SEO with redirects, metadata, internal links and launch checks.
  6. Run a controlled cutover, then monitor and fix issues quickly.

The most important decision happens before development starts. You need to determine whether each Magento feature should be migrated, rebuilt differently in Shopify, replaced with an app or native capability, or retired entirely.

Magento, Adobe Commerce and Shopify Plus: what is the difference?

Adobe renamed the paid edition of Magento to Adobe Commerce in 2021. The free edition is still called Magento Open Source, and many teams use "Magento" to mean either one.

The migration decision is usually not about whether Adobe Commerce can support your requirements. It can. The question is whether your team should keep carrying the cost of custom platform maintenance, extension management, upgrade work and developer dependency when Shopify Plus can support the workflows you actually need.

For brands with complex B2B pricing, ERP integrations, configurable catalogs or multi-market requirements, Shopify Plus is not automatically the right answer. The right migration starts by mapping those requirements against Shopify's native capabilities, its B2B features and the integrations needed to close any gaps. That is why an Adobe Commerce to Shopify Plus migration should begin with discovery, not a data export.

For a full platform comparison, see Shopify vs Magento vs BigCommerce, our breakdown of Magento vs Shopify on deployment and admin burden and, for wholesale brands, Shopify Plus vs Magento for B2B.

Why Magento migrations become difficult

Magento often accumulates years of customizations. That can include custom product attributes, extensions, theme logic, customer groups, price rules, CMS blocks, payment customizations, ERP connections and workflows built around the limitations of the original store.

Some of that is essential. Some of it is technical debt. A good migration does not recreate every old decision. It separates the capabilities your business needs from the workarounds your old platform forced you to maintain.

The biggest challenges usually fall into five areas:

  • Product attributes and configurable-product logic
  • Customer groups, tier pricing and B2B workflows
  • ERP, PIM, OMS, 3PL and fulfillment integrations
  • SEO preservation and URL changes
  • Custom extensions and front-end functionality that do not have a direct Shopify equivalent

Shopify's own Magento migration guide makes the same point: heavy tier pricing, customer-group pricing, multi-store setups and custom ERP integrations need deliberate evaluation and mapping, not a one-click migration.

Phase 1: Audit Magento before you decide what moves

Do not start by exporting your database. Start by understanding what is actually valuable. Your first migration deliverable should be a full inventory of data, systems, workflows and pages.

Audit your catalog

Identify:

  • Active products and variants
  • Discontinued SKUs
  • Configurable products
  • Bundles and kits
  • Product attributes
  • Custom options
  • Product images and digital assets
  • Category structures
  • Customer-facing specifications
  • High-revenue and high-margin products
  • Products with poor or incomplete data

Magento attributes rarely map cleanly to Shopify without planning. Some will become Shopify metafields. Some will become product or variant options. Others may need to become separate products, custom data objects or content blocks. This is why catalog mapping should happen before any bulk import.

Audit your customers and orders

Document:

  • Customer groups
  • Account types
  • Tax-exempt customers
  • Credit terms
  • Order history requirements
  • Returns and warranty windows
  • Store credit and gift-card balances
  • Password migration constraints
  • B2B company relationships
  • Customer-specific pricing rules

For historical orders, migrate what your customer-service and finance teams genuinely need. For many businesses, that means at least the order history that falls within the return, exchange, warranty or reporting period you actively use.

Customer passwords do not carry over from Magento in a usable form. Plan account activation emails or password-reset prompts as part of launch, so returning customers are not locked out.

Audit extensions and custom code

Create a feature inventory with four columns:

Magento capabilityBusiness purposeShopify replacementDecision
Custom price logicCustomer-specific pricingShopify B2B catalogs or custom logicRebuild
Product attributesTechnical product detailsShopify metafieldsMigrate
Legacy blog widgetsContent presentationShopify theme sectionsRebuild selectively
Unused extensionNo current business valueNoneRetire

Do not assume every Magento extension needs a Shopify app. Every unnecessary app creates another cost, dependency and potential performance problem.

Phase 2: Design the Shopify Plus operating model

The goal is not to make Shopify behave exactly like Magento. The goal is to create a better operating model for your team. That means agreeing on how products, content, pricing, customers and integrations will work in Shopify before the build begins.

Map Magento attributes to Shopify data

Magento attributes are flexible. Shopify uses a more opinionated data model. That is usually a benefit, but it requires a mapping exercise. For every Magento attribute, decide whether it belongs in:

  • Product title or description
  • Variant option
  • Variant metafield
  • Product metafield
  • Collection rule
  • Metaobject
  • Search filter
  • A custom integration
  • A retired field that no longer serves a purpose

Do not map hundreds of attributes simply because they exist. Map the ones that support product discovery, merchandising, operations, customer decision-making or integration requirements. Clean, structured attributes also help with AI search optimization for Shopify, because AI shopping channels read the same product data.

Plan B2B before build work starts

If you sell wholesale or operate a hybrid DTC and B2B business, B2B requirements cannot be an afterthought.

Shopify B2B supports companies, company locations, catalogs, payment terms and quantity rules. It is now available on the Basic, Grow and Advanced plans as well as Plus, but Plus adds unlimited catalogs, company-specific pricing and more payment options, which most brands migrating complex Magento B2B setups will need. Our guide to Shopify B2B setup decisions covers the plan differences in detail.

Before migration begins, document:

  • How buyers are assigned to companies and locations
  • Who can place orders
  • Which catalog each buyer can access
  • Customer-specific or company-specific pricing
  • Minimum order quantities
  • Payment terms
  • Sales-rep workflows
  • Purchase-order requirements
  • Tax-exempt status
  • ERP ownership of customer and inventory data

B2B buyers sign in through Shopify's current customer accounts, so plan the move to them as part of the build. If you sell subscriptions or use Shopify POS, confirm how those will work with B2B for your setup before you choose an implementation approach.

Decide what owns each piece of data

A migration fails when two systems both believe they own the same data. Create a system-of-record document for:

  • Product data
  • Inventory
  • Pricing
  • Customer accounts
  • Orders
  • Fulfillment status
  • Returns
  • Tax data
  • B2B companies and catalogs
  • Marketing subscriptions

For example, your ERP may remain the source of truth for inventory and fulfillment, while Shopify becomes the source of truth for storefront content, customer-facing product information, checkout and online orders. Every integration should reflect that decision.

Phase 3: Build integrations before cutover week

ERP, PIM, OMS and 3PL integrations need time. They require field mapping, error handling, retry rules, operational ownership and realistic testing. Do not leave them until the end of the project. We cover the sources-of-truth decision in more depth in 10 Shopify moves for migrations, B2B and ERP.

Start with the order lifecycle

Map what happens from the moment a customer places an order. For each order type, document:

  1. Where the order is created.
  2. Which system receives it next.
  3. When inventory is reserved.
  4. When fulfillment is created.
  5. Where shipment information returns.
  6. How cancellation, refund, exchange and partial-fulfillment states are handled.
  7. What happens when a record fails to sync.

Test DTC, B2B, guest checkout, logged-in customer, discount, tax-exempt, partial shipment, cancellation and refund scenarios. If the workflow cannot be tested before launch, it is not ready for launch.

Use connectors carefully

Many brands can use established Shopify connectors rather than paying for custom middleware. That does not mean the work is automatic. A connector still needs configuration, mapping, exception handling and monitoring.

For complex B2B data, custom product structures or unusual order workflows, a custom API-based approach may be more appropriate. The choice should be based on operational reliability, not the lowest initial implementation cost.

Phase 4: Migrate data in the right order

Import order matters because records need to keep their relationships. Shopify recommends importing products before customers, and customers before historical orders, so those links are preserved. A practical sequence is:

  1. Products, variants, images, metafields and pricing
  2. Customers and customer accounts
  3. B2B companies, company locations and catalogs
  4. Historical orders
  5. Content pages, blog posts and supporting assets
  6. Gift cards, store credit or other time-sensitive customer balances

B2B companies come before historical orders so that wholesale orders can attach to the right company and location.

Run multiple migration passes

Do not plan a single final import. Run at least three passes:

  • Test migration: Use a representative sample of products, customers, orders and content to validate mappings.
  • Full rehearsal migration: Import the full dataset into the staging environment and test every critical workflow.
  • Delta migration: Import records created or changed after your final cutover point, such as new customers, new orders, updated inventory or recent product edits.

The goal is to uncover errors before customers do.

Validate samples, not just totals

A row count is not proof that a migration worked. Validate representative examples from each important category:

  • Simple and configurable products
  • High-revenue products
  • Variant-heavy products
  • Products with unusual attributes
  • B2B customers
  • Tax-exempt buyers
  • Recent orders
  • Orders with discounts
  • Orders with partial fulfillment
  • Customers with account history
  • Content pages with organic traffic

If the most complicated records work, the easy ones usually follow.

Phase 5: Protect SEO before launch

A Magento to Shopify migration can hurt organic traffic when URL changes, redirects, metadata, internal links, canonical tags and content are ignored. The solution is not to keep every legacy URL forever. It is to preserve the value of the URLs that matter.

Build a redirect map

Create a redirect map for every valuable legacy URL. Prioritize:

  • Product pages with traffic or backlinks
  • Category pages
  • Blog posts
  • Landing pages
  • Resource pages
  • High-converting paid landing pages
  • Customer-service pages
  • URLs included in external links or campaigns

Magento categories often become Shopify collections, and the URL patterns will change. That is normal, but each old URL needs an intentional destination. Use a 301 redirect when a relevant replacement exists. Do not redirect every removed page to the homepage. That creates a poor user experience and wastes relevance.

Preserve important on-page signals

For pages you are retaining or rebuilding, preserve:

  • Page titles
  • Meta descriptions
  • Heading structure
  • Useful body copy
  • Product specifications
  • Image alt text
  • Internal links
  • Canonical tags
  • Structured data where appropriate

After launch, submit the new XML sitemap and watch Google Search Console closely for crawl errors, indexing issues and unexpected declines on high-value pages. Set expectations internally too: Shopify notes that a temporary traffic dip of 5–10% is common even with perfect redirects, and that the first 14 days after launch are critical.

Phase 6: Test like a customer and an operations team

Before launch week, conduct structured quality assurance. Do not test only the happy path.

Customer-facing tests

Test:

  • Product discovery and filtering
  • Variant selection
  • Add-to-cart behavior
  • Guest checkout
  • Logged-in checkout
  • Discount codes
  • Shipping rates
  • Taxes
  • Payment methods
  • Failed payment scenarios
  • Account creation
  • Password and account-recovery flows
  • Mobile checkout
  • Transactional emails
  • Accessibility basics

B2B tests

Also test:

  • Company account permissions
  • Buyer access to assigned catalogs
  • Customer-specific pricing
  • Payment terms
  • Purchase-order workflows
  • Tax-exempt status
  • Minimum order quantities
  • Sales-rep workflows
  • ERP order sync
  • Inventory visibility
  • Partial fulfillment

Operational tests

Your internal team needs to test:

  • Order management
  • Customer service workflows
  • Refunds and cancellations
  • Fulfillment exceptions
  • Returns
  • Finance and tax reporting
  • Integration failure alerts
  • Content updates
  • Product updates
  • Merchandising workflows

The people who will operate the store after launch should be involved in testing before launch.

Cutover: how to launch without creating chaos

No migration is risk-free. The goal is to reduce risk through preparation, ownership and a clear rollback plan. Your launch plan should include:

  1. A final go or no-go meeting.
  2. A documented owner for every system.
  3. A complete delta-migration plan.
  4. A support schedule for the first 48 to 72 hours.
  5. A rollback decision process.
  6. Monitoring for checkout, orders, integrations, 404s, traffic and payment failures.
  7. A communication plan for staff, customers and partners if needed.

Lower your DNS TTL 24 to 48 hours before the switch so the domain change propagates quickly. At cutover, complete the final data delta, confirm payment settings, point the domain to Shopify, remove password protection and begin real-time monitoring.

Do not schedule a major promotion for the exact day of a platform launch. Give the new store time to stabilize.

A realistic Magento to Shopify Plus timeline

A standard mid-market migration can take roughly 8 to 16 weeks. Complex projects involving ERP integrations, customer-specific B2B pricing, a large or configurable catalog, multiple storefronts or custom functionality can take 14 to 22 weeks or longer. A practical phased timeline for a standard project looks like this:

PhaseTypical focus
Weeks 1–3Discovery, platform audit, data mapping, integration inventory, redirect planning
Weeks 4–8Storefront development, integration work, test migration, content preparation
Weeks 9–12Full rehearsal, QA, user acceptance testing, delta-migration planning, launch preparation
Post-launchMonitoring, fixes, training and optimization

The real variable is not the Shopify theme. It is the quality of your data, the complexity of your integrations and how many business decisions are still unresolved.

When should you use a Magento to Shopify Plus migration agency?

A migration agency is especially valuable when you have:

  • A large or configurable product catalog
  • Complex attribute structures
  • Wholesale or B2B requirements
  • Customer-specific pricing
  • ERP, PIM, OMS or 3PL integrations
  • Multiple Magento stores or international markets
  • Significant SEO equity to protect
  • Custom Magento workflows with unclear ownership
  • A team that needs senior technical leadership from planning through launch

If you are still comparing partners, our shortlist of Shopify Plus agencies for high-volume brands includes the questions to ask any of them.

Kirkby, White Consulting is best for: 7–9 figure DTC and B2B brands migrating from Magento to Shopify Plus with complex catalogs, pricing, wholesale requirements and ERP or 3PL integrations.

Our Shopify migration and development process starts with an audit of the existing store, systems and business rules. Then we decide what to migrate, what to rebuild, what to retire and what needs a different approach in Shopify. For wholesale-heavy stores, that work runs alongside our Shopify B2B development.

The point is not to recreate Magento on Shopify. The point is to build a store your team can run more effectively after launch.

The bottom line

A Magento to Shopify Plus migration is a chance to remove the operational weight your current store has accumulated. It is not a reason to carry every old customization into a new platform.

Start with the business outcomes you need, map the data and integrations that support them, protect your search equity and test the workflows your team and customers actually rely on.

If you are planning a Magento or Adobe Commerce migration with complex B2B, catalog, ERP or fulfillment requirements, start with a free Shopify store audit and a 30-minute scoping call. We will tell you what should move, what should change and whether Shopify Plus is the right fit before you commit to the build.

Frequently asked questions

How long does a Magento to Shopify Plus migration take?
A standard mid-market migration can take roughly 8 to 16 weeks. Complex projects involving ERP integrations, customer-specific B2B pricing, a large or configurable catalog, multiple storefronts or custom functionality can take 14 to 22 weeks or longer. The right timeline depends on data quality, integration complexity, content volume and stakeholder availability.
Can Magento product attributes be moved to Shopify?
Yes, but Magento attributes do not map one-to-one to Shopify. They often need to become Shopify metafields, variant options, product taxonomy fields or separate data structures. Agree the mapping before migration and validate it with representative product records.
Will a Magento to Shopify Plus migration hurt SEO?
It can if URLs, metadata, internal links, content, canonical tags and redirects are not handled carefully. A proper migration includes a complete redirect map for valuable legacy URLs, preserves high-performing content, validates the XML sitemap and monitors Google Search Console after launch. A temporary dip is common even with good redirects.
Can Shopify Plus support B2B pricing and wholesale workflows?
Yes. Shopify B2B supports companies, company locations, catalogs, payment terms and quantity rules, and it is available on the Basic, Grow and Advanced plans as well as Plus. Plus adds unlimited catalogs, company-specific pricing and more payment options. Before migrating, confirm how your workflows fit Shopify's customer accounts and how subscriptions or POS will work with B2B for your setup.
What data should be migrated from Magento to Shopify?
Most migrations include active products, variants, images, customers, recent order history, pages, blog content, gift cards where applicable, redirects, and B2B company or catalog data. Themes, extensions, custom code, customer passwords and stored payment credentials do not transfer through a standard export and must be rebuilt, replaced, reset or migrated through a specialized process.
Is Shopify Plus better than Adobe Commerce for B2B ecommerce?
It depends on your requirements. Adobe Commerce offers deep flexibility for heavily customized commerce operations, while Shopify Plus reduces platform maintenance and provides native B2B capabilities such as companies, catalogs, customer-specific pricing, payment terms and quantity rules. The right choice depends on whether Shopify Plus can support your catalog, integration, pricing and operational needs without recreating unnecessary Magento complexity.

Sources

Spotted something wrong or out of date? Email hello@kirkbyconsulting.com with the details and we will correct it.