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

Troubleshooting Common Issues After Using All-in-One WP Migration and Backup

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

Content

Migrating a WordPress site can be a complex process, and sometimes things don't go exactly as planned. Based on community reports, here are some of the most frequent issues users encounter after a migration or restore with the 'All-in-One WP Migration and Backup' plugin, along with steps you can take to resolve them.

1. White Screen of Death or Blank Pages

A blank white screen after a restore often indicates a PHP error that is being hidden. The first step is to enable debugging to see the underlying error message.

  • Access your website's files via FTP or your hosting provider's file manager.
  • Locate the wp-config.php file in your WordPress root directory.
  • Find the line that says define('WP_DEBUG', false); and change it to define('WP_DEBUG', true);.
  • Save the file and refresh your website. You should now see error messages that can point you toward the specific problem, which is often a theme or plugin conflict.

2. Seeing the Old (Cached) Site

This is one of the most common issues. You log in and see the new site, but logged-out visitors see the old one. This is almost always a caching issue.

  • Clear Browser Cache: Hard-refresh your browser (Ctrl+F5 or Cmd+Shift+R) or clear its entire cache.
  • Clear Server Cache: Contact your hosting provider and ask them to clear any server-level (object) cache, Varnish cache, or CDN cache.
  • Clear Plugin Cache: If you use a caching plugin like WP Rocket or W3 Total Cache, clear its cache from your WordPress dashboard.

3. 404 Errors or Broken Pages/Posts

If your homepage works but other pages return 404 errors, the problem is likely with your permalink structure.

  • Log in to your WordPress admin dashboard.
  • Navigate to Settings > Permalinks.
  • Simply click "Save Changes" without changing any settings. This action flushes the rewrite rules and regenerates the .htaccess file.
  • If this doesn't work, ensure your server has the mod_rewrite Apache module enabled (your hosting provider can confirm this).

4. Can't Access wp-admin Login Page

If you cannot reach your login page after a migration, a security plugin is often the culprit.

  • Use FTP or your host's file manager to navigate to /wp-content/plugins/.
  • Look for the folder of your security plugin (e.g., wordfence, sucuri, all-in-one-wp-security).
  • Rename the plugin's folder (e.g., add -disabled to the end). This will deactivate the plugin.
  • You should now be able to log in. You can then rename the folder back to its original name and reconfigure the plugin.

5. Page Builder Content is Missing (Elementor, Muffin Builder, etc.)

Sometimes the site structure is restored, but content from page builders appears blank. This can be a compatibility issue.

  • First, ensure you are using the latest version of the 'All-in-One WP Migration and Backup' plugin, as compatibility for popular builders is often improved in updates.
  • If the issue persists, it may be a conflict. Try temporarily switching to a default WordPress theme (like Twenty Twenty-Four) to see if the content reappears.

6. "The backup is corrupt" Error

If the plugin reports that your backup file is corrupt during an import, the file may have been interrupted during the export or upload process.

  • The most reliable solution is to create a new export file from the original source site and attempt the import again.

Important Precautions

To avoid data loss, always create a fresh, full backup of your destination site before importing a migration package. As noted in community discussions, an import completely replaces the existing site data, and there is no built-in way to revert to the pre-import state without a separate backup.

If these steps do not resolve your issue, enabling WP_DEBUG as described in the first section is the best way to get specific error messages that can be used to search for a more targeted solution.

Related Support Threads Support