A WordPress migration fails with a “not enough space” message when the destination cannot provide enough usable working room for every stage of the move. The server may need space for the migration archive, the extracted WordPress files, the database import, and temporary files—so a destination that can hold the finished site may still fail during the transfer.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Keep the old site online, preserve a complete backup somewhere other than the full destination, measure every relevant storage limit, and then either remove disposable data, add capacity, or use a staged manual transfer. Do not switch DNS or delete the source until the restored site has passed testing.
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat the error actually means
“Not enough space” does not necessarily mean that the visible web root is full. The limiting resource can be the hosting account quota, the volume used by the destination database, or a temporary directory such as /tmp. WordPress’s disk_full condition is defined as: “There is not enough free disk space to complete the update.” A migration plugin or control panel can encounter the same practical limit while creating, unpacking, or importing a site.
A complete WordPress site has two inseparable parts:
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
- Files: the WordPress core,
wp-content, uploads, plugins, themes, and configuration files such aswp-config.php. - Database: posts, pages, settings, users, comments, plugin data, and other records stored in MySQL or MariaDB.
The database export does not contain your themes, plugins, uploads, or wp-config.php. Treating the SQL file as the whole backup can leave you with an incomplete site even if the import succeeds.
WordPress’s migration guidance therefore tells operators to back up the WordPress directory, images, plugins, other files, and the database before moving, then upload the files and import the database on the new server.
Recommended Free Tools
How much space does a migration need?
There is no WordPress-published universal multiplier such as “always allow twice the site size.” Calculate the requirement from measurements on your particular site and migration method.
| Space requirement | What it contains | Why it can be needed simultaneously |
|---|---|---|
| Existing destination data | Files, databases, logs, mail, and other accounts already using the allocation | These consume quota before the migration starts |
| Archive or backup package | The compressed migration file or uploaded backup | The package must remain available while it is unpacked or imported |
| Extracted WordPress tree | Core files, uploads, plugins, themes, and configuration | Extraction creates a second representation of much of the archive |
| Database staging and import | The SQL export and the destination database’s working data | The export may be retained while records are loaded into the database |
| Temporary workspace | Control-panel or plugin working files, often under a temporary directory | Some tools write outside the web root and are constrained by a separate limit |
| Operational headroom | Room for file moves, indexes, logs, and normal operation during the cutover | A destination that reaches 100 percent during import can fail before cleanup runs |
Measure the source file tree, the database export, and the archive produced by your chosen tool. On the destination, check the account quota, database storage, and temporary-directory usage separately. A hosting dashboard may show free web-space figures while a database quota or /tmp limit is the actual blocker.
Safe recovery runbook
1. Keep the old site available
Do not delete the source, cancel its hosting, or change DNS while the destination is unverified. The old server is your working fallback if the transfer is incomplete or the restored site has a configuration problem.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
2. Create an independent, complete backup
Before deleting anything on the destination, create a fresh copy of both the file tree and the database. Store that backup off the constrained server: an administrator’s workstation, an external hard drive sized from the measured data, or another storage service are possible locations. Verify that the files can be opened and that the SQL export exists; a backup that was never checked is not a reliable recovery point.
Keep the source running even after the backup is made. A complete backup and the live source provide two separate recovery options if a cleanup or import goes wrong.
3. Measure every storage boundary
Use the host’s control panel or shell access to inspect:
- Filesystem usage and the hosting account’s quota.
- The database volume or database-specific quota.
- The temporary directory used by the migration tool or control panel.
- Large logs, staging copies, and abandoned archives in the account.
With SSH, commands such as df -h show mounted-filesystem capacity, while du -sh on the site directory, backup directory, and temporary locations identifies which paths consume it. A hosting provider may need to report database and per-account limits that are not visible through those commands.
WordPress’s common-errors guidance notes that operations can fail when /tmp contains too many files even when another filesystem still has free space. Ask the host which temporary path the migration process uses before assuming the web root is at fault.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
4. Remove only disposable data
After confirming the independent backup, remove stale migration archives, abandoned extraction directories, old cache files, and temporary packages that are not part of the live site. Delete the copy that is consuming space, not the only copy of the backup you may need for recovery.
Do not remove wp-content/uploads, the only database export, the active database, or the source site merely because their names look large. If you cannot identify an item confidently, ask the host or the tool vendor before deleting it.
5. Add capacity when the data itself is too large
If cleanup does not create enough working room for the measured archive, extraction, import, and headroom, increase the destination storage allocation or move to a larger hosting plan. This is a capacity problem, not a setting that can be fixed safely by repeatedly retrying the same import.
Ask the provider whether the upgrade increases all relevant limits. Extra web storage does not necessarily increase database capacity or the temporary directory’s quota.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems6. Retry with a lower-space workflow
If the destination can hold the final site but not a full archive plus extraction, avoid creating a second complete copy there. Transfer the file tree and SQL export separately, or stage the archive on another machine or server and unpack it before sending the final files. Delete the temporary package only after the extracted files and database have been verified.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
7. Configure and import the destination
Create an empty destination database and import the SQL export into it. Edit wp-config.php with the destination database name, user, password, and host values supplied by the new provider. Confirm that the file paths, ownership, and permissions allow the web server to read WordPress files and write only where WordPress requires it.
Import into an empty database unless your migration instructions explicitly require another approach. Mixing old destination tables with the source export can leave stale options, users, or plugin records that are difficult to diagnose.
8. Handle a domain change safely
If the domain or site URL changes, update the home and siteurl values for the destination and perform a serialization-safe search-and-replace. WordPress warns that a naïve text replacement across the entire database can corrupt serialized values used by settings and plugin data. Use a tool that understands serialized data, and keep the original SQL export untouched so you can restore it if the replacement is wrong.
9. Test before cutover
Use a hosts-file override, a staging URL, or another private test method to inspect the destination before changing public DNS. Check:
- The front end, key pages, navigation, and responsive layouts.
- WordPress admin login, user roles, and media-library access.
- Images and other uploads from old and recent posts.
- Every active plugin and theme, including license or API connections.
- Permalinks and rewrite rules.
- Forms, email delivery, search, shopping or membership functions, and other business-critical paths.
- Scheduled jobs, backups, cron tasks, and server-side integrations.
- HTTPS certificates, redirects, mixed-content warnings, and canonical URLs.
Only after these checks pass should you lower or change DNS records. Keep the old server and the independent backup until DNS propagation and a normal operating period confirm that the move is stable.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
What is safe to delete on the new server?
The safest candidates are data that can be regenerated and that is not needed for rollback:
- Migration archives left behind after successful extraction.
- Failed or duplicate extraction directories.
- Plugin or hosting caches that the system can rebuild.
- Temporary SQL or package files after the database and files have been verified.
- Old logs that the host explicitly identifies as disposable and that are not required for troubleshooting or compliance.
Before each deletion, record the path and confirm that another copy exists elsewhere. Never use a broad wildcard deletion in a directory that contains uploads, backups, or database files unless you have identified every matching item.
Manual migration when a plugin runs out of space
A manual move is useful when automation insists on building a large package on the destination. It also makes the two backup components visible, but it requires more opportunities for configuration mistakes.
- Back up the source. Copy the complete WordPress directory and export the database to storage outside the destination.
- Prepare the destination. Create the database and user, confirm storage and temporary limits, and upload the files without first generating a second archive on the destination.
- Import the SQL. Use the provider’s database-import tool or an approved command-line method, and watch for import-size or execution-time limits.
- Update configuration. Set the destination credentials in
wp-config.php; preserve salts and other settings unless there is a specific reason to change them. - Correct URLs if needed. Apply a serialization-safe replacement when the domain changes, rather than editing every text occurrence manually.
- Verify permissions and rewrites. Make sure the web server can read the files, uploads are present, and permalink rules are active.
- Run the private test. Complete the front-end, admin, media, plugin, form, scheduled-task, and SSL checks before DNS cutover.
Manual transfer does not eliminate storage requirements; it changes where temporary copies are made. Keep the SQL export and source files off the destination until the restored site is proven.
Quick Recap
Choosing the right remedy
| Remedy | Best fit | Trade-off |
|---|---|---|
| Clean disposable files | The measured site and migration workspace fit after stale archives and caches are removed | Requires careful identification and a verified off-server backup |
| Increase destination storage | The site’s measured data plus working headroom exceeds the current allocation | May require a larger plan and confirmation that database and temporary limits also increase |
| Separate file and database transfer | The final site fits, but a combined archive cannot be created or extracted safely | More manual steps and more responsibility for configuration and verification |
| Stage off-server | The destination is too constrained for temporary packages | Needs another machine or server and an additional transfer step |
| Retry the same plugin job | Only when measurements show the earlier failure was caused by disposable residue that has been removed | Repeating without changing capacity or workflow usually recreates the same failure |
Preventing the next failed migration
- Measure the file tree, database export, archive, quota, database volume, and temporary directory before scheduling the move.
- Keep a complete files-plus-database backup away from the destination.
- Ask the host about separate limits for account storage, databases, and
/tmp. - Plan a low-space transfer path before the maintenance window instead of improvising after an archive fails.
- Document the destination credentials, URL changes, permissions, cron tasks, email settings, and DNS rollback plan.
- Schedule the cutover only when you have time to test the restored site and keep the old one available.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →




