Platforms · Magento and Adobe Commerce
Magento and Adobe Commerce development
Upgrades onto supported release lines, extension clean-ups, custom modules and integrations for businesses running Magento Open Source or Adobe Commerce – and clear advice on whether to stay.
Fit
When Magento is the right platform, and when it isn’t
Appropriate when
- Large catalogues with complex attributes and relationships
- Several websites, stores and languages run from one installation
- B2B requirements such as company accounts, negotiated pricing and quotes
- You want deep customisation and control of the code, and are prepared to maintain it
Not appropriate when
- There’s no budget for regular upgrades, security patching and capable hosting
- The catalogue and rules are simple enough for a hosted platform
- You want infrastructure and upgrades to be someone else’s job and don’t need Magento’s flexibility
- Nobody with Magento experience will look after it
Release lines
Know where your version stands
| Release line | Released | Regular support ends |
|---|---|---|
| 2.4.9 | 12 May 2026 | 31 May 2029 |
| 2.4.8 | 8 April 2025 | 31 May 2028 |
| 2.4.7 | 9 April 2024 | 31 May 2027 |
| 2.4.6 | 14 March 2023 | Ended 11 August 2026 |
Dates from Adobe’s published release schedule, checked September 2026. Adobe offers Adobe Commerce customers on 2.4.6 and 2.4.7 a year of additional support; Magento Open Source installations should plan to be on a supported line.
Development
Typical Magento work
- Upgrades. Moving to a supported release line and PHP version, with extensions and custom modules made compatible and tested on staging.
- Extension audits. Finding abandoned, duplicated or insecure extensions and replacing or removing them.
- Custom modules. Business logic in modules, plugins and observers rather than core overrides that block the next upgrade.
- Performance. Indexers, cron, caching and search configured and monitored, and slow admin screens profiled.
- Security. Patches applied promptly, admin access reviewed and unexpected code investigated.
Common problems
Stuck on an unsupported version
Upgrades postponed because core files were modified or extensions were abandoned. The longer it waits, the larger the upgrade.
Cron and indexers failing quietly
Prices, stock and search results out of date because scheduled jobs stopped and nobody was told.
Integrations that can’t keep up
Imports and exports run as one large job instead of through queues, locking tables and timing out at volume.
Integration and migration
Magento and Adobe Commerce expose REST and GraphQL APIs and support message queues, which suit high-volume ERP, PIM and warehouse integration. See integrations.
Migration options include upgrading in place, moving between Magento Open Source and Adobe Commerce, or leaving Magento. For Adobe Commerce on Cloud customers, Adobe recommends Adobe Commerce as a Cloud Service, where Adobe manages infrastructure, patching and upgrades – a real change in how much of the platform you can customise, which deserves assessment before it’s scheduled. See replatforming.
In practice
What this work typically involves
Magento work usually starts with the version, the hosting, the installed extensions and any changes made to core files, because together they decide how large an upgrade will be. From there the work is put in order – supported versions and security first, then performance and integrations – and each change is tested on staging before it goes live.
If you run Magento or Adobe Commerce, tell us the version, the hosting and what’s holding the store back; we’ll tell you plainly what we’ve done that’s comparable, and whether we’re the right people for it.
Next step
Running Magento or Adobe Commerce?
Tell us the version, the hosting and what’s holding the store back.