How to Migrate WordPress to a New Host: Zero Downtime, Zero SEO Loss Step-by-Step Guide 2026

How to Migrate WordPress to a New Host: Zero Downtime, Zero SEO Loss Step-by-Step Guide 2026

Every growing WordPress site eventually needs a better home. Your current host might be too slow, too expensive, or unable to handle your traffic. But moving a live website scares most owners. One wrong step and visitors see errors, email stops working, or months of SEO rankings vanish overnight.

The good news: WordPress migration is predictable and safe when you follow the correct order. This guide walks you through every step — from pre-migration preparation to DNS propagation strategy — so your site stays online, your email keeps working, and Google transfers your rankings to the new server without loss.

Pre-Migration Preparation

Do not start the transfer until you complete these checks. Preparation prevents 90 percent of migration problems.

1. Choose the Right Time

• Migrate during your lowest-traffic hours — typically late night or early morning for your primary audience.
• Avoid holidays, sales events, or scheduled marketing campaigns.
• Allow 2–4 hours of active work plus DNS propagation time. Do not rush.

2. Check Compatibility

• New host must support your current PHP version — ideally PHP 8.1 or higher for modern WordPress and WooCommerce.
• Verify database version compatibility — MySQL 5.7+ or MariaDB equivalent.
• Confirm SSL support — free Let's Encrypt SSL must be available before you start.
• Check file upload limits and execution time — should match or exceed current host.
• If using WooCommerce, ensure the new host supports WooCommerce system requirements fully.

3. Lower DNS TTL

Time To Live (TTL) tells internet servers how long to cache your DNS information. Lower it before migration so changes propagate faster.

1. Log into your domain registrar or DNS provider
2. Find your A record and www CNAME record
3. Change TTL from default (often 3600 seconds = 1 hour, or 86400 = 1 day) to 300 seconds (5 minutes)
4. Save. Do this 24–48 hours before migration. This step alone prevents most extended downtime.

4. Put Your Site Into Maintenance Mode (Optional)

For high-traffic or ecommerce sites, use a maintenance mode plugin during the final transfer window. This prevents customers from placing orders or leaving comments on the old database while you are copying to the new one. Low-traffic sites can skip this step.

Step 1: Full Backup of Everything

Never migrate without a complete backup stored OFF your current hosting account. If something breaks, this is your only safety net.

What You Must Back Up:

• WordPress database: Contains all posts, pages, products, orders, comments, settings
• WordPress files: Core files, themes, plugins, uploads, media library, .htaccess, wp-config.php
• Email accounts: If you use host-based email, export all mailboxes and settings separately
• SSL certificates: Note whether you are transferring or getting new ones
• DNS records: Screenshot or export all current DNS entries — especially MX records for email

Backup Methods:

• Hosting control panel: cPanel → Backup Wizard → Full Account Backup. Download to your computer.
• WordPress plugins: UpdraftPlus, Duplicator, or All-in-One WP Migration. Create backup and download all files.
• Manual method: Export database via phpMyAdmin, download all files via FTP/SFTP.

Rule: Use at least two backup methods. Plugins fail. Control panels occasionally glitch. Redundancy saves sites.

Step 2: Choose Your Migration Method

Three proven approaches. Choose based on your technical comfort and site size.

Method A: Migration Plugin — Easiest, Recommended for Most

Best for sites under 2GB. Handles database, files, and settings automatically.

Recommended Plugins:

• Duplicator: Creates a package file and installer script. Upload both to new host, run installer, done. Free version works for most sites.
• All-in-One WP Migration: Export file from old site, import into new site. Simple interface. Larger sites may require paid extension for file size limit.
• UpdraftPlus Migrator: If you already use UpdraftPlus for backups, the migrator add-on simplifies transfer between hosts.

Duplicator Step-by-Step:

1. On OLD site: Install Duplicator → Create New → Build Package → Download both files (Installer.php and Archive.zip)
2. On NEW host: Create empty database and database user → Note database name, username, password, host
3. Upload both Duplicator files to new host root directory via FTP or File Manager
4. In browser visit: yourdomain.com/installer.php (or temporary preview URL if DNS not switched yet)
5. Follow wizard: Enter new database credentials → Test connection → Run deployment → Update site URL → Finalize
6. Log into new WordPress → Confirm all content, media, plugins, settings present
7. Delete installer files from new host — security requirement

Method B: Manual Migration — For Advanced Users or Large Sites

Best for sites over 2GB, WooCommerce stores with many orders, or when plugins fail.

1. Export database: OLD host phpMyAdmin → Select database → Export → Quick export, SQL format → Download .sql file
2. Download files: FTP/SFTP → Download entire WordPress directory (wp-admin, wp-content, wp-includes, and all root files)
3. Create database on NEW host: cPanel → MySQL Databases → Create database, create user, add user to database with ALL PRIVILEGES
4. Import database: NEW host phpMyAdmin → Select new empty database → Import → Choose .sql file → Go
5. Upload files: FTP/SFTP to NEW host → Upload all WordPress files to public_html or root directory
6. Update wp-config.php: Edit file on new host → Update DB_NAME, DB_USER, DB_PASSWORD, DB_HOST values to match new database → Save and reupload
7. Test via temporary URL: Most hosts provide a temporary preview URL or IP-based access. Verify site loads before changing DNS.

Method C: Free Host Migration Service — Lowest Effort

Most reputable managed WordPress hosts offer free migration.

• SiteGround: Free migration by their team for new accounts. Submit request after signup.
• Nexcess / WP Engine: Professional migration service included. Their engineers handle the transfer.
• Bluehost / HostGator: Free migration for first site on certain plans.

How it works: Sign up for new host → Submit migration request form → Provide old host login details → Their team transfers everything → They notify you when ready to test → You update DNS.

Step 3: Test on New Host Before DNS Change

This is the most important step most people skip. Verify the new site works perfectly BEFORE pointing your domain there.

Testing Methods:

• Temporary URL: Most hosts provide something like http://server-ip/~username or temporary.preview-domain.com. Visit and browse every page.
• Hosts file edit (advanced): Edit your local computer hosts file to force yourdomain.com to load from new server IP. This lets you see exactly what visitors will see after DNS change.

Complete Test Checklist:

1. Homepage loads — correct layout, no missing images
2. All internal pages and posts open without 404 errors
3. Permalinks work correctly — save permalinks in Settings → Permalinks if needed
4. Media library shows all images and files
5. Plugins active and functioning — especially caching, security, forms
6. Contact forms submit and send email
7. If WooCommerce: Add to cart, checkout flow, payment gateway test mode
8. Admin dashboard accessible — all settings present
9. SSL working if already installed on new host
10. Site speed comparable or better than old host

Do NOT proceed to DNS change until every item on this list passes. Fix issues on the new server while visitors are still on the old one.

Step 4: DNS Update Strategy for Zero Downtime

DNS change is the only visible step to visitors. Done correctly, visitors never notice the switch.

Zero-Downtime Approach:

1. Ensure both OLD and NEW sites are fully operational simultaneously
2. Point your domain A record to the NEW host IP address
3. Keep the OLD site running unchanged for at least 72 hours
4. During propagation, some visitors see old server, some see new server. Both work. Zero downtime.
5. After 72 hours, nearly all traffic reaches the new server. You can then cancel the old hosting account.

How to Update DNS:

1. Log into your domain registrar or DNS provider (Namecheap, Cloudflare, etc.)
2. Find DNS Management or Advanced DNS
3. Locate the A record (usually @ or blank hostname)
4. Change the IP address from old host to new host IP
5. If using www CNAME, verify it points correctly to your domain
6. Save changes. TTL should already be low (300 seconds) from your pre-migration step.

What Happens During Propagation:

DNS changes spread across the internet gradually. Some internet providers update within minutes. Others take hours. This is why keeping both sites live is critical. Visitors land on whichever server their local DNS knows about. Both work. No one sees an error.

Step 5: Post-Migration SEO Preservation

Google ranks URLs and content, not servers. When done correctly, migration does not hurt rankings. But you must confirm these items:

• URL structure unchanged: Every post, page, and product URL must be identical. If URLs must change, set up 301 redirects from every old URL to the new equivalent.
• SSL active: HTTPS must work immediately. Mixed content errors (HTTP resources loading on HTTPS page) hurt rankings. Use a plugin like Really Simple SSL if needed.
• Site speed maintained or improved: Faster sites often rank better. Migration is an opportunity to improve performance.
• Google Search Console: Your site verification usually transfers automatically because it is tied to your domain, not host. Verify in Search Console that pages are still indexed. Submit a fresh sitemap as a precaution.
• No downtime: Extended downtime is the #1 cause of ranking drops during migration. The zero-downtime method in this guide prevents this.
• Robots.txt unchanged: Confirm your robots.txt file is not accidentally blocking search engines.

Step 6: Email Migration — Often Forgotten

If your email uses your domain name and is hosted by your old provider, email breaks during migration unless you plan for it.

Email Options:

• Option A: Migrate email to new host. Create identical email accounts on new host. Use email client to download all old messages, then reconfigure to connect to new server. Or use email migration tool if host provides one.
• Option B: Move to third-party email. Google Workspace, Microsoft 365, or Fastmail. DNS MX records point to them, not your host. Future host changes never affect email again. Recommended long-term strategy.
• Critical: Before changing DNS, export all email locally. If something goes wrong, you still have your messages.

Step 7: Post-Migration Monitoring and Cleanup

First 72 Hours:

• Monitor both old and new sites. Keep old hosting active.
• Test from multiple locations and devices — use friends or online tools like geopeeker.com to verify global propagation.
• Watch for broken links or missing images — install a broken link checker plugin to scan.
• Check error logs on new host — fix any PHP errors or warnings.
• Verify email is sending and receiving correctly.

After 72 Hours:

• Nearly all traffic now reaches new server.
• Reset DNS TTL back to normal value (3600 seconds or 1 hour) — reduces DNS query load.
• Install and configure caching on new host: WP Rocket, W3 Total Cache, or host-provided caching.
• Run security scan — confirm no malware introduced during transfer.
• Create fresh full backup on new host — this becomes your baseline.
• Cancel old hosting account — do not forget auto-renewal charges.

Common Migration Problems and Exact Fixes

• 404 errors on all pages except homepage: Permalinks need refresh. Go to Settings → Permalinks → Click Save Changes twice. Do not change anything — just save. This rebuilds rewrite rules.
• Error establishing database connection: wp-config.php has wrong database credentials. Double-check DB_NAME, DB_USER, DB_PASSWORD, DB_HOST against new host values.
• Mixed content warnings (HTTPS issues): Install Really Simple SSL plugin. Or run search-replace on database: change all http://yourdomain to https://yourdomain.
• Site redirects to old domain: Database still contains old URL references. Use Better Search Replace plugin to find old domain and replace with new domain.
• Email not working: MX records still pointing to old host. Update DNS MX records to new email provider. Allow 24–48 hours for email DNS propagation.
• Slow site after migration: Caching not configured yet. Install and configure caching plugin. Verify PHP version is current. Run image optimization.
• White screen of death: PHP error. Enable WP_DEBUG in wp-config.php to see exact error. Often a plugin conflict — rename plugins folder via FTP to disable all, then reactivate one by one.

Migration Checklist Summary

1. Lower DNS TTL to 300 seconds — 24–48 hours before migration
2. Full backup of database, files, email, DNS records — stored offline
3. Choose migration method: Plugin, Manual, or Host-provided service
4. Transfer site to new host
5. Test everything on new host via temporary URL BEFORE DNS change
6. Update DNS A record to point to new host IP
7. Keep both sites live for 72 hours minimum
8. Verify SEO: URLs same, SSL working, Search Console active
9. Migrate or move email — do not forget this step
10. Monitor 72 hours → Reset TTL → Configure caching → Backup → Cancel old host

Summary

• Zero downtime = both sites live simultaneously. Visitors land on whichever server their DNS knows. Both work. No one sees an error.
• Lower TTL first. Change DNS to 300 seconds one day before migration. Changes propagate in minutes, not hours.
• Test before switching. Verify every page, form, plugin, and function on the new server using temporary URL. Fix issues while visitors are still on old host.
• Backup twice. Use plugin + control panel backup. Store offline. Redundancy prevents disasters.
• SEO transfers automatically. Same URLs + same content + no downtime = same rankings. Google ranks your domain and content, not your server IP.
• Email needs planning. Either migrate mailboxes or move to third-party provider like Google Workspace. DNS MX records control where email lands.

WordPress migration feels intimidating but follows a clear sequence. Prepare thoroughly, test rigorously before the DNS switch, keep both servers live during propagation, and monitor closely. Done this way, you move to a better host without your visitors or Google ever noticing the change.