How to Plan Website Migration Without Losing Leads

Moving a website is a bit like moving house: the furniture is the easy bit. The trouble starts when nobody has labelled the boxes, the new keys do not work, and your post is still going to the old address.

Knowing how to plan website migration properly protects the things your business has spent years building – your Google visibility, enquiry forms, content, email and customer trust.

I have seen website migrations treated as a simple switch from one hosting account to another. Sometimes they are.

More often, a business is also changing domain names, redesigning pages, replacing software or altering its website structure at the same time. That is where small omissions can turn into a nasty drop in traffic or a Monday morning full of “the website’s gone” messages.

The good news is that a well-planned migration is very manageable. The aim is not to make it exciting. The aim is to make it boring, checked and uneventful.

Start with the reason for moving

Before choosing dates or copying files, be clear about what is actually changing and why. You might be moving WordPress hosting because the current provider is slow or unhelpful. You may be launching a redesign because the existing website looks dated and is not generating enquiries. Or perhaps your business has changed name and needs a new domain.

Each situation carries different risks. A hosting-only move should leave the public-facing site, URLs and content largely unchanged. A redesign can improve speed, usability and conversions, but it may also remove pages that currently bring in useful traffic. A domain change needs the most careful SEO planning because Google has to understand that the business has moved address.

Write down what must stay working after launch. For most service businesses, that includes key pages, contact forms, telephone links, email addresses, analytics, search visibility and any booking or quotation process. This simple list stops the project becoming a design exercise when it is really a business continuity exercise.

Audit the current site before touching it

A migration plan needs a reliable picture of what exists today. Do this before the new site is built, not when everyone is rushing towards a launch date.

Start by crawling or listing every important page and its current URL. Pay particular attention to service pages, location pages, blog posts that receive traffic, PDFs, image files, and any pages used in paid advertising or email campaigns. If a useful page disappears without a replacement, visitors and Google can both hit a dead end.

Then check your data. Look at which pages receive organic traffic, generate enquiries or rank for terms that matter to your business. A low-traffic page is not automatically expendable either. It may be used by an existing customer, linked from another website, or support a valuable service page.

This is one of the most common mistakes I see on WordPress redesigns. Old pages are dismissed as clutter, then a month later someone notices that a popular guide, downloadable brochure or local service page has vanished. Keep what earns its place, improve what is weak, and redirect anything that has a sensible new home.

Make a redirect map

A redirect map is simply a spreadsheet matching each old URL to its new equivalent. For example, an old `/web-design-cambridge/` page might move to `/web-design/cambridge/`. The old address should permanently redirect visitors and search engines to the new one.

Do not point every retired page to the homepage. That is tempting, but usually unhelpful. Someone looking for a specific service should land on the closest relevant page, not be dropped into the digital equivalent of a shopping centre car park.

If there is no genuinely relevant replacement, it can be better to retire the page cleanly. The key is making deliberate decisions rather than leaving broken links behind.

Build and test on a private staging site

Never rebuild a live website in public if you can avoid it. Use a staging site – a private copy where the new WordPress website can be reviewed and tested without visitors or search engines stumbling across it.

The staging site should be blocked from search engine indexing while it is under development. Otherwise, duplicate versions of your content can appear in Google, which causes needless confusion. Just remember to remove that block when the new site goes live. It sounds obvious, yet it is surprisingly easy to launch a lovely new website with a virtual “do not enter” sign still on the door.

Test the website as a potential customer would. Can they find the services they need? Does the site work properly on a phone? Are forms arriving in the right inbox? Do telephone numbers work when tapped? Is the site fast enough on a normal mobile connection, rather than just on the office Wi-Fi next to the kettle?

Also test the less glamorous parts: search, cookies, downloadable files, confirmation emails, maps, security certificates and admin logins. If the website has integrations with a CRM, booking system or email marketing platform, test those too.

Protect SEO while planning a website migration

SEO is not a separate job that happens after launch. It is part of the migration itself.

Keep page titles, headings and on-page copy where they are still relevant, especially on pages that already perform well. A redesign is a good opportunity to sharpen the wording and make calls to action clearer, but avoid rewriting every page simply because the new design looks smart. Large-scale changes to content, URLs and site structure all at once make it harder to spot what caused a problem if rankings dip.

Check that the new site has sensible internal links between related services, location pages and useful articles. Make sure the XML sitemap is available, and that the preferred version of each page is clear. For most businesses, that means choosing one version of the domain – with or without `www` – and sticking to it.

If the domain is changing, the job is more involved. Set up permanent redirects from every important old URL, verify the new domain in Google Search Console, and tell Google about the change of address where appropriate. Keep the old domain active for redirects. Letting it expire soon after launch is rather like taking down the road signs the day after moving premises.

Choose a calm launch window

Avoid launching immediately before a busy sales period, bank holiday or major campaign. Give yourself enough time to monitor the site and fix anything unexpected. For many small businesses, a quieter weekday morning works well because support is available and someone can check emails, enquiries and orders as they arrive.

Take a full backup of the old website and database before the move. Keep a copy somewhere separate from the old hosting account. A backup is not a migration plan, but it is a very useful parachute if something goes wrong.

On launch day, move through a written checklist. Check that the live site loads securely on the correct domain, redirects work, key pages return properly, forms send and receive messages, and tracking is recording visits. Check the site on a mobile as well as a desktop computer.

Watch the site after launch

A migration is not finished the moment the new website appears online. The first few weeks matter.

Monitor Google Search Console for indexing issues, broken pages and redirect errors. Keep an eye on analytics to make sure traffic is still being recorded. Test enquiry forms again, including the thank-you page and email notification. It is worth submitting a real test enquiry from a non-office email address, because mail delivery can behave differently in the real world.

You should expect small fluctuations in rankings after a significant redesign or domain move. Google needs time to recrawl and reassess the changed site. What you do not want is a sustained drop caused by missing pages, blocked indexing, bad redirects or a broken technical setting.

Keep a launch log too. Note the date, what changed, and any fixes made afterwards. If traffic shifts later, that record gives you something more useful than vague memories and crossed fingers.

A migration plan should serve the business

The best website migration is not judged by whether the new design looks different. It is judged by whether customers can still find you, understand what you do and get in touch without friction.

For a WordPress business website, I would rather see a carefully planned move that preserves valuable content and enquiry routes than a flashy relaunch that quietly wipes out years of search visibility. Build the new site well, support it properly after launch, then use the cleaner foundations to grow traffic and leads.

FAQs

How long does a website migration take?

A straightforward hosting move can often be completed in a day once it has been prepared and tested. A redesign, new domain or major content restructure usually takes longer because the planning, redirect mapping and testing are the important bits. The actual switch is only one part of the job.

Will a website migration affect my Google rankings?

It can, particularly if URLs, content or domains change. A well-managed migration with accurate permanent redirects and retained valuable content reduces the risk considerably. Small short-term movement is normal, but a large or lasting fall needs investigating.

Do I need to redirect every old page?

Redirect every useful old page to the closest relevant new page. This is especially important for pages with traffic, backlinks, rankings or customer value. Not every obsolete page needs a redirect, but leaving important ones to return an error is rarely a good idea.

Can I change my domain name and keep my SEO?

Yes, but it needs care. Use permanent redirects from the old domain to matching pages on the new one, update important business listings and keep the old domain active. Search engines need time to process the change, so do not expect it to be instant.

Should I redesign my website during a hosting migration?

It depends. Combining the two can save effort, but it also introduces more variables if something goes wrong. If your current site has valuable rankings and content, a hosting move first and redesign second can be the lower-risk option. If the site urgently needs rebuilding, plan both together with a proper audit and redirect map.

What should I check first after launch?

Check that the correct domain loads securely, key pages work, redirects work, forms deliver emails and analytics records visits. Then review Search Console over the following days and weeks for crawl errors, indexing issues and unexpected missing pages.

A little preparation before the move is cheaper than trying to recover lost enquiries afterwards. Treat the migration as part of your wider website plan, not a technical errand to squeeze in on a Friday afternoon, and your new site has every chance to start earning its keep from day one.