How to Plan Website Migration Without Losing Leads

A website migration can improve a struggling business asset – or quietly remove the pages, rankings and enquiry routes that bring work through the door. Knowing how to plan website migration properly means treating it as a business project, not a design handover. The goal is not simply to launch a smarter-looking site. It is to protect what already works while fixing what is costing you customers.

For a local service business, that might mean keeping your Dunfermline plumbing page visible in Google, making sure calls still reach the right person, and ensuring customers can submit an enquiry from a mobile without friction. A new website should leave you in a stronger position than the old one, not asking why leads have dropped.

Start with the reason for moving

Website migration can mean several things: moving to a new hosting provider, changing domain name, rebuilding an old site in WordPress, merging websites, or restructuring pages during a rebrand. Each carries different risks.

If your current site is slow, difficult to update and poor on mobile, a rebuild may be justified. If it already ranks well for profitable services, however, changing every page title, URL and piece of content at the same time creates unnecessary exposure. Improve what needs improving, but do not throw away useful search equity because the new design has a cleaner menu.

Before any work starts, agree what success looks like. This should be commercial rather than purely visual. You may want more qualified quote requests, better visibility for specific local services, faster mobile performance, a clearer route to telephone enquiries, or less time spent manually handling customer information.

Write down the answers to three questions: what must not be lost, what must improve, and who makes the final decision. This prevents a migration becoming a collection of personal design preferences.

How to plan website migration around your existing assets

The first job is to understand what is currently on the site. You cannot protect pages you have not identified.

Create an inventory of every indexable page, including service pages, location pages, blog posts, contact pages, image files and downloadable documents. Record each page’s URL, page title, main purpose, traffic level and whether it generates enquiries. Your web developer can gather much of this information, but the business owner should help identify pages that matter commercially even if analytics underestimates them.

For example, a page about emergency boiler repairs may not receive huge traffic, but one call from it could be worth far more than dozens of casual visits to a gallery page. Likewise, an older blog post may attract local search visitors every month even if it does not look like a priority internally.

Check the systems connected to the website too. These often cause more disruption than the pages themselves. Confirm how contact forms are delivered, whether you use booking software, mailing list sign-ups, payment tools, call tracking, analytics, cookie consent, live chat or CRM integrations. A form that looks correct but sends submissions to an outdated email address is not a successful launch.

Establish a performance baseline

Take a snapshot before changes begin. Record organic search traffic, rankings for priority local terms, enquiry volumes, phone calls, form submissions and the pages responsible for those actions. Keep this data somewhere accessible.

Rankings can move after a migration, particularly where content and page structure have changed. Without a baseline, it is difficult to distinguish a normal short-term fluctuation from a real problem that needs attention. It also makes it harder to judge whether the investment has improved results over the following months.

Map every old URL to a clear destination

Redirects are one of the most important parts of a website migration plan. When an old URL changes, it should normally send visitors and search engines to the most relevant new page using a permanent 301 redirect.

This is not a job for a blanket redirect that sends every old page to the homepage. Someone looking for a specific service will not appreciate being dropped at a general welcome page, and Google receives less useful information about what replaced the old content.

A proper redirect map pairs each old address with its closest equivalent. If an old service page has been replaced with an improved version, redirect it to that new service page. If two thin pages have been combined into one stronger page, redirect both to the combined page. If a page has no relevant replacement and offers no value, it may be better to retire it rather than force an irrelevant redirect.

Pay particular attention to URLs that have backlinks, traffic or proven enquiry value. Changing a page address just because a new structure looks tidier is rarely worth the risk. Clear, readable URLs are useful, but stability is useful too.

Build and test the new site before launch

The new site should be built on a staging environment, not assembled live while customers are trying to use it. This gives you room to test every important journey without exposing half-finished pages, broken menus or placeholder text.

Review the site from the perspective of a customer who does not know your business. Can they quickly see what you do, where you work and how to contact you? Is each key service easy to find? Do phone numbers work on a mobile? Does the enquiry form confirm that it has been sent?

Content should be checked carefully during a redesign. Businesses often lose valuable copy because it is considered old, only to discover that the replacement page is shorter, vaguer and less helpful to searchers. Fresh copy is worthwhile when it is clearer and more persuasive, not simply because it is new.

Technical checks matter as well. Test page speed, mobile layouts, internal links, image sizes, contact forms, tracking codes, search settings and security certificates. Ensure the staging site cannot appear in Google search results, then remove that restriction when the live site is ready. Accidentally carrying a “do not index” setting into launch can make a new site invisible.

Plan the launch window, not just the launch date

Avoid switching a website at the busiest point in your week. A restaurant should not migrate before a major weekend booking period, and a trades business should not risk its contact routes during a seasonal rush. Choose a window when the people responsible for the site, hosting and business enquiries are available to respond quickly.

On launch day, publish the site, activate the redirect map and test the most important pages immediately. Check the homepage, priority service pages, location pages, contact page, telephone links, forms and any booking or payment route. Submit a real test enquiry and confirm who receives it.

Also check that the preferred version of your domain is consistent. Visitors should not be able to reach competing versions with and without www, or through old HTTP addresses. These details can look minor, but they affect user trust and can create avoidable search confusion.

Do not announce the new site widely until these checks are complete. It is better to spend an extra hour testing than direct customers to a broken form after posting about the launch on social media.

Watch performance after the migration

A migration is not finished when the new homepage is live. For the first few weeks, monitor organic traffic, indexed pages, key rankings, form submissions and error reports. Check for 404 pages, which appear when visitors land on an address that no longer exists and has no working redirect.

Some movement in rankings is normal, especially after a substantial rebuild. A sharp or sustained drop deserves investigation. Common causes include missing redirects, removed content, blocked pages, poor mobile rendering, broken internal links or tracking that was not reinstalled correctly.

Keep the old site available as a private reference for a short period where possible. It can help resolve missed content, redirects and form details without relying on memory. Do not leave it publicly accessible as a duplicate website, though, as that creates a different set of problems.

If you are changing hosting only and retaining the same domain and site structure, the process is usually lower risk. If you are changing domains, platforms, page structure and branding together, give the planning stage more time. Combining every major change may be necessary, but it raises the need for disciplined testing and post-launch monitoring.

A well-planned migration is not about avoiding change. It is about making change accountable. Before you replace a website, make sure someone can show you what will happen to your rankings, your enquiry paths and the pages that already earn their place. That is the difference between a fresh start and an expensive interruption.