Production recovery

Stuck with AI another vendor could not ship?

About a third of our AI engagements start exactly there.

Recover the build →
Case studies Book a 30-minute discovery call

Magento to Shopify migration: data, redirects and cutover

A Magento to Shopify migration needs a feasibility decision before a launch plan. Test the catalog and checkout requirements, map retained data and behavior, then rehearse imports, redirects and customer journeys. Use the audit to estimate implementation and ongoing costs, with named owners for search monitoring, reconciliation and cutover acceptance. Platform limits and support dates need to be confirmed for the actual plan and installed release.

Kanika Mathur
By Kanika Mathur, Service Delivery Lead
Reviewed by Arjun SareenPublished Sep 30, 2026Updated Nov 16, 202613 min read
Ecommerce
A laptop showing a blurred grid of product photos on a dark desk beside small shipping boxes, a white label printer, a lamp and a printed sheet with a hand-drawn tree of empty boxes, no people
Key takeaways

The short version

  • Resolve feasibility first. Test the catalog, checkout and integration behavior before committing dates.
  • Reconcile data and relationships. Sample difficult records and rejected cases, not only total counts.
  • Map relevant destinations. Google recommends direct permanent redirects and minimizing chains; search outcomes still need monitoring.
  • Rehearse the change. Define data updates, cutover authority, recovery and evidence for acceptance.
  • Quote the audited scope. Separate platform terms, implementation, tooling and ongoing operation before comparing costs.

Should you migrate? A decision checklist

Plan a Magento to Shopify migration when the operating work you want to change can be replaced without losing essential catalog, checkout or integration behavior. Compare the cost and responsibility of maintaining the current store with the proposed platform and implementation. Resolve critical compatibility questions before selecting a launch date or assuming a migration will reduce operating cost.

Adobe's Commerce lifecycle policy provides a three-year standard support window from general availability.10 Check the current version-specific table and your support arrangement when assessing urgency. A general window does not establish the exact deadline for your installed release, runtime or extensions.

Two Shopify constraints deserve early investigation. The October 2025 changelog sets a limit of 2,048 variants per product and warns about older product APIs.7 Checkout UI extensions at the information, shipping and payment steps require Shopify Plus.8 Neither statement proves that the rest of your catalog or checkout is compatible; test the actual requirements and app support.

If the platform choice remains open, use the commerce platform comparison to examine hosting, flexibility and ownership. Keep the feasibility record specific enough that the business can see which retained behavior drives the implementation and ongoing charges.

Direct
Map old URLs to relevant final destinations and minimize redirect chains.
Google Search Central
3 years
Adobe Commerce standard-support window from general availability; verify the actual release table.
Adobe lifecycle policy
2,048
Shopify variants per product under the October 2025 changelog; test app compatibility.
Shopify developer changelog
Decision matrix: signals for moving, and signals that need design work first (Adobe, Shopify)
SignalPoints toward ShopifyNeeds design work first
Support statusA lifecycle review identifies work you want to replaceConfirm the installed release and current support arrangement
OperationsThe proposed plan reduces responsibilities you no longer wantIdentify who owns the tasks that remain
CatalogRepresentative product structures pass target testsResolve incompatible option and data models
CheckoutThe required interactions have a supported implementationConfirm plan-specific extension access and custom work
Regions and storesThe required regional operation is demonstratedVerify the current plan and organization constraints
URLsThe audited paths have verified relevant destinationsConfirm current redirect behavior and capacity
Migration feasibility: evidence before commitment
Qualitative review stages for six audit areas. Equal cells are tasks, not release dates or support durations.
Migration feasibility evidence matrixSix audit areas are checked through inspection, decision and verification. No version-specific lifecycle dates are plotted.SupportInspectDecideVerifyCatalogInspectDecideVerifyCheckoutInspectDecideVerifyDataInspectDecideVerifyURLsInspectDecideVerifyIntegrationsInspectDecideVerify
Feasibility evidence to collect before selecting dates
AreaInspectDecideVerifyOwner
SupportCurrent version and lifecycle tableMaintain or replatformAccepted support planPlatform owner
CatalogDifficult product examplesTarget data modelImport and display testsCatalog owner
CheckoutRequired interactionsSupported plan and approachRepresentative transactionsCommerce owner
DataEntities and identifiersConversion and history scopeReconciliation evidenceData owner
URLsLive paths and rewritesRelevant destinationsRedirect resultsSearch owner
IntegrationsData flows and failuresRetain or replaceEnd-to-end behaviorSystem owners
Use the feasibility record to assign evidence, decisions and verification. Confirm actual installed-release support dates against the current Adobe lifecycle table.

The Magento to Shopify migration checklist at a glance

Use the Magento to Shopify migration checklist to connect the audit, store configuration, imports, feature replacement, redirects, search checks, testing and cutover. Give each phase an owner and evidence of completion. Some work can overlap after its dependencies are settled; the list is a planning structure, rather than a guarantee that a fixed sequence fits every store.

Shopify's migration checklist covers data, payments, taxes, testing, domains and SEO.1 Translate that scope into your own acceptance record, including the exceptions and integrations your store uses. Download the migration checklist as a working tracker and add local owners, dependencies and evidence links.

Migration tracker: work and acceptance evidence
PhaseWhat you doDone when
1. AuditRecord data, behavior, URLs and dependenciesEach retained item has an owner and target
2. Store setupConfirm plan, settings and operating assumptionsConfiguration is reviewed for the chosen scope
3. Data importRehearse entity conversion and relationshipsCounts, sampled records and exceptions are reconciled
4. Theme and appsImplement retained behavior and custom fieldsRepresentative customer and operational cases pass
5. RedirectsMap relevant destinations and test importsResponse behavior and final targets are verified
6. SEO checksReview links, page purpose and indexing settingsImportant pages pass the agreed search review
7. TestingExercise transactions, accounts and integrationsFailures and unresolved limitations have decisions
8. Cutover and monitorApply the rehearsed change and response planThe authorized owner accepts operating evidence

Pre-migration audit: what to inventory first

Inventory the behavior and records the new store must preserve: catalog structure, attributes, customer journeys, historical data, URLs, extensions and integrations. Capture the current operating and search baseline before making changes. The audit should identify a destination and a verification method for each retained item, including features that appear only in exceptional transactions.

  • Catalog: inspect the largest option combinations and test them against the target model. Shopify's limit is 2,048 variants per product, and compatibility with existing app APIs still requires checking.7 Record any product that needs a different design.
  • Custom attributes: list the fields, their permitted values and where the storefront or another system uses them. Define the target representation and test display as well as import.
  • Customer and order records: define the history needed for service, reporting and account access. Confirm the export and import paths for the chosen tool rather than assuming every entity moves through the same CSV.
  • URLs: include product, category and content paths along with existing rewrites. Adobe documents product URL rewrites and store-view-specific redirects.11 Inspect your actual records instead of assuming every product uses the same suffix or category pattern.
  • Extensions: describe the business behavior each module supplies. Record whether to retain, replace, redesign or retire it, with approval from its business owner.
  • Integrations: identify each system, data direction, identifier and failure procedure. Include manual exports and scheduled jobs that may be missing from an architecture diagram.
  • Data quality: validate representative records against the target schema and the chosen import method. Keep rejected rows, correction rules and rerun behavior visible.
  • Baseline: retain important landing pages, transaction measures, customer-service issues and operating costs. Agree which signals will trigger investigation during launch.

If the audit reveals a catalog or checkout incompatibility, resolve that design before committing the rest of the schedule. A migration estimate should explain which assumptions depend on a prototype or supplier response.

Data migration: products, customers and orders

Define an entity map and rehearse the imports before moving production data. Identify how products, customers, orders, content and custom fields relate. Use products, then customers, then historical orders as the starting import sequence so order lines and customer references can resolve to records already present.112 Rehearse that sequence with the selected implementation. Validate representative records and rejected cases as well as counts. A successful file upload does not establish that the migrated store behaves correctly.

Matrixify documents its own Magento CSV conversion and Shopify import workflow.12 If you use it, follow the current instructions for the selected entity and test store. Treat it as tool documentation rather than an independent import-speed benchmark or an endorsement that every custom field will move unchanged.

Entity mapping decisions to validate with the selected method
MagentoShopifyHow it movesWatch for
ProductsTarget product and variant modelChosen import method, tested on representative recordsOption and identifier compatibility
CategoriesTarget collection and navigation designConfigured conversion or implementationRelevant destinations and customer journeys
Custom attributesExplicit target fields and display behaviorMapped conversion with sampled validationData types and theme use
CustomersChosen customer-account modelConfirmed import and access processActivation, identity and account communication
OrdersRequired history and record relationshipsVerified tool or API implementationIdentifiers, line items and reconciliation
Pages and postsTarget content and publishing structureMapped content migration or manual workAssets, metadata and URLs
  • Prepare configuration: confirm the store settings and target field meanings before loading records. Record the source and target assumptions used in conversion.
  • Dry-run representative data: include difficult product structures, missing fields and historical records. Inspect the storefront and operational result, not only the import report.
  • Reconcile relationships: test the identifiers used to connect products, customers and order lines. Preserve an inspectable map when an identifier changes.
  • Measure the import: record duration, errors and rerun behavior on your own dataset. Build the cutover allowance from that evidence using a representative rehearsal and the observed error rate.
  • Plan account communication: confirm the password and activation behavior for the chosen account setup. Test the customer message and access journey before contacting the full migrated audience.

URL mapping and 301 redirects

Map each retained old URL to its relevant final destination and test the permanent redirect behavior before traffic switches. Google recommends URL mapping, direct permanent redirects and minimizing chains for site moves.9 That guidance supports a careful migration process, not a guarantee that rankings or traffic will remain unchanged.

Build the map from the live URL inventory and existing rewrite records. Adobe supports product rewrites and store-view-specific redirects, so review the actual paths in each relevant view.11 Decide explicitly what happens to retired content rather than sending unrelated pages to a convenient common destination.

A laptop showing a blurred two-column spreadsheet of short rows on a wooden desk beside a printed sheet of blurred lines with a pencil, a black mug and a plain cardboard box under a small lamp, no people
An inspectable source-to-destination map supports redirect testing and later investigation.
Illustrative redirect decisions; confirm actual target paths and import columns
Redirect fromRedirect toPage typeNote
/gear/bags/overnight-duffle.html/products/overnight-duffleProduct with category pathIllustrative mapping; verify the relevant final page
/overnight-duffle.html/products/overnight-duffleProduct, bare URLIllustrative mapping; verify the relevant final page
/gear/bags.html/collections/bagsCategoryIllustrative mapping; verify the relevant final page
/about-us/pages/about-usCMS pageIllustrative mapping; verify the relevant final page
/discontinued-tent.html/collections/tentsRetired productIllustrative mapping; verify the relevant final page

Download the redirect-mapping worksheet to record source and destination decisions. The sample paths are illustrative. Verify each actual target and the current import format required by the selected tool before loading the map; keep explanatory columns in the working file rather than assuming they belong in an import.

  • Use the final destination: minimize chains and check that the page reached is the intended relevant replacement.9
  • Review retired pages: record whether a relevant replacement exists and test the chosen response behavior.
  • Inspect platform rules: verify current handling of reserved routes, query strings and existing pages for the actual implementation. Do not assume every Magento path behaves identically after import.
  • Validate the file: check duplicate sources, loops and mismatched destinations before a test import, then verify the resulting response.
  • Confirm capacity: check the target plan's current redirect and implementation limits against the audited inventory. A limit found during the audit is a design decision to resolve.

SEO preservation: will you lose rankings?

You can reduce avoidable search disruption by preserving relevant content and destination mappings, testing redirects and checking the new site's crawl and indexing settings. Search fluctuations can still occur during a move, and rankings and recovery time cannot be guaranteed.9 Establish an investigation process for important pages before launch.

  • Preserve the comparison: record titles, descriptions, important copy and page purpose before deciding what to change. If content changes with the platform, document the change so later analysis has context.
  • Review internal destinations: update navigation, content and other maintained links to the intended new pages. Use the approved mapping to identify inconsistent destinations.
  • Inspect indexing controls: check canonical destinations, temporary restrictions and public access as part of release acceptance. Test representative URLs and the important templates.
  • Review discovery: confirm the target site's sitemap and submission process for the chosen configuration. Keep an owner for investigating discovery and indexing problems.
  • Test the mapping at scale: record response behavior and final destinations across the inventory. Investigate broken paths, loops and unintended intermediate redirects.

Compare important landing pages and business outcomes with the baseline, accounting for changes in season, campaigns and content. A decline needs investigation rather than an assumed universal waiting period. Start with the affected mapping, accessibility to crawlers, page purpose and implementation evidence.

Apps, integrations and checkout

Recreate the business behavior of Magento extensions through a tested Shopify implementation, rather than treating installed modules as portable features. Assess native capability, an existing app, custom work or retirement for each requirement. Review checkout and integrations early because their access, plan and operational constraints can determine the rest of the migration scope.

For checkout UI extensions at the information, shipping and payment steps, Shopify Plus is required.8 Do not generalize that restriction to every checkout-related feature. Write down the exact interaction required and confirm the supported implementation before selecting the plan and quoting the work.

  • Native capability: demonstrate the required behavior with representative products and customer cases before marking the feature replaced.
  • Existing app: review support, data access, operating charges and compatibility. Shopify's variant changelog specifically warns about older product APIs, so include high-variant products in the test.7
  • Custom implementation: define the supported extension point, owner and maintenance plan. Verify the target plan permits the approach rather than inferring support from the feature name.
  • Retirement: obtain business approval and identify the effect on customer journeys, operations and data already stored.

For each integration, test identifiers, updates, duplicate events, failures and reconciliation. Verify the actual API and app constraints for the selected implementation. The store optimization guide develops the related application and performance decisions. A successful import does not prove that the ongoing order or inventory flow is correct.

Testing and launch

Rehearse the data movement and customer journeys on a test store, then approve a cutover plan with clear responsibilities and recovery conditions. Shopify's migration guidance includes testing, payments, taxes and domain work.1 Define how changes made during the migration will reach the target and who decides whether the store is ready to accept traffic.

  • Exercise representative purchases, payment outcomes, shipping and tax cases, including the failure and refund paths the business supports.
  • Test the selected customer-account flow and required historical records with representative migrated accounts.
  • Check the URL inventory against approved destinations and investigate loops, broken paths and unexpected chains.
  • Review mobile templates, custom fields, variant selection and unavailable-product behavior on relevant devices.
  • Verify that orders and stock changes reach the intended external systems, with reconciliation and retry behavior inspected.

Choose the data-change strategy through rehearsal. A store pause and a bulk transfer followed by a controlled delta have different operating implications. Document which transactions and catalog changes can occur during each stage, how they are captured and how duplicates are prevented. Do not call a strategy downtime-free without evidence for the complete customer and operational journey.

Record launch authority, domain changes, storefront access checks, redirect verification and the monitoring owner. Define the symptoms that require a correction, a pause or a recovery action. Preserve the source data and reconciliation evidence needed to investigate discrepancies, under the appropriate access and retention arrangements.

Timeline and cost

Estimate the migration schedule and cost from the audit, feasibility decisions and rehearsed data movement. Separate platform charges from implementation, apps, ongoing operation and any period of parallel running. Shopify's Plus pricing page defines plan charges and commercial conditions; use the current terms for the selected plan rather than an unsupported universal price or migration duration.6

Include data cleanup, theme work, checkout design, redirect mapping, integration testing and approval in the estimate. The website scheduling guide explains the dependency-based approach. Your cutover window needs a rehearsal using the actual data and method; measure it with representative records and a realistic rehearsal.

Schedule inputs and the evidence needed to estimate them
PhaseWhat drives durationEstimation evidence
Audit and mappingInventory completeness and unresolved decisionsEstimate against actual records and owners
Theme and appsRetained behavior and supported implementationPrototype uncertain features
Data importVolumes, conversion errors and rerun behaviorTime a representative rehearsal
CutoverChange capture and recovery approachRehearse and agree acceptance
Search transitionDiscovery, mappings and page changesMonitor; do not promise recovery time
Redirect upkeepContinuing use of old URLs and operating requirementsAssign a maintenance and review owner
Cost lines to quote against the audited scope
Cost lineEvidence to obtainWhat moves it
Platform subscriptionCurrent plan quote and commercial termsCurrency, contract term and applicable conditions
Migration servicesSupplier scope and fee basisData, custom behavior and acceptance work
Import toolingSelected app or implementation quoteEntities, volumes and required operations
Theme, apps and integrationsDefined build and ongoing-charge scopeRetained behavior, checkout and data flows
Parallel operationActual current and target operating costsRehearsal, change capture and recovery needs

Ask for each cost's billing basis, currency, contract term and included work. A platform migration charge, if absent, does not make third-party migration labor free. Include ongoing app charges, maintenance and operational ownership when comparing the proposed store with the current one.

Use the audit to decide whether the work supports a fixed scope or time-based arrangement. Bring the catalog sample, extension list, data volumes and integration map to an ecommerce development discussion. Describe the decision through the contact page, including who can approve the cutover and accept the result.

Frequently asked

Store migration questions

What should a Magento to Shopify migration checklist include?
Include feasibility, the audit, target settings, entity mapping, import rehearsal, retained features, redirects, search checks, testing and cutover. Give each workstream an owner and acceptance evidence. Capture the integrations and exceptional transactions your store actually uses. The sequence is a planning structure; overlap work only where the dependencies are settled and the responsible owners can verify the result.
How do we know whether the catalog fits Shopify?
Test representative difficult products, option combinations, attributes and storefront behavior. Shopify's October 2025 changelog specifies 2,048 variants per product and warns about older product APIs, so app compatibility still requires checking. Define the target data model and resolve exceptions before estimating the rest of the migration. A product count alone cannot establish catalog or operational compatibility.
Does checkout customization always require Shopify Plus?
Checkout UI extensions at the information, shipping and payment steps require Shopify Plus. Do not extend that statement to every checkout-related capability. Describe the exact interaction the business needs, confirm the supported implementation and plan, then test representative transactions. Include the chosen extension approach, operating charges and maintenance responsibility in the scope.
Will migration preserve our search rankings?
There is no guarantee of unchanged rankings or a fixed recovery time. Google recommends URL mapping, direct permanent redirects and minimizing chains, and search fluctuations can occur during a move. Preserve an inspectable baseline, test relevant destinations and review the target site's search settings. Monitor important landing pages and business outcomes with an owner who can investigate discrepancies.
How should we move customers and historical orders?
Define the history and customer-account behavior required, then verify the supported method for each entity in the chosen implementation. Rehearse representative records and confirm relationships, identifiers, rejected rows and rerun behavior. Test account access and customer communication separately from the file import. Matrixify documents its own conversion workflow, but that does not establish that every custom record moves unchanged or within a standard duration.
How long and how much will the migration take?
Estimate from the audited data, retained behavior, integration work, unresolved decisions and representative rehearsals. Separate platform terms from implementation, tooling, parallel operation and continuing charges. Confirm currency, contract term and inclusions for the actual proposal. A vendor target or another store's import speed cannot establish your cutover window, and an absent platform migration fee does not make supplier labor free.
What evidence should approve the cutover?
Require the agreed transaction, account, data, redirect and integration checks, plus a plan for changes that occur during migration. Identify who can accept unresolved limitations, authorize the domain change and trigger recovery. Preserve reconciliation evidence and source records under appropriate controls. The release decision should be based on the actual store behavior, with monitoring and response ownership assigned before traffic switches.
Kanika Mathur

Kanika Mathur

Author · Service Delivery Lead, Resourcifi

Kanika Mathur is Service Delivery Lead at Resourcifi. She leads the engineering pods that scope, build and run client software, from mobile apps to AI systems, and she reviews the process and figures in our engineering guides for accuracy.

Resourcifi on LinkedIn →
Arjun Sareen

Arjun Sareen

Reviewer · Head of Business Development, Resourcifi

Arjun Sareen is Head of Business Development at Resourcifi. He scopes builds with founders and product leaders, matches each project with the right team model, and hears the same buying questions every week, which is what he writes about.

Resourcifi on LinkedIn →

Like this? Get more from Resourcifi in Google Search.

Sources

  1. help.shopify.com, Shopify Help Center | Migrate to Shopify. Shopify's migration checklist covers data, payments, taxes, testing, domains and SEO.
  2. shopify.com, Shopify Pricing: Find the Right Plan for Your Business - Shopify. Shopify's Plus pricing page defines plan charges and commercial conditions.
  3. shopify.dev, The product variant limit is now 2048 for all merchants - Shopify developer changelog. Shopify's October 2025 changelog raises the product variant limit and warns about older product APIs.
  4. shopify.dev, Checkout UI extensions. Checkout UI extensions at information, shipping and payment steps require Shopify Plus.
  5. developers.google.com, Site Moves and Migrations | Google Search Central | Documentation | Google for Developers. Google recommends direct permanent redirects, mapping URLs and minimizing redirect chains for site moves.
  6. experienceleague.adobe.com, Software lifecycle policy | Adobe Commerce. Adobe's Commerce lifecycle policy provides a three-year standard support window from general availability.
  7. experienceleague.adobe.com, Product URL rewrites | Adobe Commerce. Adobe Commerce supports product URL rewrites and store-view-specific redirects.
  8. matrixify.app, Migrate from Magento to Shopify - Matrixify App. Matrixify documents its own Magento CSV conversion and Shopify import workflow.
Keep reading
Related guides worth your time
All Engineering insights →
Backend Frameworks Comparison Web & software Backend Frameworks Comparison Backend frameworks compared for 2026: Node, Django, Spring, Laravel, Go and more, by performance, ecosystem and use case... Read guide → Django vs Flask: choosing a Python web framework Web & software Django vs Flask: choosing a Python web framework Django vs Flask: compare the two leading Python web frameworks on structure, scalability, ORM and learning curve to see w... Read guide → Engineering bottlenecks: trace the work and test one change Web & software Engineering bottlenecks: trace the work and test one change Find engineering bottlenecks through work-item evidence, queue analysis and a bounded experiment. Review waiting, changed... Read guide → Healthcare technology trends Web & software Healthcare technology trends Healthcare technology trends that matter: AI in clinical workflows, FHIR interoperability, telehealth, wearables and IoMT... Read guide → Laravel Core Concepts Web & software Laravel Core Concepts What is Laravel? A PHP web framework with routing, Eloquent ORM, Blade, and queues built in. The core concepts explained... Read guide → Next.js vs React Web & software Next.js vs React Next.js is a framework built on React, not a replacement. Compare server rendering, routing, and when to use each for you... Read guide → 25 mobile app ideas worth building, with costs and revenue models Mobile & apps 25 mobile app ideas worth building, with costs and revenue models 25 mobile app ideas across AI, health, fintech and commerce, with the core features, a sourced build cost range and the m... Read guide → AI in UX Design: How AI Is Changing User Experience Product & UX AI in UX Design: How AI Is Changing User Experience How AI is changing UX design: personalization, predictive flows, generative UI and faster research, with real app example... Read guide → App development tools Mobile & apps App development tools The app development tools you actually need, by category: IDEs, frameworks, backend and BaaS, testing, CI/CD, and design... Read guide →
Bring the catalog, extensions, URLs and integration map

Which store requirements must survive the move?