Worried about downtime during your WordPress migration? The ‘zero downtime’ trick is that your old site keeps running until the new one is completely ready and tested. Only then do you switch the domain over. Your files, database, and domain all need to transition — but not all at once.
Step 1: Choose a new host with free migration service, staging environment, UK-based servers, and UK business hours support. Step 2: Create a complete backup — all WordPress files, the database, wp-config.php settings, and DNS records. Never migrate without a backup.
Your new host
Create a fresh WordPress installation, import your files and database, and configure the site to work on a temporary URL. Your old site continues running throughout this entire process. Most managed hosts complete this within 24-48 hours.
Before switching, test everything on the temporary URL: all pages load correctly, images display properly, contact forms submit successfully, WooCommerce checkout works (if applicable), and SSL is active. Don’t rush this step — finding issues now prevents customer-facing problems later.
Once everything
Tested, update your DNS A record. Propagation typically takes 24-48 hours globally. Keep your old hosting account active for a week as a safety net. After migration, check Google Search Console for crawl errors, verify email deliverability, and confirm backups are running on the new host. Our uptime SLA means your new site is monitored from day one, and our managed vs shared hosting comparison explains why the switch is worth it.
Related
Frequently Asked Questions
How do I migrate WordPress without any downtime?
The zero-downtime approach keeps your old site live until the new one is fully tested. Transfer files and database to the new host, run wp search-replace to update all URLs, test the site via hosts file modification (not DNS change), verify SSL, forms, checkout, and email delivery. Only update DNS records after everything passes testing. Use a low TTL (300 seconds) set 48 hours before migration so DNS propagates quickly when you switch. Keep the old server running for 48 hours after DNS change. Most visitors see the new server within 1-4 hours of the DNS update.
How long does DNS propagation take when migrating WordPress?
DNS propagation depends on your domain’s TTL (Time to Live) setting. If your current TTL is 3600 seconds (1 hour), changes take up to 1 hour to propagate globally. Lower your TTL to 300 seconds (5 minutes) 48 hours before migration — this pre-caches the shorter TTL at DNS resolvers worldwide so your actual DNS change propagates in minutes rather than hours. Full global propagation is typically complete within 1-4 hours after changing the A record, with most major resolvers (Google DNS, Cloudflare) updating within minutes.
What should I test after migrating WordPress to a new host?
Post-migration testing should cover: site loads correctly via the new server (test with hosts file modification before DNS change), all internal links resolve correctly with no mixed content warnings, SSL certificate is valid and HTTPS is enforced, WooCommerce checkout completes a test transaction end-to-end, all forms submit and send confirmation emails, contact form email reaches the correct inbox, admin dashboard functions correctly, media files load correctly, any custom server-side scripts function, and page load time is acceptable. Test from a different network or device to avoid browser cache showing old content.
Can I migrate WordPress myself or do I need a professional?
A standard WordPress site (no custom server configuration, standard plugin stack) is within reach of a technically confident site owner using WP-CLI and following a systematic process. The required steps are well-documented. The risk areas are: serialised data in the database (requires WP-CLI search-replace, not simple SQL), SSL configuration on the new server, email delivery configuration (SPF/DKIM), and any custom server rules (.htaccess, PHP configuration). WooCommerce migrations are more complex due to payment gateway configuration and order data integrity requirements. Most reputable managed hosts offer free migrations — taking the technical risk off your hands entirely.
What happens to my SEO rankings when I migrate WordPress?
A correctly executed migration causes no SEO ranking impact — Google follows your content to the new server with no penalty for changing hosting providers. The domain, URL structure, and content remain identical. Temporary disruption can occur if the migration causes downtime that Googlebot encounters, if canonical tags change, or if page load times change significantly (affecting Core Web Vitals scores). Monitor Google Search Console for crawl errors in the week after migration and address any issues promptly. Moving to faster managed hosting with better TTFB can actually improve Core Web Vitals scores and rankings over the following weeks.