Codexonics

Hi John,
Thanks for using Prime Mover FREE version in your projects! I see that you have issues moving a subsite in a slow server to a single site install. I think what you are going to do is possible. Below are some tips and guidance to get the most of your server when migrating a site with Prime Mover:

• Always use the latest version for both export and restore. The latest version is much faster and more stable than the previous versions. Currently the latest version is Prime Mover 1.4.7.
• If the server is slow – you can try migrating the site by parts. This is used by many our clients having issues on a very slow server. In this case – you export only the database using Prime Mover. And then you move all assets (e.g. media directories) manually via SFTP. This way you are putting less stress on a slow server.
• Also double check that the site to be exported (Blog 1) is really a multisite subsite. It happens before with some of our clients that the site is listed on Network admin sites however the site is actually installed as a single site on the same server. This explains the differences in the strange results. To find out if this is the case – login to the site itself (where you want to migrate) – go to Tools -> Site Health -> Click “Info” and then expand “WordPress” section. There is a question “Is this a multisite?” – make sure it’s “yes”. Otherwise you need to install Prime Mover on that single site and then generate the export within Tools -> Migration Tools (if it’s a single site).
• There are some Prime Mover constants that you can use to help get through with a slow server. You can try the following constants in your multisite wp-config.php

define('PRIME_MOVER_RETRY_TIMEOUT_SECONDS', 10);
define('PRIME_MOVER_PHPDUMP_BATCHSIZE', 100);

PRIME_MOVER_RETRY_TIMEOUT_SECONDS has a default of 15 seconds. However some servers might use a very low server timeout of 30 seconds – setting this to around 10 seconds might help with the timeout issue.

PRIME_MOVER_PHPDUMP_BATCHSIZE – has a default of 5000. This means the export dB process will fetch 5000 items from the database on a single query. This might seem too much for very slow servers. So setting this to a very conservative value like 100 might help with any database timeout issue.

I suggest to play around with these constants to see which helps with the export process.

• One last option does is to setup a multisite on your local (where it’s fast) and then dump the entire MySQL database (using either command line or any tools provided by your web host). And then copy all files from your remote site to local (one to one correspondence). You can then restore the database manually in your local. What you have now is a local multisite environment – a faster clone of your remote hosting. You can then use Prime Mover to extract your shop into a single site install so you can move it to any place you like.

==========================================

I think this is all we could help regarding this one. If you still need technical assistance – please contact us here and give us the details.

If our advice helps and resolves the issue – please mark this ticket as resolved. Thanks and good luck with your projects 🙂

Thanks Sdvizac for giving us 5-stars and for sharing your nice experience in using the plugin. Thanks also for sharing this to the community 🙂

Great thanks for the update..

Of course, if you migrate luxurypropertyadviser.com to luxurypropertyportugal.pt. Ideally luxurypropertyportugal.pt should look the same with luxurypropertyadviser.com. I did migrate the package to my local yesterday(the one in the screenshot). Indeed, that looks the same as your source site (luxurypropertyadviser.com).

However luxurypropertyportugal.pt is returning 404 (except homepage). I think this is a problem with your luxurypropertyportugal.pt server.

Did you manage to contact your host regarding this? Those pages should not return 404, I think there is some configuration issue in your server. This is server side, we cannot access to fix this. Thanks.

Thanks again. We manage to restore the package in our local server. However this page (/projects/propertysearch/) is rendered correctly (no 404). Your package is correct and it renders the site correctly on our end. We don’t see any 404 errors.

For example, see this screenshot here. This leads us to think that this is an issue with your server settings. This could be caused by different things – usually server related.

Can you please login to the restored site and go to Tools – Site Health – Click “Info” and then click the button “Copy site info to clipboard”. Paste this data to a text editor and save it.

Then go to Prime Mover – Contact Us and please send us this data either via text or link to download it. We will diagnose this data to see what could be wrong with your server and what we could fix.

In addition, it seems your server is nginx, can you please try this solution or this one with your web host to see if your site 404 issues would be resolved? If you don’t know how to change that – please consult your web hosting company support.

• This reply was modified 4 years, 5 months ago by Codexonics. Reason: Added link to pretty permalinks documentation

Yes the file that is exported from the old site. It’s the package with .wprime file extension. This is the package that you have migrated to this new site. We will try to debug this package to see if we are able to reproduce the 404 errors. Please upload that package to Gdrive and share the link via here.

Our support timezone is GMT + 8 (Manila time) so we will try to diagnose this first thing in our morning. Thanks again!

Hi Tectron,
Thanks for using Prime Mover! Can you please try re-saving permalinks by doing the following?

• Login to your site admin
• Go to Settings -> Permalinks
• Don’t change any settings, simply scroll down below and then click “Save changes”
• Check if you are using any caching plugin and purge all cache.
• Check if your host is using any caching features and purge it also
• Clear browser cache

Usually, this resolves most of the common 404 issues found after migration. If you are still having the issue – please contact us here and provide us the link to download your WPRIME package (you can upload this to Google drive – this is the package that you have used to migrate the site)

Once we have this package – we will use this to reproduce the issue and see if its related to the package itself or your server. Thanks!