Last updated on Jul 24, 2025
1. What’s Supported
| Task | How to Do It | Tools |
|---|---|---|
| Point‑and‑click migrations | Use a plugin on the source site | Choose a stable and well-supported migration plugin or service. |
| Manual migrations / restores | Upload archives & import via SSH | Any .zip/.tar of wp‑content + SQL dump |
| Backups & cloning | Create and Download Backups | Built‑in WP Cloud backup service |
Custom DB prefixes are fully supported—just update $table_prefix in wp‑config.php before import.
2. Restore Options
- Download the backup, then follow the manual import steps below.
3. Manual Migration / Restore in 5 steps
Collect files
- wp-content archive
- SQL dump
- Place both in /tmp via SFTP or
wget<direct‑download‑url>
Prep & unpack
cd /tmp
unzip site.zip # or tar -xvf / gunzip
mv extracted/wp-content .
mv extracted/database.sql .
Sync files
rsync -zavh /tmp/wp-content/ /htdocs/wp-content/
Import DB
Confirm table prefix → edit wp-config.php if needed.
wp db import /tmp/database.sql
Clean up & test
rm -rf /tmp/*
Visit the site and verify everything.
4. Troubleshooting
| Symptom | Likely Cause | Fix |
|---|---|---|
| White screen | Prefix mismatch | Update $table_prefix |
| Import hangs | SQL > 10 GB | Split or trim dump |
| Core files in archive | Duplicate WordPress files | Delete them—WP Cloud supplies core |
5. Large‑DB Import Errors
- If phpMyAdmin export was made with wrong permissions, ask the source host to re‑export using “Add DROP TABLE / IF NOT EXISTS” and “Disable foreign key checks” options.