WordPress Migration Failed: Not Enough Space? Fix It

If your WordPress migration failed with a “not enough space� error, the new server’s disk is full or the hosting account’s storage quota is exceeded. You can fix it by freeing up space on the new server (delete backups, old logs, or unused files) or by increasing the hosting plan’s storage limit, then re-running the migration.

Why “Not Enough Space� Happens During Migration

Migrating WordPress involves copying your entire site—files, database, media uploads, plugins, themes, and often a full backup archive—to the new server. The error typically appears when the destination server’s disk has less free space than the total size of the files you are transferring. This can happen even if your site seems small because the backup archive (e.g., a .zip or .tar.gz) can be 2–3 times larger than the uncompressed site, and the extraction process needs temporary space as well.

Common scenarios that trigger the error:

• You are using a migration plugin (like Duplicator, UpdraftPlus, or All-in-One WP Migration) that uploads a compressed package, then extracts it on the new server—requiring space for both the archive and the extracted files.
• The new hosting account has a strict storage quota (e.g., 5 GB) and your site plus the backup exceeds it.
• There are leftover files from a previous failed migration attempt, such as partial uploads or temporary extraction folders.
• The server’s temporary directory (/tmp) is full, which can cause PHP or the migration script to fail with a disk space error even if your account has space.

How to Check Available Space on the New Server

Before fixing, confirm exactly where the space shortage is. Most hosting control panels (cPanel, Plesk, or custom dashboards) show your disk usage under “Disk Usage� or “Storage.� You can also check via FTP or a file manager: look at the root of your account and sum the sizes of folders like public_html, backups, and logs. If you have SSH access, run:

df -h

This shows overall disk usage on the server. To see your account’s usage, run:

du -sh ~/

If the server itself is full (not just your quota), you cannot fix it from your account—you must contact the host. But in most cases, it’s your account quota that’s the problem.

How to Fix the “Not Enough Space� Error (Step-by-Step)

Follow these steps in order. Start with the simplest and least disruptive option.

1. Delete any existing files in the new account. If the host gave you a default “index.html� or a “coming soon� page, remove it. Check for old backups, logs, or temporary files in folders like public_html, tmp, or backups.
2. Remove the backup archive after uploading. If you uploaded a .zip or .tar.gz file, delete it once the files are extracted. The archive often takes up half the space.
3. Increase your hosting plan’s storage. Many hosts allow you to upgrade storage or move to a higher plan. This is the most reliable fix if your site is genuinely large.
4. Use a different migration method. Instead of uploading a full backup, use a plugin that transfers files directly from the old server to the new one (like Duplicator’s “ftp� transfer or All-in-One WP Migration’s “remote� option). This avoids needing space for the archive on the new server.
5. Clean up your site before migrating. Delete unused plugins, themes, old media files, and post revisions. This reduces the total size.
6. Try a manual migration. Export the database via phpMyAdmin, upload only the wp-content folder (not the whole site), and install a fresh WordPress core. This often uses less space than a full backup.

Common Misconceptions About Migration Space

Many users think the space needed equals the size of their WordPress site as shown in the admin dashboard. But the dashboard’s “Disk Usage� often only counts the database and uploads, not the entire installation. A site with 2 GB of media can easily need 5 GB of space for migration because of the backup archive, temporary files, and the extracted copy.

Another misconception: “I have 10 GB free, but my site is only 1 GB, so why does it fail?� The answer is often that the migration plugin creates a compressed archive, then extracts it, and during extraction it may need space for both the archive and the extracted files simultaneously. Also, the server’s temporary directory might be on a separate partition that is full, even if your account has space. Check /tmp with df -h if you have SSH.

How to Prevent This in Future Migrations

Plan ahead to avoid the error entirely:

• Check the new server’s free space before starting. Look at your hosting dashboard or use FTP to verify at least 2–3 times your site’s size is available.
• Use a migration plugin that streams files instead of uploading a full archive. For example, Duplicator’s “Package� can be transferred via FTP directly to the new server, and All-in-One WP Migration has a “remote� import option.
• Optimize your site before migrating. Compress images, delete old revisions, and remove unused plugins. This reduces the transfer size.
• If you are moving to a host with a strict quota, choose a plan with enough storage from the start, or ask the host to temporarily increase your quota during migration.

What to Do If the Error Persists After Freeing Space

If you’ve deleted files and still see the error, check these:

• Server temporary directory full. If you have SSH, run df -h /tmp. If it’s full, ask your host to clear it or set a different temp directory in wp-config.php by adding define('WP_TEMP_DIR', '/your/path');.
• PHP memory limit. A low memory limit can cause the migration script to fail with a misleading “disk space� error. Increase it in wp-config.php or .htaccess (e.g., php_value memory_limit 256M).
• File ownership/permissions. If the new server’s file permissions are wrong, the script may fail to write files, and the error message might be generic. Check that the web server user can write to the directory.
• Contact your host. If the server’s disk is truly full (not just your quota), only the host can resolve it.

Frequently Asked Questions

How much free space do I need for WordPress migration?

You need at least the size of your site’s uncompressed files plus the size of the backup archive. A safe rule is to have 2–3 times the size of your site’s total folder (including wp-content, database, and core files). For example, if your site is 1 GB, have at least 2–3 GB free.

Can I migrate WordPress without using extra space?

Yes, if you use a method that streams files directly from the old server to the new one, such as Duplicator’s FTP transfer or All-in-One WP Migration’s remote import. This avoids storing the backup archive on the new server. You still need space for the extracted files, but not for the archive.

Why does my migration fail even though I have 10 GB free?

Possible reasons: the server’s temporary directory is full, the PHP memory limit is too low, or the migration plugin is trying to extract an archive that is larger than the free space in your account (if your account has a separate quota). Check your account’s actual usage, not just the server’s total disk.

What is the easiest way to free up space on the new server?

Delete any default files (like index.html), remove old backups, and clear the cache folders. Also, if you uploaded a backup archive, delete it after extraction. Use your hosting file manager or FTP to see what’s taking up space.

Should I increase my hosting plan or clean up my site?

If your site is legitimately large (e.g., lots of media), increasing the plan is the long-term solution. If you have unused plugins or old backups, cleaning up is faster and cheaper. Do both: clean up first, then upgrade if needed.

Can I migrate WordPress manually to avoid the space issue?

Yes. Export the database via phpMyAdmin, upload only the wp-content folder (which contains themes, plugins, and uploads), and install a fresh WordPress core on the new server. Then import the database and update the wp-config.php file. This uses less space because you don’t upload a full backup archive.

Related

• AI in Transportation: 35 Deployments, What’s Proven
• Galaxy S7 & S7 Edge: Fix Disappeared Gallery Pictures
• Coding Agent Permissions: What to Allow & When