Your 2026 Options Now That Adobe Commerce 2.4.4 Extended Support Has Ended
Extended support for Adobe Commerce 2.4.4 ended on April 14, 2026. Adobe now provides only limited security fixes for that release line, and those end on May 31, 2027. If your store still runs 2.4.4, or 2.4.5, whose extended support ends this August, here are your realistic options and how to choose between them.
Published May 6, 2026. Author: Ecomm Guys. 4 min read.
Key Points
- Extended support for Adobe Commerce 2.4.4 ended on April 14, 2026.
- Adobe offers a security-only transitional period for 2.4.4 until May 31, 2027, with no quality fixes.
- Extended support for 2.4.5 ends in August 2026.
- Adobe also warns that older PHP versions have implications for PCI compliance.
- Your options are to upgrade within Adobe Commerce, move to Adobe's hosted service, or replatform.
Where Things Stand for 2.4.4
Adobe's lifecycle policy gives each Adobe Commerce release three years of standard support from general availability, covering quality fixes, security patches, and full support. For 2.4.4, standard support ended on April 12, 2025. Adobe then offered a year of extended support at no extra cost, and that ended on April 14, 2026.
What's left is a one-time, security-only transitional period for 2.4.4, which runs until May 31, 2027. It provides limited, isolated security fixes only, with no quality fixes. For 2.4.5, extended support ends in August 2026, with the same kind of security-only period after it.
What Security-Only Really Means
A security-only period buys time. It doesn't keep a store healthy. Without quality fixes, bugs stay unfixed, and compatibility with payment, shipping, and tax extensions gets harder to maintain as those vendors move on.
Adobe also points out that it doesn't provide fixes for third-party dependencies, such as PHP, MariaDB, OpenSearch, or Redis, that reach end of life while you're on an older release. It notes that PHP versions used by older release lines have reached or will reach end of life, which has direct implications for PCI compliance. For a store that takes card payments, that's the risk that usually forces the decision.
Your Three Options
Adobe's lifecycle page sets out the paths within Adobe. Replatforming is the third.
- Upgrade within Adobe Commerce to a supported release line, such as 2.4.7 or 2.4.8. Adobe lists standard support for 2.4.7 until May 31, 2027 and for 2.4.8 until May 31, 2028.
- Move to Adobe Commerce as a Cloud Service, which Adobe's lifecycle page names as its recommended long-term path, with Adobe managing infrastructure and upgrades.
- Replatform to another ecommerce platform, such as Shopify or Shopify Plus.
How to Choose
Start with the cost of standing still. Every Adobe Commerce upgrade involves testing extensions, custom code, and integrations. Adobe notes that upgrading within the platform doesn't end future upgrade obligations. If you've been through two or three of these cycles, add up what they cost in agency time and lost momentum.
Then look at what the store actually needs. Many mid-market Magento stores run heavy customization to do things that are now standard on Shopify: B2B pricing, multi-currency selling through Markets, and native A/B testing through Rollouts. Shopify brought B2B pricing to its Basic, Grow, and Advanced plans in April. If most of your custom code exists to fill those gaps, replatforming may cost less over three years than the next upgrade cycle.
If your store relies on deep custom logic tied to an ERP, or your team is committed to the Adobe ecosystem, an upgrade or Adobe's hosted service may be the better fit. The point is to make the decision on purpose.
If You Plan to Migrate
A migration takes planning, and the security-only window is the time to do it. Map your data first: products, customers, orders, and any B2B accounts. List every extension and decide whether it's replaced by a Shopify feature, an app, or custom work. Plan your URL redirects early, because protecting search rankings is often the biggest risk in a move. Then set a launch date well before May 2027, outside your peak season.
Make the Call by Summer
Confirm which Adobe Commerce and PHP versions you run and check them against Adobe's end-of-support table. Then cost out two paths side by side: the next upgrade and a migration. Make the call by summer, so a migration can launch before your next holiday season or early in 2027.
Want help comparing an upgrade with a move to Shopify? Book a call with our team.
Sources
- Adobe Commerce lifecycle policy Adobe Experience League
- Adobe Commerce released versions Adobe Experience League