The August 2026 Magento Support Cliff: Upgrade, Move, or Replatform

Summary

Your Magento version fell out of support on 11 August 2026. The store still runs and the licence stays valid. Adobe also states that an unsupported version is no longer PCI compliant.

Four responses are available: upgrade to a supported 2.4.x, move to Adobe Commerce Cloud, replatform, or document the risk. For most merchants the right move is the upgrade, not a replatform. This guide walks all four, starting with the one that earns us the least.

Introduction

Two things happened to Magento on 11 August 2026, and most merchants noticed one. The 2.4.6 line left regular support that day, per Adobe’s published release documentation. On the same date, 2.4.5 left extended support, its final phase of ordinary coverage.

A month later nothing has broken, which is exactly what makes this decision hard. Your board wants a position and your agency has an interest in the answer.

This article walks four paths, ordered by how little each one earns us. Every date below comes from Adobe’s own documentation, checked on 10 September 2026.

What changed for Magento on 11 August 2026?

On 11 August 2026 Adobe stopped issuing quality fixes and security patches for the 2.4.6 line. Adobe’s published release documentation puts 2.4.5 out of extended support, its last ordinary phase, on the same date.

Which Magento versions are still supported?

2.4.7, 2.4.8 and 2.4.9 remain in regular support, and 2.4.7 exits on 31 May 2027.

Magento release lifecycle dates from Adobe’s published release documentation, checked 10 September 2026. Confirm your own edition’s dates on Adobe’s versions page.

What Adobe stops doing after the end-of-support date

Your store keeps running and your licence stays valid, per Adobe’s end-of-support FAQ. Adobe calls this end of support (EOS), not end of life (EOL).

Tickets raised after the date are not resolved, and no further product changes are made. That includes security and PCI compliance changes, and community pull requests are no longer merged.

Adobe’s lifecycle policy sets a three-year standard support window from each version’s GA date. The same policy states that Adobe does not patch third-party dependencies such as PHP and MySQL.

Are you out of PCI compliance now?

Adobe says yes, and that is Adobe’s published position on its own software. Your acquiring bank, not Adobe, is the party that acts on it.

What Adobe states about unsupported versions

Adobe’s end-of-support FAQ, checked on 10 September 2026, states that an unsupported version is “no longer PCI compliant.” The same FAQ names fines, loss of card processing ability, or other penalties as consequences.

We are reporting Adobe’s statement, not a clause of the PCI DSS standard itself. We did not read that standard, so we will not name a requirement number.

Why your acquiring bank and QSA decide this

The practical consequence does not run through Adobe at all. It runs through your acquiring bank and your qualified security assessor, who judge your PCI DSS compliance. They decide whether an unsupported release line is a finding, and on what timetable.

So confirm your own position with your QSA before you assume either safety or catastrophe. Assuming is the expensive option.

Does your Magento edition change your deadline?

Possibly, and you need to confirm that yourself rather than take any agency’s word for it, including ours.

What we could and could not verify about edition differences

Adobe’s published versions page lists the lifecycle dates without drawing a distinction between editions. We checked it on 10 September 2026 and it does not mention Magento Open Source. Several agency articles assert that extended-support patches reach Adobe Commerce customers only.

We could not verify that split against Adobe’s documentation, so we will not repeat it. Confirm your own edition’s dates on Adobe’s published versions page before you plan around extended support.

If you cannot confirm that you receive extended support, plan as though 11 August 2026 was your end date.

Which of the four paths fits your store?

Four paths exist, and the table below orders them by how little each one earns us.

None of the four is a default. Each is right for a nameable situation and wrong for the others. The order is deliberate, because the cheapest honest answer belongs at the top.

Four responses to the August 2026 support cliff, ordered by how little each benefits Virtina. Compiled 10 September 2026.

How to read this decision table

Start at path 1 and only move down when a row’s do-not-choose column describes you. That rule takes thirty seconds and it is the whole method.

Most readers stop at path 1, which is the point. The paths below it are not upgrades in disguise. They are different projects, with different budgets and different risk.

Path 1: upgrade to a supported 2.4.x release

For most readers this is the right answer, and it is the one that sells us the least. Your install still fits, and the platform is not the reason growth stalled.

If that describes you, our Magento version upgrade steps guide covers the mechanics.

Should you target 2.4.8 or 2.4.9?

Target 2.4.8 if you carry a heavy extension footprint, and 2.4.9 if you want the extra year.

Adobe’s published system requirements for 2.4.8 and 2.4.9, checked 10 September 2026.

2.4.9 buys one more year, but Adobe’s system requirements put it on PHP 8.5. php.net dates that release to 20 November 2025, so vendors have had roughly ten months to certify.

2.4.8 runs on PHP 8.4 or 8.3, where extension compatibility is far more likely to already exist.

What actually drives upgrade cost and effort

An upgrade quote is built from six lines, none of them your revenue. Those six are extension re-certification, module remediation, theme rework, integration re-testing, infrastructure changes, and QA with UAT. Five numbers price all six.

• Installed extensions. Each needs re-certification on the target version.
• Core overrides. Remediation scales with how far you forked core.
• Store views. Each multiplies theme, content and QA work.
• Live integrations. ERP, PIM, tax and gateway need re-testing.
• PHP distance. A big jump is where frontend rework bites.

Budget a staging environment and a rollback plan into the same figure. Our Magento development services team scopes upgrades against those five numbers.

Path 2: move to Adobe Commerce Cloud

This fits you only if you are already on Adobe Commerce licensing and infrastructure management is the actual pain. You are handing the stack to Adobe and paying for that.

Adobe does not publish Adobe Commerce Cloud pricing or packaging, so we will not estimate it. Price it directly with Adobe, and ask what the licence covers before you compare it to an upgrade.

This section is short because the pricing is not public and we did not research it this pass.

Path 3: replatform to a different eCommerce platform

Leaving is right when the upgrade has stopped being a version bump and become a rebuild. Every upgrade is a project rather than maintenance, and total cost of ownership is dominated by upkeep.

Or you cannot staff it at a price you will pay, or your requirements genuinely simplified since you chose Magento. If three describe you, put eCommerce replatforming services on the table.

Five store profiles that should stay on Magento

Five profiles should stay.

• Complex B2B catalogues. Company accounts, contract pricing and approval hierarchies are native to Adobe Commerce B2B features.
• Multi-store hierarchies. Website, store and store-view structures lack a clean equivalent, per Magento 2 multistore configuration.
• Deep ERP integration. A tested connector is the asset, so Magento ERP integration work restarts elsewhere.
• Large attributed catalogues. Many attribute combinations do not map cleanly elsewhere.
• Mid-peak timing. Nobody should cut a store over between October and January.

If two or more describe you, upgrade.

Where merchants who do leave usually land

Most merchants who leave Magento land on WooCommerce, and we will say so. Our Magento vs WooCommerce comparison sets out where each wins.

Run the destination choice as eCommerce platform selection work, scored against your own requirements. A destination decided under deadline pressure is the most expensive kind.

Path 4: document the risk and buy a quarter

If you cannot move before your next peak, the honest position is not that you are fine. It is that you write the risk down.

What a defensible risk acceptance contains

Tell your acquiring bank and your QSA exactly where you are, in writing. Apply what hardening you can at the WAF layer, which our Magento store security guide covers.

Put a dated commitment in front of your board, naming a target release.

2.4.6 stores sit better here than 2.4.5 stores. 2.4.6 still carries extended support to 31 August 2027 and security provisioning to 31 May 2028. Adobe calls that extension a one-time exception, so do not plan a second one.

2.4.5’s last ordinary phase ended on 11 August 2026. A documented, dated, temporary position is defensible. Silence is not.

What should you check this week?

Five checks you can finish before Friday decide which path you are on.

• Version and edition. Confirm both from the admin, not from memory.
• Third-party extensions. Count them and list the vendors behind them.
• Store views and websites. Count both, because each multiplies the work.
• Live integrations. List every one, including ERP, PIM, tax and gateway.
• Current PHP version. Compare it against your target version’s requirement.

Then check the second clock. php.net ends security support for PHP 8.2 on 31 December 2026. An unsupported Magento version on PHP 8.2 has two clocks expiring five months apart.

For a second opinion on which path fits, talk to the Virtina eCommerce team.

People also ask

Does Magento stop working after end of support?

No. The software keeps running and the licence stays valid while your account is in good standing. Adobe’s end-of-support FAQ says so directly.

What stops is patching, ticket resolution and further product changes.

Is Magento 2.4.6 still safe to run in 2026?

Not indefinitely. Every vulnerability found after 11 August 2026 is patched on supported lines and left open on yours. The public fix effectively documents the flaw.

Risk compounds from here rather than decaying.

How long does a Magento version upgrade take?

Agencies typically quote 2 to 6 weeks for a straightforward version upgrade. That is what agencies quote, not a figure we can verify. Effort scales with extension count, core overrides and store views.

Conclusion

Most readers should upgrade to a supported 2.4.x and stay on Magento. That is the smallest project on the list and the one we profit from least. The deadline is real and the panic version of it is not.

Replatforming is right for a narrow profile you can name in a sentence. If complex B2B, multi-store or a working ERP connector describes you, upgrade instead. And if you cannot move this quarter, write the risk down with a date on it.