We upgrade Magento Open Source and Adobe Commerce stores from 2.3.x and early 2.4.x releases to Magento 2.4.9, including PHP, OpenSearch, MySQL/MariaDB and third-party extension compatibility. Every upgrade is rehearsed on staging, tested against your real checkout flows and shipped with a rollback plan.
Every Magento minor release has a published support window. Once a version leaves support it stops receiving security patches, and your store carries the risk. Under Adobe's lifecycle policy, standard support for Magento 2.4.6 ended on 11 August 2026, 2.4.7 is supported until 31 May 2027, 2.4.8 until 31 May 2028 and 2.4.9 until 31 May 2029.
Older versions also lock you into older infrastructure. Magento 2.4.8 removed PHP 8.1 and moved search to OpenSearch, and 2.4.9 adds official PHP 8.5 support, Symfony 7.4 LTS and Composer 2.4 compatibility. Hosting providers retire old PHP and database versions on their own schedule, so delaying an upgrade often turns a routine job into an emergency.
There is also a compliance angle. If you take card payments, PCI DSS 4.0 requires you to control and monitor scripts on payment pages. Magento 2.4.7 and later ship Content Security Policy restrictions and Subresource Integrity support for checkout that make those controls practical.
Whether you are one patch behind or several minor versions, the method is the same: audit, rehearse, fix, verify, release.
The most common path. We move stores on 2.4.4–2.4.8 to the current release and latest security patch, update PHP and services, and resolve every compatibility issue the upgrade exposes.
Older 2.3 stores need more care: Elasticsearch or OpenSearch becomes mandatory, two-factor authentication arrives for admins, and PHP jumps several versions. We plan these as a staged project.
Need to stay on your current minor version for now? We apply isolated security patches and quality patches so you remain protected while you plan the full upgrade.
We move your stack to supported PHP, MySQL 8.4 or MariaDB 11.4, OpenSearch, and Valkey or Redis, and configure them properly for production traffic.
Third-party modules are the main source of upgrade pain. We check each module against the target version, update from vendors, patch abandoned modules, or replace them.
For Adobe Commerce on cloud infrastructure we work with ECE-Tools, the cloud patches package and your integration and staging environments to upgrade safely.
Standard support dates published in Adobe's Commerce lifecycle policy. If your version is near or past its date, it is time to plan an upgrade.
Standard support ended 11 Aug 2026. Extended support for Adobe Commerce runs to 31 Aug 2027.
Standard support until 31 May 2027. Plan your upgrade during the next 6–9 months.
Standard support until 31 May 2028. Supports PHP 8.2–8.4 and OpenSearch 2.
Latest release. Standard support until 31 May 2029. Supports PHP 8.5.
Source: Adobe Commerce lifecycle policy. Dates can change; we confirm current dates during your upgrade audit.
Most failed upgrades share the same causes: no staging rehearsal, untested extensions and a rushed release. Our process removes each of them.
We run the full upgrade on a copy of your production database and media first. Your live store is untouched until the release window.
Before any code changes you receive a list of every module, its status on the target version and the fix we propose, with an estimate.
Upgrades are delivered as Composer changes and version-controlled code, so the same steps run on staging and production with no manual edits.
Database backup, code tag and a tested rollback procedure are agreed before go-live. If something unexpected happens, we can revert quickly.
A typical 2.4.x to 2.4.9 upgrade takes two to five weeks depending on the number of extensions and the amount of custom code.
We review composer.json, installed modules, custom code, theme overrides, hosting stack and integrations. We run Adobe's Upgrade Compatibility Tool where applicable and produce the compatibility report.
A staging environment is created with the target PHP, database, OpenSearch and cache versions, and loaded with a sanitised copy of production data.
Core and vendor packages are updated through Composer. We fix deprecated code, update or patch extensions, and re-test theme overrides against changed core templates.
Search, product pages, cart, checkout, payments, tax, shipping, customer accounts, admin order flows, imports and integrations are tested and signed off by you.
We deploy in a low-traffic window, reindex, warm caches and monitor logs, errors and conversion signals for a week after go-live.
Not sure how big the upgrade is? Start with an audit of code, extensions and infrastructure.
Learn moreSecurity patches, hardening and PCI DSS 4.0 checkout script controls.
Learn moreSend us your Magento version, store URL and a list of installed extensions if you have one. We will reply with the likely effort, risks and a recommended upgrade path.
Within one business day, Mon–Fri
No obligation. We reply within one business day.