Codexonics

Thank you for using Prime Mover in your projects and for rating us 5 stars! We are glad to know the plugin helps a lot in making demo sites. Cheers 🙂

Hi Marv,

Thank you for using Prime Mover! Based on your question – you want to migrate a multisite subsite (blog ID: 30) to a standalone/single-site. Yes this is possible with Prime Mover.
You simply need to:

• Login as network administrator in your multisite.
• Make sure latest version of Prime Mover is installed.
• Go to Sites -> All Sites and look for the subsite with blog ID 30.
• Click the “EXPORT blog ID : 30” button.
• Under “Export type(required)” – select “Export to single-site format“. This will create as single-site/standalone WPRIME package.
• Click “Export now” button and wait until the package creation is completed.
• You can then restore this package to your new standalone site by following this procedure.

This should work for you. For details – please refer to the plugin complete documentation.

Hi Makis,

Thank you for sharing your experience with our support and for using Prime Mover plugin. Cheers!

Hi,

Yes we apologize for this lack of clarity. We do mention that migrating/backup main site is one of our PRO features. It’s also listed under “PRO features” in plugin information page.

And yes – we agree to revise this wording to make it clear. This is now updated on the plugin page. Thank you so much for your clarification.

Cheers,
Emerson

Hello Charlene,

Thank you for using Prime Mover! Sorry to hear you have an encoding issue. We would like to reproduce this issue in our end. Can you please provide us the following?

• The link to download the WPRIME package. You can upload this package to Google Drive/DropBox and share us the link to download.
• Login to your source site (where the package is created) and go to Prime Mover -> Advanced -> Export site info -> and click “Export site info” button. This will download the site info log of your source site. Rename the log file to ‘sourcesite.log’ – so that we will know it’s from the source site.
• Send us some screenshots as to how these characters would look like (expected result) at the source site. So we will know the equivalent correct result of this screenshot: https://i.imgur.com/xtaT9O3.png
• Login to your target site (where you want the package to be restored) and go to Prime Mover -> Advanced -> Export site info -> and click “Export site info” button. This will download the site info log of your source site. Rename the log file to ‘targetsite.log’ – so that we will know it’s from the target site.
• [optional] If you can provide a correct MySQLdump .sql file with the correctly encoded Turkish characters (not generated by Prime Mover but using another tool in your source site that is correct) – please include so we will know how these characters are encoded at the source site

Please send us all the requested info in our contact form. Once we have all the info – please give us time to analyze and debug the issue. Our support timezone is GMT + 8.

Thanks again!

Hi Abby,

Thanks for the log. It’s fine, regarding the error – it stops on the plugin archiving process with the error Failed to write to archive stream. Prime Mover can longer write or archive any files.

First, please try updating Prime Mover plugin to the latest beta version since it includes some recent fixes to see if it’s handled. You can download it here. And then try re-creating the export to see if works.

Now, if the issue still reproducible – this means that either:

• Your hosting disk space is full – please double check your hosting account and ensure you have enough disk space to create the package. Prime Mover can longer archive any files since your free disk space is insufficient.
• Some of your site files are not writable or unreadable. This either due to a hosting security policy. In this case – you can still try migrating the site by parts.

Migrating the site by parts should work for you since you only need to move the database to your target site. Prime Mover does the search/replace automatically. All you need to do is to manually move your plugins/themes and media files to your target site. You can do this either by SFTP or SCP.

If your hosting disk space is fully sufficient and you want a more detailed troubleshooting on these problematic files – you can try adding this to your source site wp-config.php:

define('PRIME_MOVER_ENABLE_FILE_LOG', true);

This will actually log each file that will be added to the WPRIME archive during export. And then it stops on the problem file. Using this info – you can either deactivate that problem plugin (if its from a third party plugin of your site) and then re-create export again to see if the error is gone.

If you want to share these updated logs to us – please send it here and do not post again publicly.

If any of the above solution works for you – please mark this ticket as resolved. Thanks again!

Hello, thanks for using Prime Mover! Can you please send the link to download the runtime error log and other migration logs (you can zip it) to our contact form?

We would like to know the details of these runtime errors. We will then check if a workaround exists or if it is fixed in our latest beta version. Thanks again!