How to Move a WordPress Website to a New Host (Step-by-Step, Without Breaking It)

Moving a WordPress website to a new host looks scary, but it's really just five steps: back everything up, copy the files and database, point the domain, fix the URLs, and test. Done in the right order, downtime is a few minutes — not hours. Done in the wrong order, you can lose form submissions, break pages, or quietly tank your rankings.

I've migrated 100+ WordPress sites for clients — off failing shared hosts, off bloated 'managed' plans, and between regions. Here's the exact process I use.

Before you move: do these three things

• Take a full backup of files AND the database — not just the posts. Use your host's backup tool or a plugin like UpdraftPlus, then download it off-server.
• Note your current DNS records (A record, CNAME, MX/TXT for email). Whatever you forget to copy, you'll lose when you switch.
• Run a PageSpeed test on the current site and save the score. You'll want proof the move actually improved things.

Step 1: Set up WordPress on the new host

Install a fresh WordPress on the new host (or use its migration tool), then restore your files into the web root and import the database. If your host offers a staging domain or temp URL, use that first — you can complete the whole move without touching the live site.

Step 2: Import the database and update URLs

After importing the database, the old host's URL is still stored in wp_options (siteurl and home) and inside post content. Run a proper search-replace — Better Search Replace or WP-CLI's search-replace — never a raw SQL find/replace, because serialized data in widgets and plugin settings will break.

Step 3: Point the domain (DNS)

Lower your DNS TTL a day before, then switch the A record to the new host's IP. Propagation usually takes minutes to a few hours. Keep the old host running until the new site loads correctly on the real domain — this is your rollback plan.

Step 4: SSL, email, and redirects

• Issue the SSL certificate (Let's Encrypt/cPanel AutoSSL) BEFORE switching traffic, then force HTTPS with a redirect.
• If email is hosted with your old provider, move or re-authenticate MX records separately — this is the #1 thing people break.
• Check that all 301 redirects from the old site (htaccess or rank math) survived the move.

Step 5: Test everything (10-minute checklist)

• Every main page loads over HTTPS with no mixed-content warnings.
• Contact forms and checkout actually send/store orders.
• WP admin login works, permalinks resolve (re-save Settings → Permalinks if not).
• Search Console: no sudden crawl errors; run a URL inspection on your top pages.
• Re-run PageSpeed — a good move should be neutral or faster.

The mistakes that quietly break rankings

The two most common ranking killers after a migration are: forgetting to redirect the old URL structure (every moved page becomes a soft 404), and leaving the old site live on a public URL so Google sees duplicate content. Set 301s for anything that changed, and password-protect or delete the old install once DNS has settled.

Want someone else to handle it?

If you'd rather not do this at 11pm, I handle full WordPress host migrations — backup, transfer, DNS, SSL, testing — as part of my maintenance plans and as a one-off job. Start with a free website audit and I'll tell you exactly what your current host is costing you in speed.

→ Get a free website audit: https://www.raihanwp.com/audit — or see my maintenance & support plans at https://www.raihanwp.com/services/website-maintenance-support