Transferring your WordPress site to a new host saves costs and improves speed without downtime. Use plugins like Duplicator or manual methods for seamless migration from old to new servers.
Steps to Transfer WordPress Site to New Host
Backup Your Old Site
Install free Duplicator plugin on old site > “Create New.” Scan files/database, build package (downloads archive/installer files). Or manually: ZIP all files via cPanel File Manager, export DB via phpMyAdmin.
Download to your computer—takes 5-30 mins based on site size.
Prepare New Hosting
Sign up with new host (e.g., Hostinger), create MySQL database/user/password in cPanel. Note details for wp-config.php. Upload files to public_html via FTP (FileZilla) or File Manager.
Import Database and Files
Access new phpMyAdmin > Import old .sql file (under 256MB; compress if larger). Edit wp-config.php: replace DB_NAME, DB_USER, DB_PASSWORD with new ones.
Run installer.php (from Duplicator) > follow prompts to connect DB, admin login. Or manual: update URLs if domain changes via phpMyAdmin SQL query.
Update DNS and Test
Point domain nameservers to new host (e.g., ns1.newhost.com). Edit hosts file (127.0.0.1 yourdomain.com) to test live without propagation delay (24-48 hrs).
Clear caches, check plugins/themes. Go live post-verification.
Plugin Alternatives
All-in-One WP Migration (free up to 512MB): Export/import with one click. WPvivid Backup: Free full-site clones.
Tips and Warnings
Zero downtime: Test on staging subdomain first. Large sites (>2GB)? Use cPanel Staging Tool or paid services. Backup everything twice.
Common WordPress Host Transfer Errors
WordPress migrations often trigger errors from mismatched configs or incomplete transfers, causing downtime for Jorhat sites. Addressing these proactively ensures smooth transitions.
Database Connection Failures
“Error establishing a database connection” tops the list—caused by wrong DB_NAME, DB_USER, or DB_PASSWORD in wp-config.php on the new host.
Fix: Verify credentials in new cPanel > MySQL Databases. Re-import .sql if corrupted. Check hosting firewall blocks (common with Hostinger).
Broken Images and 404 Errors
Missing media files or wrong URLs create broken images/links post-migration. Permalinks need refresh via Settings > Permalinks > Save.
Fix: Run Better Search Replace plugin to update old URLs. Verify uploads folder permissions (755 folders, 644 files).
White Screen of Death (WSOD)
PHP memory exhaustion or plugin conflicts show blank pages. Often from large databases overwhelming new host limits.
Fix: Enable WP_DEBUG in wp-config.php, check error logs via cPanel. Deactivate plugins via FTP (rename /plugins folder temporarily).
DNS Propagation Delays
Site loads old host 24-48 hours post-nameserver change, frustrating users. Temporary domain mismatches break SSL.
Fix: Lower TTL beforehand. Edit local hosts file (127.0.0.1 yourdomain.com) for instant testing. Reissue SSL certificate.
File Permission Issues
“Permission denied” errors block uploads or admin access. New hosts default to restrictive chmod settings.
Fix: FTP to public_html, set 755 (dirs)/644 (files). Restore .htaccess if excluded during ZIP export.
| Error Type | Cause | Quick Fix |
|---|---|---|
| DB Connection | Wrong wp-config | Verify MySQL credentials |
| 404/Broken Links | URL mismatch | Search Replace plugin |
| WSOD | PHP limit | Increase memory_limit=256M |
| DNS Issues | Propagation | Hosts file edit |
| Permissions | chmod wrong | 755/644 via FTP |