If your online store still runs on Magento 1, you are operating on a platform that reached the end of its life in June 2020. It still takes orders. It also no longer receives security patches — and for a system that processes payments and holds customer data, that is a serious position to be in. The reason so many stores stayed put is the same reason this is hard: moving to Magento 2 is not an upgrade. It is, by the platform owner’s own account, a rebuild.
Why Magento 2 is effectively a new platform
When Adobe set out the move from Magento 1 to Magento 2, the guidance was unusually blunt: treat it as more than a version upgrade. It is effectively an entirely new platform, with substantial differences in how it is built, and the transition should be approached as a new build. Every extension and every piece of custom code has to be reviewed, rewritten and made compatible with the new framework.
For a typical store, that custom code and those extensions are not incidental. They are the shipping logic, the payment integrations, the bespoke checkout, the connections to your stock and accounting systems — the things that make the store yours. None of it moves across untouched. The catalogue and customer data can be migrated, but the store itself is rebuilt around them.
Free · 4 minutes
Would you survive contact with a determined attacker — or an auditor?
Fourteen questions on access, patching, detection, and recovery — the basics that prevent most real incidents, and the ones most often assumed rather than verified. Banded finding on screen, full sheet by email.
Why this stranded so many merchants
Because the move was a rebuild, a large share of merchants — hundreds of thousands of stores worldwide — delayed it, and many never made it before support ended. The result is a long tail of live commerce sites running on an unsupported platform, kept alive by unofficial community patches or by nothing at all.
For an e-commerce business, this is the most exposed version of the stranding problem. A store is a payment system. An unsupported payment system is a compliance and security risk first and a functionality risk second. The cost of a breach on an out-of-date store — financial, regulatory and reputational — dwarfs the cost of the migration that was being avoided.
Rebuild, replatform, or reconsider
Here is the part most Magento 1 merchants get wrong. Because the move is a rebuild either way, Magento 2 is no longer the automatic answer. The honest question is what platform best fits the business now. Magento 2 remains the right choice for stores with complex requirements that genuinely need its depth. For many smaller and mid-sized stores, the forced rebuild is the moment to ask whether a simpler, lower-maintenance platform would serve better, at a fraction of the running cost.
That is a commercial decision, not just a technical one, and it should be made with a clear view of what the store actually needs — not driven by the assumption that the next version of the same product is the only road forward.
What to do now
Start by mapping what the store relies on: which extensions and customisations are load-bearing, which integrations matter, what data must migrate, and what the business actually needs from its platform going forward. That assessment determines whether the destination is Magento 2 or something else, and it sizes the rebuild before you commit to a number.
If you are taking payments on Magento 1, the exposure is real and present, not theoretical. We will work out the safest, most cost-effective way off it.
Start a ConversationBuild and rescue work
Hands-on delivery of this kind is handled by Sixteen Pillars Studio.
Looking at an acquisition, supplier, or major project?
The greatest risks are rarely visible in the executive summary. The Sixteen Pillars framework surfaces the technology risks that diligence usually misses.