Moving Your Website to a New Host? Protect More Than the Website.

1. First, understand what is actually moving

Before changing anything, identify where each part of your digital setup currently lives.

Four services are commonly confused:

• Website hosting stores the files, databases and other resources that run your website.
• Domain registration controls ownership and renewal of your domain name.
• DNS tells internet services where your website, email and other services should be directed.
• Business email handles addresses such as name@yourcompany.com.

These services can all come from the same provider—but they don’t have to.

For example, your website might be hosted with one company, your domain registered elsewhere, your DNS managed by another service, and your business email hosted separately.

That is why changing hosting does not necessarily mean transferring your domain or changing your email provider.

Before starting a migration, understand these relationships.

2. Record the existing setup before touching DNS

One of the safest things you can do before a migration is document the current environment.

Record or export:

• Website files
• Website database
• Domain registrar
• Current nameservers
• DNS records
• Existing mailboxes
• MX records
• SPF, DKIM and DMARC records
• SSL configuration
• Important website URLs
• Redirects
• Contact forms
• Google Analytics or Google Tag Manager
• Google Search Console
• Any third-party services connected through DNS

This gives you a reference if something behaves differently after the migration.

Pay particular attention to the existing DNS zone.

DNS may control considerably more than where the website loads. It can also control email delivery, email authentication, subdomains and third-party services.

Replacing an entire DNS configuration without understanding those dependencies can create problems that have nothing to do with the website itself.

3. Take a complete backup

Before moving anything, create a current backup of the website.

Depending on the website, that can include:

• Website files
• Databases
• Uploaded media
• Configuration files
• Redirect rules
• Email data, where email is part of the hosting environment

For a dynamic website, an old backup may not contain recent enquiries, orders, user accounts or content changes.

There is another important distinction:

Having a backup is not the same as knowing the backup can be restored.

Where practical, verify that the backup is complete and that the required files and database can actually be used to restore the website.

And don’t remove the existing website simply because a backup has been created.

The original environment is still valuable during the transition.

4. Prepare the new hosting before changing DNS

A common mistake is changing the domain first and then starting to build or restore the website on the new server.

A safer sequence is:

Set up → Restore → Test → Switch

Configure the new hosting environment first.

Restore the website and database, then test as much as possible before directing public traffic to it.

Check important areas such as:

• Homepage
• Main service/product pages
• Navigation
• Images and downloadable files
• Database-driven content
• Contact forms
• HTTPS/SSL
• Redirects
• Mobile layout
• Important integrations

The objective is simple:

The new environment should be ready before visitors are sent to it.

If problems are found at this stage, they can usually be addressed without affecting the live website.

5. Protect your business email

This is one of the most easily overlooked parts of a hosting migration.

If your company uses addresses such as sales@yourcompany.com or info@yourcompany.com, first establish where those mailboxes are actually hosted.

If email is hosted with the existing web-hosting provider, the mailboxes themselves may need to be migrated.

If email is hosted separately—for example through another business email service—the mailboxes may not need to move at all.

But their DNS records still need to be preserved.

Important records can include:

• MX records — tell other mail systems where incoming email should be delivered.
• SPF — helps identify which systems are authorised to send email for your domain.
• DKIM — provides a cryptographic signature that helps receiving systems verify messages.
• DMARC — provides instructions for handling messages that fail authentication checks and can provide reporting.

You don’t need to become a DNS specialist to move your website.

But you do need to avoid deleting or replacing records you don’t understand.

A website can load perfectly from the new host while company email has quietly stopped arriving.

If you’re also planning to change your email provider, treat that as its own migration process and plan how existing messages and new incoming mail will be handled during the transition.

NEST8’s Business Email service is designed around this broader setup, including migration and the DNS configuration surrounding professional domain email.

6. Protect your existing search visibility

Changing hosting does not automatically mean changing your website’s URLs or content.

If this is purely a hosting migration, unnecessary website changes can make troubleshooting harder.

Where possible, preserve:

• Existing URLs
• Page titles and descriptions
• Page content
• Heading structure
• Canonical tags
• Structured data
• Internal links
• Redirects
• robots directives
• XML sitemap

Before migration, it is useful to have a record of the website’s important URLs and current Search Console data.

After the move, check that important pages still return the expected status and haven’t accidentally acquired noindex directives, incorrect canonical URLs or broken redirects.

If the project also involves a redesign, domain change or major URL restructuring, the SEO requirements become more extensive. Old URLs may need to be mapped to their most relevant replacements using permanent redirects.

That is no longer simply a hosting migration—it is also a website and SEO migration.

Our SEO services consider these technical foundations alongside content and search visibility.

7. Make the DNS cutover carefully

Once the new environment has been tested, the domain needs to direct visitors to it.

How that should happen depends on the existing setup.

In some cases, the nameservers change.

In others, only specific DNS records need to change.

There is no universal instruction that is correct for every website.

Before changing DNS, know:

• Where DNS is currently managed
• Which record directs the website
• Which records control email
• Which records belong to third-party services
• What exactly needs to change
• What needs to remain untouched

This is particularly important when moving from one hosting provider to another.

Blindly recreating only the website record and forgetting the rest of the DNS zone can disrupt services that were working perfectly before the migration.

Change what needs to change—not everything simply because it exists.

8. Don’t cancel the old hosting immediately

Seeing the website load from its new host does not mean the migration should immediately be considered finished.

Keep the old hosting account available until the important services have been verified.

That gives you a fallback while checking:

• Website functionality
• Database content
• Forms
• Email
• DNS
• SSL
• Redirects
• Analytics
• Search behaviour

It can also be useful during DNS propagation, when different users or systems may temporarily resolve the domain differently.

Only close the previous hosting account after you’re confident the new environment contains everything required and the services depending on the old environment are no longer needed.

9. Check the first 24–72 hours carefully

Migration doesn’t end when DNS changes.

The period immediately after cutover is when you should pay closest attention.

Check the website from different devices and connections.

Verify:

• Website loads correctly
• HTTPS works without certificate warnings
• Important pages are accessible
• Images and files load
• Contact forms submit correctly
• Enquiry emails arrive
• Business email can send and receive
• Redirects behave correctly
• No unexpected 404 errors appear
• Analytics continues recording visits
• Google Search Console can access the website
• Important conversion paths still work

If the website generates enquiries, test the complete journey, not just the page.

Google/Direct visit → Service page → Contact page → Form submission → Enquiry received

A website migration is successful when the business processes surrounding the website continue working—not merely when the homepage opens.

Website Hosting Migration Checklist

Use this as a practical starting point before changing hosting providers.