Support for Magento Open Source 2.4.6 ends on 11 August 2026. This guide covers what that means, how upgrading compares with migrating to Shopify Plus, and exactly what breaks when Magento data meets Shopify's model — written by the team that runs these migrations.
Magento 2 support depends on your version and edition. Support for the 2.4.6 release line ended on 11 August 2026. Version 2.4.7 ends 9 April 2027, 2.4.8 ends 11 April 2028, and 2.4.9, released 12 May 2026, runs to 12 May 2029. Support for 2.4.5 ended 9 August 2025 and 2.4.4 ended 12 April 2025.
| Release line | Released | Support ends | Status |
|---|---|---|---|
| 2.4.9 | 12 May 2026 | 12 May 2029 | Current |
| 2.4.8 | March 2026 | 11 April 2028 | Supported |
| 2.4.7 | March 2026 | 9 April 2027 | Supported |
| 2.4.6 | March 2026 | 11 August 2026 | Ends imminently |
| 2.4.5 | — | 9 August 2025 | Unsupported |
| 2.4.4 | — | 12 April 2025 | Unsupported |
| 2.4.0–2.4.3 | — | 28 November 2022 | Unsupported |
| 2.3 and earlier | — | 8 September 2022 | Unsupported |
Dates are from Adobe's published lifecycle policy and released-versions documentation. Confirm your own version in the admin panel before making any decision — editions and versions both change over a store's life, and assuming based on when the store was built is how teams discover they are already unsupported.
Adobe offers one additional year of support at no extra cost to Adobe Commerce customers on 2.4.6 and 2.4.7. Magento Open Source gets nothing further. So the same version number carries two different deadlines depending on whether you hold a paid Adobe Commerce licence or run Open Source. Record your edition as well as your version number.
Nothing stops working on the day. What stops is security patching — when a vulnerability is found in core code after your line's support ends, no fix is issued for your version. For merchants handling card data, running unpatched commerce software also raises questions with PCI compliance and, increasingly, with cyber insurers. Adobe has separately introduced enforced version upgrades on Adobe Commerce Cloud, reserving the right to decommission environments running unsupported versions.
We sell Shopify migrations. You should read this section knowing that, and it is written so you can act against our interest if that is the right call.
The common assumption is that upgrading is the conservative, low-cost choice and replatforming is the expensive one. For 2.4.9 that assumption is wrong, because the supported stack moved substantially. 2.4.9 expects PHP 8.5, MySQL 8.4 or MariaDB, Composer 2.10, OpenSearch 3, RabbitMQ 4.3, Varnish 8 and nginx 1.30. Two changes catch teams out: Elasticsearch no longer appears in the supported matrix at all, and Redis has been replaced by Valkey.
That makes an upgrade a server rebuild as much as a code change. Hosting has to be part of the conversation from day one. Add extension compatibility across every third-party module you run, and a major-version Magento upgrade is frequently within range of a replatform — while leaving you on the same platform, facing the same exercise again in two to three years.
| Option | When it makes sense |
|---|---|
| Upgrade to 2.4.9 | You have deep custom functionality with genuine competitive value, in-house Magento engineering, and infrastructure you are willing to keep owning. |
| Adobe Commerce as a Cloud Service | You want to stay in Adobe's ecosystem and move off self-managed infrastructure. Adobe's own recommended path. |
| Mage-OS or Magento Open Source | You need to remove licence cost and have the engineering capacity to maintain the platform yourself. |
| Migrate to Shopify Plus | Your constraint is release speed, checkout limitations, operational overhead, or the cost of carrying your own infrastructure — and your custom functionality can be rebuilt or replaced. |
If your Magento build encodes real competitive advantage and you employ engineers who know it, upgrading is defensible. If your store is a standard catalogue carrying years of accumulated extensions, and your team waits on a developer to publish a landing page, that is what a replatform actually fixes.
Magento and Shopify model products differently. These are the mismatches that decide the real scope of a migration, and they are the reason two stores with the same product count can differ by a factor of three in cost.
| Magento type | Shopify equivalent | Difficulty |
|---|---|---|
| Simple | Product with one variant | Trivial |
| Configurable | Product with variants across up to 3 options | The main constraint — see below |
| Grouped | Separate products, linked by collection or a bundle app | Moderate; merchandising decision required |
| Bundle | Bundle app or a custom bundle builder | Significant; often custom work |
| Virtual | Product with shipping disabled | Trivial |
| Downloadable | Digital product plus a delivery app | Moderate |
Shopify raised the per-product variant limit from 100 to 2,048 in October 2025, across all plans. It did not raise the option limit, which remains 3 per product. Magento configurable products routinely use four or more attributes, and those products cannot map one-to-one onto Shopify without restructuring.
A Magento product configured on colour, size, material and length is a four-axis product. Shopify permits three. There are three ways out, and the choice is a merchandising decision as much as a technical one: combine two attributes into a single option value, split the product and link the parts with Combined Listings so shoppers still experience one product, or move the fourth attribute to a line-item property or a custom-options app.
Audit your configurable products for option count before you budget the migration. A catalogue where 5% of products have four or more attributes is a different project from one where 60% do, and this is the number most migration quotes never ask for.
Magento stores product data in an entity-attribute-value model with attribute sets — arbitrarily many attributes, defined per product type. Shopify has a flatter model plus metafields and metaobjects. Every Magento attribute has to be triaged: does it become a variant option, a metafield, a metaobject reference, a tag, or is it dead weight nobody has used in four years? Migrations that skip this triage import the dead weight and carry the mess onto a more expensive platform.
Magento's three-level hierarchy of websites, stores and store views has no single Shopify equivalent. Depending on why the hierarchy exists, it maps to Shopify Markets for currency and language, to expansion storefronts for genuinely separate brands, or it collapses entirely because it was only ever a workaround. A Shopify Plus contract includes your primary store plus nine expansion storefronts, which covers most multi-brand structures without additional licences.
Passwords cannot be migrated from Magento — or from any platform. Shopify sends account activation invitations instead. For a store with a large logged-in customer base, that email is a launch-critical communication and needs planning, not discovering.
Magento appends a URL suffix — by default .html — to product and category URLs, and nests products inside category paths. Shopify uses fixed prefixes: /products/, /collections/, /pages/ and /blogs/. Neither the suffix nor the nesting can be reproduced on Shopify, so effectively every indexed URL on a Magento store changes and needs a 301 redirect.
| Magento URL | Shopify destination |
|---|---|
| /footwear/sneakers/red-shoes.html | /products/red-shoes |
| /catalog/product/view/id/1234 | /products/red-shoes |
| /footwear/sneakers.html | /collections/sneakers |
| /about-us.html | /pages/about-us |
| /blog/post-title | /blogs/news/post-title |
| /catalogsearch/result/?q=shoes | /search?q=shoes |
| /footwear/sneakers.html?color=red | /collections/sneakers?filter.p.m.custom.color=red |
Magento's url_rewrite table is the most valuable asset in the whole migration and the one most often ignored. It holds every historical URL the store has ever served, including rewrites created when products were renamed years ago. Export it. Then reconcile it against a live crawl and Search Console data, because the union of those three sources is your real redirect map — and it is always larger than the product export suggests.
Shopify Plus permits up to 20,000,000 URL redirects against 100,000 on standard plans, which for a long-lived Magento catalogue is frequently the difference between a complete redirect map and a compromised one. Our Shopify Plus migration services page covers redirect strategy across all source platforms.
Twelve to sixteen weeks for a typical Magento store — longer than migrations from WooCommerce or BigCommerce, because of attribute triage and extension replacement.
Version and edition confirmed. Crawl the live site, export the url_rewrite table, pull Search Console and backlink data. Inventory every extension and integration. Count products by type and configurable products by option count.
Every Magento attribute assigned a Shopify destination. Every URL mapped, signed off by you. Both happen before design, because both change the collection architecture.
Concepts, then full page design in Figma.
Products and variants first, then customers, then order history. Verified at each stage. Shopify Plus includes unlimited staging stores, so production is never touched.
Each Magento extension mapped to a Shopify app, rebuilt as a custom app, or retired. This is usually the longest track on a Magento project.
Development against approved designs, then cross-device, cross-browser, checkout and integration testing.
DNS cutover in your lowest-traffic window. Redirects go live with the store. Sitemap resubmitted the same day.
Daily Search Console checks through the first fortnight: coverage, 404s, index status, rankings on your top revenue URLs.
Magento migration projects at Solo Media Group start at around $20,000 and are quoted as a line-item estimate. Shopify Plus is billed separately by Shopify from $2,300 per month on a three-year term or $2,500 on a one-year term. Magento migrations sit at the higher end of our range because of attribute triage and extension replacement.
Our full Shopify Plus cost guide covers budgeting across build types. Platform pricing above is Shopify's published figure; above a high monthly volume, billing moves to a variable platform fee whose thresholds Shopify does not publish and which should be confirmed with their Plus team rather than taken from any agency page, ours included.
Solo Media Group is a Platinum-tier Shopify migration company with 75+ replatforms and new builds delivered since March 2018, rated 5.0 from 37 reviews on the Shopify Partner Directory. Migrations from Magento and Adobe Commerce are the ones we are asked to run most often.
Two catalogues of 5,000 products can differ threefold in migration cost depending on product types and attribute depth. Count configurable products by option count before you accept any quote — including ours.
It holds every historical URL the store has served. Migrating from the current product export alone silently drops years of accumulated link equity.
Some do, some need rebuilding as custom apps, and some exist only because Magento could not do something natively that Shopify does. Each needs a decision in week one, not week eight.
Importing every attribute because it exists reproduces a decade of mess on a platform that costs more per month. Triage is the point of the exercise.
A real Magento migration takes twelve to sixteen weeks. If your support date is weeks away, the honest sequence is to patch or upgrade to buy time, then migrate properly — not to compress a replatform into the gap.
Support for the 2.4.6 release line ends 11 August 2026. 2.4.7 ends 9 April 2027, 2.4.8 ends 11 April 2028, and 2.4.9 runs to 12 May 2029. Support for 2.4.5 ended 9 August 2025 and 2.4.4 ended 12 April 2025. Adobe Commerce licence holders on 2.4.6 and 2.4.7 receive one additional year at no cost; Magento Open Source does not.
The store keeps running, but Adobe stops issuing security patches for your version. New core vulnerabilities go unfixed. For merchants handling card data this raises PCI compliance questions and is increasingly relevant to cyber insurance cover.
Not as different as most people assume. Upgrading to 2.4.9 requires PHP 8.5, MySQL 8.4 or MariaDB, OpenSearch 3 and Valkey in place of Redis, so it is a server rebuild as much as a code change, plus extension compatibility work. A major-version upgrade is often within range of a replatform — while leaving you facing the same exercise in two to three years.
Twelve to sixteen weeks for a typical store, longer than migrations from WooCommerce or BigCommerce. Attribute triage and extension replacement are the two tracks that extend a Magento project.
Our Magento migration projects start at around $20,000, quoted as a line-item estimate, and sit at the higher end of our migration range. Shopify Plus is billed separately from $2,300 per month on a three-year term or $2,500 on a one-year term.
Not if redirect mapping is complete before launch. Magento appends a .html suffix and nests products in category paths; Shopify does neither. Effectively every indexed URL changes, so the redirect map must be built from the url_rewrite table, a live crawl, and Search Console data together.
Usually, with restructuring. Shopify allows up to 2,048 variants per product across a maximum of 3 options. Magento configurable products often use four or more attributes, which need combining, splitting with Combined Listings, or moving to line-item properties.
Grouped products become separate Shopify products linked by collection or a bundle app. Bundles need a bundle app or a custom bundle builder. Both are merchandising decisions, made during scoping.
Yes — complete order history including refunds and fulfilment status, alongside customers, addresses, tags and marketing consent state.
Yes. Passwords cannot be migrated from any platform. Shopify sends account activation invitations, and that email should be planned as part of launch communications.
In most cases, restructured. Magento's websites, stores and store views map to Shopify Markets for currency and language, or to expansion storefronts for separate brands. A Plus contract includes your primary store plus nine expansion storefronts.
Patch or upgrade to buy time, then migrate properly. A twelve-to-sixteen week project compressed into a few weeks fails in the places that cost the most — redirects and integrations. Any agency agreeing to the compressed timeline is skipping work you will pay for later.
