MarketPulse decision guide
Ecommerce Platform Migration Questions
Before anyone quotes for a move, answer the questions that decide whether to leave your current platform at all, and where to go if you do.
Three things to settle before you ask anyone for a migration quote.
Most ecommerce platform migration questions get asked too late, after a developer has sent a quote and the owner has half decided. This page is for the earlier moment, when you are still weighing whether to leave your current platform at all and, if you do, which one to move to.
A move costs you twice. You pay once for the work, and then again in the weeks when staff relearn the admin, customers set new passwords and Google recrawls every address on the site. Below you will find the reasons that clear that bar, the ones that do not, the questions to ask about data, apps, fees, contracts and search traffic, and a go/no-go score you can fill in this week. Once the score says yes, the store migration checklist takes over and walks through the execution.
Which reasons justify a platform migration?
A move earns its cost when the platform itself blocks something the business needs and no app, plugin or theme change can fix it. Test every reason with one question: would a developer on your current platform call this impossible, or only expensive? When the answer is “expensive”, price that fix and set it against the migration before you decide.
| Reason | Why it can justify a move | Test it before you commit |
|---|---|---|
| The platform cannot run a sales channel you need, such as a shop-counter till that shares stock with the website | Every month without it costs sales you can count | Ask two developers on the current platform, in writing, whether it can be built and at what price |
| Hosting, updates and security take more time than you have | A self-hosted store needs updates, backups and monitoring every month | Add up the hours spent on updates and fixes in the last six months |
| Fees grow faster than sales | Per-order charges and stacked app fees rise with volume | Run the three-year comparison further down this page |
| The platform, or a plugin the shop depends on, is being retired | You will have to move anyway, on someone else’s deadline | Find the end-of-support date on the vendor’s own site |
| You cannot export your own data | Each year of new orders makes the exit harder | Run a full export of products, customers and orders today and open the files |
Which reasons do not justify a move?
None of these needs a new platform:
- “The site looks dated.” A new theme on the same platform changes the look for a fraction of the price. Design and platform are two separate decisions.
- A slow store. Find the cause before you blame the platform. Oversized images, app scripts and a heavy theme are the first suspects, and all three travel with you if they get copied across.
- A developer who let you down. Replacing a person costs less than replacing the software.
- A first-year discount from the new vendor. The saving happens once, while relearning the admin costs your team hours every week for a while.
- One missing feature that an app already covers. Price that app for three years first; it is the cheaper fix in most comparisons.
A simple rule: if the reason fits inside the sentence “we don’t like how it looks or feels”, fix it where you are.
What should you ask about your data before deciding?
Data is where migrations go wrong quietly, so begin with a count, because the count decides the method. Shopify’s own Migrate to Shopify guide lists the content you can bring across: products, customers, historical orders, gift cards and store credits, blog posts and pages. It also sets the order of import: products first, then customers, then historical orders, so that each old order connects to the right person and the right item.
Answer these with real numbers from your current admin:
- Products and variants. How many items, and how many sizes or colours per item? Shopify’s guide says a single shipping policy page can be pasted by hand, while a catalogue of 250 products likely needs a CSV file or a migration app.
- Customer accounts. How many customers log in with a password? Those passwords stay behind. Shopify states that customer passwords cannot be migrated with a CSV file, so you invite customers to create new ones. The WooCommerce guide to moving from Shopify says the same for the opposite direction: customers reset their passwords after the move.
- Order history. How many years do you need on the new platform, and who needs them?
- Gift cards and store credit. Are there open balances? That is money you owe customers, so each balance has to arrive intact.
- Reviews and consent. Do reviews sit in the platform or in an app with its own export? Can you export email and text-message consent as separate fields?
If any answer is “we don’t know”, you are not ready to decide. Half a day of exports and counting costs far less than discovering open gift card balances in week three of the build.
Which apps and plugins have to come with you?
List every app, plugin and outside service that touches the store, then mark what happens to each one on the target platform. Apps belong to a platform, so a move means finding a replacement for most of them, and every replacement brings its own monthly fee and setup time.
Example: the app list of a garden centre (invented shop, for illustration):
| Job the tool does | Available on the target platform? | What replaces it | Setup hours |
|---|---|---|---|
| Product reviews | No | A new review app, fed by an export file | 3 |
| Accounting sync | Yes, same connector | Reconnect and test | 1 |
| Delivery date picker | No | A paid app with a monthly fee | 4 |
| Email marketing | Yes | Reconnect, check signup forms | 2 |
| Product filters | Built into the new theme | Theme settings | 5 |
That list adds 15 hours of setup before a single product moves. Then ask the question that settles most debates: which of these jobs does the target platform do with no app at all? Each one is a saving for the fee comparison below, and each job that needs a new paid app goes in the cost column.
How do you compare platform fees over three years?
Compare three years, never one. The one-off migration cost needs time to pay back, and first-year discounts make a twelve-month view look better than it is. List plan fee, apps, hosting, theme licence, payment processing and maintenance hours for both platforms. Take processing fees from each provider’s official pricing page on the day you compare, and write that date next to the figure.
Example (made-up figures): a bike shop pays 310 a month today across plan, apps and hosting. The target platform comes to an estimated 240 a month once the apps are replaced.
- Monthly saving: 310 − 240 = 70
- Saving over three years: 70 × 36 = 2,520
- One-off cost: a migration quote of 5,500, plus 30 hours of the owner’s time valued at 35 an hour (1,050), comes to 6,550
- Payback on fees alone: 6,550 ÷ 70 = roughly 94 months, close to eight years
On fees alone this move is a clear NO. The picture changes when the move unlocks sales. Suppose the new platform lets the shop offer click and collect, and the owner expects 25 extra orders a month at 20 of margin each. That adds 500 a month, so the payback becomes 6,550 ÷ (70 + 500) = about 11.5 months.
Be strict with that extra-orders figure: write down a number you can defend, with the date, and check it a year after the move. For the full picture of running costs, see the guide to what a small business store costs to build and run.
What do your contracts and accounts lock you into?
Read these before deciding, because one notice period can push the move back by months:
- Platform plan. Monthly or annual? An annual plan paid in advance changes the best start date.
- Payment provider and till hardware. Look for a minimum term, an exit fee or a terminal lease. Shopify publishes a supported hardware list for its own POS, so compare your card readers and printers model by model.
- Theme and plugin licences. Paid licences stay with the old platform. On the Shopify side, paid themes are non-refundable, so use the theme preview before you buy.
- Domain and email. Who is the registrar, and does your email run through the same account? Shopify’s migration guide warns that a domain still connected to the old platform can cause SSL certificate errors, so it gets disconnected there first.
- Your developer or agency. Who holds the admin logins today, and does the contract say they hand them over when you leave?
How much search traffic is at risk, and can you carry it?
Every platform has its own address pattern. Shopify’s guide gives the example of a shipping policy page moving from /policies/shipping-policy to /pages/shipping-policy, and WooCommerce’s guide points out that Shopify uses /products/item where WooCommerce uses /product/item. So a platform switch changes most of your URLs, and Google treats that as a site move.
Google’s documentation on site moves with URL changes gives three facts that belong in the decision itself:
- Rankings fluctuate while Google recrawls, and for a medium-sized site it can take a few weeks or more before Google shows the new URLs in place of the old ones.
- Permanent redirects (301 and 308) do not cause a loss in PageRank. The risk lies in redirects that are missing or point to the wrong page.
- Google advises changing one thing at a time. A new domain, a new platform and a new design should happen one after the other.
Now size your own exposure. Pull last year’s orders by source from your analytics. Example: if 400 of 1,000 yearly orders started with a Google search, a few unsettled weeks in your busiest month put a real share of sales at risk, so pick a quiet month instead; Google itself suggests timing the move for a dip in traffic. Then count the addresses that need a redirect: products, categories, blog posts and images that get search visits. Shopify allows up to 100,000 URL redirects below the Plus plan, yet each line still has to be mapped by a person.
Go or no-go: how do you score the move?
Score each line 0, 1 or 2 and add up the total. Be strict with yourself: a 2 needs evidence on paper.
| Question | 0 points | 1 point | 2 points |
|---|---|---|---|
| 1. Does the move fix a problem the current platform cannot solve? | No | Only at a high price | Yes, confirmed in writing by two developers |
| 2. Does the three-year comparison favour the move? | It costs more | About even | Pays back within 24 months |
| 3. Can you export products, customers and orders today? | No | Partly | Yes, files opened and checked |
| 4. Do you know your counts (variants, accounts, gift cards, orders)? | No | Some of them | All of them |
| 5. Does every app job have a replacement? | Gaps with no fix | Gaps with paid workarounds | All covered |
| 6. Can every contract end within three months? | No | With an exit fee | Yes |
| 7. Is there a quiet trading month in the next six months? | No | A slower few weeks | Yes, a clear low season |
| 8. Is search traffic small, or are redirects already mapped? | Large share, nothing mapped | Large share, partly mapped | Small share or fully mapped |
| 9. Do staff have time to learn the new admin and till? | No | Some time | Yes, training booked |
| 10. Is this the only big change planned? | Domain, design and platform at once | Two changes together | Platform only |
15 to 20: GO. Move on to the execution checklist. 10 to 14: fix the weak lines first and rescore in a month. Below 10: STAY and solve the problem on the platform you already run.
Which platform should you move to?
Choose the destination by who will look after it, then by features:
- Who handles hosting, updates and security? A hosted platform does it for you. A self-hosted one such as WooCommerce puts the work on you or your developer, and in return its documentation notes that product data sits in your own WordPress database, giving you full ownership of it.
- Does it run your shop counter? If you sell in person, the till and the website have to share one stock count.
- Can you hire for it near you? Count the developers in your area who work on that platform before choosing it, because you will need one again after launch.
For a business with a physical shop, the comparison of Shopify and WooCommerce for local business sets POS, local pickup and delivery side by side.
FAQ
How long should the migration decision take?
Give it four to six weeks: one week for exports and counts, one or two for the app list and the three-year fee comparison, and the rest for quotes. Read contract notice periods on day one, since they can stretch that timeline.
Will switching platforms hurt my Google rankings?
Google says rankings fluctuate while it recrawls a moved site, and a medium-sized site can take a few weeks or more to settle on the new URLs. Permanent redirects do not lose PageRank, so lasting damage comes from missing or wrong redirects. That makes the redirect map the biggest search job in any move.
Can customers keep their passwords after a platform move?
No. Shopify says passwords cannot be migrated with a customer CSV, and WooCommerce says passwords from Shopify do not transfer either. Plan an email that invites customers to set a new password, and test it on a staging store first.
Should I redesign the store during the migration?
Google’s site move guide advises changing one thing at a time. Move first on a theme that looks close to the current store, let traffic settle, and redesign afterwards.
My current contract runs for another eight months. Should I wait?
Price both options. Example: eight remaining months at 150 is 1,200 you pay either way, so leaving early only makes sense if the new platform brings in more than that over the same eight months.
Can I move one part of the store first?
Google suggests large sites can move section by section, while small and medium sites should move all URLs at the same time. A local shop’s catalogue fits the second group, so plan one move on one date.
Who should answer these questions, a consultant or a developer?
The decision questions suit you or a consultant; a developer prices and runs the build once the answer is yes. The guide to ecommerce consultant vs developer explains which role to bring in first.
What should you do before asking for migration quotes?
Run the exports, fill in the app list and score the ten questions. If the total says GO, write the reasons and the three-year numbers on a single page and send that page with every quote request, so each provider prices the same job. The guide on comparing ecommerce service quotes helps you line the replies up.
If you would like a second look at your score or your fee comparison before you commit, send MarketPulse a message through the contact form and we will help you prepare the decision.
Decided to move? Read these next
The execution checklist, the platform comparison and the cost guide pick up where this decision ends.