Sales: 0203 002 0710
Accounts: 0208 432 3002
Admin: 0208 432 6953
A growing online shop can reach the point where its existing platform costs more in lost sales, admin time and marketing limitations than it saves. This guide to ecommerce site migration explains how to move without putting hard-won rankings, customer trust or day-to-day trading at risk.
For most businesses, a migration is not simply a design project. It may involve changing platform, rebuilding product pages, connecting stock systems, improving checkout, moving hosting or introducing better reporting. The commercial opportunity can be significant, but so can the cost of getting the details wrong. A site can look excellent on launch day and still lose revenue if redirects, product data, payment settings or tracking have been missed.
The first question is not whether Shopify, WooCommerce, Magento or another platform is best. It is what the new website needs to achieve that the current one cannot. A retailer processing a modest number of straightforward orders has different needs from a wholesaler with customer-specific pricing, complex product options and a back-office system to integrate.
Set measurable objectives before any build begins. You may want to improve mobile conversion rates, reduce the time spent updating stock, make paid advertising more profitable, support trade accounts or give your team a clearer view of sales performance. These objectives help decide what must be retained, what should be improved and what can be left behind.
A cheaper platform is not always cheaper over time. Subscription costs, transaction fees, app charges, development work and support requirements all need to be considered. Equally, a highly customised system may offer flexibility but create greater maintenance costs. The right choice depends on the way your business sells, not on whichever platform is currently receiving the most attention.
A detailed audit is the foundation of a controlled migration. Treat the existing website as a source of valuable commercial information, even if you are replacing it because it has become difficult to manage.
Record every indexable URL, including products, categories, brand pages, blog posts, help pages and any landing pages used in advertising. Identify the pages that generate organic visits, enquiries, sales and backlinks. These pages require particular care because removing or changing them without a plan can reduce visibility in search results.
The audit should also cover product information. Check the quality of titles, descriptions, images, prices, variants, stock codes, delivery rules, tax settings and related products. Migration is often a good opportunity to improve inconsistent data, but it is not wise to make widespread untested changes at the same time as moving platforms. Decide which content needs cleaning before import and which changes can wait until trading is stable.
Do not overlook customer and order data. Establish what must be moved for operational, legal and customer-service reasons. Customer passwords usually cannot be transferred in readable form, so customers may need to reset them. Previous orders, returns, gift cards, loyalty balances, subscriptions and trade pricing can all need separate migration plans.
A website launch date can create pressure to rush, particularly if an old platform is being retired. A better approach is to map the customer journey and test each stage before committing to launch.
Consider how someone finds a product through Google, an advert, social media or a direct visit. They should be able to land on the right page, understand the offer, choose options, add products to their basket, pay securely, receive confirmation and contact you if they need help. If the business sells to trade customers, test account approval, agreed pricing, VAT handling, purchase orders and repeat ordering too.
It is also worth mapping internal journeys. Can staff update stock, process an order, issue a refund, manage returns and respond to customer queries without relying on manual workarounds? The new site should reduce friction for the people running the business as well as the people buying from it.
Search engine visibility is one of the most common casualties of an ecommerce migration. When a URL changes, search engines and visitors need clear instruction on where the old page has moved. This is done through permanent 301 redirects, mapped from each valuable old URL to its closest relevant new equivalent.
Avoid sending large numbers of old pages to the homepage. A visitor looking for a specific product should be taken to that product, its replacement or the most relevant category. Broad redirects frustrate users and can weaken the relevance signals that support rankings.
Keep page titles, headings, product copy and internal links under review as well. A new design should not accidentally remove useful copy, product filters or category information that helped pages rank. If an item is genuinely discontinued and has no suitable replacement, a properly handled unavailable-product page may be more honest than directing the customer somewhere unrelated.
Test redirects on a staging site where possible, then monitor them after launch. Search performance may fluctuate briefly while search engines recrawl the new site, but sharp declines in traffic or sales need prompt investigation rather than hopeful waiting.
Data migration is rarely as simple as exporting a spreadsheet and uploading it elsewhere. Platforms use different fields, image rules, product structures and variant logic. A product with colour and size options, for example, must retain the correct stock level, price, image and SKU for every variation.
Complete a test import before the final migration. Compare a representative selection of products, customers and orders against the source data. Check spelling, imagery, URLs, weights, prices, sale prices, tax calculations and stock quantities. Test how products appear on mobile as well as desktop, particularly where long names or multiple variants are involved.
Use a final data freeze before launch. This means agreeing a point at which changes to products, stock or customer records are either paused or carefully recorded, so they can be copied into the new system. Without this control, orders or stock updates made during the move can be lost.
A working checkout is the commercial heart of an ecommerce site. Run real test orders using every payment method offered, including cards, digital wallets, finance options or PayPal where applicable. Confirm that authorisations, confirmation emails, order notifications, refunds and stock adjustments all work as expected.
Delivery deserves equal attention. Test UK mainland, Highlands and islands, Northern Ireland, international destinations, free-delivery thresholds, collection options and bulky-item rules where relevant. Incorrect delivery charges are a quick way to lose margin or create difficult customer conversations.
Measurement should be in place before paid traffic is sent to the new site. Confirm that analytics, ecommerce conversion tracking, advertising pixels and consent settings are configured correctly. You need to know which channels generate profitable sales, not merely visits. Track revenue, conversion rate, average order value, checkout abandonment and the performance of key product categories from the first day.
A practical pre-launch check should cover at least these areas:
Launching at a quiet trading time gives your team room to respond if anything needs attention. Avoid major promotional campaigns, price changes or a large email send during the first hours unless the site has been thoroughly tested and support cover is available.
Once the new site is live, check the pages that matter most: best-selling products, high-traffic categories, campaign landing pages and checkout. Place a real order, test it on a mobile phone and review the emails received by both the customer and the business. Monitor server errors, failed payments, broken links and search-console reports closely.
Keep the old site and its data accessible for a defined period, subject to security and data-protection requirements. It can be invaluable when resolving an order query, checking historic content or confirming how a product was previously configured.
The first few weeks reveal how real customers use the new site. They may search for terms your product navigation does not use, abandon baskets because delivery information is unclear, or contact you about a feature that made sense internally but not to buyers. These are useful signals, not a reason to panic.
Review sales data alongside customer feedback and search performance. Prioritise changes that remove barriers to purchase or improve the return from SEO and paid advertising. Npwebservices approaches ecommerce projects with this longer-term view: a website should support measurable growth after launch, not simply look different on launch day.
A carefully planned migration protects the value you have already built while giving your business a stronger platform for the next stage of growth. Give the process enough time, test the details that affect real orders, and keep commercial performance at the centre of every decision.
