EasyTools Migrator Backup Size Guide: From Under 1 GB to 50 GB

EasyTools Migrator is designed to help WordPress users back up, transfer and restore websites more easily. However, the maximum backup size that can be uploaded or restored successfully does not depend on the plugin alone.

Your hosting storage space, PHP memory, server performance and internet connection can all affect the migration process.

This guide explains the recommended method for website backups below 1 GB, between 1 GB and 3 GB, from 3 GB to 10 GB and for very large backups up to 50 GB.

Important: Backup Size Is Not the Only Requirement

A large upload limit does not automatically mean that your server can restore a large website successfully.

Before starting a migration, check the following:

• Available server disk space
• PHP memory limit
• Maximum execution time
• ZIP extension availability
• Folder permissions and writability
• Backup file integrity
• Hosting type and server performance

EasyTools Migrator checks most of this for you. Open the Export screen and you will see live panels for ZipArchive ready, Uploads writable and Server limits, including your free disk space and browser upload maximum. Check these before starting rather than after a failure.

Free Tier and Premium

The free version of EasyTools Migrator backs up sites with up to 3 GB of exported content, measured against your database and wp-content only — WordPress core, caches and old backups are not counted against you.

Premium removes the size limit entirely. If your site is larger than 3 GB, you will need Premium for the sections below.

See Site Migrator Premium →

Backup Size Guide

Below 1 GB: Direct WordPress Upload

Backups below 1 GB are comfortable for direct browser upload through the EasyTools Migrator interface. This suits small business websites, blogs, portfolios, simple WooCommerce stores and sites with a limited media library.

Recommended method: Upload the backup directly through WordPress. Keep the browser tab open until it finishes.

1 GB to 3 GB: Direct Upload or Server Upload

Backups between 1 GB and 3 GB usually still work through direct browser upload, because the file is sent in small pieces and each piece retries automatically if the connection stumbles.

The remaining risks are a long transfer on an unstable connection, closing the browser tab early, insufficient free disk space on the destination, or hosting CPU and memory limits during restore.

Recommended method: Direct upload is reasonable on a stable connection. If your connection is unreliable, upload through cPanel File Manager, FTP or SFTP instead, then select the backup from inside EasyTools Migrator.

3 GB to 10 GB: Server Upload Recommended

For backups larger than 3 GB, server-side upload is the more practical route. The plugin can handle the transfer in pieces, but moving several gigabytes through a browser simply takes a long time and asks a lot of your connection.

Recommended method: cPanel File Manager, FTP, SFTP, hosting control panel upload, or SSH where available. The server also needs enough memory and free disk space to extract and restore. This size requires Premium.

10 GB to 50 GB: Strong Hosting or VPS Recommended

Very large backups require significantly more server resources. Shared hosting may not provide enough disk space, PHP memory, CPU or file-processing capacity.

Recommended method: Upload through SFTP, FTP, SSH or cPanel File Manager. A VPS, cloud server or dedicated server is strongly recommended.

Above 50 GB: Advanced Server Migration

For backups above 50 GB, use an advanced server-to-server method: SSH transfer, server-to-server copy, rsync, hosting-provider migration assistance, or manual database and file transfer.

Contact your hosting provider before restoring a backup of this size. Confirm that the destination server has sufficient storage and resources.

Recommended Free Disk Space

Restoring a backup requires more space than the backup file itself. During restoration the server may temporarily hold the uploaded ZIP, the extracted WordPress files, temporary restore data and database import files at the same time.

Plan for at least 2 times the backup size in free disk space, and 3 times for comfortable headroom.

Recommended PHP Settings

Because the plugin works in small resumable batches, it does not need unusually large PHP limits. The same modest configuration works for a 1 GB site and a 30 GB site:

upload_max_filesize = 64M
post_max_size = 64M
memory_limit = 256M
max_execution_time = 120
max_input_time = 120

For very large sites, the only value worth raising is memory to 512M.

Recommended Upload Method by Backup Size

Common Reasons Large Migrations Fail

• The server runs out of disk space partway through
• The browser tab is closed before the upload finishes
• The ZIP extension is unavailable
• The destination folder is not writable
• The hosting account reaches its CPU or memory limit
• The backup file is incomplete or corrupted
• The destination database uses a narrower character set than the source

Best Practice for Large Backups

For backups above 3 GB, follow this process:

1. Confirm the destination server has enough free disk space.
2. Check the Server limits panel on the Export screen.
3. Confirm the ZIP extension is enabled.
4. Upload the backup using FTP, SFTP, SSH or cPanel File Manager.
5. Verify the file size on the server matches the original.
6. Run Check Backup File before restoring.
7. Start the restoration from EasyTools Migrator.
8. Keep the restore screen open until it reports completion.

Frequently Asked Questions

Do I need a huge upload limit to migrate a big site?

No. EasyTools Migrator sends the backup in 5 MB pieces, so an upload limit of 16 MB to 64 MB is enough whether your site is 1 GB or 30 GB. Free disk space matters far more than upload size.

Can EasyTools Migrator restore a 50 GB website?

It can work with very large backups, but success depends on the destination server. A 50 GB migration normally requires server-side upload, substantial free disk space and a VPS or dedicated server.

Can I upload a 3 GB backup through WordPress?

Yes, in most cases. The upload is chunked and each piece retries automatically. On an unstable connection, FTP or File Manager is still the calmer option.

Why does my upload stop before reaching 100%?

Usually the browser tab was closed, the connection dropped for an extended period, or the server ran out of disk space. Progress is saved, so you can resume rather than start again.

Why do I need two to three times the backup size as free space?

The server temporarily holds the archive and the extracted files at the same time, plus database import data during the restore.

Does raising max_execution_time to two hours help?

No. Each batch deliberately finishes well inside your limit, so anything above roughly 60–120 seconds makes no difference. What matters is that your host does not terminate requests sooner than PHP expects.

What is the safest method for a large website?

Upload the backup directly to the destination server through SFTP, FTP, SSH or File Manager, run Check Backup File, then start the restoration from EasyTools Migrator.

Final Recommendation

EasyTools Migrator can process both small and large WordPress backups. The practical maximum depends on your hosting environment — and in almost every case the deciding factor is free disk space, not upload limits.

• Use direct WordPress upload for backups below 3 GB.
• Use FTP, SFTP or File Manager for backups above 3 GB.
• Use a VPS or dedicated server for backups between 10 GB and 50 GB.
• Use advanced server-to-server migration for backups above 50 GB.
• Always keep at least twice the backup size free on the destination.