Magento Upgrade Calculator

It depends on the same things the calculator rates: how many release lines the store crosses, the extensions, the custom code, the storefront, the integrations and the number of store views. We quote a fixed scope after we have read the store, so the number is about your code rather than an average.

The length follows the complexity. Most of the time goes into extensions, custom code and testing rather than the core itself, which is why the calculator lists what drives the rating. The written scope after our assessment carries the dates.

In most cases yes. Composer moves the store to the target release line in one upgrade, not through every line in between. What cannot be skipped is the change those lines made: to the database, the search engine, PHP and the APIs your code relies on.

Adobe's system requirements list PHP 8.5 for 2.4.9, which makes it the first line on 8.5. Check that your host offers it before choosing 2.4.9 as the target.

Adobe lists PHP 8.3 or 8.4, MariaDB 11.4 or 11.8 or MySQL 8.4, OpenSearch 3, Valkey 8.1, RabbitMQ 4.3 and Varnish 8 for the newest 2.4.8 patch. The table on this page has every line.

Regular support for 2.4.7 ends on 31 May 2027, for 2.4.8 on 31 May 2028 and for 2.4.9 on 31 May 2029, per Adobe's lifecycle policy. 2.4.6 is past regular support and on extended support until 31 August 2027. The calculator counts the days for your line.

The store keeps running, but new security fixes stop arriving in that line's regular releases, extension vendors stop shipping for it and hosts retire the PHP it needs. The risk grows quietly until a scan, a payment provider or an attacker forces the upgrade.

2.4.9 has the longest support, to 31 May 2029, but needs PHP 8.5 and, per Adobe, a MariaDB upgrade before the move. 2.4.8 is supported to 31 May 2028 and runs on PHP 8.3 or 8.4. The hosting you can get and the extensions you depend on usually decide it.

It is closer to a replatform. The service runs no Luma theme and allows no code inside the core, so customisations are rebuilt outside it with App Builder, API Mesh, webhooks and events. The calculator rates it accordingly.

Only if each one has a release built for the target line. Most active vendors ship one; some have gone quiet. We check every module against its vendor's releases first, then patch, replace or remove the ones that have no compatible version.

No. A Luma theme keeps working, but its template overrides are checked against every release. Some stores use the upgrade to move to Hyvä, which became free and open source in November 2025.

The requirements and support dates come from Adobe's own pages and were checked on 2 November 2026. The complexity rating is a weighted reading of your answers, not a quote: it tells you what to look at first, and our assessment replaces it with facts from your code.

No. The calculator runs in your browser. Nothing leaves the page unless you press Send This to Our Team and then submit the contact form, which shows you the summary first.