01Why more stores are leaving Magento
Magento, now Magento Open Source and Adobe Commerce, is a powerful platform, but it needs servers, updates and ongoing development. Adobe gives each 2.4.x release three years of standard support from general availability: standard support for 2.4.6 ended on 11 August 2026 and for 2.4.7 it ends on 31 May 2027, according to its lifecycle policy. Every major upgrade is a small project. Many mid-sized stores prefer a hosted platform such as Shopify and spend that budget on the business instead.
The decision is not automatic. If the store relies on very specific logic (complex B2B pricing, configurators, several stores with different rules), the first step is checking how it fits in Shopify. That comparison is part of the diagnosis.
02Where SEO gets lost in a migration
Rankings are rarely lost because of the platform change itself. They are lost because of what breaks along the way:
- Old URLs returning 404 because nobody redirected them.
- Mass redirects to the homepage or a generic category, which Google may treat as soft 404s (not-found pages).
- Titles, meta descriptions and category copy that were never migrated.
- Images without alt text, or renamed with meaningless file names.
- A noindex tag or a staging robots.txt left active after launch.
- Changing platform, domain, design and category structure at once, with no way of telling what caused a drop.
Google sums it up in its site move guide: prepare a map of old and new URLs, redirect with 301s, update sitemaps and watch Search Console. It also notes that permanent redirects do not lose PageRank and that fluctuations for a few weeks are normal. The general method is in the ecommerce migration SEO checklist.
03URL inventory and the 301 redirect map
In Magento, product and category URLs are set in the catalogue configuration: they can carry a .html suffix and, depending on the settings, the category path. Magento also keeps old URL rewrites in its own table. In Shopify the structure is fixed: products live under /products/, collections under /collections/ and pages under /pages/. That is why almost no URL matches.
The inventory gathers every URL that matters: those in the current sitemap, those with clicks or impressions in Search Console, those with external links and those used in live campaigns. Each one is mapped to its exact equivalent:
| Magento | Shopify | Note |
|---|---|---|
| /product-name.html | /products/product-name | Product to product, never to the category |
| /category/subcategory.html | /collections/subcategory | Check whether the hierarchy is flattened |
| CMS page | /pages/… | Policies, contact, about |
| Blog post (extension) | /blogs/…/… | Keep date and author where possible |
| Filters and parameters | Equivalent collection or filter | Only URLs with real traffic |
Shopify lets you create URL redirects in the admin and import them by CSV, and recommends setting them up before the domain is transferred. Discontinued products go to their replacement or to the closest collection, never to the homepage. The whole map is reviewed before the switch.
04Catalogue, variants and attributes
Magento works with simple, configurable, grouped and bundle products, and with attribute sets. Shopify works with products, options and variants, plus metafields for extra data. A Magento configurable product usually becomes a product with variants, but not always: there are limits on options and variants per product, so check Shopify’s current documentation before designing the catalogue.
For each product type, the target structure is decided and tested with a sample before the full catalogue is imported. SEO titles, meta descriptions, category copy and image alt text are migrated too.
05Customers, orders and passwords
Shopify recommends importing products first, then customers, then historical orders, so each order is linked to its customer and products. Historical orders are migrated with apps or the API, not with the customer CSV.
Passwords cannot be migrated: Shopify says so in its customer import help. After the switch, customers receive an invitation to activate their account. A clear notice is prepared, by email and on the store itself, so nobody thinks their account is gone.
06Extensions, integrations and what does not carry over
A Magento installation collects extensions over the years, and many are no longer used. I list all of them and note the real job each one does in the store: whether a Shopify app covers it, whether it needs custom development, or whether the store can do without it. The ERP, logistics, invoicing, taxes per country, payment gateways and carriers go through the same filter. That list is signed off in writing before work starts, so launch day brings no surprises.
07Rehearsal, launch and Search Console
Before the switch, the new store is rehearsed: test orders, payments, transactional emails, taxes, shipping and a sample of redirects. On launch day the domain is connected, all redirects go live, any staging block is removed and the new sitemap is submitted.
Afterwards, Search Console is checked for crawl errors, not-found pages and sitemap indexing. Any 404 that appears is fixed with a new redirect. If the source store is PrestaShop or WooCommerce, the details change; see the guides on PrestaShop to Shopify migration and WooCommerce to Shopify migration. The whole process, from inventory to post-launch follow-up, is described in my web and ecommerce migrations service.