A Magento upgrade the shop does not notice.
The work is not in the upgrade itself. It is in finding out which module still works afterwards.
Short answer
A Magento upgrade takes a shop to a newer release of Magento 2.4, with the matching PHP version and security improvements. Adobe supports each release for three years; after that there are no more patches. Jevana first checks every module against the new version, runs the upgrade on a staging environment, tests ordering and paying, and only then switches the live shop.
Patch, update or upgrade
| Type | What it is | How often | How much work |
|---|---|---|---|
| Security patch | Closes a flaw, changes nothing else | A few times a year | Small, part of maintenance |
| Module update | New version of a single component | Ongoing | Small to medium |
| Upgrade | New release of Magento itself | Available about yearly | A project |
You recognise a patch by an addition such as -p4 after the version number. An upgrade shows in the last digit: from 2.4.7 to 2.4.9.
Where Magento stands now
- Latest release
- Magento 2.4.9, released on 12 May 2026.
- Support
- Three years per release. For 2.4.8, from April 2025, it runs into 2028.
- Out of support
- Regular support for 2.4.6 ended in August 2026.
- Source
- The overview with dates from Adobe itself. We check it before we plan an upgrade.
How we do an upgrade
- 01
Check
Every module and every custom change is checked against the new version. You get the list.
- 02
Trial run
The upgrade on staging, with a copy of the real shop. This is where what is going to break, breaks.
- 03
Repair
Update, replace or adapt modules until everything works.
- 04
Test
Search, ordering, paying, shipping, the integrations. By us and by you.
- 05
Switch over
At a time with few visitors. The old version stays ready.
Questions
How often does a new Magento version come out?
Adobe releases a new Magento 2.4 version about once a year, and in between a few security patches a year for all supported releases. The patch dates are announced in advance. You do not have to follow every new release straight away, as long as the version you run still receives patches.
What is the risk of falling behind on updates?
The risk is that known flaws stay open. As soon as Adobe releases a patch, attackers can also see what was vulnerable, and unpatched shops are scanned automatically within days. The usual results are stolen customer data or a script that reads payment details. In time, payment providers also refuse shops that do not meet security requirements.
Can an upgrade happen without closing the shop?
Largely. Preparation and testing happen on staging while the shop stays open. The switch itself needs a short maintenance period, which we plan for the quietest moment of the week. Orders that come in until then are carried over. If something goes wrong, we put the previous version back.
Our shop runs a version that is no longer supported. What now?
Then the upgrade comes first, ahead of any other wish. We start with an inventory of modules, because that decides how big the job is. If the jump spans several releases, we go to the latest in one move, not step by step. In the meantime we can close the best-known flaws at server level.
Is Magento at the end of its life?
No. Magento 1 stopped in June 2020, and that is where the confusion comes from. Magento 2 is actively developed: release 2.4.9 is from May 2026 and is supported until 2029. What does expire are the individual releases, each after three years. There is also Mage-OS, a community-maintained release of the same code.
Goes well with
-
Magento maintenance and support
Patches, updates, monitoring and a contact for outages, for a fixed monthly amount.
-
Magento migration
From Magento 1 or another platform to Magento 2, with products, customers, orders and search visibility carried over.
-
Magento security
Cleaning up a hacked shop, and setting up a healthy one so a flaw does not become a data breach.
-
Hyvä
A Magento frontend that loads a fraction of the JavaScript. We build and migrate Hyvä themes.
Tell us what you run.
An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.
or email info@jevana.systems