If your store runs on Magento or Adobe Commerce, a decision is coming — if it has not arrived already. Versions reach the end of their support window, extensions need updating, hosting and upgrade costs build up, and at some point the question changes from “how do we upgrade?” to “should we still be on this platform?”
There are three realistic options: upgrade in place, move to Adobe’s SaaS edition, or replatform. Each is right for some businesses and expensive for others. This guide sets out when each fits, and how to decide.
First, check where you stand
Before weighing options, answer five questions:
- Which version are you on? Magento 1 reached end of support in June 2020. For Magento 2 and Adobe Commerce, each 2.4.x release has its own support window under Adobe’s lifecycle policy. An unsupported version gets no security patches, which also matters for payment-card compliance.
- How many extensions and custom modules do you run? And which of them still matter to how you sell?
- Which systems do you integrate with? ERP, PIM, OMS, WMS, CRM, marketing and payments.
- What do hosting, upgrades and maintenance cost each year, including your team’s or agency’s time?
- What is the business asking for that the current store cannot deliver quickly?
Those answers usually point clearly at one of the three options.
Option 1: Upgrade in place
Stay on Magento Open Source or Adobe Commerce — on Adobe’s cloud infrastructure or self-hosted — and bring the store up to a supported version.
It fits when:
- your customisations are central to how you sell — complex pricing, configurators, B2B workflows — and would be costly to rebuild;
- you have, or can keep, a team or partner who knows the codebase;
- the platform still does what the business needs, and the main problem is the version you are on.
The trade-off: upgrades are a recurring project, not a one-off. Every release means updating extensions, retesting customisations and planning downtime. Budget for that cycle, not just the next upgrade.
Option 2: Move to Adobe Commerce as a Cloud Service
Adobe now offers a SaaS edition, Adobe Commerce as a Cloud Service, in which Adobe runs the platform and its upgrades. It keeps you in the Adobe ecosystem — including native B2B and its data model — while removing much of the upgrade burden.
It fits when:
- you want to stay on Adobe Commerce for its capabilities, but stop running upgrades and infrastructure yourself;
- your customisations can be rebuilt as extensions outside the core, using Adobe’s extensibility tools;
- you are already invested in other Adobe products.
The trade-off: customisations that change the core directly will not carry over as they are. Audit them first: some will move easily, some need rebuilding, and some you may decide you no longer need. Confirm edition features and commercial terms with Adobe.
Option 3: Replatform
Move to a different platform — most often Shopify Plus for D2C brands and simpler B2B, sometimes Salesforce Commerce Cloud or a composable platform for large, complex operations.
It fits when:
- much of your custom Magento code recreates features another platform includes as standard;
- upgrades, hosting and maintenance consume budget that should go into growth;
- you want a smaller platform team and faster changes, and can accept less control of the code.
The trade-off: a migration is a substantial project. Product, customer and order data, integrations, URLs and redirects all need careful planning so you do not lose revenue or search rankings. Our Magento to Shopify Plus migration checklist shows what is involved, and our comparison of Shopify, Adobe Commerce and Salesforce Commerce covers the main destinations.
Choosing between the three
| Signal | Upgrade in place | Adobe SaaS edition | Replatform |
|---|---|---|---|
| Customisations are central to how you sell | ✓ | Possibly, if they can move to extensions | Costly to rebuild |
| Upgrades and hosting consume too much budget | — | ✓ | ✓ |
| You want to stay in the Adobe ecosystem | ✓ | ✓ | — |
| Much custom code recreates standard features | — | — | ✓ |
| You want a smaller platform team | — | ✓ | ✓ |
| Native B2B on Adobe is a must | ✓ | ✓ | Depends on destination |
How to decide
- Audit your version, extensions, custom modules, integrations and annual running cost.
- List what the business needs in the next three years, and what the current store cannot deliver.
- Score the options against those needs — our free Platform Selection Scorecard works for comparing staying with moving.
- Compare total cost over three to five years, including the team, not just licence and hosting.
- Plan the move, whichever way you go, with data, integrations, URLs and redirects mapped before work starts.
Get help deciding
We work with brands on all three paths: upgrading and supporting Adobe Commerce stores, and planning and running platform migrations. If you would like an independent view of your options, our advisory team can audit your store and lay out the choices with their costs.
Frequently asked questions
Is Magento still supported?
Magento 1 reached end of support in June 2020. Magento 2 — as Magento Open Source and Adobe Commerce — is supported, but each 2.4.x release has its own support window under Adobe's lifecycle policy. Check your exact version against that policy; running an unsupported version means no security patches.
What is Adobe Commerce as a Cloud Service?
Adobe Commerce as a Cloud Service is Adobe's SaaS edition of Adobe Commerce, where Adobe manages the platform and its upgrades. Customisations are built as extensions outside the core rather than as changes to it, so existing Magento customisations need to be assessed before moving.
Should I upgrade Magento or migrate to Shopify Plus?
Upgrade if your customisations are core to how you sell and you have a team to maintain them. Consider Shopify Plus if much of your Magento code recreates features Shopify includes, if upgrades and hosting consume your budget, or if you want a smaller platform team. An audit of your extensions and integrations usually makes the answer clear.
How long does a Magento to Shopify Plus migration take?
It depends far more on the number of integrations and custom features than on the number of pages or products. A straightforward D2C store moves much faster than a B2B operation with ERP integration and complex pricing. A discovery phase that maps every integration and URL gives you a reliable timeline.