A website migration can look like a design project on a spreadsheet and become a revenue problem the moment it goes live. If product URLs disappear, tracking stops working or the checkout fails on mobile, the cost is immediate. Knowing how to migrate ecommerce website properly means treating it as a business-critical change, not simply moving pages from one platform to another.

A good migration protects the parts of your site that already work: search visibility, product data, customer trust, conversion paths and reporting. It also gives you a stronger platform to grow from. The difference comes down to planning, testing and accountability before launch day.

Start with the commercial reason for moving

First, be clear about why you are migrating. Perhaps your current platform is slow, difficult to manage, costly to maintain or unable to support the integrations your team needs. You may be replatforming from WooCommerce to Shopify, moving to a more capable version of Magento, or replacing a custom system that has become a bottleneck.

The reason matters because it shapes the brief. A migration designed to improve site speed and mobile conversion needs different priorities from one driven by complex B2B pricing, international selling or stock management. Do not assume a newer platform will fix poor product information, weak category structure or a confusing checkout. Those problems move with you unless they are addressed.

Set measurable outcomes before work starts. This could include maintaining organic traffic to key categories, reducing checkout abandonment, improving page speed, cutting admin time or making paid campaign tracking more reliable. These objectives give the project team something practical to work towards and help you judge whether the move was worthwhile.

Audit the current website before anything is built

The old site is your evidence base. Before changing it, create a full record of what exists and what performs. This includes URLs, page titles, meta descriptions, headings, product pages, category pages, blog content, images, downloadable files and internal links.

Pay close attention to pages that bring in organic traffic, earn backlinks or generate sales. A discontinued product page may have little commercial value now, but if it attracts valuable search traffic, deleting it without a plan can damage performance. Equally, there is no sense carrying over hundreds of thin, duplicate or obsolete pages just because they exist.

Your audit should also cover the less visible parts of the shop. Check payment gateways, shipping rules, tax settings, stock feeds, email flows, reviews, wish lists, trade accounts, discount codes, consent tools, customer service software and any connection to your accounting or warehouse system. These are often where migrations become delayed or expensive.

Baseline your current performance too. Record organic traffic, revenue, conversion rate, average order value, paid campaign results, crawl errors and page speed. Without a baseline, it is hard to separate normal seasonal movement from a migration issue after launch.

Build the new site around customers, not the old platform

A migration is a useful moment to improve the buying journey, but it is not an excuse to redesign everything on instinct. Use real data from search terms, site search, analytics, customer feedback and sales teams to decide how people should find and compare products.

Keep category structures logical and URLs readable. For an ecommerce business, category and subcategory pages are often as commercially important as individual product pages. They help customers browse and give search engines a clear understanding of your range. If you change the structure, map every old URL to the closest relevant new page.

Product data needs particular care. Names, descriptions, variants, prices, stock status, specifications, delivery information and images should be complete and consistent before import. Rushed data migration creates duplicate products, missing variations and filters that do not work properly. It also makes the new site look unfinished, which is not a good first impression for returning customers.

How to migrate ecommerce website URLs without losing visibility

URL mapping is one of the most important parts of how to migrate ecommerce website successfully. Every valuable old URL needs a clear destination on the new site. Where a page has a direct equivalent, use a permanent 301 redirect. Where there is no equivalent, redirect to the nearest genuinely relevant category or replacement product where appropriate.

Avoid redirecting every removed page to the homepage. It is unhelpful for visitors and gives search engines little context. Never leave important old URLs to return a 404 error simply because they were missed during the build.

Redirects should be prepared before launch, then tested in bulk. Check for redirect chains, loops and pages that land in the wrong place. One redirect is usually fine. A chain of several redirects wastes crawl budget, slows the customer journey and makes future maintenance harder.

The new site must also have its own technical basics in place: accurate canonical tags, a clean XML sitemap, sensible internal linking, indexation controls and correct handling of filtered or faceted pages. These details are not glamorous, but they affect whether your new site can be crawled, understood and trusted by search engines.

Test the full buying journey on a staging site

Do not wait until launch to find out whether the shop works. Use a password-protected staging environment to test every meaningful customer journey across desktop and mobile.

That includes browsing categories, using search and filters, choosing variants, adding products to the basket, applying discounts, selecting delivery, paying by each available method and receiving order confirmation emails. Test edge cases as well, such as out-of-stock products, failed payments, guest checkout, trade pricing and international addresses if they apply to your business.

The most useful testing is done by people who were not involved in building the site. They are more likely to spot unclear wording, broken buttons and assumptions that the project team has stopped noticing. Ask your customer service and sales staff to test it too. They know the questions buyers actually ask.

Before launch, confirm that:

• analytics and ecommerce revenue tracking record test transactions correctly
• conversion tags for paid campaigns fire only where they should
• cookie consent settings do not block essential measurement unnecessarily
• transactional emails arrive, display correctly and contain accurate order information
• stock, pricing and order data sync correctly with connected systems

Plan launch as a controlled release

Avoid launching during your busiest sales period, a major promotion or a time when key staff are unavailable. Most migrations have a few issues after go-live, even when they have been well tested. Give yourself space to respond without putting unnecessary revenue at risk.

Put one person in charge of the launch checklist and agree who owns each area: development, content, SEO, paid media, operations and customer service. A clear decision-maker prevents the familiar situation where everyone assumes someone else has checked the checkout or redirects.

At launch, remove any staging restrictions, switch the site to the live domain, activate redirects, submit the new sitemap and run immediate checks on priority pages. Place real test orders where possible, including on mobile. Review the site in different browsers and watch for mixed content warnings, broken images, missing scripts and errors in the browser console.

Monitor performance closely after go-live

The first few weeks are about finding and fixing issues quickly. Check orders, revenue, conversion rate, payment failures, error pages, search console coverage, crawl errors and organic landing-page traffic daily at first. Compare performance with the baseline you recorded earlier, while allowing for normal day-to-day variation.

Some short-term movement in rankings is possible when URLs and site architecture change. That does not automatically mean the migration has failed. What matters is whether priority pages are indexed, redirects work, pages are crawlable and traffic begins to settle. If a high-value category falls sharply, investigate the specific page rather than making broad changes across the site.

Keep the old site and its data accessible for a sensible period. You may need it to check historic orders, compare content or recover a missed URL. Do not cancel hosting or remove backups immediately after launch.

A well-run migration is not invisible. It is controlled, measured and focused on protecting revenue while improving the platform beneath it. If the move feels rushed, pause and fix the gaps before customers find them. That decision is usually cheaper than repairing lost sales and search visibility afterwards.