<\/span><\/h4>\n\n\n\nThis is consistently the most-reported problem with this plugin, and the causes stack up in roughly this order of likelihood: PHP limits still too low (upload_max_filesize<\/code>, post_max_size<\/code>, max_execution_time<\/code>, memory_limit<\/code>), your hosting account running low on disk space, a site that’s large for your hosting tier, a slow connection, or a conflict with another active plugin. Start with the PHP limits, since that’s the most common cause, then check disk usage in cPanel and clear out old backups or unused plugins and themes if space is tight.<\/p>\n\n\n\nIf you’ve genuinely fixed all of that and it’s still failing, real users have hit this exact wall: the upload completes fine, but the import throws an error right at 100%, even after correctly raising both PHP and web server limits. At that point, the bottleneck has moved somewhere those settings don’t reach, so skip the plugin upload entirely. Connect via FTP or from cPanel file manager, drop the .wpress<\/code> file directly into wp-content\/ai1wm-backups\/<\/code> on the new site, then refresh the Import screen; the plugin will pick it up from there.<\/p>\n\n\n\n<\/span>Manual Method<\/span><\/h3>\n\n\n\n<\/span>Raw folders listing, right after uploading your files.<\/strong><\/span><\/h4>\n\n\n\nYou extracted the zip into a subfolder instead of directly inside public_html<\/code>. Open File Manager and confirm wp-content<\/code> and .htaccess<\/code> are sitting directly inside public_html<\/code>, not nested one level down.<\/p>\n\n\n\n<\/span>Error establishing a database connection<\/strong><\/span><\/h4>\n\n\n\nWordPress can’t reach the database, which almost always traces back to wp-config.php<\/code>. Either the database name, username, or password doesn’t match what you actually created, or the database user was never granted privileges on that database.<\/p>\n\n\n\n<\/span>Too many redirects when you try to load the site.<\/strong> <\/span><\/h4>\n\n\n\nThis usually means your Site URL and Home URL don’t agree with each other, or SSL isn’t fully active yet on the new host. Recheck the “Fix the site URLs” step<\/p>\n\n\n\n
<\/span>A 500 Internal Server Error.<\/strong> <\/span><\/h4>\n\n\n\nAlmost always either a PHP version mismatch between your old and new host, or a corrupted .htaccess<\/code> file from the transfer. Match the new host’s PHP version to what your old host was running, or regenerate .htaccess<\/code> from Settings \u2192 Permalinks inside