Separate the platform name from the real risk
Magento end of life is often used as shorthand for concern about an ageing ecommerce build. The useful question is not whether a label sounds alarming, but whether the particular store can still be maintained safely, reliably and at a sensible cost. A retailer may have custom code, old extensions, unsupported infrastructure, incomplete documentation or no clear route for applying changes. Those are practical risks whether they appear singly or together.
Avoid making a decision solely from a generic support statement or a supplier’s sales message. Establish the exact version, hosting arrangement, integrations, extension inventory and change history. Ask the technical team to explain what is known, what is uncertain and what would happen if a security issue, payment change or operational fault required urgent work. A clear baseline turns a vague concern into a decision that can be prioritised.
Assess the store in business terms
An ageing build is not automatically failing. Review its effect on customers and staff: checkout reliability, page speed, search, merchandising, stock accuracy, order handling, returns and reporting. Look at the time needed to make a routine promotion or fix a defect. Consider whether the business can get timely support from people who understand the implementation. Repeated manual work and reluctance to change the site are often as significant as a visible outage.
Set out the consequences of doing nothing for the next year or two, rather than inventing a single dramatic outcome. Risks may include a slower response to faults, increasing maintenance effort, incompatibility with a service the business uses or difficulty recruiting suitable support. Balance those risks against revenue, planned growth, budget and other priorities. This is how Magento end of life becomes a proportionate business discussion rather than an abstract technical warning.
When patching is proportionate
Patching can be the sensible route when the current store meets business needs, its architecture is understood and the work closes specific, evidenced gaps. It may include applying available updates, replacing a problematic extension, improving backups and monitoring, documenting deployment steps or updating the hosting environment. The aim is to reduce risk and buy time, not to describe every older system as modern.
Before approving patch work, ask for a defined scope, dependencies, test approach, rollback plan and an explanation of residual risk. A patch programme should include regular review because the cost of keeping a custom build stable can change. If each update exposes another unknown dependency, that evidence may point towards a rebuild or a planned platform change instead.
When a rebuild is the better answer
A rebuild can be appropriate when the retailer wants to retain Magento but the existing implementation is too hard to improve safely. This route allows the team to simplify custom features, review extensions, improve data flows and document how the store works. It is not a copy-and-paste exercise. Rebuilding every historical workaround recreates the problem in a cleaner codebase.
Use discovery to separate requirements from habits. Test whether complex pricing, product configuration, trade accounts, warehouse links and content workflows are still needed in their current form. Agree which capabilities must be present at launch and which can follow later. A phased rebuild is often less disruptive than trying to solve every request in one release, provided the first phase supports real trading.
When replatforming deserves consideration
Replatforming is proportionate where the retailer’s needs have changed, the current platform creates persistent delivery friction or a different product better fits the operating model. A hosted platform may reduce infrastructure responsibility for a business with straightforward retail requirements. A different enterprise or open-source option may suit complex catalogue, integration or control needs. No platform removes the work of making good decisions about data, content and operations.
Compare options against realistic scenarios using the retailer’s own catalogue, discounts, fulfilment rules and customer journeys. Include implementation cost, ongoing support, apps or extensions, integration ownership, data portability and the skills needed internally. A platform demo proves little unless it covers the awkward cases that currently consume time or cause revenue risk.
Make a staged and accountable decision
Bring together commercial, operational and technical owners to review the evidence. Choose a near-term action, such as urgent remediation or a support audit, and a longer-term direction with review points. Keep a risk register that states the issue, impact, owner, mitigation and date for reassessment. This makes it possible to act on the most important weaknesses without committing prematurely to a large replacement programme.
For retailers considering Magento end of life, the right answer can be patching, rebuilding or replatforming. The proportionate choice depends on the actual build, the confidence of the support model and what the business needs next. Good advice makes those trade-offs visible, tests assumptions and leaves the retailer with a maintainable plan rather than a fear-driven deadline.
Need a straight answer about your own website?
Tell us what you are trying to achieve and we will help you work out the most useful next step.
Talk to CMS →Other Insights
Ecommerce
WooCommerce to Shopify Migration for SME Retailers
What an SME retailer should prepare before moving from WooCommerce to Shopify, and how to decide whether the change is worthwhile.
Read insightAI search
Answer Engine Optimisation for B2B Websites: Where to Start
A practical starting point for making a B2B website easier for search engines and AI tools to understand, quote and send visitors to.
Read insightManufacturing
What a manufacturing website needs to do before it can generate better enquiries
A good manufacturing website does more than show capability. It helps the right buyer understand the offer and decide whether to get in touch.
Read insight