Short answer: A website migration to a new host works best in five steps: take a full backup, lower your DNS TTL a day early, copy the site to the new server, test the copy before anything public changes, then switch DNS at a quiet hour. Keep the old hosting active until the new site and email are confirmed working.
Most people put off a website migration to a new host for the same reason: they’re worried the site will break, email will vanish, or Google will forget them overnight. Those things do happen, but almost always because a step was skipped or done in the wrong order, not because moving hosts is inherently risky. This guide lays out that order, explains what each step protects you from, and points to the detailed how-tos for the parts that need them. If your domain is still registered somewhere else, that’s fine; you don’t have to move it at the same time, and our guide to registering, transferring and managing a domain explains why the two are separate.
What actually moves when you change hosts
A website is several separate pieces that happen to live together on your current host. Listing them before you start is the single most useful thing you can do, because anything left off the list is what goes missing.
- Files. Your site’s code, themes, plugins, uploaded images and documents, usually everything under
public_htmlor a similar folder. - Databases. WordPress, Laravel, online stores and most CMS platforms keep content, orders and users in MySQL or MariaDB, not in the files.
- Email. Mailboxes, forwarders and autoresponders, if your current host also runs your email.
- DNS records. The A, MX, CNAME and TXT records that tell the internet where your site and mail live, plus any SPF or DKIM records for email delivery.
- Server settings. Cron jobs, PHP version and extensions, redirects in
.htaccess, SSL certificates and any custom configuration your developer set up years ago.
Your domain registration is a different thing again. It sits with a registrar and simply points somewhere. You can change where it points without moving the registration.
Step 1: Back up everything before you touch anything
Before any copying starts, make a complete backup you control: a full account backup from your control panel if it offers one, or a download of the files plus a database export. Store it off the old server, on your computer or in cloud storage. This is your undo button. If the copy goes wrong, or the old host closes your account sooner than expected, you can still rebuild.
Check the backup actually opens. A zip that won’t extract or a database dump that stops halfway is worse than no backup, because it gives you false confidence.
Step 2: Lower your DNS TTL a day ahead
TTL (time to live) is how long other networks cache your DNS records before checking for changes. Many records sit at several hours. If you switch DNS while the TTL is long, some visitors keep landing on the old server for that long.
About 24 hours before the switch, edit your A record (and MX record, if email is moving) at your current DNS provider and drop the TTL to something short, such as 300 seconds. You need to wait out the old TTL for the change to take effect, which is why this happens a day early. After the move settles, you can raise it again.
Step 3: Copy the site to the new host
How you copy depends on what you have on both ends:
- cPanel to cPanel. A full cPanel backup can usually be restored on the new server, and hosts running WHM can pull accounts across with cPanel’s Transfer Tool. This keeps files, databases, email and settings together. We also have an older walkthrough on migrating your website from another host using cPanel.
- WordPress. Copy the files and the database, then make sure
wp-config.phphas the new database name, user and password. A migration plugin can bundle this up, but it’s still files plus a database underneath. - Custom apps. Laravel and similar frameworks need their environment file, storage links, scheduled tasks and queue workers recreated, not just the code copied.
Once the copy is made, freeze changes on the old site. New blog posts, orders or form entries that land on the old server after the copy won’t be on the new one unless someone syncs them. If you run a store, pick a slow period or plan a short content freeze.
Step 4: Test the new copy before switching DNS
This is the step people skip, and it’s the one that prevents most bad surprises. You can view the site on the new server while the public still sees the old one. The common way is the hosts file method: add a line to your computer’s hosts file that maps your domain to the new server’s IP address, so only your machine goes to the new copy. Some hosts also give you a temporary preview address.
Walk through the site the way a visitor would:
- Open the home page, a few inner pages and a blog post.
- Log in to the admin area and save something small.
- Submit a contact form and check the message arrives.
- Run a test checkout if you sell online.
- Look for missing images, broken links and mixed-content warnings.
Remove the hosts file line when you’re done, or you’ll keep seeing the new server and think DNS has already switched.
Step 5: Switch DNS at a quiet time
When the copy checks out, point the domain at the new host. You can either change the nameservers at your registrar to the new host’s nameservers, or keep your current DNS provider and just update the A record to the new IP. Our walkthrough on how to point a domain to your hosting covers both options.
Do it when your visitors are least active. Because you lowered the TTL, most traffic follows within minutes, but some networks hold on to old records longer. That’s why the old hosting stays switched on until everything is confirmed.
Step 6: Check email, SSL and search after the move
The first hour after the switch is for confirming the less visible parts:
- Email. Send and receive from each mailbox. If mail moved, update the incoming and outgoing server settings on phones and desktop mail apps, and make sure MX, SPF and DKIM records point to the right place.
- SSL. Confirm HTTPS loads without warnings on every version of the domain, with and without
www. - Search. A host change with the same URLs is not a big event for Google. Its documentation on moving a site without changing URLs says to keep the old hosting running for a while and watch crawl activity in Search Console. If your URLs aren’t changing, don’t add redirects you don’t need.
Only cancel the old hosting after a few days of normal traffic and email on the new server, and after you’ve saved one last backup from it.
How to keep website migration downtime low
No honest guide can promise nothing will ever blip, but you can make disruption small and short:
- Never cancel the old hosting before the new site is confirmed.
- Lower TTL in advance, not on the day.
- Freeze content changes between the copy and the switch, or sync them before you switch.
- Test on the new server with the hosts file before going public.
- Move email and website together only if you’re ready to update every device that sends mail.
Moving to a bigger plan at the same time
A migration is a natural moment to rethink the plan size. If your site has been hitting resource limits on shared hosting, read our comparison of VPS vs dedicated server vs cloud before choosing where to land, so you only move once.
Free website migration at ResellerBytes
If you’re moving to ResellerBytes, free website migration is included on every SSD hosting plan. The process follows the same order as this guide. You order a plan, open a migration ticket and share access to your current host inside the ticket only. The team copies the site while your current one stays live, you preview the copy on the new server, and then you switch DNS when you’re happy. If you want mailboxes moved too, mention them in the ticket and the team will confirm what can be moved for your setup before starting.
To help the move go smoothly, have these ready: the domain names being moved, a hosting login or full backup from your current host, access to your DNS or registrar, and a note about anything unusual like cron jobs, specific software versions or custom email routing.
Frequently asked questions
How long does a website migration take?
It depends on the size of the site, the number of mailboxes and how quickly access to the old host is available. A small site can be copied in an hour or two; DNS changes then take minutes to several hours to reach everyone, depending on TTL.
Will my website go down during the move?
Not if you follow the order above. The old site keeps serving visitors while the copy is made and tested. The only switch-over is the DNS change, and keeping the old hosting active covers anyone whose network still has the old record cached.
Do I need to transfer my domain when I change hosts?
No. Hosting and domain registration are separate. You can leave the domain with its current registrar and just point it at the new host. Transferring the registration is optional and can be done later.
Will changing hosts hurt my SEO?
Usually not, when the URLs stay the same and the site works on the new server. Problems come from broken pages, missing redirects after URL changes, or long outages. Test before switching and keep an eye on Search Console for a couple of weeks.
Can I move email along with my website?
Yes, but plan it. Mailboxes need to exist on the new host before MX records change, and every device that sends mail needs updated settings. Some people move the website first and email a little later to keep each step simple.
What should I do with my old hosting account?
Keep it running until the new site, email and SSL are confirmed working for a few days. Take one final backup, then cancel it.
By ResellerBytes Team. External sources last checked 22 October 2026.
Share this content:
