Magento 2 End of Life: Adobe’s Real Support Dates and Your Three Options

There’s no Magento 2 end of life date. Adobe publishes support dates for each release line, not for the platform as a whole, and several lines crossed a support boundary in 2026. Extended support for 2.4.4 ended April 14, 2026 (opens in new tab), and extended support for 2.4.5 ended August 11, 2026, the same day standard support for 2.4.6 ended.

Those dates end support for specific versions. Magento 2 itself doesn’t end.

Your actual deadline depends on three things you can look up quickly: which release line you run, whether you’re on Adobe Commerce or Magento Open Source, and whether your store runs on Adobe Commerce on Cloud or on your own servers. We build Shopify stores and move merchants off Magento, and this is the breakdown we give a merchant who asks how long they have.

Adobe revises its lifecycle pages, so check the linked page before you commit to a date.

No. Adobe gives each version a three-year standard support window (opens in new tab) from its General Availability (GA) date. Adobe doesn’t publish an end date for Magento 2 as a whole. Adobe is still shipping new release lines: Adobe Commerce 2.4.9 reached general availability on May 12, 2026, and Magento Open Source 2.4.9 (opens in new tab) has its own release notes.

So a question about Magento 2 end of life is really a question about your release line. On Adobe’s schedule, a store on 2.4.9 has standard support until May 31, 2029. An Adobe Commerce store on 2.4.4 is already past standard and extended support and gets security-only fixes until May 31, 2027. Both stores run Magento 2.

Adobe’s support comes in three tiers. Standard support (opens in new tab) includes quality fixes, security patches, and full Adobe Commerce on-call support, and it runs three years from a line’s release date. Adobe’s contractual terms set the same period for 2.4.4 onward: a three-year Software Support Period (opens in new tab) from each version’s release date.

Extended support is the second tier. Adobe offers one year of additional support at no additional cost for Adobe Commerce customers on versions 2.4.6 and 2.4.7, covering quality and security patches for the core application. The two older lines have already used their extra year: extended support for Adobe Commerce 2.4.4 and 2.4.5 ended in April and August 2026, as planned.

The third tier is temporary. The security-only period is a one-time, time-limited transitional period available only for versions 2.4.4, 2.4.5, and 2.4.6, and it provides limited isolated security fixes only, with no quality fixes. Adobe’s instruction to merchants is “Treat the security-only period as migration time, not as a long-term support tier.” Adobe says the period won’t be extended beyond the published dates.

Hotfixes for critical issues go to all customers on a supported version, so a line outside all three tiers doesn’t get them. And the software your store runs on is your responsibility: Adobe doesn’t provide security and quality fixes for third-party services and software dependencies, such as PHP and MySQL, that may reach end of life while customers are in the three-year or extended support period for Adobe Commerce.

Every date in the table below is Adobe’s support date (opens in new tab) for an Adobe Commerce release line (opens in new tab). Adobe Commerce is the licensed product. The last column applies only to Adobe Commerce on Cloud, Adobe’s platform-as-a-service hosting, and gives the date by which a Cloud store must upgrade or move to Adobe Commerce as a Cloud Service (opens in new tab).

2.4.9 and 2.4.8 are in standard support, and 2.4.7 stays in standard support until May 31, 2027. 2.4.6 is past standard support and in extended support. 2.4.4 and 2.4.5 are past standard and extended support, and their security-only period ends on May 31, 2027.

Older lines are already out. Regular support ended (opens in new tab) November 28, 2022 for 2.4.0 through 2.4.3, September 8, 2022 for 2.3, December 1, 2019 for 2.2, June 30, 2019 for 2.1, and March 31, 2018 for 2.0.

Regular support for the 2.4.6 release line ended on August 11, 2026 (opens in new tab). Adobe publishes two dates for the end of extended support for the 2.4.6 release line: August 31, 2027 (opens in new tab) and August 30, 2027 (opens in new tab). They’re a day apart, so plan against August 30.

After extended support, 2.4.6 moves into the security-only period, which ends on May 31, 2028.

The PHP runtime is the earlier constraint for 2.4.6. Adobe supports PHP 8.2 or 8.1 for 2.4.6 (opens in new tab). PHP 8.1’s end of life was December 31, 2025, and PHP 8.2’s is December 31, 2026 (opens in new tab), which affects 2.4.6 where PHP 8.2 is used. PHP’s own end of security support for 8.2 (opens in new tab) is the same December 31, 2026.

Adobe’s advice for those stores is to “plan upgrade or migration before the end of 2026 to maintain PCI compliance.” Adobe adds that “PCI compliance is the merchant’s responsibility to assess.” A 2.4.6 store therefore stays inside Adobe’s extended support until August 2027, but its runtime reaches end of life about eight months earlier.

Extended support ended April 14, 2026 for 2.4.4 and August 11, 2026 for 2.4.5 (opens in new tab). Both lines receive only isolated security fixes, and only until May 31, 2027. Adobe’s 2.4.5-p17 (opens in new tab) patch for the 2.4.5 line is dated May 12, 2026.

These two lines are also stuck on an old PHP version. Adobe supports only PHP 8.1 for 2.4.4 and 2.4.5 (opens in new tab), and PHP 8.1 reached end of life on December 31, 2025 (opens in new tab). A store on either line can’t move to a supported PHP version without moving to a newer release line. On Cloud, the upgrade deadline for both is June 1, 2027.

2.4.7 has the most time of the lines under pressure. It’s in standard support until May 31, 2027 and in extended support until May 31, 2028 (opens in new tab), with no security-only period after that. On Cloud, its upgrade deadline is June 1, 2028.

Adobe ties the PHP 8.2 date only to 2.4.6. Adobe supports PHP 8.3 or 8.2 for 2.4.7 (opens in new tab), and a 2.4.7 store still on 8.2 has the same December 31, 2026 PHP end of life. Moving that store to 8.3 is a smaller job than changing release lines.

For comparison, standard support runs until May 31, 2028 for 2.4.8 and May 31, 2029 for 2.4.9, with extended support not yet announced for either.

The dates above are Adobe Commerce dates. Adobe’s contractual lifecycle policy doesn’t apply to Magento Open Source (opens in new tab). Extended support security patches (opens in new tab) are available to Adobe Commerce customers only. They’re not available for the Magento Open Source code base (opens in new tab).

Adobe’s lifecycle policy covers Adobe Commerce. That doesn’t mean Adobe has dropped Open Source. It shipped Open Source 2.4.9 in May 2026.

Extended patches are for Commerce only, so don’t plan on an extended-support patch path for an Open Source release line once it leaves standard support. If you run Open Source, treat the Adobe Commerce end of standard support for your line as your working Magento end of life date.

Enforcement is new in this cycle, and it applies to Adobe’s hosting, not to the software license. It covers Adobe Commerce on Cloud (PaaS) environments running Adobe Commerce versions 2.4.4 through 2.4.9 (opens in new tab). It doesn’t apply to Adobe Commerce as a Cloud Service (SaaS) environments or Adobe Commerce on-premises deployments.

Adobe’s stated policy (opens in new tab) is that starting June 1, 2027, it will no longer maintain Cloud environments running unsupported Commerce versions. Adobe says “This includes suspending traffic to the affected infrastructure. As a result, your ecommerce storefront will go offline.”

Adobe sets the deadline by version. Cloud stores on 2.4.4 or 2.4.5 have to upgrade or move to Adobe Commerce as a Cloud Service by June 1, 2027. Stores on 2.4.6 or 2.4.7 have until June 1, 2028, and for 2.4.8 or 2.4.9 an upgrade is “Not required at this time.”

Adobe gives two dates for what to do. It asks Cloud customers to move before their line’s extended support ends. The enforcement dates in the table are when traffic suspension can start, and each one comes after that line’s extended support ends.

The earliest Cloud deadline is about the software a store runs on, not its release line, and it applies to every Cloud version from 2.4.4 through 2.4.9. Adobe set October 30, 2026 as the deadline for Cloud stores to move MariaDB 10.5 and below to 10.6 or higher (opens in new tab), any Elasticsearch to OpenSearch, and RabbitMQ 3.9 and below to 3.13 or higher.

A second round is due May 31, 2027: PHP 8.1 and below to 8.2 or higher, MariaDB versions below 10.11 to 10.11, OpenSearch 1.x to a newer version, RabbitMQ versions below 3.13 to 4.3, and Redis 5 and below to Valkey 8 or higher.

How those two dates apply depends on the release line, and Adobe isn’t consistent here. For Cloud stores on 2.4.4 or 2.4.5, Adobe’s per-version deadlines mark dependency upgrades as required by October 30, 2026. But Adobe’s per-dependency deadlines give May 31, 2027 for several items, including an OpenSearch 1.x item that names 2.4.4 and 2.4.5 customers. Treat October 30 as the date that applies and get your line’s dates confirmed in writing by your account team.

For 2.4.6 through 2.4.9, the date is October 30, 2026 or May 31, 2027, depending on the software. Elasticsearch 7.17 reached End of Support (EOS) on January 15, 2026 (opens in new tab).

Adobe’s stated policy is that a Cloud store that misses its deadline has its inbound traffic suspended, which takes the storefront offline. Adobe gives a way out for stores that are close: if you have concerns about meeting the deadline and need a short extension, Adobe asks you to contact your account team or Adobe Support as soon as possible. For a store that stays non-compliant after suspension (opens in new tab), Adobe’s policy is that it may terminate cloud services, initiating the decommissioning process, after which “all data and assets within the hosted ecommerce environment, including all instances, environments, and branches, will be permanently deleted and cannot be restored.”

A store on your own servers doesn’t get switched off. Adobe Commerce software doesn’t shut down (opens in new tab) once the end of support date is reached or passed. Traffic suspension is a policy for Adobe’s own Cloud hosting, and it doesn’t apply to on-premises deployments.

What does change for a self-hosted store is support. Adobe says “Once a version of Adobe Commerce software is no longer supported, that version is no longer PCI compliant,” and Adobe Commerce won’t work to resolve support tickets that were opened after the end of support date for that software version. You’ll no longer receive security patches, and Adobe allows outside help: you can look for security firms, developers, or partners who will provide support for unsupported versions of Adobe Commerce.

Magento 1 reached end of life on June 30, 2020. None of the Magento 2 support tiers above apply to a Magento 1 store. If you’re still on Magento 1, the options below all start from a store that’s had no platform support since mid-2020.

Magento 2 works differently. Each release line gets its own dates, so the platform keeps running while individual lines go out of support. That’s why Magento 2 end of life depends on which version you run.

For Adobe Commerce on Cloud, Adobe gives two paths (opens in new tab): upgrade to Adobe Commerce on Cloud 2.4.9, or migrate to Adobe Commerce as a Cloud Service. Leaving Adobe isn’t one of them. Replatforming to Shopify is the third path, and the support calendar sets the timeline for all three.

An upgrade keeps you on the platform your team and integrations already run on. 2.4.9 has standard support until May 31, 2029 (opens in new tab), with extended support not yet announced. Adobe supports PHP 8.5 for 2.4.9 (opens in new tab), so a store coming from 2.4.4 or 2.4.5 on PHP 8.1 moves up several PHP versions at once.

For Cloud customers, Adobe describes its security cadence (opens in new tab) as “Monthly isolated security fixes for faster and predictable protection against critical vulnerabilities” and “Annual patch releases with long term support.” The tradeoff is the three-year window itself. A store that lands on 2.4.9 in 2027 reaches the end of standard support on May 31, 2029, and Adobe hasn’t announced extended support for 2.4.9.

This is Adobe’s preferred path. Adobe calls Adobe Commerce as a Cloud Service (opens in new tab) “Adobe’s recommended long-term destination for all Adobe Commerce on Cloud customers,” with the pitch that “You eliminate recurring upgrade cycles” and “Adobe manages all infrastructure, patching, and upgrades automatically.” That recommendation is addressed to Cloud customers, and it’s a vendor steering customers to another of its own products.

Adobe says its migration tooling (opens in new tab) is “available at no cost to you.” Get pricing for the service and a migration timeline in writing from your account team. Adobe lists Commerce Storefront, Merchandising Services, Product Visuals, and Developer Platform (opens in new tab) as the products behind it.

The third path moves your catalog, customers, order history, URLs, and integrations to a different platform, and your store gets rebuilt on Shopify. It’s the only one of the three that takes you off Adobe entirely. It’s also the biggest change for your team’s day-to-day work, and it runs on the same deadlines, because the Magento store has to stay supported and online until cutover. Our Shopify migration services page describes how we run these moves across platforms.

Can Shopify’s own migration app import a Magento store? Shopify’s Store Migration app (opens in new tab) is free and built by Shopify. It moves product and customer data into Shopify from Square, WooCommerce, Etsy, Wix, Amazon, eBay, Clover, and Lightspeed R/X (Vend). Magento isn’t on that list.

The app also lets you upload a CSV file or, on supported platforms, connect your account to import automatically with guided setup. The older Store Importer app (opens in new tab) isn’t currently available on the Shopify App Store.

That leaves CSV import, third-party migration apps, a Shopify Partner, or custom API work. Those are Shopify’s own migration methods (opens in new tab), alongside manual copying. Shopify recommends importing products first, then customers, then historical orders. We’ve covered the same mechanics for another platform in our WooCommerce to Shopify migration guide.

Magento’s configurable products are where catalog mapping takes the most work. Shopify’s productOptionsCreate (opens in new tab) mutation returns the error “Can only specify a maximum of 3 options.” By default, stores have a limit of 2048 product variants for each product (opens in new tab). Any Magento product with more than three configurable attributes has to be restructured before it can be imported.

Volume sets the import method. Shopify caps product CSV files at 15 MB each (opens in new tab), so larger catalogs get split across several files. Shopify’s bulk variant mutations (opens in new tab) can create, update, or reorder up to 2,048 variants at a time and delete up to 250 at a time.

Do customer passwords carry over? No. Passwords can’t be migrated from another store by CSV (opens in new tab), so after the import you invite customers to set new ones. Customer CSV files are capped at 15 MB.

Multipass (opens in new tab) doesn’t solve the password problem. It requires a Shopify Plus plan, and Multipass login is only available with legacy Customer accounts, which you have to choose explicitly in your Customer Accounts settings in the Shopify admin before you can enable Multipass. Multipass lets customers signed in on your external site log in to your Shopify store without entering credentials again, by sending a signed token that redirects them. That’s single sign-on from another site, not a password transfer.

Magento and Shopify build URLs differently. Adobe Commerce uses ID-based URLs internally (opens in new tab), but you can create SEO-friendly URLs for customers, so a URL like /peripherals/keyboard.html sits on top of /catalog/category/id/6. On Shopify, URLs are built from handles: the handle is used to build the URL for the resource (opens in new tab), giving paths like /products/{handle} and /collections/{handle}.

The redirect map translates Magento /{category}/{url-key}.html and /{url-key}.html product URLs to /products/{handle}, and Magento /{category}.html category URLs to /collections/{handle}. In Magento, saving a category can create product rewrites under category paths (opens in new tab). Check whether a Magento product is reachable at several URLs, because each of them needs its own redirect.

On Shopify, a redirect only fires from a URL that no longer loads a page (opens in new tab), and redirects are 301s. The maximums are 100,000 redirects on non-Plus plans and 20 million on Plus.

URLs with query strings may not redirect as expected, so test your Magento filtered category URLs. Redirect paths are unique (opens in new tab), so a shop can’t have more than one redirect with the same path. The rest of the redirect process is in our SEO migration checklist.

B2B doesn’t require Shopify Plus. Shopify B2B comes with up to 3 catalogs on Basic, Grow, and Advanced (opens in new tab), and unlimited B2B catalogs on Plus, which is listed from $2,300/mo. Shopify’s pricing changes, so check the page. B2B doesn’t support purchase options (opens in new tab), such as subscriptions, pre-orders, and try before you buy.

Checkout customization on Shopify uses extensions and Functions, not template edits. Checkout UI extensions (opens in new tab) for the information, shipping, and payment steps are available only to stores on a Shopify Plus plan. Shopify Functions (opens in new tab) work on every plan except Shopify Starter, though only Plus stores can run custom apps that contain Shopify Function APIs (opens in new tab), and checkout.liquid is unsupported (opens in new tab) for the Information, Shipping, and Payment checkout steps. If your Magento checkout is heavily customized, that’s the main point for evaluating Plus, and our Shopify Plus agency page covers how we assess plan fit.

For Magento stores running several websites or store views, Shopify’s plans include localized selling with Shopify Markets, with local currencies and local payment methods requiring Shopify Payments. Plan to map Magento’s website, store, and store view structure rather than copy it.

On compliance, Shopify says “Shopify is certified Level 1 PCI DSS compliant (opens in new tab). This compliance extends by default to all stores powered by Shopify.” That’s Shopify describing its own platform. Adobe’s statement that PCI compliance is the merchant’s responsibility to assess reflects a different platform model.

How long does a Magento to Shopify migration take? It depends on catalog structure, customer count, redirect volume, and integrations. Adobe’s calendar sets the latest possible finish date. A Cloud store on 2.4.4 or 2.4.5 has to cut over before June 1, 2027 or upgrade on Cloud to stay online, and its dependency upgrade deadlines fall before that date.

For a Cloud store on 2.4.4 or 2.4.5, the first date is October 30, 2026, when Adobe’s per-version deadlines list dependency upgrades as due. Some of Adobe’s per-dependency deadlines carry May 31, 2027 instead. The second is June 1, 2027, the version deadline.

Whichever path you choose, the current store has to stay compliant until cutover. A Shopify launch after October 30, 2026 doesn’t lift the dependency upgrades, which apply to the Magento store until cutover.

For a Cloud store on 2.4.6 or 2.4.7, enforcement comes on June 1, 2028. Adobe asks you to move before extended support ends, which is August 2027 for 2.4.6 and May 31, 2028 for 2.4.7, and the end of life for a 2.4.6 store’s PHP 8.2 is December 31, 2026. For a self-hosted Adobe Commerce store, nothing gets switched off, but Adobe ties PCI compliance and ticket support to being on a supported version. For Open Source, plan around your line’s end of standard support, because Adobe’s extended patches aren’t available for it.

Our recommendation depends on where your Magento budget goes. If most of it keeps the platform current (release upgrades, PHP moves, dependency changes like the October 30 list) rather than building things your customers see, replatforming to Shopify takes you off that cycle, and that’s what we’d recommend. Adobe makes the same claim for Adobe Commerce as a Cloud Service, so price both.

If your business logic lives in custom Magento modules that Shopify’s three-option limit, B2B restrictions, or Plus-only checkout steps can’t hold, price the upgrade to 2.4.9 against a rebuild. Adobe Commerce as a Cloud Service is the option for Cloud customers who want to stay with Adobe and are prepared to migrate within Adobe to do it.

If Shopify is on your shortlist, start by planning a Magento to Shopify migration with us. The free audit gives you a scoped estimate before you commit to anything, and every migration we run includes the Shopify build.