Upgrade plan
An audit of your version, PHP, MySQL or MariaDB, OpenSearch, Redis and Varnish, with the target release and what has to change.
Magento & Adobe Commerce upgrades
Magento upgrades, without the drama.
Moving to a newer Magento 2.4 release, or getting off an old one, means checking every extension, theme override and custom module against the new version. I do that work on staging, fix what breaks, and you approve before anything goes live.
What's included
What I'll do for you.
Extension compatibility
Every third-party module checked against the target version: updated, patched or replaced where the vendor has stopped.
Custom code fixes
Your own modules and theme overrides updated for changed core classes, deprecated APIs and newer PHP.
Hyvä and headless
Upgrades for Hyvä themes and headless storefronts, with the GraphQL schema checked against your frontend.
Adobe Commerce Cloud
Upgrades through the Cloud pipeline, including services and ece-tools changes.
Staging sign-off
Checkout, payments, search, imports and integrations tested on staging. You approve before the production release.
How it works
Safe by default.
AI agents help me investigate, draft and test faster. A person still approves every step that matters.
- 01
Tell me the problem
Describe it in plain words by phone, Slack or email, and share staging or log access.
- 02
Diagnose and agree
I find the cause and agree the plan and estimate with you before any code is written.
- 03
Fix and review
The change is built and tested, then I review every line before you see it.
- 04
You approve on staging
You try it on staging. It goes live only when you say so.
Experience
From projects I've led and worked on.
- ETB Technologies: around 40 custom modules kept current through Magento upgrades.
- Trade Radiators on Adobe Commerce Cloud 2.4.6, and Goodfellow Reference Materials on Adobe Commerce Cloud 2.4.7.
- Leicester City FC: a headless Magento 2.4 store with a Nuxt storefront, upgraded without breaking Kit Builder or the EPOS integration.
FAQ
Questions, answered.
How long does a Magento upgrade take?
It depends on how far you're jumping and how many extensions and custom modules you run. A minor 2.4.x upgrade on a tidy store is much quicker than a jump across several releases with dozens of modules. I give you a written estimate after reviewing the codebase.
Will my extensions still work after the upgrade?
I check each one against the target version before we start. Most vendors ship compatible releases; where one hasn't, I patch it, find a replacement or rebuild the feature, and agree that with you first.
Do you upgrade on the live site?
No. All upgrade work happens on staging. Production is only touched for the release itself, at a time you choose, with a rollback plan ready.
Can you upgrade Adobe Commerce Cloud and Hyvä stores?
Yes. I work on Adobe Commerce Cloud projects and Hyvä storefronts, as well as headless Magento with Nuxt and Alokai.
Can I try you out before committing to an upgrade?
Yes. The first task is free: up to two hours, for example an upgrade feasibility review that lists which extensions and custom modules will need work.
First task free
Judge my code
before you pay for it.
Send me a bug, a slow page or a small fix, up to two hours of work. I'll do it on your staging site at no cost.
Claim your free task