Plugin how-tos · Guide
How to Fix All-in-One WP Migration Stuck Imports
Short answer
A stuck All-in-One WP Migration import is most often caused by low PHP limits, a host upload cap, or low disk space. Check Site Health first, raise upload_max_filesize, post_max_size, memory_limit, and max_execution_time, then retry the import. If the browser upload still fails, use WP-CLI restore or the paid Unlimited Extension to work around host limits.
Key takeaways
- The Import screen shows your host PHP upload cap, not a plugin cap, as of November 2026.
- ServMask says you need free disk space equal to 2.5 times your site size for a restore.
- Cloudflare Free and Pro plans cap a single upload at 100 MB, which can stop a large import.
- The plugin error log sits at wp-content/plugins/all-in-one-wp-migration/storage/error.log.
- After a successful import, clear caches and re-save permalinks under Settings > Permalinks.
- Keep the old host live for 7 to 14 days after a move, so you can roll back if needed.
Why does All-in-One WP Migration get stuck during import?
A stuck import usually means the server stopped the job, not that the plugin lost the file.
All-in-One WP Migration moves your database, media, themes, and plugins in one .wpress file. That single file can be large, so a small PHP limit can stop the job part way through.
The progress bar is browser-side, so it can freeze while the server is still working or after the server has already stopped the job.
The vendor page on WordPress.org says the plugin is used by over 60 million websites, as of November 2026. It also says the free plugin exports sites of any size, while your hosting company decides how large a file you can upload.
That split explains many stuck imports: the export works, then the import hits a host limit.
Common causes, in order, are low PHP limits, a host or CDN upload cap, low disk space, a plugin conflict, and a damaged .wpress file. Work through them in that order, and check the result after each change. A backup guide can help you keep a safe copy before you retry.
What should you check first when the progress bar stops?
Check whether the import already finished, then check disk space and Site Health before you change any setting.
Open your site in a new browser tab and look for the migrated content. ServMask says in its migration troubleshooting guide that a bar stuck near 100% may mean the import finished but the browser never got the final reply. If the content is there, do not start the import again.
Next, check free disk space in your hosting panel. ServMask says in its troubleshooting help page that you need enough space to store the backup file and rebuild the site, equal to 2.5 times your site size. A site of 2 GB needs about 5 GB free for the restore to run.
Then open “Tools > Site Health > Info > Server” in WordPress. Note upload_max_filesize, post_max_size, memory_limit, and max_execution_time.
Those four numbers tell you if the server can accept and process your file. If any value is far below your file size, that is your first fix.
How do you raise the PHP limits that stop an import?
Raise the PHP limits in .user.ini, php.ini, or .htaccess, then confirm the new values in Site Health before you retry.
ServMask gives these values in its upload limit guide: upload_max_filesize 512M, post_max_size 512M, memory_limit 256M, max_execution_time 300, and max_input_time 300.
Its migration troubleshooting guide gives a higher set for large imports: the same upload values, plus max_execution_time 600, max_input_time 600, and memory_limit 512M. Start with the first set, and use the higher set if the import still stops.
Use the file your host reads. For Apache, add php_value lines to .htaccess in your WordPress root.
For LiteSpeed or Nginx, or when .htaccess does not work, create or edit .user.ini in the same folder with plain values. If you have php.ini access, edit that file instead.
| Setting | What it controls | ServMask example value |
|---|---|---|
| upload_max_filesize | Largest single uploaded file | 512M |
| post_max_size | Largest whole form request | 512M |
| memory_limit | Memory one PHP script can use | 256M to 512M |
| max_execution_time | Seconds a script can run | 300 to 600 |
| max_input_time | Seconds PHP waits for input data | 300 to 600 |
Do not try to raise upload_max_filesize or post_max_size with @ini_set() in wp-config.php. ServMask says those two are PHP_INI_PERDIR settings, so PHP will not change them at run time. The lines look like a fix and do nothing.
PHP itself ships with small defaults. The PHP manual lists memory_limit at 128M and upload_max_filesize at 2M by default, as of November 2026.
It also says post_max_size must be larger than upload_max_filesize. Many shared hosts raise these defaults, but some do not, so check your own values.
If your host locks PHP settings, ask support to raise them. ServMask says some hosts override your edits at server level, and only the host can change a locked value. A hosting choice guide can help if your current plan cannot meet the limits your site needs.
Why does the import stop at 100%?
The bar at 100% means the browser finished sending the file, not that the server finished the restore.
ServMask links this case to its help page on uploads stuck at 100% from its upload limit guide. It says to wait 30 to 60 seconds after 100% and to raise max_execution_time above the upload time.
The server is still moving the file into place, so give it that minute before you close the tab or click Stop.
After the upload, the plugin still has to unpack files and restore the database. If max_execution_time or memory_limit runs out during that stage, the job stops and the bar stays still. That is why a 100% bar with no progress for several minutes points at the restore stage, not the upload stage.
Check the site in a new tab first, as above. Then check the error log for a fatal error during the database step.
If the log names memory, raise memory_limit to 512M and retry. If the log names time, raise max_execution_time to 600 and retry.
What if your file is larger than your host upload limit?
If the file is larger than the limit on the Import screen, raise the PHP limit, shrink the export, or use a method that skips the browser upload.
First, compare the file size with the number on the Import screen. ServMask says that number comes from WordPress function wp_max_upload_size(), which is the smaller of upload_max_filesize and post_max_size. Raise both values, not just one, or the smaller value still caps the upload.
Second, check the layers in front of PHP. ServMask says Nginx client_max_body_size, Apache LimitRequestBody, mod_security, and a CDN cap can block an upload that is under the PHP number.
Cloudflare docs list the maximum upload size as 100 MB for Free and Pro plans, 200 MB for Business, and up to 5 GB for Enterprise, as of November 2026. A file over 100 MB can fail on Cloudflare Free even when PHP allows 512 MB.
Third, shrink the export if you can. Export again without large media folders you can move by FTP, or split the work into smaller parts. Compare cPanel backups with plugin backups if you need a second route for the files.
Fourth, consider the paid route. ServMask says the Unlimited Extension costs $69 per year for up to 50 sites, as of November 2026, and uses chunked transfer so each request stays under host limits.
The free plugin has no hard-coded import cap in current versions, so the paid extension is a way around host limits, not a way around a plugin limit.
How do you fix a stuck import with WP-CLI?
Use WP-CLI restore when browser uploads keep timing out, because it skips browser and web server time limits.
ServMask says in its migration troubleshooting guide to run wp ai1wm restore backup.wpress from the command line. Replace backup.wpress with your own file name. The command runs on the server, so a slow browser connection cannot stop it.
You need the Unlimited Extension for WP-CLI commands. The plugin page on WordPress.org says WP-CLI commands are not in the free plugin, and running them without the extension only prints a notice. With the extension, wp ai1wm backup creates a backup and wp ai1wm restore restores one.
Steps for a WP-CLI restore
- Upload the .wpress file to the server by FTP or SFTP, in binary mode.
- Open SSH and move to your WordPress root folder.
- Run wp ai1wm restore backup.wpress with your real file name.
- Wait for the command to finish, and do not close the SSH session early.
- Open the site and the admin area in a browser to check the result.
If you do not have SSH access, ask your host if they can run the command for you. If they cannot, use the PHP limit fixes above and retry the browser import with a smaller file.
How do you check the error log and find the real cause?
Open the plugin error log first, then turn on WordPress debug logging if the log is empty.
ServMask says in its troubleshooting help page to look at wp-content/plugins/all-in-one-wp-migration/storage/error.log when an export or import has a problem. Open that file by FTP or in your hosting file manager. A memory error, a time error, or a database error there points straight at the fix.
ServMask also says the memory limit should be at least 256M, and larger sites may need more. If the log shows an allowed memory size error, raise memory_limit to 512M. If it shows a maximum execution time error, raise max_execution_time to 600.
If the log is empty, add debug logging to wp-config.php above the line that says stop editing. ServMask gives these lines in its migration troubleshooting guide: define WP_DEBUG as true, define WP_DEBUG_LOG as true, and define WP_DEBUG_DISPLAY as false. Then retry the import and read wp-content/debug.log.
Check the PHP versions on both sites as well. ServMask says the plugin works across old and new PHP versions, but your themes and plugins may not.
WordPress.org recommends PHP 8.3 or greater, with MySQL 8.4 or greater or MariaDB 10.11 or greater, and HTTPS support, as of November 2026. A source site on PHP 7.4 and a destination on PHP 8.3 can fail for theme or plugin code, not for the migration file.
How do you confirm the import worked after it finishes?
Check the home page, the admin area, media, links, and login before you point DNS at the new host or delete the old site.
Start with the front end. Open the home page, three inner pages, and three images.
If every page except the home page shows a 404, re-save permalinks under “Settings > Permalinks” and click Save Changes. The plugin page on WordPress.org lists that step for 404 errors after a move.
Next, log in with the source site admin account. The import overwrites users on the destination, so the old destination login may no longer work.
Use the source site credentials. If login fails, reset the password from the login screen.
Then check media and links. Open “Media > Library” and confirm thumbnails load. Click five posts and check that images and links point at the new domain.
The plugin page on WordPress.org says broken images often mean wp-content/uploads did not transfer fully, or file permissions are wrong. Directories should be 755 and files should be 644.
Clear all caches last, then re-save permalinks again. The plugin page on WordPress.org says to clear caches and re-save permalink settings after a restore. A host change guide can help you check redirects and search settings after the move.
What mistakes should you avoid?
Avoid closing the tab early, editing plugin files to raise the cap, and deleting the old site before you have checked the new one.
- Do not close the browser tab while the bar is moving, even at 100%. Wait at least 60 seconds, then check the site in a new tab.
- Do not edit the plugin constants file to raise the limit. ServMask says the old AI1WM_MAX_FILE_SIZE constant was removed years ago, and edits vanish on the next update.
- Do not import a damaged file twice. If the import reports a CRC mismatch, re-export from the source site and re-download the file in full. Compare file sizes on both ends.
- Do not keep the old host for only a day. The plugin page on WordPress.org says to lower DNS TTL to 300 seconds at least 48 hours before the move, and to keep the old host active for 7 to 14 days as a safety net.
- Do not skip the backup before you retry. Keep a copy of the .wpress file and a copy of the destination database, so a failed retry does not leave you with no working site.
- Do not leave debug logging on. Remove the WP_DEBUG lines or set them to false after you finish, so errors are not written to a public log file.
Frequently asked questions
How long should I wait before I call an import stuck?
Wait at least 60 seconds after the bar reaches 100%, because the server may still be moving the file. Then check the site in a new tab. If nothing has changed after 10 to 15 minutes on a small site, or after 30 minutes on a large site, stop and check the error log and Site Health.
Why does my import stop at 0%?
A stop at 0% usually means the upload never reached PHP. Check the file size against the limit on the Import screen, check for a firewall or security rule that blocks large uploads, and try a smaller file. If the limit is low, raise upload_max_filesize and post_max_size, or ask your host to raise them.
Can I import a .wpress file larger than 512 MB for free?
Yes, if your host allows it. The free plugin has no hard-coded import cap in current versions, and the limit you see comes from your host PHP settings and any CDN or firewall in front of PHP. Raise those limits, or shrink the export, and the free import can work. The paid extension is only needed when host limits cannot be changed.
What do I do if the import says the file is damaged?
Re-export the site from the source, then download the new file in full without stopping the download. Compare the file size on the source and on your computer. If they differ, the download was cut short. Transfer the file by FTP in binary mode, not ASCII mode, to avoid damage during transfer.
Will I lose my login after an import?
Your destination login may change, because the import overwrites users with the source site users. Log in with the source site admin username and password. If you cannot log in, use the password reset link on the login page, or ask your host to help you reset the admin password.
When should I ask my host for help?
Ask your host when PHP settings are locked, when disk space is full, when the error log names a server limit you cannot change, or when the import fails the same way after you raised the limits. Give them the file size, the Site Health values, and the last lines of the error log so they can act fast.
Sources
- All-in-One WP Migration and Backup WordPress.org
- Why All-in-One WP Migration Shows an Upload Limit (And How to Fix It) ServMask Blog
- 15 Common WordPress Migration Errors and How to Fix Them ServMask Blog
- Troubleshooting ServMask Helpdesk
- Requirements WordPress.org
- Default Cache Behavior Cloudflare Docs
- Description of core php.ini directives PHP.net
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
