Moving to a new web host without losing email or rankings

To move your website to a new host without losing email or Google rankings, keep the domain and every page address exactly as they are, and change only where the domain points. List everything the old host does first. Copy the site to the new host and test it there. Lower your DNS TTL about a week ahead, copy every DNS record, including your email records, then switch. Keep the old hosting running until its traffic has stopped.

This guide covers a change of hosting company where your domain and page addresses stay the same. If your page addresses are changing too, that is a different job, with redirects, and we point you to the right guide below.

Key takeaways

  • A hosting move keeps your domain and page addresses. If addresses change, plan it as a redesign or migration, with redirects.
  • Write down everything the old host does for you: website, DNS, email, certificates, backups, scheduled jobs and forms.
  • Copy and test the site on the new host before visitors see any change.
  • Lower the DNS TTL about a week ahead, recreate every DNS record exactly, then switch.
  • Keep the old hosting until traffic to it reaches zero, and watch Search Console.
  • Your new host will handle personal data for you, so you need a written contract that covers UK GDPR Article 28.

Is this a hosting move or a site move?

Google’s guide to changing your hosting says “A change in hosting infrastructure means switching hosting providers or moving to a content distribution network (CDN).” It adds: “This guide is only for migrations that don’t affect the user-visible URL.”

That is the case this guide covers. The same domain, the same page addresses and the same content, served from a different company’s servers. Visitors should notice no difference.

If anything visible changes at the same time, such as a new platform, a new design that changes page addresses, or a new domain, plan it as a site move instead. Our website redesign checklist covers redirects and launch checks, and our guide to moving from Wix or Squarespace covers a change of platform. In our view, it is safer to change host first and redesign later, or the other way round, than to do both at once, because when something goes wrong you’ll know which change caused it.

Step 1: list what you have

Many hosting accounts do more than serve the website, and the extras are easy to miss. Before you contact a new host, write down:

  • The domain registrar: the company the domain is registered through, the account it sits in and the renewal date.
  • The DNS: who runs it. It may be your registrar, your old host or a separate service. Export or screenshot every record.
  • The website: its files, its database and which software versions it runs on.
  • Email: whether your mailboxes are with the old host or a separate email service, and the MX, SPF, DKIM and DMARC records that go with them.
  • The security certificate that gives you https, and whether it renews automatically.
  • Backups: what the old host keeps, and a full copy you have downloaded yourself.
  • Logins: hosting, website admin, DNS and email, and who holds each one.
  • Forms: every form on the site, where it sends enquiries and how that email is sent.
  • Scheduled jobs: anything that runs on a timer, such as backups, feed imports or reminder emails.
  • Everything else in the DNS: subdomains, verification records for Google and other services, and any records your phone system, booking tool or email marketing service relies on.

Two questions decide how big the job is. Does the old host run your DNS? And does it run your email? If the answer to either is yes, the move involves more than the website, and the sections below on DNS and email apply in full.

Step 2: check you control the domain

You don’t need to move your domain to change host. The domain stays where it is, and you change the records that tell the internet which server to use. What you do need is control of it.

  • The domain should be registered to your business, in a registrar account you can log in to. Our guide to checking whether you own your website takes five minutes.
  • Check the renewal date, and that renewal won’t fall in the middle of the move. Our guide to domain renewal explains how to make sure it renews.
  • Make sure the email address on the registrar account is one you read, not a former supplier’s.

If you also want to move the domain to a different registrar, our suggestion is to do it as a separate step, before or after the hosting move. Our guide to leaving a pay-monthly website explains how domain transfers work.

Step 3: plan the timing and lower the TTL

Every DNS record has a TTL (time to live): how long other systems may keep a copy before checking again. If the TTL is long, some visitors will keep reaching the old server for longer after you switch. Google’s advice: “Consider lowering the TTL to a conservative low value (for example, a few hours) at least a week in advance of the move to refresh DNS caches faster.”

For the timing, our suggestions:

  • Overlap the two hosting contracts by at least a month. Check the old contract’s notice period, and don’t give notice until the move is finished.
  • Switch on a quiet weekday, when someone can check the site, the forms and the email straight afterwards. Avoid the day before a holiday or a tender deadline.
  • Agree a content freeze: nobody edits the old site between the final copy and the switch, so no changes are lost.

Step 4: copy and test the site on the new host

Google’s first step is to “upload a copy of your site to your new hosting provider”, then “verify that it works as expected by thoroughly testing all aspects of how your users interact with your site”. It suggests you “review all elements of your site: pages, images, forms, and downloads (such as PDF files)”.

Google also suggests testing on a temporary address before the real domain points at it, and warns: “To prevent accidentally letting the test site get indexed, add the noindex robots rule to the HTML or the HTTP headers of your pages.”

On the new copy, check:

  • Every page address is the same. Compare the site’s sitemap, or a crawl, on the old and new copies. A hosting move should change no addresses.
  • Existing redirects still work, including http to https and with or without www, as the old site used them.
  • Forms send, and the email arrives. Send a test from every form and check it reaches the right person, not spam.
  • Scheduled jobs run on the new server, and the old ones are switched off at the right moment.
  • The security certificate. Ask the new host when it will be issued: before the switch, or only once the domain points at them, and how long that takes. Our guide to SSL certificates and browser security warnings explains what can go wrong.
  • Search Console verification. Google says “make sure you don’t forget to include your current verification file in your new copy of the site”, if you verify that way.
  • Nothing blocks Google. Google warns about firewall or denial of service protection: “Make sure it does not block Googlebot’s ability to reach the DNS or the hosting provider’s servers.”

What happens to your email?

In our view, email is easy to break in a hosting move, because it depends on DNS records that are often overlooked. Google explains that when someone emails you, the sender’s computer “looks up the MX records for your email domain” “to figure out where to deliver it”, in its help page on MX records.

If your email is with a separate email service

Your mailboxes don’t move, so your MX records shouldn’t change. The risk is losing them by accident when the DNS moves. If the DNS is moving to the new host, recreate every email record there exactly before you switch:

  • MX, which says where email for your domain is delivered.
  • SPF, which lists the servers allowed to send for you. Google’s SPF help says “Your SPF record should include the domains (or IP addresses) of all servers that send email for your organization (domain)”, and lists “Web servers” among them. If your website sends form emails itself, the new server may need adding, or the forms can send through your email service instead.
  • DKIM, a signature on each message. Google says “DKIM helps protect your domain against spoofing by authenticating your email with a DKIM signature.”
  • DMARC, which Google says “tells receiving email servers what action to take on messages sent from your domain that don’t pass SPF or DKIM authentication”. The National Cyber Security Centre (NCSC) adds, in its email security and anti-spoofing guidance, that “DMARC also generates reports, which you can use to understand how your email is being handled.” Those reports are a useful check after a move.

If your email is with the old host

Then your email is moving too. Set up every mailbox and shared address at the new provider first, copy the old messages across, and only then change the MX records. Google’s advice for changing MX records: “Schedule the change to your MX records when your email volume is low, such as in the evening or on the weekend.” It also suggests telling key contacts the date and time of the change and how to resend any message that bounces. Our guide to business email on your own domain explains these records in more detail.

Step 5: switch the DNS

When the copy is tested and the TTL has been low for a week, you’re ready. First, remove anything you added to hide the test copy. Google says “Be sure to remove any such blocks from the new copy of the site when you’re ready to start the move.” Then: “You start the move by updating the DNS records to point to the new hosting provider.”

There are two common ways to do it:

  • Change the website records only where your DNS is now. The email and other records stay untouched. This is the lower-risk route, in our view.
  • Move the whole DNS to the new host by changing the domain’s nameservers. Every record has to exist at the new host first, exactly as before, or email and other services stop.

Straight after the switch, check that the site loads from the new server, that every page shows the padlock, that each form sends, and that email arrives and sends normally.

How long should you keep the old host?

Until nobody is using it. Google’s overview says to shut down the old hosting “when you’re confident that all users, including Googlebot, are receiving content correctly from the new infrastructure and no one is using the old infrastructure.” It suggests keeping an eye on the server logs on both, and says “once the traffic to the old provider reaches zero, you can shut down your old hosting infrastructure”.

Before you cancel, also make sure:

  • email has worked normally for at least a week, which is our suggestion;
  • you have downloaded a final full backup, and any old emails you need;
  • nothing else still points at the old server, such as a subdomain or a scheduled job.

In Search Console, Google says “it’s normal to see a temporary drop in Googlebot’s crawl rate immediately after the launch, followed by a steady increase over the next few days”. Watch the page indexing and crawl reports for a few weeks. Nobody can promise rankings won’t move. In our view, though, a move that keeps the same addresses and content gives Google little to reassess.

Contracts, data and where it is stored

This section is general information, not legal advice. If you’re unsure what applies to your business, check with an adviser.

Your website holds personal data: enquiries, job applications, perhaps client logins. A host that stores it for you is usually acting as your processor, so Article 28 of UK GDPR applies. It says “the controller shall use only processors providing sufficient guarantees to implement appropriate technical and organisational measures”, and that the contract “shall be in writing, including in electronic form”. It also says “The processor shall not engage another processor without prior specific or general written authorisation of the controller.”

Before you sign with the new host:

  • Read its data processing terms, and check they cover what Article 28 requires.
  • Ask where the servers and the backups are located, and which other companies it uses to provide the service.
  • Ask how it will tell you about a security incident. Our guide to website security for a growing business lists more questions to ask a host.

Location matters because, as guidance from the ICO (the UK’s data protection regulator; since 30 September 2026 its legal name is the Information Commission) on international transfers puts it, “People risk losing the protection of UK data protection law if their personal information is sent (or made accessible) outside the UK.” If the new host would store or access data outside the UK, read that guidance or ask an adviser.

Finally, the old host. Article 28 says a processor’s contract must provide that it, “at the choice of the controller, deletes or returns all the personal data to the controller after the end of the provision of services relating to processing, and deletes existing copies”. Once you have your final backup, ask the old host in writing to delete your data, including its backups, and keep the reply.

The move on one page

When Do this
A month or more before List what the old host does, check you control the domain, agree the new host’s terms
A week before Lower the TTL; copy and test the site on the new host
Switch day Final copy, DNS records recreated, switch, then test pages, forms and email
The weeks after Watch the old server’s logs and Search Console
Old traffic at zero Final backup, cancel the old hosting, ask the old host to delete your data

Common questions

Will changing host affect our Google rankings?
In our view, if the domain, page addresses and content stay the same, there is little for Google to reassess. Google says a temporary drop in crawl rate after the move is normal. Nobody can promise rankings either way.

Do we have to move our domain too?
No. The domain can stay with its current registrar. You only change the records that point it at the new host.

Will we lose email during the move?
It shouldn’t, if your email records are recreated exactly before the DNS changes. If your mailboxes are moving too, some messages may bounce during the change, so tell key contacts how to resend.

How long does the switch take?
Changing the records is quick. How quickly every visitor reaches the new server depends on the TTL, which is why Google suggests lowering it at least a week before.

Can we move host and redesign at the same time?
You can, but in our view it is easier to spot and fix problems if you do one, check it, then do the other.

Free help

If you’d like help with a move

We’re Hintling Studio, an independent web design studio registered in London. We build websites for established businesses across the UK. If you’re getting a new website from us, you can add “Move an existing site / content migration (up to 20 pages, including redirects from the old page addresses to the new ones, so old links lead to the right page)”. Hosting and your domain are extra.

See our work and what’s in each package, or tell us about your current site.

Sources checked on 18 November 2026: Google Search Central, Google Workspace Help, the NCSC, legislation.gov.uk and the ICO. Hintling Studio is not connected with Google, Wix, Squarespace, the NCSC or the ICO (Information Commission).

Is your website working for you?

A one-page checklist to score your website in about ten minutes. No sign-up and no email needed: just download it.

Preview of the one-page Is your website working for you? checklist

Let’s build yours.

Send us a short brief and we’ll reply with a fixed quote and a timeline. No calls needed unless you want one.