E-commerce Replatforming: How to Move Your Online Store Without Losing Sales or Search Traffic

Moving an online store to a new platform is one of the riskier projects an e-commerce business takes on. The store keeps trading while it is being rebuilt, and a mistake at launch shows up immediately as lost orders or a drop in search traffic.

Most of that risk is manageable if the work is planned as a data and URL migration first and a redesign second. Whether you are moving to a hosted platform or to a custom build through e-commerce development, the same questions apply: what moves, what does not, and how customers and search engines find the new pages.

Signs it is time to move, and when it is not

Replatforming makes sense when the platform itself is the constraint. Typical signs are a version that is no longer supported or patched, hosting and plugin costs that rise faster than revenue, routine changes that need a developer every time, slow pages that tuning has not fixed, and requirements the platform cannot meet, such as multiple currencies, wholesale pricing or a connection to your warehouse system.

It is the wrong answer when the real problem is something else. A dated design can be replaced with a new theme, and poor conversion is often a matter of product content, pricing or checkout friction. A migration takes sustained attention and carries search risk, so it should buy you something a smaller project could not.

Plan the data before the design

Start with an inventory of everything the current store holds and decide, item by item, whether it moves, gets cleaned up first, or is left behind. The four main groups are:

• Products: variants, SKUs, images, categories, attributes, stock levels and custom fields.
• Customers: accounts, addresses, marketing consent status and customer groups.
• Orders: the history needed for support, returns, accounting and reporting.
• Content: category descriptions, blog posts, policy pages, page titles and meta descriptions.

Order matters, because records refer to each other. Shopify's own migration guide, for example, advises that you import products first, then customers, then historical orders so that they connect properly. Run at least one full trial import well before launch to expose the mismatches: variants that do not map, attributes with no equivalent field, and duplicate customer records.

What usually cannot be migrated cleanly

Some data does not survive the move, and it is better to know that at the start than in launch week.

Customer passwords

Passwords are stored in a scrambled form that is specific to the old system, so they generally cannot be carried across. Shopify states that you cannot migrate customer passwords from another store using a CSV and must invite customers to create new ones. Whatever platform you choose, plan the account reactivation email and brief your support team before it goes out.

Saved cards and subscriptions

You never hold full card numbers yourself, so stored payment methods can only move if your old payment processor transfers them securely to the new one. Stripe's documentation notes that the previous processor might take a few days or several weeks to transfer the data. If you sell subscriptions, start this conversation early.

Order history and reviews

Old orders can often be imported as records, but details such as refunds, partial shipments, discounts and tax breakdowns may not map exactly. Decide how many years you need on the new platform and archive the rest in an export your finance team can open. Reviews held in a third-party tool usually follow you; reviews built into the old platform may need a separate import.

URL mapping and redirects

This is the part that protects your search traffic. Almost every platform uses its own URL structure, so product and category addresses will change. Search engines treat a changed address as a new page unless you tell them where the old one went.

Google's guidance on site moves with URL changes describes the process: list your old URLs from sitemaps, server logs and analytics, map each to its new equivalent, and use server-side permanent redirects. Google says to redirect straight to the final destination rather than through a chain, and to keep redirects in place for at least one year. Its redirects documentation explains that a permanent redirect (status 301 or 308) tells Google to show the new address in results, while a temporary one keeps the old address.

In practice, map every URL that earns traffic, has external links or takes orders, one to one. Sending discontinued products or whole sections to the home page is a known mistake: Google warns that redirecting many old URLs to one irrelevant destination can be treated as a soft 404. Send a retired product to its closest replacement or its category instead, and update internal links, canonical tags and the XML sitemap to the new addresses.

Integrations you will have to rebuild

Data moves; integrations do not. Each connection to an outside service has to be set up again and tested on the new platform, and this work is routinely underestimated.

• Payments: gateway accounts, wallets, fraud rules, refunds and settlement reports.
• Shipping: carrier rates, zones, label printing and tracking emails.
• Tax: US sales tax and UK VAT are set up differently on every platform, so have your accountant confirm the configuration.
• Email and marketing: order notifications, abandoned cart flows, list sync, analytics and advertising tags.
• Back office: inventory, ERP, accounting and marketplace or shopping feeds.

Ask for a written list of every integration, who owns it, and how it will be tested.

Choosing a launch date, testing and a rollback plan

Google suggests timing a move for a period of lower traffic where your business is seasonal. For most stores that means avoiding the weeks before Black Friday and Christmas and any sale already advertised. Launch early in the week, when the full team is available for the following days.

Before launch, place real test orders covering each payment method, a discount code, a refund, and domestic and international addresses. Run the redirect map through a crawler to confirm each old URL returns a permanent redirect to a live page. Google also advises lowering your DNS TTL at least a week ahead so the switch takes effect faster.

A rollback plan answers one question: if checkout fails on launch day, how do you get back to taking orders within the hour? Keep the old store intact and switchable, agree who can make the call, and decide in advance what happens to orders placed on the new store if you revert.

Common mistakes to avoid

The same few errors account for most painful migrations. Google lists leaving a noindex rule or robots.txt block from the staging site in place as a common one, and it can remove pages from search quietly. Others are changing the design, URL structure, content and domain all at once, so no one can tell which change caused a drop; dropping page titles and descriptions that were ranking; losing orders placed during the final import; and ending the old platform contract before the data has been verified.

What to watch in the first weeks after launch

Expect some movement. Google says rankings may fluctuate while it recrawls the site, and that for a medium-sized site it can take a few weeks or more for new URLs to replace old ones in results. That is normal; a sustained fall on specific pages is not, and usually points to a missing or wrong redirect.

Check daily at first: order volume and conversion rate against the same period before launch, payment failures, 404 errors, and the indexing and sitemap reports in Search Console. Watch support messages for login problems and missing order history.

What to do next

Before speaking to any vendor, export your top landing pages and their traffic, list every integration the store depends on, and write down what the current platform prevents you from doing. Those three documents turn a vague replatforming idea into a scope that can be estimated. If you are comparing a hosted platform with a custom build, our article on custom software development cost drivers explains what moves the budget.

Conclusion

A store migration succeeds when nothing surprising happens: customers find their accounts, old links land on the right pages, orders flow to the warehouse, and search traffic settles after a few weeks. That outcome comes from a complete data inventory, a one-to-one redirect map, rebuilt and tested integrations, a quiet launch date and a rollback you never need.

Entrant Technologies builds websites, web applications and e-commerce stores. If you are planning a move and want a second opinion on scope, you can request a quote and describe your current setup.