How to Migrate Your Website to a New Host (Step-by-Step Guide)

Disclosure: This post contains affiliate links. If you make a purchase through these links, I may earn a small commission at no extra cost to you.

Photo by Jessica Lewis — Pexels

Switching web hosts sounds terrifying. I get it. The thought of your site going offline, losing files, or tanking your Google rankings keeps a lot of people stuck on bad hosting way longer than they should be.

But here's the truth: I've migrated sites seven times over the past three years. The longest downtime? About 12 minutes. And my SEO rankings? They actually improved after most moves because the new hosting was faster.

This guide walks you through the entire process — from backup to DNS propagation. No fluff. Just the steps I follow every single time.

Before You Start: Why Are You Migrating?

Quick gut check. Make sure you're moving for the right reasons:

• Slow page speeds — your site takes 3+ seconds to load
• Frequent downtime — you're seeing 503 errors more than once a month
• Bad support — tickets take days to get a response
• Price hikes — your renewal rate tripled from the intro price
• Outgrowing your plan — you need more resources than shared hosting offers

If any of these sound familiar, moving is the right call. Hosting directly affects your site's speed and how it performs in search results. Don't stay on a sinking ship.

Step 1: Pick Your New Hosting Provider

Do your homework before signing up anywhere. Here's what I look for:

• Server locations — close to your target audience
• Uptime guarantee — 99.9% minimum (read our guide on what uptime guarantees actually mean)
• Free migration — many hosts offer this, and it saves a ton of hassle
• SSD storage — faster than traditional HDD by a huge margin
• Support quality — check reviews from real users, not just the marketing page

Two providers I've had consistently good experiences with:

Hosting.com offers free migration on all plans. Their support team handled my last transfer in under an hour — I literally didn't have to touch anything. If you're running WordPress, their Managed WordPress hosting is worth a look.

InterServer has been around since 1999 and they're one of the few providers with a price-lock guarantee — your renewal rate stays the same. Their migration assistance is included free.

Photo by Lukas Blazek — Pexels

Step 2: Create a Full Backup

This is non-negotiable. Before you change anything, back up everything:

• Website files — themes, plugins, uploads, custom code. All of it.
• Database — export your MySQL/MariaDB database (phpMyAdmin makes this easy)
• Email accounts — if you use hosting-based email, export those too
• Configuration files — .htaccess, wp-config.php, any custom settings

I always keep two copies: one on my local drive and one in cloud storage (Google Drive or Dropbox). Paranoid? Maybe. But I learned the hard way after a botched migration in 2023 where my only backup was on the old server that got wiped. Don't be me.

For WordPress users: Plugins like UpdraftPlus or Duplicator make this dead simple. Run a full backup, download the archive, and verify the file isn't corrupted before moving on.

Step 3: Document Your Current Setup

This step gets skipped constantly and it causes headaches later. Write down:

• PHP version (check in your hosting panel or with phpinfo())
• Database version (MySQL 5.7? 8.0? MariaDB 10.x?)
• All DNS records — A records, CNAME, MX (especially if you use email)
• SSL certificate details — who issued it, when it expires
• Cron jobs or scheduled tasks
• Custom server configurations

I keep a simple text file for each site. Takes 10 minutes and saves hours of troubleshooting later. Trust me on this one.

Step 4: Set Up Your New Hosting Account

Sign up with your new provider and configure the environment to match your current setup:

• Set the same PHP version (or newer, if your CMS supports it)
• Create a new database with the same name and charset
• Set up FTP/SFTP access
• Install an SSL certificate (most providers offer free Let's Encrypt — read about why SSL matters)

Important: Don't change your DNS yet. You want to set everything up and test it on the new server before sending any real traffic there.

Step 5: Transfer Your Files and Database

Here's where the actual migration happens. You've got three main options:

Option A: Let Your New Host Do It (Easiest)

Most quality providers offer free migration. Give them your old hosting credentials and they handle everything. This is what I do 90% of the time now. Hosting.com completed my last migration in about 45 minutes with zero issues.

Option B: Use a Migration Plugin (WordPress)

Duplicator Pro or All-in-One WP Migration let you package your entire site into a single file, then import it on the new server. Works well for sites under 2GB. Larger sites might need the paid version or manual transfer.

Option C: Manual Transfer (Full Control)

1. Upload your website files via SFTP (FileZilla works great)
2. Import your database through phpMyAdmin on the new server
3. Update your configuration file (wp-config.php for WordPress) with new database credentials
4. Verify file permissions are correct

Manual transfer takes longer but gives you complete control. I go this route for non-WordPress sites or when I want to clean up old files during the move.

Photo by Negative Space — Pexels

Step 6: Test Before Switching DNS

This is the step most people skip. Don't.

Before updating your domain's nameservers, verify that everything works on the new server. Here's how:

• Edit your local hosts file — point your domain to the new server's IP address on your computer only. On Windows, edit C:\Windows\System32\drivers\etc\hosts. On Mac/Linux, edit /etc/hosts.
• Use a temporary URL — many hosts provide a temporary address (like server123.hostingprovider.com/~youraccount) to preview your site.

Check every page. Test your contact forms. Try the checkout process if you run a store. Click through your navigation. Look for broken images and missing CSS. I once forgot to update a hardcoded absolute URL in a theme file — took me an hour to figure out why images weren't loading on the new server.

Step 7: Update DNS Settings

Once you're confident the new server is working properly, it's time to switch DNS. Go to your domain registrar (wherever you bought your domain) and update the nameservers to point to your new host.

Your new hosting provider will give you nameserver addresses — usually something like ns1.hosting.com and ns2.hosting.com.

Timing tip: Do this during your lowest-traffic period. Late night or early weekend morning works best. DNS changes can take anywhere from 15 minutes to 48 hours to fully propagate, though in my experience it's usually done within 2-4 hours.

Step 8: Monitor and Wait for DNS Propagation

DNS propagation means the change is spreading across the internet. During this window, some visitors will see your site on the old server, others on the new one. That's normal.

Critical: Keep your old hosting account active during this period. Don't cancel it yet. If something goes wrong, you want the ability to switch back.

Tools I use to check propagation status:

• whatsmydns.net — shows DNS status across different global locations
• dnschecker.org — similar tool with a clean interface

Once all locations show the new IP address, you're in the clear.

Step 9: Post-Migration Checklist

After DNS has fully propagated, run through these checks:

• [ ] All pages load correctly — no 404 errors, no broken layouts
• [ ] SSL certificate is active — check for the padlock icon
• [ ] Forms work — contact forms, newsletter signups, checkout
• [ ] Email is working — send test emails to and from your hosting email
• [ ] Redirects are intact — especially 301 redirects for SEO
• [ ] Site speed is improved (or at least the same) — run a quick test on GTmetrix
• [ ] Google Search Console — submit your sitemap again and check for crawl errors
• [ ] Analytics is tracking — verify Google Analytics or your tracking tool is collecting data

Photo by Pavel Danilyuk — Pexels

Step 10: Cancel Your Old Hosting (But Not Too Soon)

Wait at least 72 hours after the DNS switch before canceling your old hosting. I usually wait a full week just to be safe. This gives you a fallback if anything unexpected pops up.

Before canceling, download one final backup from the old server. You never know when you might need a reference copy of your old configuration.

Common Migration Mistakes (I've Made Most of These)

• No backup — always, always back up first. This should be muscle memory by now.
• Canceling old hosting too early — DNS might still be pointing there for some users.
• Forgetting about email — if your email runs through your hosting, update MX records or you'll lose incoming mail.
• Hardcoded URLs — search your database and files for the old server's IP or temp URL. A quick find-and-replace fixes this.
• Ignoring PHP version differences — your site might break on a newer PHP version if plugins aren't compatible. Test first.
• Skipping the SSL setup — your site will show a "Not Secure" warning and browsers might block access entirely.

What About SEO During Migration?

Good news: a host-to-host migration (same domain, different server) has minimal SEO impact if done correctly. Google doesn't care which physical server your site lives on. They care about:

• Downtime duration — keep it under an hour and you're fine
• URL structure — don't change URLs during migration unless absolutely necessary
• Speed improvements — if your new host is faster, you'll likely see a rankings boost
• 301 redirects — if any URLs change, set up proper redirects immediately

In my experience, rankings either stay flat or improve after migration to better hosting. I've never seen a penalty from a clean host-to-host move. That said, it can take 4-12 weeks for search performance to fully stabilize. Don't panic if you see minor fluctuations in the first few weeks.

For more on the hosting-SEO connection, check our article on how hosting affects your search rankings.

Frequently Asked Questions

How long does a website migration take?

The actual transfer takes 30 minutes to a few hours depending on site size. DNS propagation adds another 2-48 hours. Total time from start to finish: plan for a weekend just to be comfortable.

Will my site go down during migration?

Brief downtime is possible during the DNS switch — typically 5-30 minutes. If you do it right (keeping both hosts active during propagation), most visitors won't notice any interruption at all.

Can I migrate my site myself or do I need a developer?

If you're on WordPress, migration plugins make it doable for anyone. For custom-built sites, basic FTP and database knowledge helps. When in doubt, use your new host's free migration service — it's what they're there for.

Do I need to change my domain name to migrate?

No. Migrating to a new host and changing your domain are completely separate things. You keep your domain, you just point it to different servers.

Ready to Move?

Migrating your website isn't as risky as it feels. With a solid backup and a clear checklist, the process is mostly waiting for DNS to propagate while you refresh whatsmydns.net every 10 minutes (we all do it, no shame).

If you're looking for a reliable new home for your site, I recommend starting with Hosting.com for their free migration service or InterServer for their price-lock guarantee. Both have handled my migrations without a hitch.

And if you're looking for budget-friendly options to migrate to, we put together a list of the best cheap web hosting services in 2026 that won't break the bank.