100+

Magento Upgrades Delivered

0

Data Loss Incidents

£100/hr

Billed to the Minute

100%

Staging-Tested First

Not sure what version you're running? Here's how to find out:

  1. Admin footer: Log into your Magento admin panel - the version number is displayed in the bottom-left corner of every page (e.g. Magento ver. 2.4.7-p3)
  2. System notifications: Navigate to System > Notifications - Adobe posts release notifications here when new versions are available
  3. Ask us: If you don't have admin access or aren't sure what the version number means, send us your store URL and we'll check for you - free of charge

If the version you see doesn't match the latest Adobe Commerce release, your store needs attention.

Known Security Vulnerabilities

Every missed release is a published exploit. Attackers actively scan for unpatched stores, and card skimmers, data breaches, and admin takeovers are real consequences.

Outdated PHP Versions

Old Magento means old PHP. End-of-life PHP receives no security patches, leaving the entire language your store runs on vulnerable.

Extension Incompatibility

Extension developers release updates alongside Magento. Miss one and you start missing them all, introducing their own security holes and bugs.

Performance Degradation

Each release includes query optimisations, caching enhancements, and rendering improvements. Older versions are measurably slower.

Upgrade Debt Compounds

Jumping one version is straightforward. Jumping five means resolving years of breaking changes, deprecated APIs, and extension conflicts.

Loss of Adobe Support

Adobe only supports the current release line. No help if something goes wrong, no access to the latest features and tools.

Your Magento version dictates which PHP version you run. PHP versions have a fixed support lifecycle - typically 2 years of active support followed by 1 year of security-only fixes. After that, no patches are released at all.

Here's why this matters:

  • PHP 7.4 - End of life since November 2022. No security patches for over 3 years. Still required by Magento 2.4.3 and earlier.
  • PHP 8.1 - End of life since December 2025. No longer receiving security patches. Required by Magento 2.4.4–2.4.6.
  • PHP 8.2–8.4 - Currently supported. Required by Magento 2.4.7+.

If your Magento version requires an end-of-life PHP version, upgrading Magento is the only path to getting back onto a supported, secure PHP release. We handle both the Magento and PHP upgrades together as a single, tested deployment.

Adobe publishes a support schedule for every Magento release. Stores on unsupported versions stop receiving security patches, which is a PCI-DSS compliance risk.

  • Magento 2.4.6: support ends 11 August 2026
  • Magento 2.4.7: support ends April 2027
  • Magento 2.4.8 LTS: support until April 2028
  • Magento 2.4.9: expected release May 2026

If your store runs on 2.4.6 or earlier you should plan an upgrade before August 2026 to stay within the Adobe security patch window.

2.4.6 → 2.4.8 LTS

Typical timeline: 2–3 weeks. Indicative cost: £1,600–£3,200.

The most common Magento upgrade we run today, particularly urgent ahead of 2.4.6 end-of-support in August 2026. Includes PHP 8.2 or 8.3 alignment and extension compatibility.

2.4.5 → 2.4.8 LTS

Typical timeline: 3–4 weeks. Indicative cost: £2,400–£4,800.

Two minor versions plus PHP and database schema changes. Extension compatibility is the biggest variable here, particularly for stores running older third-party modules.

2.4.4 → 2.4.8 LTS

Typical timeline: 4–5 weeks. Indicative cost: £3,200–£6,400.

Larger jump with multiple security and platform changes layered together. Often a good moment to also patch any extensions that have fallen behind.

2.3.x → 2.4.8 LTS

Typical timeline: 6–10 weeks. Indicative cost: £6,000–£14,000.

Major upgrade across multiple breaking changes including the Elasticsearch/OpenSearch requirement, MySQL 8 and PHP 8. Treated as a re-platform rather than a patch.

Magento 1 → Magento 2.4.8

Typical timeline: 12–20 weeks. Indicative cost: from £25,000.

Full Magento 1 to Magento 2 migration with data, extension and theme rebuild. Run as a discrete project, not an "upgrade".

Magento Open Source → Adobe Commerce

Typical timeline: 4–8 weeks. Indicative cost: £6,000–£15,000 (excluding Adobe licence).

Edition migration with B2B module activation, Page Builder enablement and Adobe Sensei configuration. Plan with the Adobe Commerce licence renewal cycle in mind.

Every Magento upgrade is billed at £100/hour to the minute against a fixed scope. We provide a written estimate after a free 30-minute assessment of your store, hosting and extensions.

For most stores we recommend upgrading to Magento 2.4.8 Long Term Support. This version receives security patches for the longest period and has the most stable extension ecosystem. Merchants who want the latest features and are comfortable with more frequent upgrades can move to 2.4.9 when it releases in May 2026.

If the upgrade is a chance to rethink your frontend, it is also worth considering a move to Hyva theme development alongside the version upgrade, particularly if Core Web Vitals and performance are a priority. Either path is handled by our in-house Magento developers.

An outdated Magento core version is almost always accompanied by outdated third-party extensions. This is one of the most overlooked risks in Magento stores:

  • Extension developers follow Magento's release cycle. When you stop upgrading Magento, you stop upgrading your extensions too - because newer extension versions require newer Magento versions.
  • Payment and shipping extensions are critical. Outdated payment gateway modules may not support current PCI DSS requirements. Outdated shipping modules may miscalculate rates or fail silently.
  • Abandoned extensions create security holes. Some extensions lose developer support entirely. These become permanent vulnerabilities in your store until they're replaced.
  • We audit every extension during upgrades. We check compatibility, identify abandoned modules, recommend replacements, and ensure everything works together after the upgrade.

We've delivered over 100 Magento upgrades with zero data loss. Here's the process that makes that possible:

1. Assessment & Audit

We audit your current Magento version, PHP version, all installed extensions, and any custom code. You get a clear report of what needs updating, what's compatible, and what needs replacing - plus a fixed cost estimate.

2. Staging Upgrade

We perform the entire upgrade in a staging environment that mirrors your production store. Every extension, every customisation, every integration is tested here first. Nothing touches your live site until it's proven to work.

3. Testing & QA

Full regression testing across checkout flows, payment processing, shipping calculations, admin operations, and customer-facing functionality. We test on multiple devices and browsers to catch everything before go-live.

4. Production Deployment

We deploy during low-traffic windows using our automated deployment pipeline with instant rollback capability. Most upgrades complete with under 15 minutes of maintenance mode. Your data, orders, and customers are never at risk.