Migrating WordPress sounds risky, but with the right order of operations you can move hosts with no visible downtime. The trick: fully build and test the site on the new host before you touch DNS. Here's the reliable method.
Before you start
- Access to both hosts (old and new)
- Your new WordPress hosting plan ready, with a temporary URL or IP to preview the site
- A recent full backup (you'll make a fresh one anyway)
Step 1: Back up everything
Export two things from the old host: all files (the wp-content folder especially) and the database (via phpMyAdmin export or a migration plugin). Keep a copy locally — this is your rollback if anything goes wrong.
Step 2: Set up WordPress on the new host
On the new host, create the site and database. With one-click installers this takes minutes. Don't point your domain yet — you'll work on a temporary URL the host provides so the live site stays untouched.
Step 3: Transfer files and database
Upload your wp-content (themes, plugins, uploads) to the new server, import the database, and update wp-config.php with the new database name, user and password. A reputable migration plugin can automate most of this if you prefer.
Step 4: Test on the temporary URL — this is the key step
Browse the site on the new host's temporary URL. Check the homepage, a few posts, the admin login, forms, and — for WooCommerce — a test checkout. Fix any issues now, while the live site is still served by the old host. Nobody sees this staging work.
Step 5: Lower your DNS TTL (a day ahead)
The day before the switch, reduce your domain's DNS TTL (e.g., to 300 seconds). This makes the later DNS change propagate in minutes instead of hours — the single biggest lever for a clean cutover.
Step 6: Switch DNS
Point your domain's A record (or nameservers) to the new host. Because you lowered the TTL and both copies are live during propagation, visitors are served seamlessly from one host or the other — no error pages, no gap.
Step 7: Keep the old host for 48 hours
Leave the old site running for a couple of days while DNS fully propagates worldwide. Once analytics and server logs show all traffic hitting the new host, you can safely decommission the old one.
Common mistakes to avoid
- Switching DNS before testing — the #1 cause of visible downtime.
- Forgetting to update
wp-config.phpdatabase credentials → connection errors. - Hardcoded old URLs in the database → run a safe search-replace (many migration plugins do this).
- A high DNS TTL left in place → hours of split traffic.
Make the destination worth it
A clean migration is wasted on a slow host. Migrate to a stack that's actually faster: Infrawire's managed WordPress hosting runs on NVMe SSD and Ryzen with free SSL and daily backups, and 24/7 support if you want a hand during the cutover. New to choosing a host? See how to choose the best WordPress hosting.
FAQ
Will my visitors see any downtime?
Not if you test on the temporary URL first and lower the DNS TTL before switching. Both sites stay live during propagation.
How long does a migration take?
The transfer itself is usually under an hour for a typical site; DNS propagation completes within minutes to a few hours with a low TTL.
Can support migrate the site for me?
Often, yes — ask your new host. Infrawire's support can assist with the transfer on WordPress hosting plans.