WordPress Development
WordPress Hosting Migration: A Complete Zero-Downtime Migration Guide
A WordPress hosting migration done wrong means downtime and broken sites. Here is the complete process — from backup to DNS cutover — for a risk-free migration.
Migrating a WordPress site from one host to another is a routine task that carries significant risk when done without a clear process. A botched migration can mean hours of downtime, broken links, lost data, or a site that only partially works on the new host. Here is the complete, low-risk migration process.
When to migrate your WordPress hosting
- Performance problems: your current host is causing slow page loads, high TTFB, or resource limits that affect site functionality
- Cost optimisation: you are paying too much for your current hosting tier relative to what you need
- Reliability issues: frequent downtime events or poor support response times
- Scaling up: your site has outgrown shared hosting and needs managed WordPress hosting
- Security incident: your site was compromised and you want a fresh server environment
- New features: you need staging environments, automatic backups, or CDN integration that your current host does not provide
Pre-migration preparation
Use UpdraftPlus to create a full backup — both files and database. Download the backup files to your local computer. This is your insurance policy. Never start a migration without a confirmed working backup.
Record your current PHP version, WordPress version, plugin list, active theme, and any server-specific configurations (.htaccess rules, php.ini settings). Screenshot your current DNS settings.
Create your account on the new host. Do not point your domain to the new host yet — you need to test the migrated site first.
Plugin-based migration (Duplicator, All-in-One WP Migration) for most sites. Manual migration via FTP and phpMyAdmin for full control. Host-assisted migration for hosts that offer it free.
Method 1 — Plugin migration with Duplicator
Duplicator is the most reliable free plugin for WordPress site migration. It packages your entire site into a single installer archive:
Go to Plugins › Add New, install Duplicator. Go to Duplicator › Packages › Create New. Run the wizard — Duplicator creates a .zip archive of all your files and database, plus an installer.php file.
Download the installer.php and the .zip archive to your computer. The archive can be very large for sites with many media files.
Connect to your new hosting account via FTP/SFTP. Upload installer.php and the .zip archive to the root of your new hosting account (typically public_html/).
In your new hosting control panel (cPanel), create a new MySQL database, database user, and password. Note all three — you need them for the installer.
Visit yourdomain.com/installer.php (using a temporary URL if available, or temporarily pointing the domain). The Duplicator installer extracts the archive and rebuilds your site on the new host.
Before changing DNS, test every page, form, and function. Check WooCommerce checkout, contact forms, media display, and admin functionality.
Method 2 — Manual migration
Manual migration gives you complete control and is necessary when plugin-based migration fails (very large sites, custom configurations):
In your current host’s phpMyAdmin, select your WordPress database and click Export. Use SQL format. Download the .sql file.
Connect via FTP/SFTP to your current host. Download the entire WordPress installation — all core files, wp-content (themes, plugins, uploads), and wp-config.php.
Create a new MySQL database in your new host’s cPanel. Import your .sql file via phpMyAdmin.
Upload all downloaded WordPress files to the new host’s public_html/ via FTP/SFTP. This is the most time-consuming step for large sites.
Edit wp-config.php with the new host’s database name, database user, and database password.
If your URL changes (from http:// to https://, or from a temporary URL), use Better Search Replace to update all database references to the old URL.
DNS cutover — making the switch live
The DNS cutover is when you point your domain to the new host. This is the highest-risk step — do it only after thorough testing:
- Reduce TTL before migrating: 24-48 hours before migration, lower your DNS TTL to 300 seconds (5 minutes). This means DNS changes propagate globally within minutes rather than hours.
- Update nameservers or A record: either update your nameservers to the new host’s nameservers, or update the A record to point to the new host’s IP address.
- Propagation time: even with a low TTL, full global propagation takes up to 2 hours. During this time, some visitors reach the old host and some reach the new host.
- Keep old host active: maintain your old hosting account and site for at least 48 hours after DNS cutover. If anything goes wrong, you can revert DNS immediately.
- SSL certificate on new host: ensure the SSL certificate is installed and HTTPS works on the new host before cutting over. Many hosts install SSL automatically when the domain is pointed.
Post-migration checklist
- Verify all pages load correctly and images display
- Submit a test contact form and verify the notification email arrives
- Test WooCommerce checkout end-to-end (if applicable)
- Check Search Console for any crawl errors that appeared after migration
- Verify Google Analytics is still tracking (check Realtime report)
- Run PageSpeed Insights to confirm performance on new host
- Update all saved bookmarks, email signatures, and external links to the new server
- Set up backup schedule on the new host
Need your WordPress site migrated to a new host?
Simple Automation Solutions performs WordPress hosting migrations with zero downtime and full post-migration verification for businesses worldwide.
Frequently asked questions
How long does a WordPress hosting migration take?+
A typical business website (under 1GB total) migrated via Duplicator takes 2-4 hours including testing and DNS cutover. Large WooCommerce stores or media-heavy sites (over 5GB) can take 6-12 hours due to file transfer times. The DNS propagation phase adds 1-4 hours of waiting before the new site is live globally. Planning for a full-day migration window for any production site is prudent — this allows time for unexpected issues and thorough testing before committing to the cutover.
Can I migrate WordPress without any downtime?+
Near-zero downtime migration is achievable with proper planning. Set up and test the new site completely before changing DNS. Use a hosts file edit on your local computer to preview the new site at the new host while your domain still points to the old host. When confident, change DNS with a pre-reduced TTL (300 seconds). The only ‘downtime’ is the brief period while DNS propagates — typically under 15 minutes for most visitors with a low TTL. Some managed WordPress hosts (WP Engine, Kinsta) offer assisted migration specifically to minimise downtime.
What should I do if my site breaks after migration?+
First: do not panic and do not immediately revert DNS. Most post-migration issues are fixable. Common problems: database connection errors (wrong credentials in wp-config.php — recheck them), white screen of death (enable WP_DEBUG and check the error log), missing images (check file permissions on /wp-content/uploads/ — should be 755), mixed content warnings (run Better Search Replace to update http:// URLs to https://). If you cannot resolve the issue within 2-3 hours, revert DNS to the old host (which is still running) while you diagnose further.
