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

Troubleshooting All-in-One WP Migration: Fixing Stuck Backups and Restores

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

Content

Experiencing a backup or restore process that gets stuck is one of the most common and frustrating issues users report with the All-in-One WP Migration and Backup plugin. The process might freeze at 0%, 85%, 99%, or any point in between. Based on community reports and solutions, this guide outlines the most effective troubleshooting steps to resolve these hangs.

Why Do Backups and Restores Get Stuck?

The process typically stalls due to server resource limitations, configuration conflicts, or issues within the WordPress environment itself. The plugin is performing intensive file and database operations, and if the server cannot complete these operations within its set constraints, the process will fail to finish.

Common Solutions to Try

1. Adjust Server PHP Configuration

This is the most frequent fix. The import/export process requires significant resources. You need to increase the following values in your php.ini file on your server or hosting control panel (e.g., cPanel):

  • max_execution_time: Set to 7200 (2 hours) or higher.
  • memory_limit: Set to 1024M (1GB) or higher.
  • post_max_size & upload_max_filesize: Must be larger than your backup file.

After making these changes, remember to restart your web server (e.g., Apache, Nginx) for them to take effect.

2. Check for Plugin or Theme Conflicts

Other plugins, especially caching plugins like W3 Total Cache, can create massive files that bloat the backup size and cause timeouts. Before running a backup or restore, try these steps:

  • Switch to a default WordPress theme (e.g., Twenty Twenty-Four).
  • Deactivate all other plugins except All-in-One WP Migration.
  • If the process completes successfully, reactivate your plugins and theme one-by-one to identify the culprit.

3. Free Up Server Disk Space

The restoration process requires free space often double the size of your backup file. If your server runs out of disk space, the process will fail. Check your available disk space in your hosting control panel and remove any unnecessary files.

4. Enable Debugging to Find the Root Cause

If your site shows a critical error after a failed restore, enabling WordPress debugging can reveal the specific problem. Add these lines to your wp-config.php file:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true ); // Logs errors to wp-content/debug.log
define( 'WP_DEBUG_DISPLAY', false ); // Hides errors from site visitors

After reproducing the error, check the wp-content/debug.log file for clues. Also, ask your hosting provider for your server's PHP error logs, as they often contain more detailed information about timeouts or memory exhaustion.

5. Verify the Backup File Integrity

A corrupted backup file will always fail to restore. You can verify its contents using a free tool like Traktor. This web application allows you to upload your .wpress file and check that it contains a valid database and all your site files.

6. Consider a Manual Restoration

If all automated methods fail, a manual restore is a reliable last resort. You can use a tool like Wpress-Extractor to unpack your .wpress file. Once extracted, you can manually upload the files via FTP and import the SQL database using phpMyAdmin, following the standard WordPress moving guide.

When to Seek Further Help

If you are using a premium extension (e.g., Unlimited Extension, Multisite Extension), note that support for those products is handled directly by the 'All-in-One WP Migration and Backup' team and cannot be addressed on independent forums. For persistent issues on the free version, your hosting provider's support team can be a valuable resource, as they can confirm your server's configuration and examine its logs for specific errors.

Related Support Threads Support