Help for owners
My Magento 2 version is no longer supported and I need to upgrade
Short answer
Adobe says standard support runs three years from a version's release date, and that its published lifecycle page covers Adobe Commerce. Each release also needs matching PHP, database and search versions, so an upgrade is a platform change, not a button. Find your exact version first, then plan a tested upgrade on a copy.
Does this sound like your situation?
- My store runs an old Magento 2 version and I do not know if it is still supported.
- My developer says an upgrade will break extensions.
- My host will stop offering the PHP or database version I use.
- A card payment or security audit flagged old software.
- The store still works, so nobody has dared to touch it.
Why does this happen?
Each version has a support window
Adobe says standard support runs for three years from the General Availability date of each version and covers quality fixes, security patches and on-call support. A one-year extension and a security-only period are offered for selected versions, and Adobe says the transitional period will not be extended beyond published dates.
Confirmed by experienceleague.adobe.com
The support page covers Adobe Commerce
Adobe's lifecycle page says nothing about Magento Open Source support periods, so if you run Open Source, confirm your version's status with the Adobe release information and not by assumption.
Confirmed by experienceleague.adobe.com
Cloud stores face harder consequences
For Adobe Commerce on Cloud, Adobe says it will stop maintaining environments running unsupported versions, may suspend traffic, and that data can be permanently deleted and not restored if an environment stays non-compliant.
Confirmed by experienceleague.adobe.com
Newer versions need newer software
Adobe says it supports only the system combinations in its requirements tables, and that you must upgrade, for example, the database before the commerce version when the new version requires it. PHP, MariaDB or MySQL, search and cache versions all move together.
Confirmed by experienceleague.adobe.com
Extensions are the usual blockers
Adobe notes that vendor bundled extensions were removed from the core in the 2.4.4 line and have to be installed through the vendor. Third-party extensions that are not updated stop working with the newer core.
Confirmed by experienceleague.adobe.com
What can I do about it today?
- Find your exact versionLog in to the admin panel and read the version in the footer. Write it down with the PHP and database versions from your host.
- Ask your host what they supportWhich PHP and database versions are available, and until when?
- Export a list of your extensionsAsk your developer for the list with versions and vendors, and which are still maintained.
- Do not upgrade on the live storeA new version should be tried on a copy first, with a full backup.
- Check the support status in writingRead Adobe's lifecycle page and confirm in writing whether your version is covered.
- Plan a date outside peak salesHold changes before your busy season.
When should I bring someone in?
- Your version is out of support and the store takes payments.
- The upgrade has already failed once on a copy.
- Several extensions are old or the vendor has gone.
How do I handle it?
- Read the starting pointVersion, PHP, database, search engine, extensions and custom code are listed on one page.
- Choose the target by the requirements tableI pick the target version and software versions that Adobe actually lists together.
- Upgrade a copy firstThe upgrade runs on a copy of the store with a fresh backup of the live one.
- Deal with each extensionEach one is updated, replaced or removed, with your say on what the store still needs.
- Go live with a way backThe switch is planned with a tested rollback, then I check orders, payment and email.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is an old version unsafe?
Adobe says support includes security patches during the support period. Once a version leaves it, new fixes stop for that version, so risk grows with time.
Will the store go offline during the upgrade?
It does not need to if the upgrade is done on a copy and the switch is planned, but I cannot promise zero downtime for every store.
Can I stay on my version?
Some stores do for a time. It is a business and risk decision, and for cloud environments Adobe describes consequences for unsupported versions.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.