Moving a website to a new host is manageable when you separate the site move from email and domain changes. The safest sequence is: inventory, back up, build and test on the new host, copy the current DNS settings, then switch only the records that need to change. Keep the old host available until the new site, forms and email have been checked.
Before you move: make a site and DNS inventory
List the domain registrar, current host, nameservers, email provider, DNS records, SSL setup, forms, booking tools, analytics and any connected services. Export or screenshot the DNS zone, including A/AAAA, CNAME, MX, TXT and verification records. Note which provider manages each service. This prevents a common mistake: replacing nameservers without recreating the records that deliver business email or prove service ownership.
Choose a low-traffic change window, tell the people who handle enquiries, and confirm you can access both hosting accounts and the registrar. Record your key URLs and take a full backup of website files and database. Save the backup somewhere outside the old hosting account and check that its archive is readable.
Build and test on the new host first
- Install or migrate the website on the new host using its staging URL or a protected preview.
- Check the platform and runtime requirements, configuration values, file permissions and database connection.
- Preview the homepage, service pages, contact details, images, mobile layouts and any password-protected areas.
- Submit every contact or quote form. Confirm the email arrives at the intended address and that connected CRM, WhatsApp or booking actions work.
- Install or prepare HTTPS on the new host. Check for mixed-content warnings and confirm canonical URLs still use the preferred HTTPS domain.
- Compare the old and new URL list. If URLs change, prepare one-to-one permanent redirects for pages with a clear replacement.
Switch the website without interrupting email
If the email provider stays the same, leave its MX records and associated TXT records unchanged. When changing only the website host, update the website’s A/AAAA records or the specific web CNAME as instructed by the new host. Avoid changing nameservers unless necessary. If nameservers must change, first reproduce the full DNS zone at the new DNS provider and verify mail, verification and other service records there.
DNS changes may take time to appear everywhere. During the transition, some visitors may reach the old host and others the new one. Keep the old site available and avoid editing content on only one copy. Follow the host’s instructions for DNS and SSL; providers configure these differently.
After the DNS change
Test the live domain on desktop and mobile. Check key pages, forms, telephone links, email delivery, HTTPS, analytics and Search Console verification. Review server logs and Search Console for crawl or indexing errors. Submit the current sitemap if its URL or contents changed. Google recommends managing URL changes with mapped redirects and monitoring the move; the process does not guarantee that every page will retain its previous position immediately. See Google’s site-move guidance.
Keep the old hosting account until you have confirmed the new website is stable and you have a separate verified backup. Then cancel it according to the old provider’s terms. Keep the domain registration active and separate from hosting so future host changes remain under your control.
Common migration mistakes
- Changing nameservers before copying email and verification records.
- Testing only the homepage while quote forms or booking flows are broken.
- Forgetting to renew or transfer paid plugin and theme licences.
- Launching a staging site that blocks Google after the production move.
- Deleting the old host before checking backups, redirects and form delivery.
If you are planning a rebuild too, review our small business launch checklist and compare the ongoing costs in the website running-cost guide. For a review of your current website, visit the Bennie Studio app.
Hosting interfaces and DNS behavior vary by provider. Follow your registrar, host and email provider’s current instructions before changing production records.