To migrate a WordPress website to a new server safely, take a full backup, copy the files and database to the new host, test the site on a temporary URL, lower your DNS TTL in advance, switch DNS during a quiet period, and then check SSL, forms, redirects and Google Search Console once the new server is live. If the domain and URLs stay the same, a careful server migration shouldn’t affect search rankings.
Most migration problems come from skipped testing: broken forms, missing SSL, mixed content or a forgotten “discourage search engines” setting left on from staging.
Before You Migrate
- Choose hosting that matches your traffic, with current PHP versions, server caching, daily backups and staging environments.
- Take a full backup of files and the database, and store a copy off the server.
- Note your current DNS records, email settings and any server-level redirects.
- Lower your DNS TTL to about 300 seconds a day or two before the switch so changes take effect quickly.
- Record baseline speed, traffic and rankings for comparison.
Step-by-Step WordPress Migration
1. Copy Files and Database
Use a migration plugin such as Duplicator, All-in-One WP Migration or your new host’s migration tool, or move files by SFTP and export and import the database manually.
2. Update Configuration
Update wp-config.php with the new database credentials, and run a safe search-and-replace if any URLs change.
3. Test on a Temporary URL
Use your host’s preview URL or edit your local hosts file to test every key page, form, checkout, login and integration before switching DNS.
4. Switch DNS
Update your domain’s A record or nameservers during a low-traffic period. Keep the old server running for a few days until DNS has fully propagated.
5. Install SSL and Force HTTPS
Confirm the certificate is active and every page loads over HTTPS without mixed-content warnings.
After the Migration
- Make sure Settings, Reading, “Discourage search engines” is unchecked.
- Check robots.txt and the XML sitemap.
- Submit test forms and confirm email notifications arrive.
- Verify analytics and tag tracking are firing.
- Watch Google Search Console for crawl errors and Core Web Vitals changes.
- Clear all caches and the CDN.
When a Migration Also Changes URLs
If you’re changing domains, URL structure or platforms at the same time, the move becomes a site migration with real SEO risk. Map every old URL to its new one with 301 redirects, update internal links, and use Search Console’s Change of Address tool for a domain change.
How M16 Marketing Helps
Our managed WordPress hosting includes migration, and our WordPress development team handles complex moves and redesigns with SEO protection.
Frequently Asked Questions
Will migrating my WordPress site hurt SEO?
If the domain and URLs stay the same and the site is tested properly, a server migration shouldn’t hurt rankings. Changing URLs or domains requires 301 redirects and more care.
How long does a WordPress migration take?
Copying a typical site takes a few hours. DNS changes can take from minutes to 48 hours to propagate fully, which is why lowering TTL in advance helps.
What is the best way to migrate WordPress?
For most sites, a reputable migration plugin or the new host’s migration service. Large or complex sites may need manual migration by a developer.
How do I avoid downtime when migrating?
Test the site on the new server before switching DNS, lower DNS TTL ahead of time, switch during low traffic and keep the old server running until propagation finishes.
What should I check after migrating?
SSL, forms, email delivery, analytics tracking, robots.txt, the search engine visibility setting, sitemaps and Search Console errors.
