A platform decision starts with the business problem. Your store might need a specific integration, a more manageable catalogue or a dependable way to make routine changes. Moving can help, but it also brings delivery costs, dependencies and a transition for the people running the business.
The cost of waiting is a question to investigate. Gather evidence for three options: maintain the current setup, make a focused improvement, or migrate. Keep confirmed expenditure separate from staff capacity, risk estimates and possible future revenue.
Start with the costs you can verify
Choose a comparison period and record the source of every figure. A current invoice, signed renewal term or delivery record is more useful than a general industry benchmark. Note currency, tax, contract end dates and which costs will continue whichever platform you choose.
| Area | Evidence to collect | Decision it supports |
|---|---|---|
| Recurring tools | Platform, hosting, app and support bills. | What can actually stop, and when? |
| Team effort | Recorded maintenance and change work. | Where could capacity be used better? |
| Customer friction | Observed journeys, support themes and usable analytics. | Which problem deserves a fix first? |
| Dependencies | Systems, owners, contracts and required data. | What must work through the transition? |
| One-off work | A proposal with scope, exclusions and checks. | What would the move cost to deliver? |
Keep cash, time and opportunity separate
A subscription cancellation becomes a cash reduction when the approved change takes effect and the next bill confirms it. Check whether another service replaces it, whether a contract remains payable and whether the business still needs the function.
Time released from repetitive work is useful capacity. A person being able to do other work does not automatically reduce payroll or put that amount in the bank. Record the workflow, time measurement and business decision separately.
Customer friction can justify investigation without a revenue forecast. Use real page behaviour, support evidence and purchase journeys to describe the problem. A platform switch does not establish a conversion or sales gain; any claimed improvement needs its own measurement and context.
Compare the whole operating cost
Build comparable totals for staying, improving and moving. Include the initial investigation, design and development, data preparation, integration work, internal review time, training, launch support and ongoing operation. Check overlap costs while two systems are in use and the terms for ending the old contracts.
Do not add the same benefit twice. Faster staff work, reduced agency hours and an assumed revenue increase may describe overlapping opportunities. Mark uncertain amounts as estimates with their assumptions, and keep missing evidence visible.
Our Shopify operating-cost guide provides a broader comparison, while the Shopify app-waste checklist helps investigate existing bills and dependencies before cancelling anything.
Check what a migration must preserve
List the products, customer and order records, URLs, content and business rules that matter. Decide what can transfer, what needs rebuilding and what requires a different workflow. Shopify’s migration guidance is a starting checklist; the actual transfer still needs a plan for your source system and requirements.
- Map important customer routes and agree how redirects will be checked.
- Test representative products, records and integration journeys before launch.
- Agree who reviews the work, the release window, recovery approach and handover.
- Record post-launch checks and any remaining exceptions.
The 12 Boards consolidation record describes collection mapping, landing pages and redirects. The Purvis Beer migration record describes a move from Kentico to Shopify. These are delivered-work examples, with commercial outcomes measured separately.
Check support dates against the actual installation
If support coverage is part of the decision, identify the exact platform edition, version, patches and contract. Use the vendor’s current policy and the installation’s circumstances. Adobe publishes a Commerce lifecycle policy; a single date for every Magento or Adobe Commerce store would not be a reliable assessment.
Support status can make a decision urgent, but an invented breach cost will not improve the plan. Record the known gap, responsible owner and options for investigation or remediation.
Choose the smallest useful next step
A focused repair or an upgrade may solve the problem more directly than a migration. A move becomes worth scoping when requirements, delivery risks, costs and ownership are clear enough to compare. It can also be sensible to gather more evidence before committing.
Sonder scopes Shopify design and development around the store’s needs. Plus is considered when its current capabilities fit a requirement, rather than assumed from turnover. Snowball is ongoing Shopify care within agreed monthly capacity, priorities and timing. A migration, rebuild or substantial integration needs its own agreed scope and required approvals.
Sources and review
Substantively reviewed on 26 October 2026. This is a planning guide, with no quoted project price, measured savings benchmark or promised commercial result. Confirm current vendor terms and use your own evidence.