Hello Dave, thank you for using the Prime Mover plugin! I’m sorry to hear you have errors on import. We’ve checked that line in the code, and it pertains to querying the database to retrieve the rows for the search-and-replace process. By default, it retrieves 25,000 rows, which would work in most hosting situations.
In your case – you have a huge amount of data in these rows, so it can hit the memory limit. To resolve this – you need to lower the query result in rows as much as possible. Prime Mover has a setting for this. For details – please refer to the detailed solution:
- Reset your target to a fresh WordPress install.
- Install and activate the latest Prime Mover plugin (currently version 2.0.4).
- Once fully activated – go to Prime Mover -> Runtime settings -> Search-replace batch size.
- Currently, this is set to 25,000. Change it to something very low that would fit your server memory. For example, change it from 25000 to 1000 or even 500. This allows Prime Mover to fetch 1000 or 500 rows at a time. Hopefully, this should fit your server memory requirements.
- Save the setting.
- Try restoring the package the way you used to restore it. You should not hit the memory limit settings since you are now fetching a very small number of rows from the database at a time.
This should work – otherwise if you still have the same issue. Please send us a copy of your WPRIME package by uploading it to Google Drive and send us the link to download it by using our developer contact form here.
Thanks again, and please let me know if you still need technical assistance. If the proposed solution works, please mark this ticket as resolved.
