Magento 2 and Adobe Commerce upgrades
Magento 2.4.9 upgrades for stores that can't afford to stop
Patched, supported and quicker, without a weekend of broken checkout. We take Magento 2 and Adobe Commerce stores to 2.4.9, PHP 8.4 and OpenSearch in one go. Every module gets checked, the upgrade happens on a copy of your live store, and we fix whatever breaks there. Then we test each store view and release in a quiet slot, with the old version ready to put back. Once the scope is clear you get a fixed price, and afterwards a changelog of everything we touched. The release date fits around your trading calendar.
- Four-language B2B store moved to 2.4.9
- Elasticsearch to OpenSearch included
- Fixed price once the scope is known
- Released with a way back
4
Store languages moved to 2.4.9 on one B2B store
0
Console errors after launch on that store
PHP 7.4 → 8.4
Out-of-support PHP replaced on a hacked store
Magento 2.4.x and Adobe Commerce stores several releases behind on security patches
Multi-store and multi-language shops with lots of third-party extensions
Merchants whose host is dropping Elasticsearch or their PHP version
Teams whose last upgrade stalled or got rolled back
Nobody wants to upgrade when nobody can say what will break. An extension licence has lapsed and Composer won't resolve. A payment module never got updated for PHP 8. Someone edited core files years ago. Elasticsearch has to go, because 2.4.8 onwards runs on OpenSearch. Every month you wait is another month of missing security patches, and your PHP version's support runs out in the meantime. The bigger the gap gets, the bigger the job.
signs-you-need-this.log
- ›You're on Magento 2.4.6 or older, or a PHP version close to end of life
- ›Composer fails because an extension licence or repository has gone
- ›An earlier upgrade was abandoned or rolled back
- ›Your host is dropping Elasticsearch or your PHP version
- ›Security scans keep flagging missing patches
- ›Nobody on the team knows which core files were changed
Upgrades go wrong on live when nobody tried them first. We run ours on an exact copy until the real release is boring.
- Step 01
Compatibility check
We list every custom and third-party module, theme and patch, check each one against the target Magento and PHP versions, and flag lapsed licences and abandoned extensions. You get a list of what upgrades cleanly, what needs fixing and what should be replaced.
- Step 02
Fixed-price plan
Once the check is done the scope is clear. We quote a fixed price and agree target versions for core, PHP, MySQL or MariaDB, OpenSearch and Redis, plus a release date.
- Step 03
Upgrade on a copy
We copy production to staging, upgrade core and dependencies, move Elasticsearch to OpenSearch and fix broken code by hand. Every catch gets written down, from store-view locale mismatches to PHP 8.4 deprecations.
- Step 04
Test it like a customer would
Real checkout with your payment methods, admin order flows, integrations, cron, indexers and each store view in a real browser. You sign it off on staging before live is touched.
- Step 05
Release with a way back
The tested code goes live in a planned slot outside your busy hours. Live settings and data stay as they are, and we can roll back until we've seen orders coming through.
- Step 06
Keep an eye on it
For a while after launch we watch logs, orders, search and cron, and fix anything that shows up under real traffic.
Pick your current version and roughly how many extensions you run. You'll see the upgrade path and what usually gets in the way.
Risk
Medium
Delivery
Planned release
Your path to 2.4.9 + PHP 8.4
- Compatibility audit of every module
- Upgrade to 2.4.9 on a 1:1 staging clone
- Elasticsearch → OpenSearch 2.x
- PHP 8.4, MySQL 8.4, Redis/Valkey tuning
- Switch-over practised on staging, old version kept ready
Likely blockers
- Some third-party modules will need patches
- Expired extension licences block Composer updates
- Elasticsearch is no longer supported in 2.4.9
Dead extensions don't stop us
A lapsed licence or an abandoned extension isn't the end of the upgrade. We patch it for the new PHP version, swap it for an alternative or rebuild the feature, and tell you which option will last best.
Everything in one go
Magento, PHP, MySQL, OpenSearch and Redis all move to supported versions together, so you aren't paying for another project in six months.
A fixed price after the check
You know the cost before we start. If something turns up that the check didn't catch, you hear about it before we do the work.
We look for malware while we're in there
Upgrades are when old malware tends to surface. On one routine upgrade we found hidden scripts earlier developers had missed, so now we check every time.
From our clients
Scopebit did an outstanding job upgrading our Magento store and resolving complex payment integration issues. Their experience shows, especially in payments, security, and checkout architecture. The job was handled professionally from start to finish.
Reviews from real clients. We leave their names off.
Related services
Malware removal & security
Skimmers and backdoors removed, the way in found and closed, and a report your payment provider can use.
Performance optimisation
Faster category pages, checkout and admin, with every change measured before and after.
Magento audit
A fixed-price look at security, code, speed and upgrade path, with findings sorted by what matters.
Support & maintenance
A monthly retainer with developer time set aside for you, plus patches, monitoring and first call on incidents.
Tell us what you're planning for the store.
You'll speak to one of the developers. We'll tell you which route we'd take, what usually goes wrong on projects like yours and where we'd start.
Happy to sign an NDA · Everything tested on staging first · The code is yours