How to move to a new online store platform without losing traffic and data

Online store migration means moving the catalog, customers, orders and page URLs to a new platform so that buyers and Google don't notice a break. There are two main risks: losing search traffic (the URLs changed and the old ones are not redirected) and losing data (customers, order history, reviews, analytics settings).

This article does not recommend any platform. It is about the process, which is the same for any move. The search rules are taken from Google Search Central documentation; the rest is practical logic, which is marked as such.

First, determine what type of move you have

Google distinguishes two cases, and the amount of work depends on which one it is:

1. Page URLs change (the new platform builds URLs differently, the domain or protocol changes): this is a "site move with URL changes", which needs redirects and careful mapping of old URLs to new ones (Google Search Central).
2. URLs stay the same, only the hosting or the platform underneath changes: this is a move without URL changes, where the main task is switching DNS and not losing Googlebot's access (Google Search Central).

Practical takeaway: if the new platform can preserve your URLs (products, categories, articles), do so. Every preserved URL is a redirect you don't have to maintain and a risk that isn't there. If it can't, prepare a full mapping.

Preparation (2–6 weeks before the move)

1. Build an inventory

• URLs. According to Google, collect old URLs from the sitemap, server logs, analytics, the CMS and the links report in Search Console. Also account for images, video, JavaScript and CSS (Google).
• Traffic and orders. Record a baseline: sessions by source, organic traffic by page, revenue by channel, conversion for the last 3–6 months. Without it you can't tell seasonality from losses.
• The most important pages. Separately single out the top pages by organic revenue and backlinks: they are checked manually first.
• Settings. Product feeds, ad accounts and Merchant Center, pixels, integrations with accounting and delivery, email templates.

2. Build a redirect map

For every old URL, determine the new one. According to Google:

• use server-side permanent redirects (301 or 308); client-side ones (JavaScript, meta refresh) only as a last resort;
• redirect each old URL straight to the final one, with no chains: Googlebot can follow up to 10 hops, but Google advises keeping a chain no longer than 3 and preferably under 5;
• don't send many old URLs to one irrelevant page, such as the homepage;
• for content you are not moving, return 404 or 410 (Google).

Google's redirects page clarifies the difference: permanent (301/308) signal that the new URL should become canonical and shown in results, while temporary (302/303/307) keep the old one in results (Google Search Central). A move needs permanent ones.

Example (illustrative). Before: `/category/zhinochyi-odyag/dress-123`. After: `/zhinky/sukni/dress-123`. In the map this is one row, and in the platform settings a rule that can be applied in bulk by pattern, but exceptions (products without a match) have to be handled manually.

3. Prepare the new platform

• Catalog. Move and check attributes, variants, photos, reviews; tidy the structure (catalog structure). Data from a PIM or spreadsheets is easier to clean first.
• Customers and orders. Import them and check a sample: amounts, statuses, addresses, history. Separately find out whether buyer accounts can be moved. Passwords are usually stored as hashes, and not every platform accepts them, so customers may need to reset their password. This is general practical caution, not research data: check the documentation of both platforms.
• Law and privacy. Buyers' personal data remains your responsibility during the transfer: check the contract with the new provider and the policy (GDPR, cookies).
• Technical SEO. Self-canonicals, hreflang, internal links, the sitemap and structured data must point to the new URLs (Google). A short audit: technical audit.
• Staging copy. Block the test site from indexing (`noindex` or password access), and lift the block before launch.

4. Set up analytics and measurement

• Move the tags and events (`view_item`, `add_to_cart`, `purchase`) and check on test orders that the "Ecommerce purchases" report in Google Analytics shows revenue, views and add-to-carts (Google Analytics Help).
• Prepare a "before and after" report against your baseline from step 1.
• Google advises setting up analytics on both sites and making sure the server can handle the increased Googlebot crawl after the move.

5. Choose the timing

Google recommends moving in a period of low traffic, since rankings may fluctuate temporarily. For a store this means not launching right before the peak season (Black Friday, New Year, March 8) and leaving time before it to fix errors.

Moving day

The sequence Google describes for a move with new URLs (Google):

1. Turn on the redirects.
2. Check that canonicals point to the new URLs and remove any temporary `noindex`.
3. Test the redirects with the URL Inspection Tool or a script.
4. If the domain or subdomain changes, submit the Change of Address tool in Search Console for each verified variant of the old domain. It does not apply to an HTTP→HTTPS, www or path change.
5. Submit the new sitemap, delete the old one.
6. Update links in social networks, profiles, ad campaigns and on partner sites that link to you.

For a move without URL changes the procedure is different (Google): well before the move, at least a week ahead, lower the TTL on the DNS records to a few hours so the change propagates faster; make sure a firewall or DDoS protection does not block Googlebot; switch the DNS; after traffic to the old server disappears, turn it off.

For a store, add: check checkout and payment with real cards, that email and SMS fire, order statuses, exports to the warehouse and delivery (Nova Poshta or others), a working ad feed.

After the move: what to check

• Search Console. According to Google's documentation, the number of indexed URLs in the old sitemap should decrease and in the new one grow; redirect warnings in the old sitemap are expected.
• Server logs. Googlebot visits, unexpected response codes, user traffic.
• Analytics. Traffic falls on the old URLs and grows on the new ones. Compare organic traffic and revenue with the baseline.
• 404s and redirects. Daily during the first week, look for URLs that return 404 but had a match in the map.
• Conversion and funnel. Checkout drops faster than SEO if something broke (key metrics, cart abandonment).

How long to wait. Google gives no calendar dates: for medium-sized sites the transition can take several weeks or more, large sites need longer, and the move is complete when Googlebot has visited all old and new URLs at least once. Rankings may fluctuate temporarily (Google). So for the first 2–4 weeks don't make other big changes to the site, so as not to mix up the causes.

How long to keep redirects. According to Google's current guidance, at least a year, and longer if they still get traffic. Turning them off earlier risks losing signals (Google).

Who does what

This is a typical split, not a requirement from the sources.

Rollback plan

Before switching, agree on what to do if something goes wrong: the old site keeps running at a temporary address, the redirects can be turned off quickly, and orders from those days won't be lost. For short availability problems, Google advises using temporary redirects, which keep the old URL in results (Google).

Common mistakes

• Sending all old URLs to the homepage.
• Forgetting images, PDFs, filtered pages and blog posts.
• Lifting the `noindex` block on the new site too late (or not at all).
• Building redirect chains of three to five hops.
• Moving right before the season.
• Not saving the "before" baseline and then arguing whether there was a drop.
• Not checking payment and shipping on real orders.
• Changing structure and design at the same time as the platform, when each change makes finding the cause harder.

FAQ

Will I lose rankings in Google when changing platforms? Temporary fluctuations are possible: Google says so directly. Losses are minimized by preserved URLs or clear permanent redirects, a new map, correct canonicals and monitoring after launch.

How long should I keep redirects after the move? According to Google's current guidance, at least a year, longer if there is still traffic through them.

Do I need a 301 redirect if the URLs haven't changed? No, but you need to check DNS, accessibility for Googlebot and that the test environment is blocked.

What do I do about customers and passwords? Import them and check a sample; for passwords, find out in advance whether the new platform supports moving them, otherwise prepare a password reset email.

How long does a migration take? The technical part depends on the catalog, and search "settling" per Google can take several weeks or more.

Related terms

• Online store catalog structure
• SaaS platform, custom store or vibe coding: what to choose
• Technical site audit
• Technical specification
• PIM system
• Key metrics of an online store: what to watch daily, weekly and monthly

Sources

• Google Search Central, How to move a site (with URL changes) — developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
• Google Search Central, Moving a site with no URL changes — developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes
• Google Search Central, Redirects and Google Search — developers.google.com/search/docs/crawling-indexing/301-redirects
• Google Analytics Help, Ecommerce purchases report — support.google.com/analytics/answer/12924131