On December 31, 2026, PHP 8.2 stops getting security fixes. PHP is the programming language Magento is written in, and 8.2 is the newest version that Magento 2.4.6 can run on. Adobe’s own standard support for 2.4.6 ended on August 11, 2026, and 2.4.7 loses it on May 31, 2027, so for a store on either version, how to upgrade Magento (Adobe Commerce) has become a question with a date on it.
Standard support is the period when Adobe still releases quality fixes and security patches for a version. Adobe Commerce licenses get one more year on 2.4.6 and 2.4.7, and Magento Open Source stores don’t. The longer a store waits, the bigger the jump gets, and the real question is whether your extensions and your server will come through it.
How to upgrade Magento: the steps at a glance
To upgrade Magento (Adobe Commerce), check your version, bring PHP, the database, search and cache up to what the target release needs, and test every extension on a staging copy with a full backup. Then turn on maintenance mode, run composer require-commerce and composer update, run setup:upgrade, rebuild code and static files, and test before you release.
- Check your version with
bin/magento --versionand pick the target release (2.4.9, or 2.4.8 if an extension isn’t ready). - Bring the server up to the target’s requirements: PHP, the database, OpenSearch and Valkey.
- Check every extension and custom module against the target version.
- Back up the database, code and media, and make a staging copy of the store.
- Turn on maintenance mode, stop cron and let the message queues finish.
- Run
composer require-commercewith the new version, thencomposer update. - Run
setup:upgrade, compile the code and deploy static files. - Test the store, turn maintenance mode off and release with a rollback plan.

Check your Magento version and when its support ends
Run bin/magento –version to see your exact release. Adobe gives each Magento 2.4 release three years of standard support: 2.4.6 lost it on August 11, 2026, 2.4.7 loses it on May 31, 2027, 2.4.8 on May 31, 2028 and 2.4.9 on May 31, 2029. Adobe Commerce licenses get one extra year on 2.4.6 and 2.4.7.
To check your Magento version, run the first command from the store root. The second lists the 2.4 releases Composer can move you to. On Adobe Commerce, the package is magento/product-enterprise-edition.
bin/magento --version
composer show magento/product-community-edition 2.4.* --available | grep -m 1 versionsThe extended year on 2.4.6 and 2.4.7 is for Adobe Commerce customers only, so a Magento Open Source store on 2.4.6 has been outside Adobe’s support since August 11, 2026.
Adobe sends hotfixes for critical security issues only to supported versions, which is why stores on older releases needed a separate StyleSmuggler fix for older Magento versions. A store still on Magento 1 needs a move to Magento 2 first, covered in our Magento 2 migration guide.
The jump also grows with every release you skip. Adobe says regular updates take less effort overall than infrequent ones, because technical debt builds up in between.

For the extended and security-only periods of every 2.4 release, see our guide to Magento end of life dates.
๐ Quick takeaway
Plan backward from your version’s date. Standard support for 2.4.7 ends on May 31, 2027, and 2.4.6 is already past its date, so a store on either should book the upgrade now.
What Magento 2.4.9 needs on your server
Magento 2.4.9 runs on PHP 8.5, with PHP 8.4 allowed only for the upgrade itself. Adobe’s system requirements list MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9, Composer 2.10, Varnish 8 and nginx 1.30 for it. Redis cache isn’t supported on 2.4.9, and Elasticsearch isn’t listed, so plan both moves before the upgrade.
Adobe supports only the combinations it lists. The table compares the latest 2.4.8 patch with 2.4.9 for on-premises stores.
| 2.4.8 (latest patch, 2.4.8-p5) | 2.4.9 | |
|---|---|---|
| PHP | 8.4, 8.3 | 8.5 (8.4 for the upgrade only) |
| MariaDB | 11.4, 11.8 | 12.3 |
| MySQL | 8.4 | 8.4 |
| Search | OpenSearch 3 | OpenSearch 3 |
| Cache and sessions | Valkey 8.1 | Valkey 9 |
| Composer | 2.10 | 2.10 |
| Varnish | 8 | 8 |
| nginx | 1.30 | 1.30 |
| Message queue | RabbitMQ 4.3 or ActiveMQ Artemis 2 | RabbitMQ 4.3 or ActiveMQ Artemis 2 |
| Standard support ends | May 31, 2028 | May 31, 2029 |
Source: Adobe Commerce system requirements (on-premises), October 13, 2026.
If an extension has no 2.4.9 release yet, 2.4.8 on PHP 8.4 is a supported stop until May 31, 2028. For server sizing and the full matrix for every supported line, see our guide to Magento 2 system requirements.
PHP 8.5 and the database come first
PHP 8.4 is allowed for the upgrade only, and PHP 8.2 and 8.3 are no longer supported from 2.4.9. For the database, Adobe’s instruction is to upgrade to MariaDB 12.3 before you upgrade to 2.4.9. On MySQL, the latest 2.4.6 and 2.4.7 patches have no supported version, while 2.4.8 and 2.4.9 support MySQL 8.4. A move to MySQL 8.4 needs restrict_fk_on_non_standard_key set to OFF, or the import fails on foreign keys (see the errors section).
Valkey replaces Redis for the cache
Valkey is an open-source, Redis-compatible in-memory data store that Magento uses for its cache and sessions. Adobe states that Redis cache is not supported for 2.4.9, or for patch releases later than 2.4.5-p16, 2.4.6-p14, 2.4.7-p9 and 2.4.8-p4, and that Valkey takes over where Redis is not supported. Adobe ties the change to Redis 7.2 reaching end of support and to Redis licensing changes.
Code changes in 2.4.9 that can break extensions
Four changes in 2.4.9 reach code that extensions commonly touch: the WYSIWYG editor moved from TinyMCE to HugeRTE, Symfony Cache replaced the deprecated Zend_Cache, a native MVC implementation replaced Laminas MVC, and all Symfony dependencies moved to Symfony 7.4 LTS, with updated type declarations on classes that extend Symfony core classes. An extension that hooks into the editor, the cache layer or a Symfony class needs a 2.4.9 release from its vendor, or a patch.
๐ Quick takeaway
On 2.4.9, Adobe no longer supports Redis for the cache, so moving the cache to Valkey 9 is part of the upgrade. The same goes for patch releases after 2.4.6-p14, 2.4.7-p9 and 2.4.8-p4, so even staying on your current line means changing the cache.
Check extensions and custom code before you upgrade
Before you upgrade Magento, list every extension and custom module and confirm that each one supports the target version. On Adobe Commerce, Adobe’s Upgrade Compatibility Tool scans the code and returns the critical issues, errors and warnings to fix first. On Magento Open Source, composer why-not shows which installed packages block the new version.
Start with composer show, which prints every installed package with its version. For each extension, open its Commerce Marketplace listing or the vendor’s page and check the Magento versions it supports. Adobe’s advice for any extension that needs an update is to work in a new branch with your extensions disabled.

An upgrade is a good moment to remove extensions nobody uses, and our list of Magento 2 extensions every store needs helps decide which to keep.
On Adobe Commerce: run the Upgrade Compatibility Tool
The Upgrade Compatibility Tool checks a customized Adobe Commerce instance against a specific version and returns the critical issues, errors and warnings to fix before upgrading. The target version is a required parameter:
bin/uct upgrade:check <dir> -c 2.4.9Add --ignore-current-version-compatibility-issues to see only the issues the jump from your current version introduces.
On Magento Open Source: ask Composer what blocks the upgrade
Adobe makes the tool available for Adobe Commerce instances only. On Magento Open Source, Composer’s why-not command tells you which packages block a given package from being installed:
composer why-not magento/product-community-edition 2.4.9Each line names an extension to update, replace or remove. The tool is one of the differences covered in our Adobe Commerce vs Magento Open Source comparison.
Back up the store and set up a staging copy
Take a database dump and a copy of the code and media before you change anything, then run the whole upgrade on a staging copy of the store first. Adobe marks its built-in setup:backup command as deprecated and points to binary backup tools such as Percona XtraBackup. Strip customer data from the staging copy before developers use it.
A backup has three parts: a database dump, the code and the media files. Code belongs in Git, and the dump should come from a tool made for it, since Adobe lists bin/magento setup:backup as deprecated since 2.3.0 and disabled by default. Restore the dump once on another server, so you know the backup works.

Adobe lists prerequisites to meet before the upgrade starts:
- Convert all database tables from COMPACT to DYNAMIC row format, and from MyISAM to InnoDB.
- Set the open files limit (ulimit) to 65536 or more.
- Check that cron jobs are running.
- Install the Composer root update plugin with
composer require magento/composer-root-update-plugin ~2.0 --no-update, thencomposer update. It resolves the changes the root composer.json needs before a new product version.
Then build the staging copy with the same Magento, PHP, database, search and cache versions as production, and customer data removed. Every step in the next section runs there first. Our breakdown of the Magento 2 upgrade process covers how an upgrade project is planned and tested.
๐ Quick takeaway
Run the whole upgrade on a staging copy first, with customer data removed. Every error in the troubleshooting section below is cheaper to meet there than on the live store.
Run the Magento 2 upgrade with Composer
On an on-premises store, the Magento 2 upgrade runs from the command line through Composer, the PHP package manager. Turn on maintenance mode, stop cron, back up composer.json, run composer require-commerce with the target version, then composer update and setup:upgrade. In production mode, compile the code and deploy static files before you turn maintenance mode off.

Composer reads composer.json, works out which versions of every package fit together and downloads them. If Composer is new to you, our walkthrough of how Composer installs a package covers the basics. The commands below use magento/product-community-edition, and Adobe Commerce stores use magento/product-enterprise-edition instead. The same four steps move a store between patch releases, such as 2.4.8-p4 to 2.4.8-p5, or to the latest version from any 2.4 release.
1. Put the store in maintenance mode and stop cron
bin/magento maintenance:enable
bin/magento cron:remove
bin/magento cron:run --group=consumersMaintenance mode returns a 503 page to visitors. Add --ip=<address> for each person who needs to see the store meanwhile. Adobe warns that starting the upgrade while message queue consumers are running may cause data corruption, so remove the cron jobs, run the consumers group once and wait for it to finish.
2. Point Composer at the new version
cp composer.json composer.json.bak
composer require-commerce magento/product-community-edition 2.4.9 --no-update
composer updateThe copy of composer.json is your way back if Composer cannot resolve the new version. composer require-commerce replaces the old composer require for Magento packages. It accepts --interactive-root-conflicts to resolve conflicts in the root composer.json one by one and --force-root-updates to apply Adobe’s values. With neither flag, it keeps your existing values where they conflict and shows a warning, so read the output.
3. Update the database and rebuild the code
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf generated/code/*
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deployThe rm -rf lines clear the file caches and generated code, and if the cache runs in Valkey or Redis, clear it there too. setup:upgrade updates the database schema and data, setup:di:compile compiles the code, and in production mode setup:static-content:deploy writes the static files, because production mode does not generate them on request. Run every command as the file system owner, as Adobe requires.
4. Test the store and reopen it
Before you turn maintenance mode off, run your testing checklist from an exempted IP: the storefront pages, a test order through checkout and the admin screens your team uses. Then reopen the store, reinstall the crontab and confirm the version.
bin/magento maintenance:disable
bin/magento cron:install
bin/magento --versionRestart Varnish with service varnish restart if the store runs it. Adobe’s own check: if the storefront does not load properly, the upgrade was unsuccessful.
๐ Quick takeaway
Adobe changed the upgrade command from composer require to composer require-commerce, and its upgrade steps start by installing the magento/composer-root-update-plugin package. Do that first, before any version change.
Can you upgrade Magento from the admin panel?
No. Adobe deprecated and removed the Web Setup Wizard in 2.4.0, and its release notes say you must use the command line to install or upgrade from that version on. A manual upgrade from a downloaded archive remains a last resort for a server without Composer access.

How to upgrade Magento on Adobe Commerce Cloud
On Adobe Commerce Cloud, you run the upgrade in a Git branch and let the deployment apply it. Update the service versions in .magento/services.yaml, run composer require-commerce for the Commerce package and composer update, then commit and push. Service upgrades in Pro Staging and Production need an Adobe Support ticket and at least two business days’ notice.
An Adobe Commerce upgrade on Cloud is the same application upgrade, with the server work replaced by configuration files and Adobe’s deployment. Create a branch from the Integration environment, then update .magento/services.yaml with the versions the target needs for MariaDB, OpenSearch, RabbitMQ and Valkey or Redis, and .magento.app.yaml for new hooks and environment variables.
On Pro projects, Adobe Commerce Support installs or updates services in Staging and Production, so those environments need a Support ticket. Production changes require at least two business days’ notice, excluding weekends, and Staging requests are usually completed the same day. PHP version, Composer updates, extensions and environment settings are self-service. Validate the upgrade in Staging or Integration before scheduling Production, and plan a full reindex if OpenSearch is part of the change.
Then update the application in the branch:
# Only if the target is outside your current constraint
composer require-commerce "magento/magento-cloud-metapackage":">=CURRENT_VERSION <NEXT_VERSION" --no-update
composer require-commerce magento/product-enterprise-edition 2.4.9 --no-update
composer update
git add -A
git commit -m "Upgrade"
git push origin <branch-name>
# After deployment, on the environment
php bin/magento --versionB2B stores add composer require-commerce magento/extension-b2b <version> --no-update before composer update. Review the m2-hotfixes directory and the QUALITY_PATCHES list in .magento.env.yaml for patches that no longer apply. git add -A is required because of the way Composer handles base packages. A representative from your team or implementation partner must be online for the whole Production upgrade window.
Adobe’s recommended long-term route for Cloud customers is Adobe Commerce as a Cloud Service, where Adobe runs patching and upgrades itself.
๐ Quick takeaway
On Adobe Commerce Cloud, book the Production window early. Pro service upgrades need at least two business days’ notice, and from June 1, 2027 Adobe stops maintaining Cloud environments that run unsupported versions.
Common Magento upgrade errors and how to fix them
Most failed Magento upgrades stop at one of a few points: Composer can’t resolve the package versions, a command fails on file permissions, the server runs out of memory while compiling, or MySQL stops on a foreign key error after a database move. Each has a known fix, and meeting it on staging keeps the live store out of it.
“Your requirements could not be resolved to an installable set of packages”
Composer found a package with no release that fits 2.4.9. Restore the backup with cp composer.json.bak composer.json, run composer why-not magento/product-community-edition 2.4.9 to see which packages block the version, then update, replace or remove each one and run the require-commerce command again.
Permission errors in generated/, var/ or pub/static/
A command ran as the wrong user, often root, and the files it created now belong to that user. Adobe’s rule is that all Magento CLI commands must be run by the file system owner. Reset ownership of the affected directories to that user and rerun the command that failed.
The server runs out of memory while compiling
Adobe says upgrading applications and extensions can require up to 2 GB of RAM, and a system with less needs a swap file or the upgrade might fail. In our projects, raising the memory limit for the single command also helps: php -d memory_limit=4G bin/magento setup:di:compile.
“Failed to add the foreign key constraint” after moving to MySQL 8.4
This is MySQL ERROR 6125, and it appears when a dump is imported into MySQL 8.4 with default settings. From MySQL 8.4.0, foreign keys on non-unique keys must be enabled explicitly. Set restrict_fk_on_non_standard_key = OFF under [mysqld] and run the import again.
“We’re sorry, an error has occurred while generating this email.”
Adobe’s fix for this error after an upgrade: reset file system ownership and permissions as a user with root privileges, then clear var/cache/, var/page_cache/ and generated/code/ and reload the page. If it persists, check that setup:di:compile finished without errors.
Who should run your Magento upgrade?
Your own developers can run a Magento upgrade when someone on the team has done one before and the store has few custom modules. Large or heavily customized stores usually go to an agency. An AI agent can do the routine work on a copy of the store, while a developer reviews the changes and a person approves the release.
Run it in-house if:
- Someone on your team has run a Magento 2.4 upgrade before
- The store runs a handful of maintained extensions and little custom code
- You have a staging server that matches production
Hand it to an agency if:
- The store carries custom modules, a custom theme or ERP and PIM integrations
- The jump also moves PHP, the database and the cache
- You need a fixed scope and one team accountable for the release
For stores with custom modules or integrations, scandiweb’s Magento upgrade services plan the jump around your extension list and run it through staging to release.
Use Ari if:
- You want the routine upgrade work done on a copy of the store
- You have a developer or partner who reviews the pull request and releases it
Ari, the AI agent for Magento built by scandiweb, runs Magento upgrades on a store copy with customer data removed. It reads every module first, resolves the dependencies for the target version, and patches modules that have no compatible release while keeping their tests. Then it runs Composer, setup:upgrade, compilation, static content and the test suites on that copy, while the live store and its database stay as they are. You get one pull request with the diff, a module report and screenshots, and your developer reviews and merges it through your own staging and release. Plans start from โฌ99 a month per store.

Frequently asked questions about how to upgrade Magento
How can I upgrade Magento 2 to the latest version?
Check that your server meets the new release’s requirements, test your extensions on a staging copy, then run composer require-commerce magento/product-community-edition 2.4.9 –no-update (product-enterprise-edition on Adobe Commerce), composer update and bin/magento setup:upgrade. In production mode, compile the code and deploy static files, then confirm with bin/magento –version.
What is the latest version of Magento?
Magento 2.4.9 is the latest release, out since May 12, 2026 for both Adobe Commerce and Magento Open Source. Adobe supports it until May 31, 2029. The latest patches for older lines are 2.4.8-p5, 2.4.7-p10 and 2.4.6-p15, and 2.4.10 is in alpha.
Can I skip versions when upgrading Magento?
Within 2.4 you can usually go straight to 2.4.9 with one composer require-commerce, as long as the server meets 2.4.9’s requirements first. Adobe names two exceptions: a store below 2.4.1 must first move to a Composer 2-compatible release such as 2.4.2, and a 2.3 store going to 2.4.6-p13 needs the magento/inventory-composer-installer package first.
Do I need to upgrade PHP before upgrading Magento?
Yes. PHP has to be on a version the target release supports before you run Composer. Magento 2.4.9 runs on PHP 8.5, allows PHP 8.4 only for the upgrade itself, and dropped PHP 8.2 and 8.3. PHP 8.2 also stops getting security fixes on December 31, 2026, which Adobe flags as a PCI compliance risk.
Will my store go offline during a Magento upgrade?
Only while maintenance mode is on during the production deployment. In that window Magento returns a 503 maintenance page, and you can let your own team in with bin/magento maintenance:enable –ip=<address>. The rest of the work happens on staging. On Adobe Commerce Cloud, the store also runs in maintenance mode during each deployment.
Is the Upgrade Compatibility Tool available for Magento Open Source?
No. Adobe says the Upgrade Compatibility Tool is available for Adobe Commerce instances only. Magento Open Source teams check compatibility with composer why-not, each vendor’s release notes for the target version, and a full setup:di:compile run on a staging copy, which shows code that no longer compiles against the new release.
How long does a Magento upgrade take and what does it cost?
In scandiweb’s projects, a clean jump between 2.4 releases usually takes two to four weeks and costs $3,000 to $8,000. A bigger jump with an extension audit takes four to eight weeks and $15,000 to $40,000. Extensions and custom code decide where a store lands, and most of the time goes into testing on staging.
Can I roll back a Magento upgrade?
Yes, if you restore the backup you took before the upgrade. Running composer require-commerce with the old version often isn’t enough, because setup:upgrade has already changed the database schema and data. Keep the database dump, the previous code release and composer.json.bak until the new version has run cleanly in production for a while.
Plan your Magento upgrade before the support date
Knowing how to upgrade Magento comes down to order: find your version’s support date, bring the server up to the target release, clear every extension on a staging copy, and only then run Composer on production. Starting a few months before that date leaves time to test 2.4.9 properly and fix what the tests find.
On Adobe Commerce Cloud, add the Support ticket lead time to that plan. scandiweb has 23+ years in eCommerce and 894+ Adobe certifications. If your team would rather not run the jump to 2.4.9 itself, our Magento support team can review your extension list and plan the upgrade around your support date.
Not sure what will break on the way to 2.4.9? Send us your extension list and we will map the upgrade with you.






























Share on: