🔄 WordPress Hosting Migration Guide 2026

1. Inventory Your Current Setup

• Database size—Note total size (wp_posts, wp_postmeta, wp_users, custom tables)
• File count and storage—Check disk usage (/wp-content/uploads typically largest)
• Installed plugins and themes—Document all active plugins and custom modifications
• SSL certificate status—Note if using Let's Encrypt (free, automated) or commercial certificate
• Email accounts—If hosting includes email, plan to migrate or forward
• Subdomains—Document any subdomains (blog.example.com, shop.example.com, etc.)
• Cron jobs—Note any custom WordPress crons or server-level scheduled tasks
• DNS records—Screenshot current DNS configuration for reference

2. Select Your New Host

Use the hosting comparison guides to select your new provider based on your specific needs. Key considerations for migration:

• Does the new host offer free migration assistance?
• What's the uptime SLA during the transition period?
• How many free migrations are included in your plan?
• Do they support WordPress staging environments?
• Is there a 30-day money-back guarantee if you're unhappy?

3. Plan Your Migration Window

• Timing matters—Schedule migration during lowest-traffic periods (typically early morning or middle of the night for US sites)
• Avoid peak publishing—Don't migrate during times when content is actively being published or edited
• Communicate with team—If you have editors, notify them the site will be briefly unavailable
• Customer notification—For business sites, consider posting a maintenance notice beforehand
• Backup timing—Plan backup creation for immediately before migration

Most professional hosting providers (Bluehost, SiteGround, WP Engine, Hostinger, HostGator) offer free or paid migration services. This is the safest option for non-technical users.

Step-by-Step Process

1. Contact the new host's support—Tell them you're migrating. They'll send migration instructions or request your old host credentials
2. Provide access credentials—Your new host needs either cPanel login, FTP credentials, SSH access, or database credentials
3. Create backup at old host—Take a full backup before migration begins
4. Authorize the migration—Give the new host permission to access and copy files
5. Monitor the process—The migration typically takes 1-4 hours depending on site size
6. Test on new host—Before DNS switch, verify site functions correctly at the new host
7. Point DNS to new host—Update nameservers or A records (see DNS switching section below)
8. Wait for propagation—DNS changes take 24-48 hours to fully propagate
9. Monitor for issues—Watch for broken images, missing plugins, email delivery problems

WordPress migration plugins like Duplicator, All-in-One WP Migration, and MigrateDB Pro automate the export/import process with a user-friendly interface.

Popular Migration Plugins

Using Duplicator (Step-by-Step)

1. Install and activate Duplicator on your current site
2. Create a package (full site backup with database and files)
3. Download the package to your computer
4. Upload the package to your new host (via cPanel File Manager or FTP)
5. Run the Duplicator installer on the new host
6. Follow the prompts to configure database and paths
7. Test the site at the new host's temporary URL
8. Update DNS to point to the new host
9. Clean up—delete the installer file from the new host

For complex sites or custom setups, manual migration gives you complete control. This involves downloading the database and files, then uploading to the new host.

Step 1: Backup Database

• Via phpMyAdmin (in cPanel): Export database as SQL file
• Via WP-CLI: Run wp db export filename.sql
• Via backup plugin: Download database dump from plugin
• Store the SQL file safely (this is critical—don't lose it)

Step 2: Download All Files

• Use FTP/SFTP to download the entire /public_html or /www directory
• This typically includes: wp-content, wp-admin, wp-includes, wp-config.php, .htaccess
• Download time varies by site size (small: 5 mins, large: 30+ mins)
• Verify all files downloaded completely before proceeding

Step 3: Upload to New Host

• Create a new database on the new host (save credentials)
• Upload all files via FTP to the new host's public_html directory
• Upload the SQL database dump via phpMyAdmin
• Edit wp-config.php to point to new database credentials

Step 4: Fix URLs (Critical)

If your site's domain or structure changed, WordPress stores full URLs in the database. You'll need to update them:

• Option A: Use Find & Replace in phpMyAdmin (run SQL: UPDATE wp_posts SET post_content = REPLACE(post_content, 'old-domain.com', 'new-domain.com');)
• Option B: Use MigrateDB Pro for automated find/replace
• Option C: Use Search and Replace plugin after site is live (faster, safer)

Understanding Nameservers vs A Records

You have two options for pointing your domain to the new host. The method depends on how your domain is registered:

Option A: Update Nameservers (Recommended)

Changes where your entire domain points. Best if you're using the new host's nameservers.

• Login to your domain registrar (GoDaddy, Namecheap, Domain.com, etc.)
• Find "DNS Settings" or "Nameservers" section
• Replace old nameservers with new host's nameservers (your new host provides these)
• Save changes—propagation takes 24-48 hours (sometimes up to 72 hours)
• You can check propagation status at whatsmydns.net

Option B: Update A Record (Advanced)

Points just your domain's A record to the new host. Useful if you want to keep other DNS records elsewhere.

• Login to your domain registrar's DNS settings
• Find the A record for your domain (or www subdomain)
• Change the IP address to your new host's IP
• Save changes—propagation is faster (24 hours typical)
• This method requires more technical knowledge

Pre-DNS Switch Testing Checklist

• ☐ Test site at new host's temporary URL (provided by host)
• ☐ Verify all pages load without errors
• ☐ Check all images and assets load correctly
• ☐ Test contact forms, if any
• ☐ Verify WooCommerce checkout (if applicable)
• ☐ Test login and admin dashboard functionality
• ☐ Confirm SSL certificate is valid (green lock icon)
• ☐ Check email delivery (if host provides email)
• ☐ Test on mobile device
• ☐ Check mobile responsiveness

Critical Checks During DNS Propagation

• Monitor site uptime—Use Uptime Robot or similar service to confirm availability
• Check error logs—Review server error logs at new host for any PHP or configuration errors
• Test from different locations—DNS propagates gradually, so test from multiple geographic locations
• Clear browser cache—Old DNS records may be cached locally, forcing cache clear with Ctrl+F5
• Monitor traffic patterns—Verify traffic is reaching new host (check analytics)
• Test email delivery—Send test emails from contact forms, password resets
• Check for SSL warnings—Ensure no "insecure connection" warnings appear
• Verify backups working—Confirm backup system is running at new host

Common Post-Migration Issues

2 weeks before: Plan and select new host | 1 week before: Create backups, prepare documentation | 1 day before: Do final testing, notify team | Migration day: Execute migration, test at new host | DNS switch: Update nameservers | 1-2 days after: Monitor and resolve issues | 1 week after: Confirm everything stable, cancel old host if satisfied