BugWP logo BugWP
Back to Community
Home / Community / Plugin → All-in-one wp migration and backup

Troubleshooting All-in-One WP Migration: Common Import Stalls and How to Fix Them

31 threads Sep 7, 2025 Plugin → All-in-one wp migration and backup

Content

Many users of the All-in-One WP Migration and Backup plugin encounter a frustrating issue: the import process gets stuck at a certain percentage. This problem can manifest at various points, such as 0%, 2%, 74%, 86%, 99%, or even 100%. Based on community reports and common resolutions, this guide outlines the most frequent causes and their solutions.

Why Does the Import Get Stuck?

The import process is complex and depends heavily on your server's configuration and resources. A stall typically occurs when the plugin encounters a server-imposed limit it cannot bypass. It is rarely a permanent failure of the plugin itself but rather a sign that your hosting environment needs adjustment.

Common Causes and Solutions

1. Server Upload Limits (The Most Common Cause)

If the import stalls during the file upload phase (often between 0% and 100%), the most likely culprit is a server configuration limit. The plugin is trying to upload a file larger than what your PHP settings allow.

  • Solution: You must increase the following PHP settings in your `php.ini` file or via your hosting control panel. The values must be larger than your backup file.
    • upload_max_filesize
    • post_max_size
    • max_execution_time
    • max_input_time
    • memory_limit
  • Many hosting providers can assist you in making these changes. If you are unsure how to proceed, contacting their support is the recommended first step.

2. Server Processing Limits During Restoration

If the progress bar completes the upload (reaches 100%) but then hangs during the restoration phase (e.g., "Done preparing options" or "Updating plugins"), the server is timing out while trying to unpack the file and restore the database.

  • Solution: Similar to the upload issue, this requires increasing max_execution_time and memory_limit. The most effective way to diagnose this is to check your server's error logs. Your hosting provider can provide these logs, which will explicitly state which resource limit was exceeded.

3. Hosting Provider Restrictions

Some hosting providers implement strict firewalls, security software, or resource throttling that can interfere with the import process. This can result in errors like "404 at 0%" or immediate failure.

  • Solution: If you have confirmed your PHP settings are correct and the problem persists, the issue may be with your host. Community reports indicate that contacting the hosting provider is essential. In some cases, if the host is unable or unwilling to adjust their settings to accommodate the plugin's requirements, finding a more compatible hosting provider may be the only solution.

4. Browser or Network Issues

Less commonly, the problem can stem from the browser or a network intermediary like Cloudflare.

  • Solution: Try using an incognito/private browser window to rule out extensions causing conflicts. If you use Cloudflare, try temporarily pausing it or adjusting settings to disable caching for the import process, as it can sometimes block the necessary file upload requests.

Important Final Steps

  • Be Patient: For very large sites, the process can take a long time. One user reported success after waiting "many hours" for an import stuck at 2%.
  • Don't Navigate Away: The plugin may show 100% for an extended period while it finalizes the database restoration. Avoid closing the browser tab until you see a complete success message.
  • Check the Site: If the import seems stuck, try opening your website in a new browser tab. Often, you may find an error message there (e.g., a plugin conflict) that you can resolve, which will allow the import to complete.

By methodically working through these common causes, most import stall issues can be resolved. The process almost always involves collaborating with your hosting provider to ensure the server environment is properly configured for the task.

Related Support Threads Support