Migrating an E-commerce Store Without Losing Revenue
An online store moved from one e-commerce platform to another, for example WooCommerce to Shopify. Meek Media planned and executed the move so the things that drive revenue came across intact: product rankings, category URLs, structured data, customer reviews, analytics and conversion tracking. The goal was a new platform without a gap in sales or search visibility.
- Client
- E-commerce store (name withheld)
- Privacy
- Client name withheld
How do you migrate an e-commerce store without losing rankings or revenue?
Plan the migration around what earns money today. Meek Media mapped every product and category URL to its new address with 301 redirects, rebuilt product structured data, carried customer reviews across, and set up analytics and conversion tracking on the new platform before launch, then verified each piece once the store went live.
What makes an e-commerce platform migration so risky?
The client needed to move their store from one e-commerce platform to another, for example from WooCommerce to Shopify. A new platform can bring better tools and easier management, but a store migration puts revenue directly at risk. Product pages that rank bring in buyers. Category URLs hold links and history. Reviews build trust and feed rich results. Analytics and conversion tracking tell the business whether any of it is working.
Platforms handle these things differently. URL structures often change, and some platforms enforce fixed URL patterns that cannot simply be copied. Structured data comes from different themes or apps. Reviews may live in a plugin that does not exist on the new system. Tracking tags and purchase events have to be rebuilt from scratch. If any link in that chain breaks, the damage shows up quickly: products drop out of search, rich results disappear, and the business loses the data it needs to spot the problem. The migration had to protect all of it at once.
What we found
- Store moving between e-commerce platforms, for example WooCommerce to Shopify
- Product rankings that had to be preserved
- Category URLs at risk of changing on the new platform
- Structured data needing to be rebuilt on new templates
- Customer reviews needing to be carried across
- Analytics and conversion tracking that had to work from day one
How did Meek Media protect rankings and revenue during the move?
We treated the migration as a checklist of revenue-critical assets, each with an owner, a plan and a test. Mapping and preparation happened before launch, the switch itself was verified against that plan, and monitoring continued after go-live to catch anything the new platform handled differently.
-
1
Inventory products, categories and rankings
Every product, category and content URL on the old store was collected from crawls, sitemaps, analytics and Search Console. Pages were prioritised by organic traffic, rankings, revenue and backlinks, so the highest-value URLs got the closest attention. This inventory became the master list for redirects, content checks and post-launch testing. Nothing was left to memory.
-
2
Map category and product URLs
Each old URL was mapped to its exact equivalent on the new platform and redirected with a permanent 301. When the destination enforces its own URL patterns, as Shopify does with its /products/ and /collections/ paths, the map bridges the old structure to the new one. Product slugs and titles were kept consistent where possible so pages stayed recognisable to search engines.
-
3
Rebuild product structured data
Product structured data, including name, price, availability, identifiers and review information, was implemented on the new templates using schema.org Product markup. It was validated with Google's Rich Results Test against a sample of products. This protects the store's eligibility for product rich results, which can disappear quietly if a new theme omits or breaks the markup.
-
4
Migrate customer reviews
Reviews were exported from the old system and imported into a review solution on the new platform, keeping each review attached to the correct product along with its rating, date and content. Reviews were checked on the page and in the structured data so shoppers still see them and search engines can still read them. Losing reviews costs both conversions and search appearance.
-
5
Rebuild analytics and conversion tracking
Analytics, ecommerce events and conversion tracking were set up on the new store and tested before launch. Test purchases confirmed that purchase events, revenue values and transaction data were recorded correctly. Without working tracking, a store cannot tell whether the migration has affected sales, so this step was treated as launch-critical. It had to work on day one.
-
6
Launch verification and monitoring
At launch, the complete old URL list was tested against the redirect map, sitemaps were submitted, and staging restrictions were removed. Product pages, checkout, structured data, reviews and tracking were spot-checked on the live store. Search Console and analytics were then monitored for crawl errors, indexing changes and shifts in organic traffic and conversions. Issues were fixed as they appeared.
What We Delivered
- Prioritised inventory of product, category and content URLs
- Old-to-new 301 redirect map for products and categories
- Product structured data on new templates, validated
- Customer review migration with product matching
- Analytics and conversion tracking setup with test transactions
- Launch checklist and post-launch verification crawl
What Other Teams Can Learn From This
List what earns revenue before you move
Before choosing templates or apps, identify the pages, data and tracking that drive sales today. Top products, key categories, reviews and conversion events belong on a migration checklist with an owner each. Anything not on that list is at risk of being missed, and missing pieces tend to show up as lost sales.
Expect the new platform to change your URLs
Different platforms structure URLs differently, and some do not let you replicate the old pattern. Accept that early and plan a precise redirect map rather than trying to force the old structure. Test it against every old URL before launch. Redirects should be one-to-one, not bulk redirects to the homepage.
Tracking is part of the migration, not an add-on
If analytics and conversion tracking break during a move, you cannot tell whether rankings or sales changed. Set them up on the new platform and confirm them with test purchases before launch. That way any change in performance after go-live can be spotted and investigated quickly. Data you do not capture during the switch cannot be recovered later.
Frequently Asked Questions
Will moving from WooCommerce to Shopify hurt my SEO?
It does not have to. SEO problems during a platform move come from changed URLs without redirects, lost content, missing structured data and broken internal links. With a complete redirect map, content carried across and structured data rebuilt, a store can move platforms while keeping its search visibility.
Can I keep my URLs when changing e-commerce platforms?
Sometimes, but not always. Some platforms enforce fixed URL paths for products and collections. Where URLs must change, every old URL needs a 301 redirect to its new equivalent. Keeping product slugs the same, even within a new path, makes mapping simpler and pages easier to recognise.
What happens to product reviews during a platform migration?
Reviews usually live in a plugin or app on the old platform, so they need to be exported and imported into a review tool on the new one. Each review should stay attached to the right product, with its rating and date, and appear in the product's structured data after migration.
How do you check a store migration went well?
Test every old URL against the redirect map, crawl the new store for errors, validate product structured data and confirm reviews display. Run test purchases to check tracking. Then watch Search Console and analytics for indexing problems, ranking drops or changes in conversions over the following weeks.
Related Case Studies
Rebuilding a 10,000+ Page Website Without Losing SEO
A website with more than 10,000 pages needed a complete redesign, and thousands of those pages were indexed and ranking. Meek Media planned the rebuild so search value carried across: URL architecture, page templates, metadata migration, redirects, structured data, internal linking and a structured launch QA process that checked the new site before and after it went live.
Read the case study →
Recovering a Website After a Google Algorithm Traffic Collapse
After a major Google update, this site lost 60–80% of its organic traffic. Meek Media audited everything that shapes how Google judges a site: content quality, backlinks, site architecture, duplicate pages, search intent and technical SEO. We then rebuilt the organic strategy around the pages that deserved to rank, rather than chasing the update itself.
Read the case study →
Core Web Vitals Rescue for a High-Traffic Website
This website had strong traffic but failed Core Web Vitals. Heavy scripts, large images, layout shifts, slow server responses and third-party integrations were all dragging down the experience. Meek Media tackled the problem on two fronts, optimising the front-end architecture and the server infrastructure behind it, so pages loaded faster, responded quicker and stayed visually stable.
Read the case study →
Facing a similar problem?
Every engagement starts with a free audit. We find what is holding your site back, show you the fix, and scope the work to your goals before you commit.