Navigate to /wp-content/plugins/all-in-one-wp-migration/constants.php . Locate the line defining AI1WM_MAX_FILE_SIZE . Change the value to allow a higher limit: define( 'AI1WM_MAX_FILE_SIZE', 100 * 1024 * 1024 * 1024 ); Use code with caution. Method 4: Exclude Media and Large Files
Upload chunks to your new server via SCP, FTP, or cloud storage.
Select from the dropdown menu in the top right. Open the constants.php file. Search for the line containing AI1WM_MAX_FILE_SIZE . Change the value to allow a massive size limit. By default, it might look like this: define( 'AI1WM_MAX_FILE_SIZE', 2 << 28 ); Use code with caution.
If you have SSH access, use the plugin's CLI commands:
Empty the spam and trash comment folders entirely. allinone wp migration 100gb fix
: One of the most frequent DIY fixes is locating constants.php within the plugin folder (usually around line 282) and modifying the AI1WM_MAX_FILE_SIZE definition. By increasing the multiplier, users have reported seeing the import limit jump to 2TB in the WordPress dashboard.
The All-in-One WP Migration plugin is excellent, but its free version limits imports to 512MB. If you are trying to move a 100GB digital empire, you need a workaround that bypasses server restrictions and plugin limits without corrupting your database.
A: If you frequently work with large WordPress sites, investing in a dedicated migration tool like Migrate Guru or using your web host's built-in staging and transfer tools can provide a simpler experience. These tools are designed specifically to handle large transfers without requiring you to wrestle with PHP configuration files.
Before we fix it, let's understand the enemy. All-in-One WP Migration (Ai1WM) is brilliant for small to medium sites (under 5GB). But at 100GB, you hit three hard barriers: Method 4: Exclude Media and Large Files Upload
Large files often fail during the browser upload phase, causing the import to get stuck at 100% .
cd wp-content tar -czf uploads_part1.tar.gz uploads --exclude="*.tmp" --exclude="cache" split -b 10G uploads_part1.tar.gz "uploads_chunk_"
You won’t export 100GB in one go. Instead:
@ini_set( 'upload_max_filesize' , '128G' ); @ini_set( 'post_max_size', '128G' ); @ini_set( 'memory_limit', '2048M' ); @ini_set( 'max_execution_time', '7200' ); @ini_set( 'max_input_time', '7200' ); Use code with caution. 3. Bypass the Browser Upload via FTP (The Best Fix) Search for the line containing AI1WM_MAX_FILE_SIZE
: Large migrations often fail if security plugins like Wordfence or caching plugins are active during the import.
A: Yes, it is possible, though you are in a more complex scenario. For a site of this magnitude, adjusting PHP limits is often not enough because server resources can get overwhelmed. The most robust solution would be to use the official Unlimited Extension in combination with the FTP file manager method . You will likely also need a VPS or dedicated server, as typical shared hosting plans won't have the necessary resources.
: Temporarily turn off Wordfence, Sucuri, or server-level firewalls (like ModSecurity) on the target site during the import. They often mistake a massive file import for a cyberattack and block the process.
php_value upload_max_filesize 100G php_value post_max_size 100G php_value memory_limit 2048M php_value max_execution_time 0 php_value max_input_time -1 Use code with caution.