Hosting, DNS and domain are three different things

Before you start, find out who controls each of these. They are often confused, and a move that touches the wrong one causes most of the trouble.

PieceWhat it doesWho usually controls it
Domain registrationYour right to use the nameA registrar; see our domain ownership guide
DNSThe records that send web traffic, email and verification checks to the right placesThe registrar, the old host or a separate DNS provider
HostingThe server that stores and serves your site's files and databaseYour hosting provider

A hosting move normally changes only the hosting and a few DNS records. ICANN's domain transfer FAQ points out that you may be able to change hosting providers, or update nameservers or the hosting address, instead of transferring the domain between registrars, which avoids the transfer process and its 60-day restrictions.

Step 1: list everything the old host does

Many small businesses find out what their host was doing only after it stops. Write down:

  • Every DNS record, not just the one for the website. Export or screenshot the full list: A and CNAME records, MX records for email, and TXT records used for email authentication and for verifying tools like Search Console. Cloudflare's explainer on MX records shows how these route your mail.
  • Email. Is your business email hosted by the same company as the website? If so, moving the site and cancelling the old plan can also end your mailboxes.
  • Forms and notifications. Where does each form send its submissions, and does it rely on the old server's mail settings? Our guide to contact forms that stop sending lists the usual failure points.
  • Everything else on the account: other domains, subdomains, scheduled tasks, SSL certificates and any connections to your CRM or booking tools.
  • A full backup of files and database that you have downloaded yourself, not one that lives only on the old host.

Step 2: copy the site and test it before anyone sees it

Google's guide to changing your hosting describes the order: prepare and test the new hosting first, then switch DNS, then watch traffic, then shut down the old host.

What a copy means depends on the platform. A simple site may be a folder of files; a content management system usually also needs its database exported and imported. On the new host, check:

  • Every page, image and download opens, including old pages you rarely visit.
  • Each form submits and the notification arrives where it should.
  • Phone links, booking links and any embedded tools still work.
  • Search Console verification still works: if you verified with an HTML file or a tag in your template, it must be in the new copy too.
  • Any temporary "noindex" or robots.txt blocks used on a test address are noted, so they can be removed at launch.

If you test on a temporary address, Google suggests adding a noindex rule there so the test copy isn't indexed by accident.

Step 3: lower the TTL a few days ahead

DNS answers are cached for as long as each record's TTL says. Cloudflare's TTL explainer describes it as how long a DNS cache can serve a record before checking for a new copy. Google suggests lowering the TTL to a conservative value, such as a few hours, at least a week before the move, so the switch spreads faster when you make it.

Step 4: switch the records, not the whole DNS, if you can

There are two ways to point traffic at the new host:

MethodWhat changesThe risk
Update the website records (usually A or CNAME)Only web traffic movesLow, as long as you edit the right records
Change nameservers to the new hostA different company now answers for *all* your DNS recordsEmail and verification break unless every record was recreated there first

If you do change nameservers, compare the new DNS zone with the list from Step 1, record by record, before you switch. Then remove any temporary crawl blocks and make the change.

SSL certificates. Many hosts issue a free certificate automatically. With Let's Encrypt's common HTTP-01 check, the certificate authority fetches a file from your domain, so it can only succeed once the domain points at the new server. Ask your new host how they handle this, so visitors don't see a security warning in the first hours.

Step 5: watch both hosts, then retire the old one

  • Check your site from different networks and with a public DNS lookup tool, such as Google's Admin Toolbox Dig, until they all show the new address.
  • Send a test email to and from your business address, and submit each form again.
  • Keep an eye on Search Console. Google says a temporary dip in crawling right after a hosting change is normal.
  • Don't edit content on the old host during the switch; changes made there may be lost.

Google's advice is to shut down the old hosting only when traffic to it has stopped. In practice, keep the old plan and your downloaded backup for a while after the move, and cancel only once you've confirmed email, forms and every page work from the new host.

When to get help

A static or simple site can be moved by a careful owner following this list. Get help if your site runs on a database-driven platform you didn't set up, if email lives with the old host, or if nobody knows who controls the DNS. Our hosting, SSL and backups questions help you compare hosts, and if you're also changing page addresses, read redesigning without losing search traffic first.

What this guide can't do

Every host and DNS provider labels settings differently, and some include migration tools or limits of their own. Check your providers' current documentation before you change records, and keep a copy of the old settings so you can switch back.

Questions

Will moving hosts hurt my Google rankings?

If your page addresses stay the same and the new site serves the same content reliably, Google's guidance treats this as a hosting change rather than a site move with URL changes. It notes that crawling may dip briefly after the switch and then recover. If you're also changing addresses, plan redirects as a separate job.

Do I have to move my domain name too?

No. Your domain registration, your DNS and your hosting can all be with different companies. Most hosting moves only need the DNS records pointed at the new server. Transferring the domain to a new registrar is a separate process with its own rules and locks.

How long will my site be down during the move?

With the new copy tested before you switch DNS, there's usually no planned downtime: some visitors reach the old host and some the new one until DNS caches update. Keep the old site running and unchanged during that window.

Sources and further reading

Official documentation changes. Check the current version before you rely on a rule, limit or setting.

Next step

See a site built around your real details.

Look at sample layouts (fictional previews, not client work), read published website pricing, or ask for a free concept preview.

Already happy with your site? Website Maintenance covers monitoring, a monthly form test, backups and edits.