Still on Magento 2.4.6 or older? Here is the upgrade path.
Regular support for 2.4.6 ended on 11 August 2026; 2.4.4 and 2.4.5 have had no fixes since 2025. The current lines are 2.4.8 and 2.4.9. An upgrade is a project with a fixed quote: compatibility audit, staging upgrade, tests, release. The free check reads your version from the outside, so start there.
Adobe Commerce customers have paid extended support (2.4.6 to 31 August 2027). Magento Open Source does not.
| Line | Standard support |
|---|---|
| 2.4.4 | ended 12 April 2025 |
| 2.4.5 | ended 12 August 2025 |
| 2.4.6 | ended 11 August 2026 |
| 2.4.7 | ends 31 May 2027 |
| 2.4.8 | ends 31 May 2028 |
| PHP 8.1 | ended 31 December 2025 |
| PHP 8.2 | ends 31 December 2026 |
| PHP 8.3 | ends 31 December 2027 |
| 2.4.9 | current line, supported to 31 May 2029 |
Source: Adobe Commerce lifecycle policy and php.net. The free report shows the dates that apply to your store.
Four things an unsupported store carries.
- No security patches
Open Source stores on 2.4.6 and older get nothing from Adobe any more. Every new vulnerability stays open until you upgrade, and card data flows through that store.
- PCI DSS and your payment provider
An unsupported platform is a finding in a PCI questionnaire. Payment providers and insurers ask; "we are upgrading" is the answer they want to see dated.
- Extensions stop being updated
Vendors drop old lines first. Fixes and new versions land on 2.4.7 and up, so every month on 2.4.6 makes the eventual move bigger.
- PHP and the server
Old lines pin old PHP. PHP 8.1 lost security support at the end of 2025; a store on it runs an unpatched runtime, whatever Magento version it has.
Four steps, staging first.
A typical store (one or two store views, 20 to 40 extensions, a few custom modules) takes 40 to 120 hours from 2.4.6 to 2.4.9, most of it extension work and testing. Stores on 2.4.4 or 2.4.5, or with many custom modules, take longer. The fixed quote follows the compatibility audit, in two working days.
- Fixed price, agreed before work starts
- Done on staging; your window for the release
- Hyvä at the same time? See the migration page; doing both in one project saves a round of testing.
- Compatibility auditEvery extension and custom module checked against the target release (2.4.8 or 2.4.9), PHP, OpenSearch, Composer 2 and the database version. You get the list: compatible, update needed, replace, drop.
- Staging upgradeA copy of production upgraded on staging, with the extension updates, the PHP move and the data patches. Nothing touches the live store.
- Regression testsCheckout with every payment method, shipping, promotions, indexing, cron, admin workflows, integrations (ERP, PIM, search). Your team tests the parts only they know.
- ReleaseIn your maintenance window, with a rollback plan. Monitoring for the first days, then the monthly plan keeps the store on a supported line.
See what is slowing your store down
Free, no call. Results by email within one working day.