Every Magento Open Source and Adobe Commerce release line has a fixed end date, and PHP has its own calendar underneath it. These guides set out the dates, what changes when they pass and the ways forward, so that an upgrade is a decision you plan rather than a deadline you discover.
Which Magento Open Source release lines still receive fixes, how that differs from Adobe Commerce, what happened to Magento 1 and what running an unsupported version risks.
The dates for every 2.4 release line, what changes for Open Source and Adobe Commerce, the PHP clock underneath and the three ways forward.
What an Adobe security bulletin tells you, how -p releases, isolated patches and hotfixes fit together, what changed in July 2026 and how quickly to act on each priority.
The honest trade: what Shopify takes off your plate, what it asks you to give up, how products, customers, orders and URLs move, and where migrations go wrong.
Every article here describes work we do every week, for stores of every size. You get a written plan and estimate once we have examined the store.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.
