To migrate a WordPress site to a new host, you copy its files and database to the new server, update the settings that point to the old one, test everything on the new server privately, then switch your domain’s DNS so visitors arrive at the new host. Done in that order, with the right preparation, there’s no downtime and nothing gets lost. This checklist covers every step, from planning to the checks after launch.
Key takeaways
- Most migration problems come from skipping preparation, not from the copy itself.
- Lower your DNS “time to live” a day or two before you switch, so the change takes effect quickly.
- Test the site on the new server before changing DNS, using a temporary address or a hosts-file entry.
- Don’t forget email: MX records and any hosting email accounts must move too.
- Keep the old hosting running for at least a week after the switch.
Before you start: the pre-flight checklist
Good migrations are mostly planning. Gather this first:
- Access details for the old host, the new host, the domain registrar and the DNS provider (they may be different companies).
- A list of what runs on the old hosting: the website, email accounts, other domains, scheduled tasks and any extra databases.
- Your current DNS records, exported or screenshotted, including MX, TXT and any subdomains.
- Versions of PHP, WordPress and the database on the old server.
- A full backup of files and database, stored somewhere other than the old server.
- A quiet time for the switch, away from your busiest trading hours.
Check that the new host meets WordPress’s recommended requirements, including PHP 8.3 or newer. Moving to a newer PHP version is a good time to find outdated plugins, but test it rather than discovering problems on launch day.
Step 1: Lower the DNS TTL
The TTL (“time to live”) tells internet providers how long to remember your DNS records. If it’s set to a day, some visitors will keep reaching the old server for up to a day after you switch. One or two days before the move, lower the TTL on your main records to 5 minutes (300 seconds). Afterwards, set it back.
Step 2: Copy the files
Copy the whole WordPress folder, including wp-content (themes, plugins and uploads) and hidden files such as .htaccess. Use SFTP, an archive from the hosting panel, or a migration tool. Large upload folders can take hours, so start early.
Step 3: Export and import the database
Export the database from the old host (phpMyAdmin or a command-line tool), then import it into a new, empty database on the new host. Note the new database name, user, password and host address.
Step 4: Update wp-config.php
Edit wp-config.php on the new server so the four database settings match the new database. If the domain is staying the same, that’s usually all. If the domain is changing, you’ll also need to update URLs throughout the database with a proper search-and-replace tool that handles serialized data. The WordPress migration guide explains why a plain text replace can break settings.
Step 5: Test before you switch DNS
This is the step people skip, and it’s the most important. View the site on the new server before the public does:
- Use a temporary address your new host provides, or
- Edit your computer’s hosts file to point your domain at the new server’s IP address, just for you.
Then test properly:
- Home page and key landing pages load and look right.
- Images, fonts and videos load, with no missing files.
- Contact forms send, and the emails arrive.
- Logins work, including the admin area.
- Shop pages, cart, checkout and payment work, ideally with a test order.
- Search, filters and any booking tools work.
- The site works on a phone as well as a computer.
Step 6: Set up SSL on the new server
Install an SSL certificate on the new host before you switch, or as soon as DNS changes. Without it, visitors see a security warning. Check your CDN’s SSL mode too. A mismatch between the CDN and the server is the classic cause of redirect loops after a move.
Step 7: Plan the email move
Email is the most common casualty of a website move. Decide where email will live:
- Microsoft 365 or Google Workspace: keep the existing MX, SPF, DKIM and DMARC records exactly as they are.
- Email on the old hosting: create the same mailboxes on the new host, copy the messages, and update MX records when you switch.
Our guide to business email on your own domain explains the records involved.
Step 8: Switch the DNS
Update the A record (and AAAA record if you use IPv6) for your domain and www to the new server’s IP address. If you’re moving nameservers instead, copy every existing record to the new DNS provider first. Missing a single TXT record can break email verification. Our guide to pointing your domain to a new host covers each method, and our domain and DNS management service can handle it for you.
Step 9: After launch, check again
- Test the key pages, forms and checkout again on the live address.
- Submit a test enquiry and a test order.
- Check Google Search Console for crawl errors over the next week.
- Confirm backups are running on the new host.
- Set the DNS TTL back to a normal value.
- Watch the old server’s logs. If traffic still arrives there after a few days, something still points at it.
Step 10: Close the old hosting, carefully
Keep the old account for at least a week. Before cancelling, download a final backup and confirm nothing else (another site, a mailbox, a scheduled task) still depends on it.
Common migration mistakes
| Mistake | What happens |
|---|---|
| Not lowering the TTL | Visitors split between old and new servers for a day or more |
| Forgetting email records | Email stops arriving, often unnoticed for days |
| Plain text search-and-replace of URLs | Broken widgets and settings from damaged serialized data |
| Skipping the pre-switch test | Customers find the problems first |
| Cancelling the old host too soon | Lost files or mail you didn’t know were there |
If you’d like a version focused purely on avoiding downtime, see our guide to website migration without downtime. Moving from a hosted builder instead? Read moving from Wix to WordPress.
Or let us handle it
All of this is included free with every plan on our hosting plans page. Our free website migration covers your website, database and email, tested before we switch anything.
Frequently asked questions
How long does a WordPress migration take?
The copy usually takes a few hours, depending on size. Allow a day or two overall for preparation, testing and DNS changes.
Will my website go down during the move?
Not if it’s done in the right order. The new copy is tested first, and the old site stays live until DNS switches over.
Can I use a migration plugin?
Yes, for smaller sites. Large sites, shops and sites with email on the hosting often need a manual or assisted migration.
Will migrating hurt my SEO?
Not if the domain and URLs stay the same. Changing domain or URL structure needs redirects to protect rankings.
What happens to my email when I change hosts?
If it’s with Microsoft or Google, nothing, as long as the DNS records are kept. If it’s on the old hosting, the mailboxes must be recreated and copied.
Sources
- Moving WordPress, WordPress Developer Resources
- Requirements, WordPress.org
- Editing wp-config.php, WordPress Developer Resources