How to Fix All-in-One WP Migration when Stuck at 100%?
If you are seeking to solve the error of All-in-One wp migration stuck at 100%, you are in the right place.
It’s a very common problem the import might be stuck at 0% or 100% or any other number with that plugin. I have faced the issue and searched about it. Here is an overall summary to fix the issue.
In that post, I am showing you two ways to solve the problem. Let’s start.
“All-in-One WP Migration” plugin has 3 options:
First Way: Uses of “import”
All-in-One WP Migration allows you to upload up to 512 MB for free edition. If your file is less than 512 MB and the upload stucks at 100% or any other number, please follow the steps:
Step 1: Check PHP configuration in your hosting’s Cpanel if “UPLOAD_MAX_FILESIZE” and “POST_MAX_SIZE” are set greater than your file’s size or 512 MB. To get more information you might contact your hosting company.
Step 2: Now you need to install a little bit older version of the All-in-One WP Migration plugin. You can download V7.5 from here.
Step 3: Go to WordPress Dashboard > Plugins > Add New > Upload Plugin > Choose File > Selected All-in-One WP Migration File Extension that you just download > Install Now.
Step 4: After installation is finished, activate the plugin and go to All-in-One WP Migration again and import your .wpress file. Now the problem should be fixed.
This is the first way to fix All-in-One WP migration Stuck at 100%.
Second Way: Use of “backups” instead of “import”
Step 1: First of all, export your .wpress file locally using the “Export” option
Step 2: Login to FTP using FileZilla or any other File Transfer Protocol Software to access the hosting files of your live server.
Step 3: Go to the “backup” directory of the All-in-One WP Migration Plugin; wp-content/ai1wm-backups/ and upload your .wpress file
Step 4: Now you need to restore it. Go to your WordPress Dashboard > All-in-One WP Migration > Backups, and you will find your .wpress file which is available there. Click on the “Restore” option by following the below screenshot:
Step 5: After some time, you will get the below popup. Click on “Proceed” to continue:
Step 6: After a few minutes later, everything is done!
Note: Please make sure you are using an older version of the All-in-One WP Migration plugin. Version 7.5 has worked for me. Unfortunately, if it will not work for you please try to use another older version of the plugin.
Using the older version from github worked perfectly. THANK YOU!
Worked for me — use version 6.7 from GitHub
THiS DOES NOT WORK ANY MORE
Restore for download is a chargeable service!
Its not working. Restore option available only for Paid version. Try Migrate Guru it works so well with so much ease.
How can I do this? Can you link me a tutorial please? Many thanks
This article was helpful to me
Please notify me on your new post
Thank you so much, finally I was able to upload it.
Downloaded and installed the github verion “All-In-One-WP-Migration-With-Import” but it reseted the website, and I lost my data.
and if I already exported my site to a file and left the hosting to another one can I do something to make it work? the import stucks on 21.56%
That’s right. The older 6.7 version works perfectly. You can find it in GitHub here: https://github.com/d0n601/All-In-One-WP-Migration-With-Import
Works for me today, too
Works for me, in 2022. Thanks!
It works fine till Step 5. Post that it says: Restore” functionality is available in a paid extension.
You could also download the backup and then use “Import from file”.
Tried using the older version of it to see if it works, still same.
A solution to this would be appreciated. Thanks
The one linked to is not 6.7. Search Google for it. I found one at GitHub and it works great.
Non même avec la V6.7, j’ai le même message qu’herbert.
What are you referring to when you say 6.7? Is that the version of PHP? The version of the plugin? Can you be more specific please?
They are refering to an older version of the plugin -> V6.7, I found it somewhere on the web, if you can’t find it let me know
Having the same problem – you should have specified at the beginning of the article that a paid version was required