
Magento Upgrades
Get onto a supported version, and get your retainer back
We’re a Magento agency and an Adobe Commerce Bronze Partner, working with brands doing £2m or more online. We upgrade Magento 2 and Adobe Commerce stores, and most of our Magento clients have been through upgrades with us. Our lead developer is Adobe-certified. If you’d rather plan it in person, we’re right next to Piccadilly station in Manchester.
You know the upgrade needs doing. It keeps moving down the list. The last one took longer than anyone said, and peak is always a few months away. Meanwhile the store sits another version behind, and the next patch is harder to apply than the last.
So we scope it properly first. Every extension, customisation and integration gets tested on a staging copy of your store, and the go-live date stays clear of your busy weeks.
Most projects start with an NNP Workshop, which gives you a ranked list of what to fix and what each fix is worth.
Which versions are still supported?
Adobe publishes the dates on its released versions page. This is where they stand:
| Version | Regular support ends |
|---|---|
| 2.4.6 and older | Already ended (2.4.6 on 11 August 2026) |
| 2.4.7 | 31 May 2027 |
| 2.4.8 | 31 May 2028 |
| 2.4.9 | 31 May 2029 |
PHP has its own clock. PHP 8.2 stops getting security fixes on 31 December 2026, and each Magento release only runs on certain PHP versions, so the two usually get planned together. Your host patches the servers and PHP, and we look after the application on top.
To see what you’re on, check the bottom right of any page in your Magento admin. What losing support means for your store goes through the rest.
What’s included in a Magento upgrade?
A written scope first
We go through your extensions, custom code and integrations. Then we tell you what needs updating, what needs replacing and what you can drop. You’ll know the size of the job before you commit to it.
Extensions dealt with properly
Extensions cause most of the work on an upgrade. Plenty will have a compatible release. Some will have been abandoned, and those need replacing. Most long-running stores also have a few doing nothing at all, and every one you drop is one you never have to test again.
The upgrade, on staging
Your store’s upgraded on a staging copy, so your customers don’t see any of it. We fix what comes up there.
Testing what makes you money
We run through checkout, payments, your ERP and warehouse connections, and the journeys your customers actually use, before anything goes live.
A go-live you’ve picked
We agree the date with you, away from your busiest weeks. For most retailers, that means somewhere between January and the end of summer.
Should you move to Hyvä at the same time?
If you’re still on Luma, it’s the cheapest moment to do it. An upgrade and a Hyvä move both need the same regression testing, so one project saves you paying for it twice. Hyvä migration replaces the slow part of the store your customers actually feel, and it’s where a technical job starts paying for itself.
Willow & Hall show what that looks like. They’d stayed on Magento 1 until Adobe stopped supporting Opayo on it. That decided the timing for them. We moved them to Magento 2 on Hyvä, the site got 80% faster and sales went up 15%.
Conversion Rate Reached
Increase in Sales
Faster than their old website
Do you need to replatform instead?
Almost certainly not because of a support date. An upgrade costs a fraction of a migration, and plenty of Magento stores asking to leave are really fighting an old theme and a pile of extensions. If you’ve properly outgrown the platform we’ll tell you, and what it costs to run Magento 2 will help you weigh it up.
What happens after the upgrade?
You’ve got two choices. You can leave it there, and come back when the next version needs doing. Or you can put it on a Magento support retainer. We apply security patches the day Adobe releases them and keep you current, so you never face a big jump again.
Either way, the time your developers spent on patch panics can go on growing the store.
What our clients say
"What impressed us most was how quickly Actuate identified the root cause. Within the first call they'd spotted the metadata issue that had been tanking our traffic. Everything that followed has been just as sharp."
I like working with Actuate because they care about what they do, they clarify the detail to get the job done right. They have worked incredibly hard with our complex needs and have been on hand for help and advice every step along the way...
Without Actuate's help and support, our original website wouldn’t have succeeded. Time was of the essence, and Actuate stepped in to deliver a swift turnaround. The new site has performed exceptionally well ever since. We continue to grow thanks to Actuate. ❤️ Thanks guys!”
Their team leverages their expertise to provide sound opinions and advice to guide the project in the right direction.
I worked with Actuate on the redevelopment of the Pickett London website. Their team is an excellent asset for any company or team, it was a pleasure to work with them - easy to communicate with, easy to reach and always willing to help.
Working with Actuate is a pleasure — they are really trying to help, they listen and offer solutions to solve the problems. Thanks for all your help so far.
We've worked with Actuate for several years and the results have been consistent. Conversion rate up 113%, AOV up, bounce rate down. They know our business inside out, and it shows.
Frequently Asked Questions.
Ask my questionIt depends on how far you’re jumping and how many extensions and customisations you’ve got. Moving from 2.4.7 to 2.4.8 on a tidy store is a far smaller job than jumping several versions on a store with dozens of extensions. We’ll give you a timeline in the written scope.
Usually the latest release your extensions support, as that gives you the longest runway before the next upgrade. Today that’s 2.4.9 for most stores.
We do the work on a staging copy and test it there, so your customers won’t see it until the planned go-live.
Often, yes. Each Magento release only runs on certain PHP versions, and older PHP versions lose security fixes on their own timeline. We’ll plan both together with your host.
Technically, yes. In practice you’ll be without security patches, extension updates get harder to find and your payment provider may start asking questions. The cost and the risk grow every month.
Yes, both. They share the same release schedule, though Adobe Commerce licence holders can get extended support on some older versions.
Tell us what's getting in the way
Tell us a bit about your site and what you want it to do next, and we'll come back to you with what we'd look at first.
"*" indicates required fields