moving website hosting? protect your site, email and domain first.
Changing hosting should not mean losing customer enquiries, old emails or control of your domain. The safest migrations are the ones that account for every connected service before anyone changes DNS.
Know what you are actually moving
When a business says it is "moving its website", it could mean three separate changes. The website files may move to a new server. The email accounts may stay where they are, or move to a new provider. The domain registration may remain with the current registrar even when the website and email change.
Those services share the same address but not the same job. A rushed migration treats them as one switch. A controlled migration lists the services independently and decides what must move, what must stay and who has the authority to approve each change.
Take a real backup before you touch DNS
For a simple website, make a complete copy of the files and databases. For a content-managed website, capture the database, uploads, themes, plugins and configuration. Keep a separate copy somewhere you control. A backup is only useful if you know how to restore it.
Email deserves equal care. Identify the current provider, list every mailbox and alias, confirm who has access, and export important historical mail if mailboxes are moving. Do not assume that copying website files also copies the inbox. They are not the same data.
Map the records that keep everything working
DNS is the address book that tells the internet where to find your website and how to route your email. The main website record may change during a hosting move. Your email's MX records might not. Email authentication records such as SPF, DKIM and DMARC also matter and must be reviewed carefully if the sending service changes.
Make a record of the current settings before editing anything. Note which records are managed by the registrar, hosting company and email provider. In a business with shared hosting and third-party email, changing the wrong record can interrupt mail without making the website migration any more successful.
Test the replacement site before switching
Build the new environment and check it thoroughly: home, services, forms, images, downloads, mobile layout and HTTPS. Test contact forms with a real destination address. Check that page titles, canonical URLs and internal links point to the live domain, not a temporary preview address.
If the website structure is staying the same, preserve those public URLs. If URLs are changing, prepare direct permanent redirects before launch. Google has separate guidance for changing hosting without changing URLs and for site moves that change URLs. These are not interchangeable projects.
Make the switch and watch what happens
When the new environment is ready, update only the DNS records that need changing. Keep the old hosting active during the transition while caches refresh and traffic reaches the new server. Monitor the website, form submissions and email delivery from more than one connection.
Check the next business morning too. A migration that "looked fine" for ten minutes may still have an undetected enquiry form error or an employee whose mailbox has not synchronised. Do not cancel the old account until the site and relevant mail services have been tested and important content is accounted for.
What to ask a new hosting supplier
Ask who owns the domain; what exactly is included in the migration; whether historical email will move; who configures DNS and SSL; whether there is a rollback plan; and how long the old environment should remain available. Get answers in writing.
A good migration is almost boring. Customers keep reaching the right pages, staff keep receiving mail and the business keeps control of its domain. That outcome matters more than how quickly someone can change a nameserver.
what informed this piece.
Further reading behind this article.
keep reading.
More practical thinking from wonkla.