1. Choosing a plan without checking requirements

Check that the new plan supports what your site needs: the PHP version and extensions, database version, disk space, email accounts, SSH or cron access, and any special software. A site that needs Node.js, Redis or a specific PHP extension may need a VPS rather than shared hosting. Ask support before you order if you are unsure.

2. Moving without a complete backup

Before you start, take a full backup of files, databases and email from the old host, and store a copy on your own computer or cloud storage. If something goes wrong in the move, or the old account is closed early, that copy is all you have. On cPanel, a full account backup includes everything. See our cPanel backup and restore guide.

3. Forgetting the database

Copying files is not enough for WordPress, Joomla, shops and most modern sites: the content lives in the database. Export it, import it on the new server, and update the database name, user and password in the site’s configuration file.

4. Changing DNS before testing

If you point the domain to the new server before checking it, visitors see whatever is broken. Test first by pointing only your own computer at the new server with the hosts file. Our hosts file guide shows how.

5. Not lowering the TTL in advance

DNS records have a TTL that tells resolvers how long to cache them. A day before the move, lower the TTL of your A and MX records, for example to 300 seconds. The switch then reaches most visitors within minutes instead of hours.

6. Forgetting email

If your email is hosted with your website, it moves too. Create the same mailboxes on the new server, copy old mail over IMAP, and update the MX, SPF and DKIM records. During the DNS change, some mail may still arrive at the old server, so check both for a few days. If your email is hosted elsewhere, such as Google Workspace, make sure the MX records are copied exactly.

7. Leaving out SSL

Without a certificate on the new server, visitors see a security warning. On cPanel, AutoSSL issues a free certificate once DNS points to the server. Check it in SSL/TLS Status straight after the switch, and make sure the site still redirects to HTTPS.

8. Breaking URLs and SEO

Keep the same domain, URLs and site structure. If URLs must change, add 301 redirects from every old URL to its new one. After the move, check Google Search Console for crawl errors and submit the sitemap again.

9. Cancelling the old hosting too early

Keep the old account running for at least a week after the DNS change. It catches late email, lets you copy anything you forgot, and gives you a fallback if something unexpected breaks.

10. Not checking the site after the move

Once the switch is complete, test the important things: forms, logins, checkout, search, cron jobs, and emails sent by the site. Compare page speed with the old host. Our site speed guide lists useful tools.

Migration checklist

• ✓ Check the new plan meets the site’s requirements.
• ✓ Take a full backup and store a copy off both servers.
• ✓ Lower the DNS TTL a day before the move.
• ✓ Copy files, databases and email to the new server.
• ✓ Update configuration files with new database details.
• ✓ Test the site with the hosts file.
• ✓ Change DNS (A and MX records, or nameservers).
• ✓ Check SSL, forms, email and cron jobs.
• ✓ Watch both servers for a few days, then cancel the old hosting.

Getting help with the move

Our support team can help plan a move to UnderHost and copy cPanel accounts between servers. Open a ticket with the details of your current hosting. For the full process, see our guide to moving a website without downtime.