Knowing what to check before moving a website to a new host can help prevent a technical change from disrupting customer inquiries, sales, or everyday operations. The key is to plan the move around everything your website depends on, not just the pages visitors see.
Start by identifying exactly what is changing. A hosting change does not automatically require a domain transfer, a new email provider, or different website addresses. Keeping those pieces separate can make the work easier to plan and test.
Clarify what is changing
Write down which accounts and systems are involved before scheduling the move:
- Website hosting: Where the website files and database will live.
- DNS: The service and settings that direct visitors and email to the right places.
- Domain registration: The account that manages ownership and renewal of the domain name.
- Email: The provider and settings used for business mail.
- Website addresses: Whether the site will keep the same domain, page URLs, and secure connection.
If you are only changing the web host and keeping the same domain and page addresses, this is different from changing your URLs. Google’s site move guidance covers the extra planning involved when URLs change, including redirect considerations. Make that distinction early so the work matches the move you are actually making.
A domain transfer is also separate from moving website hosting. You can generally keep your domain with its current registrar while changing where the website is hosted. If you are considering transferring the registration as well, review the ICANN registrant FAQs and keep that change distinct from the hosting move.
Record DNS and email settings
Before changing DNS, make a copy of the current records and note which services rely on them. Website records may point a domain or subdomain to the current host. Email records may direct incoming mail or help other services verify that outgoing messages are legitimate.
Check the records used by your setup, which may include A or AAAA records, CNAME records, MX records, and TXT records. Do not assume every record should point to the new website host. In particular, if your email is staying with its current provider, preserve the mail-related settings and confirm the new DNS configuration with that provider.
It also matters who controls DNS. The registrar, DNS provider, web host, and email provider may be different companies. Confirm you can access the account that will make the DNS change and know who is responsible for updating it. If you are changing DNS providers as part of the move, follow the new provider’s setup instructions, such as Cloudflare’s full DNS setup guidance, and verify the records before switching.
Back up the whole site and know how to restore it
A usable migration backup should cover the website files and its database, not just a copy of the homepage. Depending on the site, it may also be important to preserve configuration files, uploaded media, scheduled tasks, and other settings needed for the site to work.
Check that the backup is recent, stored somewhere separate from the site being moved, and accessible to the person doing the migration. Ask how restoration works before you need it. A backup is most useful when you know what it includes and how to recover the site or a specific item from it.
If customers can submit forms, place orders, or make other changes while the move is underway, agree on how new information will be handled. The plan might include a short period when changes are paused or a final data sync before the switch. The right approach depends on how the site works.
For more on planning and checking backups, see how to think about website backup retention.
Test the new host before changing DNS
Do not treat a homepage loading as proof that the migration is ready. Test the site on the new host before sending normal visitor traffic there. A staging setup can help you review changes away from the live site; see how a staging environment can help with website changes.
Use a checklist based on what your customers actually do. Test the important paths from start to finish:
- Open key pages and check that images, downloads, and other resources appear or work as expected.
- Submit contact, quote, or booking forms and confirm that the messages reach the right inbox.
- If the site accepts payments or orders, test the relevant customer journey using the site’s appropriate test process.
- Check account access, search, menus, and any other features visitors rely on.
- Confirm that the secure version of the site loads correctly and that there are no obvious broken links or browser warnings.
Check the site on a phone as well as a computer, and review any connected tools that matter to the business, such as analytics or appointment systems. A migration can expose configuration details that were specific to the old host, so make sure the features are actually working on the new environment.
Plan the switch and keep a rollback route
Before making DNS changes, write down the current settings so they can be restored if the move needs to be reversed. Agree on who will make the change, how the team will know the new site is working, and who will respond if an important feature fails.
Keep the old hosting account available while you verify the new site, email, and customer-facing functions. Avoid canceling it just because the new homepage opens. If you need to return traffic to the old host, you will need the old site and its relevant settings to remain usable. Ask your current host about its account and data-retention terms rather than assuming how long access will continue.
Security deserves attention throughout the move. Use trusted access to hosting and DNS accounts, share credentials only with the people who need them, and confirm that security settings and software updates are in place on the new host. For WordPress or Joomla!, check that the core software, extensions, themes, and plugins are accounted for as part of the move.
Check the live site after the move
Once DNS points visitors to the new host, repeat the essential tests on the public site. Confirm that pages load over a secure connection, forms and customer workflows still work, and business email can send and receive. Check for missing images, broken links, unexpected errors, or redirects to the wrong address.
If the site’s URLs changed, review the redirect plan and monitor the site’s search visibility. If the URLs stayed the same, the move is primarily a hosting change, but it is still worth checking that important pages can be reached and that tracking tools are working.
Frequently asked questions
Do I need to transfer my domain to change web hosts?
No. Domain registration and website hosting are separate. You can usually keep the domain with its current registrar and update the DNS settings that direct visitors to the new host.
How can I test the website before changing DNS?
Ask the new host what preview or staging method is available. Review key pages and customer functions on the new environment before directing normal visitors there.
Will changing web hosts affect my business email?
It can if the DNS records used for email are changed or lost. Record the existing mail settings, confirm where email is hosted, and verify the relevant records before and after the DNS switch.
When can I cancel the old hosting account?
Wait until the new site and its important functions are verified, and you are confident you no longer need the old environment for rollback or data recovery. Confirm the old host’s account and data-retention terms before canceling.
Make the move a planned handoff
A careful migration starts with clear boundaries, a restorable backup, preserved DNS and email settings, and real testing of the tasks customers use. If you are preparing a move, Zevonix Cloud provides website migration that includes file and database transfer, DNS, SSL, and post-migration checks. Get in touch to discuss what your site needs before the switch.