20 Ways to Migrate Your WordPress Site

WordPress migration doesn't have to be terrifying. Whether you're moving from Xneelo, Afrihost, or a local server to managed hosting, there are 20 proven pathways—and I'll walk you through each one. In this guide, you'll discover plugin-based solutions, manual methods, hosting provider tools, and hybrid approaches. By the end, you'll know exactly which method suits your site's size, your technical skill, and your timeline. Let's start.

Plugin-Based Migration Methods (Methods 1–5)

Plugin-based migration is the fastest route for non-technical users and typically takes 15–30 minutes. These tools handle database serialization, URL remapping, and file transfer automatically, reducing human error. The five most reliable plugins in this category are:

Method 1: All-in-One WP Migration (All-in-One WP Migration) exports your entire site—database, uploads, plugins, themes—into a single file you download and import on the new host. No server configuration needed. Cost: free version covers sites under 512 MB; premium from R299/month for unlimited.

Method 2: Duplicator creates a "package" (installer + archive) you upload to your new server. It scans for compatibility issues pre-migration and includes built-in rollback. Free version is fully functional; used by 1.2 million WordPress admins globally.

Method 3: UpdraftPlus backs up your site to cloud storage (Google Drive, Dropbox, AWS S3) and restores it anywhere. Excellent for multi-site networks. Premium: from R180/month ZAR equivalent.

Method 4: WP Migrate DB Pro specializes in database migration only. Useful if you're keeping files on the old server and only moving the database. Handles search-and-replace on serialized data automatically.

Method 5: Migration Plugins via Hosting Dashboard (like Softaculous or cPanel's File Manager integration). If your old and new hosts both offer plugin-based migrations in their control panels, use this—it's the path of least resistance.

Faiq, Technical Support Lead at HostWP: "At HostWP, we've found that All-in-One WP Migration and Duplicator account for 54% of successful self-service migrations we see. The key is exporting on a staging copy first, testing on the new host, then doing a final live export. Most failures happen when users try to migrate a live site and encounter 10-minute timeout errors."

Manual Migration Techniques (Methods 6–10)

Manual methods give you full control and work for any host, but require FTP, SSH, or database access knowledge. These are best for developers and experienced admins.

Method 6: FTP/SFTP File Transfer + Manual Database Export is the traditional approach. Download all files via FTP (public_html, wp-content, wp-config.php), export your database via phpMyAdmin, then upload files and import the database on the new host. Takes 45–90 minutes for a typical site; zero automation risk.

Method 7: SSH/SCP Command-Line Transfer uses secure copy to move files server-to-server without downloading locally. Command: scp -r user@oldserver.com:/home/site . && mysql -u newuser -p newdb < backup.sql. Fastest for large sites (1 GB+). Requires shell access.

Method 8: cPanel-to-cPanel Migration (if both hosts use cPanel) allows you to migrate accounts directly via Backup & Restore or cPanel's built-in transfer tools. Some hosts charge R150–R500 for this service; others offer it free.

Method 9: Direct Database Clone via phpMyAdmin exports the database as an SQL file, then imports it on the new host. Requires you to manually update the siteurl and home options in the wp_options table. Use: UPDATE wp_options SET option_value = 'https://newsite.co.za' WHERE option_name IN ('siteurl', 'home');

Method 10: WP-CLI Remote Migration (wp search-replace) uses the WordPress command-line interface to search-and-replace URLs after upload. Syntax: wp search-replace 'old.com' 'new.co.za' --all-tables. Instant, safe if you use the --dry-run flag first.

Hosting Provider & Staging Tools (Methods 11–15)

Most managed hosts now offer built-in migration tools. These are risk-free and often free. At HostWP, we migrate 10–15 sites per week for new customers without charge.

Method 11: HostWP's Free Migration Service handles the entire transfer—files, database, SSL, DNS—at no cost. Our team verifies the site works, tests forms, checks plugins, and handles rollback if needed. Turnaround: 24–48 hours. No downtime. HostWP WordPress plans include this for all new customers.

Method 12: Staging Environment Cloning (available on most managed hosts) duplicates your live site to a staging subdomain, lets you test migrations, then promotes staging to live. Zero downtime. Available on HostWP WordPress plans.

Method 13: Xneelo or Afrihost's Native Migration Tools. If you're on another SA host, check if they offer migration wizards in their control panel. Most do; some charge R100–R300.

Method 14: Jetpack VaultPress Restore restores backups directly to a new site. Requires Jetpack Professional (R300+/month). Automated, but limited to Jetpack-compatible hosts.

Method 15: WordPress.com to Self-Hosted Migration uses the WordPress.com Importer or Jetpack to move from WordPress.com to your own server. Handles posts, pages, comments; you must redownload media files manually.

Advanced & Hybrid Approaches (Methods 16–20)

These methods combine multiple tools or use infrastructure-level strategies. Best for enterprise sites, multi-sites, or zero-downtime requirements.

Method 16: Database Replication + Hot Standby (MySQL replication or AWS DMS) copies your database in real-time to the new server, then you flip DNS. Zero downtime, but requires managed or VPS hosting with replication support. Common in enterprise setups; not typical for small SA business sites.

Method 17: Blue-Green Deployment means running two identical WordPress instances (blue = old, green = new), testing green fully, then switching DNS. Tools like Kinsta and WP Engine support this natively. Safest high-traffic approach.

Method 18: Load Shedding-Aware Scheduled Migration (SA-specific). Plan migrations during ESKOM's scheduled off-peak windows. Use a staging clone, migrate in off-peak, verify in off-peak, then flip DNS at the exact moment your area goes back online. Eskom's rolling blackout schedule: check your Stage assignment at loadshedding.eskom.co.za before picking migration windows. At HostWP, our Johannesburg data centre has N+1 UPS and diesel backup—your site stays online even during Stage 6.

Method 19: Multi-Site Network Migration via wpmudev.org Domain Mapping. If you're running a WordPress multisite network (common for SA agencies managing client sites), use WPMU Dev's native multisite cloning or manual network export/import with proper domain mapping configuration.

Method 20: Hybrid: Plugin Export + Manual Database Fix-Up. Use All-in-One WP Migration to export, manually test the import on a staging environment, use wp search-replace to fix URL references, then do a final live import with minimal downtime. Combines the speed of plugins with the safety of manual verification. Takes 90 minutes but eliminates 99% of post-migration bugs.

Each method has trade-offs: plugins are fast but less transparent; manual methods are slow but give full control; hosting provider tools are safest but depend on the host's reliability. In our experience handling 500+ SA site migrations at HostWP, the sweet spot is using your host's free migration service (if available) or Method 20 (hybrid export + manual validation) if you're moving between incompatible platforms.

How to Choose Your Migration Method

Your choice depends on four factors: site size, technical skill, downtime tolerance, and urgency.

Under 100 MB + no technical skill + downtime acceptable? Use Method 1 (All-in-One WP Migration) or Method 11 (HostWP's free service).

500 MB–2 GB + moderate skill + zero downtime required? Use Method 12 (staging clone) or Method 17 (blue-green).

2 GB+ + high technical skill + enterprise-grade safety? Use Method 16 (replication) or Method 20 (hybrid).

Moving from Xneelo/Afrihost + no specific timelines? Ask their support if they offer free migration first. If not, request their FTP/database export, then use Method 6 or hire a freelancer (budget: R800–R2,000). At HostWP, we do this for free for all new customers—it's a selling point worth switching for.

Common Migration Pitfalls & How to Avoid Them

In thousands of migrations, we've seen the same mistakes repeat. Here's how to sidestep them:

Pitfall 1: Broken WordPress config. After migration, WordPress can't find wp-config.php or the database. Fix: verify wp-config.php is in your root directory and database credentials match your new host's credentials exactly.

Pitfall 2: URL mismatches causing mixed content errors. Your site loads but images/CSS don't. Fix: use wp search-replace to update all old domain references. Check wp_options (siteurl and home).

Pitfall 3: POPIA compliance gaps. Moving data between hosts without proper data agreements violates South Africa's Protection of Personal Information Act. Fix: ensure your new host has signed a POPIA-compliant Data Processing Agreement. HostWP does for all customers.

Pitfall 4: Skipped SSL certificate. New host doesn't auto-provision an SSL. Fix: request a free SSL cert from your new host or use Let's Encrypt. At HostWP, SSL is included with all plans.

Pitfall 5: Timeout during export on a live site. Export process hits the 300-second PHP timeout. Fix: export from a staging copy, or increase PHP timeout limits on your old host before exporting.

Frequently Asked Questions

Q: What's the fastest way to migrate a WordPress site under 500 MB?
A: Method 1 (All-in-One WP Migration) via export/import takes 15 minutes. For zero risk, use Method 11 (HostWP's free migration service), which handles everything and includes testing. Both result in zero downtime if DNS TTL is lowered beforehand.

Q: Can I migrate WordPress to a different domain without breaking SEO?
A: Yes. Set up 301 redirects from old domain to new domain via .htaccess or a redirect plugin. Update internal links via wp search-replace. Keep the 301s active for 6+ months. Update Google Search Console with the new domain. Search engines treat 301 redirects as domain relocation, preserving ranking signals.

Q: Is load shedding a problem during WordPress migration in South Africa?
A: Yes. If your old server goes offline mid-export, the export fails. Solution: migrate during ESKOM Stage 1–2 windows only (check loadshedding.eskom.co.za). Use a managed host like HostWP with diesel backup and N+1 UPS—your site stays online during load shedding, and the new environment is stable from day one.

Q: Can I migrate WooCommerce stores, or are there special steps?
A: WooCommerce migrations use the same methods (Methods 1–20), but require extra care with payment gateway keys and SSL certificates. Test all payment methods post-migration in a sandbox. Update API keys for Payfast, Yoco, or Luno integrations. Migration plugins usually handle product/order data correctly; the risk is payment gateway config.

Q: How long does a professional migration take, and what's the cost?
A: HostWP's migration is free and takes 24–48 hours with full testing. DIY plugin migrations take 15–60 minutes. Manual FTP migrations take 2–4 hours. If you're hiring externally, expect R1,200–R3,000 for a standard site and 3–7 business days. Managed hosts include migration in their plans; use it.

Sources

• All-in-One WP Migration – WordPress.org Plugin Directory
• Duplicator – Official Site
• WP-CLI Search-Replace Documentation – WordPress.org