Moving a website to a new host sounds simple until you think about what can go wrong: broken pages, lost emails, slipping rankings. Done in the right order, with testing before you switch anything public, it need not cost you traffic.

I have managed websites through hosting changes as an IT and Digital Operations Manager at TechLand Bangladesh, and earlier as an SEO Expert and Project Manager at Again Software and Solutions. I also run my own store, synex.bd.

Why Move to a New Host?

People change hosts for sensible reasons: a slow plan, unhelpful support, rising renewal prices, or a site that has outgrown shared hosting. Treat the move as a project: the goal is no broken pages, no lost emails, and no dip in search visibility.

Before You Move: The Pre-Migration Checklist

Most migration problems come from skipping preparation.

Take a Full Backup

First, back up your website files and database, and keep a copy on your own computer. Never rely only on a backup stored on the old host — the server you are leaving. With a content management system, back up both parts: the database holds your posts, pages, settings and accounts. My guide on how to back up your website covers this in more detail.

Note Down Your DNS and Email Settings

Record your DNS records before changing anything: A, CNAME, MX and TXT records. Take screenshots or export the zone file. If your email is hosted with your current provider, check whether it moves with the site. Losing email is a common, avoidable mistake.

Lower the TTL on Your DNS Records

TTL, or time to live, tells other servers how long to remember your DNS records. A day or two before the move, lower the TTL on your main records to a short value, such as 300 seconds, so the change spreads faster. Raise it again afterwards.

Check What the New Host Needs

Confirm the new host supports your site: the right PHP version, the database type your site uses, and enough storage and bandwidth. Ask whether they offer a free migration service. Even if they do, keep your own backup and stay involved in testing.

Moving Your Files and Database

There are two parts to the move: the files and the database. Transfer your website files to the new host by downloading them from the old host and uploading them to the new one, or by using a migration plugin or the file manager in your new control panel. Check the transfer completed fully, including hidden files.

Next, move the database: export it from the old host, create a new empty database on the new host, and import it there. Then update your site's configuration file with the new database name, username, password and host. One wrong character here is a common cause of the database connection error, so double-check every value.

Test Everything Before You Switch the DNS

This step protects your traffic: never point your domain at the new host until you have tested the site there. Most hosts give you a temporary URL or let you preview the site by editing your computer's hosts file. Click through the preview as a visitor would: key pages, forms, search, and checkout or login. Check images, menus and the SSL certificate.

Also check page load speed, broken links and redirects from old URLs. Fix problems now, while the old site is still live and you have a working site to fall back on.

Updating Your DNS Records

Once the new copy passes testing, update your domain's DNS records to point at the new host, usually by changing the A record to the new server's IP address. If your domain's nameservers point at your hosting provider, you may need to change the nameservers instead, so check your setup first.

DNS changes take time to spread, a process called propagation. For a while, some visitors reach the old server and some the new one. That is normal. Avoid content changes during this window, since an edit on one server may not appear on the other. See my explainer on what DNS is and why a website goes down.

Post-Move Checks

The site is live, but the job is not finished. Check these:

• SSL certificate: confirm every page loads over HTTPS with no mixed-content warnings.
• Forms and email: submit your contact form and check the messages arrive.
• Speed: test load times on key pages.
• Search Console: watch for crawl errors or a drop in indexed pages.
• Analytics: confirm tracking still records visits, so you can spot any traffic change.
• Broken links: click through important pages to catch anything left behind.
• Redirects: test that old URLs redirect correctly.

Keep the old account active for a week or two. Cancelling too early removes your safety net before the new setup proves stable.

Have a Rollback Plan Ready

Even a well-planned migration can hit a surprise, so decide in advance what to do if something goes wrong. The simplest rollback is to point your DNS records back to the old host, where the original site is still intact. Delete nothing there until the new site runs smoothly.

Set a clear point for rolling back rather than keep patching. If the new site shows errors you cannot fix quickly, or forms and checkout are broken, revert the DNS and investigate calmly. A rollback is not a failure; it is a safety step.

Frequently Asked Questions

Will changing hosts hurt my SEO?

Not by itself. Problems come from downtime, broken pages, missing redirects, or a much slower site. If URLs and content stay the same and the new host is fast, search engines should treat the move as routine.

How long does a website migration take?

A small site can be moved in a few hours; a large store can take a day or more, plus DNS propagation time. Plan the move for a quiet period and give yourself a comfortable margin.

Will my website go down during the migration?

It should not. Your old site stays live while you build and test the copy on the new host. Short downtime is possible if something goes wrong, which is why testing first and a rollback plan matter.

Do I need to tell Google about the move?

For a hosting-only move, where the domain and URLs stay the same, there is no change-of-address step in Search Console. Just monitor the coverage and performance reports for a week or two and fix any crawl errors.

Conclusion

Migrating to a new host does not have to cost you traffic. Back up everything, note your DNS and email settings, lower the TTL, move files and database carefully, and test before you switch the DNS. Then check SSL, forms, speed and Search Console, and keep the old host running until the new one proves stable. Visitors, and Google, should barely notice anything changed.