Security patches only reach current releases
Adobe ships security patches for the current 2.4 releases only. A store that stays behind keeps every published vulnerability open, with your customer and payment data behind it.
Magento 2 upgrade & performance · Lead Magento 2 developer · Adobe Commerce Expert certified
Magento 2.4 upgrade, done safely.
PHP 8, security patches, performance. Fixed price.
I upgrade Magento 2 stores to the current 2.4.x release and PHP version, fix every extension and custom module that breaks on the way, and tune the stack so the store is measurably faster than before. Rehearsed on staging, switched in one planned window, quoted as a fixed price after a short audit.
- Adobe Commerce Expert
- 20 years in e-commerce
- Open Source, Adobe Commerce, Mage-OS
- Toptal network since 2019
Why upgrade now, not next year
An outdated Magento is not a cosmetic problem. It is unpatched vulnerabilities, a PHP version your host wants to retire, extension vendors that stopped testing against your release, and a store that gets slower while the gap to the current version gets more expensive to close.
PHP and the rest of the stack move on
Hosting providers retire old PHP versions, extension vendors stop supporting them, Elasticsearch gave way to OpenSearch. Each year you wait, the jump gets bigger. PHP 8 alone is noticeably faster than 7.x.
Slow Magento is usually a configuration problem
Most slow stores I see are not slow because of Magento. They are slow because of misconfigured caches, indexers running on save, cron piling up, heavy queries and third-party extensions. An upgrade is the right moment to fix that, and to measure it.
What the upgrade includes
The fixed quote covers everything below. Anything outside it is named in the quote before you sign, not discovered during the project.
- Pre-upgrade audit Current Magento, PHP, database and search versions, every third-party extension and custom module, applied patches, server setup and a performance baseline. You get a written report and a fixed quote.
- Core upgrade Magento Open Source, Adobe Commerce or Mage-OS to the current 2.4.x release, with the matching PHP 8, MySQL or MariaDB, OpenSearch, Redis, Varnish and Composer versions.
- Extensions and custom code Third-party extensions updated, replaced or removed; custom modules fixed for deprecated APIs and PHP 8; dead code and unused modules dropped.
- Security All Adobe security patches applied, admin and API hardening checked, known-vulnerable packages replaced, two-factor authentication and admin URL reviewed.
- Performance tuning Full-page cache with Varnish, Redis for cache and sessions, indexers on schedule, cron cleaned up, slow queries and heavy extensions profiled and fixed.
- Measured before and after Server response time, Largest Contentful Paint and Lighthouse on the same pages and devices, recorded in the audit and repeated after go-live.
- Rehearsal and cutover Full upgrade run on a staging copy with production data, timed, then one planned production window with a rollback tested in advance.
- Go-live and 30 days of care Monitoring of errors, orders and performance after the switch, documentation of what changed, and fixes for anything the upgrade broke, free for 30 days.
How the upgrade runs
-
Audit and fixed quote
I check versions, extensions, custom code and server setup, measure the store, and send a written plan with a fixed price and a cutover date.
-
Upgrade on staging
The full upgrade runs on a staging copy of your production store. Broken extensions and custom code are fixed there, and you test your daily workflows.
-
Tune and measure
Caches, indexers, cron, queries and heavy extensions are tuned on staging. Before-and-after numbers go into a short report you can show your team.
-
Cutover and 30 days of care
The production switch happens in one planned window with a rollback ready. I watch errors, orders and performance afterwards and fix what the upgrade broke, free, for 30 days.
What it costs
Starting price below. The exact figure comes after the audit, fixed, and it does not move unless you change the scope.
Fixed price
Magento 2 upgrade & performance
Audit, core and PHP upgrade, extensions and custom code fixed, security patches, performance tuning, measured results, rehearsed cutover and 30 days of care.
from €3,500
Plan an upgrade →What moves the price
How many releases you jump: one patch release is a different job from a jump from 2.3. Then the number of third-party extensions and how well they are maintained, the amount of custom code, Adobe Commerce B2B features, and whether the hosting has to change too.
What is not included
Hosting fees and licences for paid extensions or Adobe Commerce. Redesigns and new features are quoted separately. If you also want to leave Luma behind, see the Hyvä migration, which combines well with an upgrade.
Questions about Magento upgrades
Which version should we upgrade to?
The latest 2.4.x release at the time of the project, with the PHP version Adobe supports for it. That is the line that receives security patches. If a critical extension is not ready for the newest release yet, the audit says so and we decide together whether to wait for the vendor or replace the extension.
Will the store be down during the upgrade?
Not during the project; all work happens on a staging copy. The production cutover is one planned maintenance window, usually one to two hours at a quiet time in your time zone, with a rollback plan that has already been tested on staging.
We are several versions behind. Is that a problem?
It is normal, and it is the most common starting point. A jump from 2.3 or an early 2.4 release brings extra steps: OpenSearch becomes mandatory, PHP moves to 8, MySQL to 8, and more extensions need replacing. The audit covers all of it and the quote stays fixed.
Can you make the store faster without upgrading?
Yes, if your version still receives security patches. Performance tuning on its own starts with the same audit and the same before-and-after measurement. In most slow stores, though, outdated PHP and extensions are part of the problem, so the upgrade and the tuning usually belong together.
Tell me which version you are on
Send your store URL, the Magento and PHP version if you know them, and what bothers you most: security, a slow store, or a vendor that stopped supporting your release. I reply within one business day.