Scope: Prime Mover Free / Pro version
Prime Mover has its own naming conventions for the packages. By default, the file name contains an alias of the site title, date and time the package was created. For example: mystore_06-29-2019_0443pm_export_package.wprime
It belongs to My Store website created on 4:43pm June 29, 2019. However, it would be a bit tricky to identify if the package is for single-site or multisite.
Identify if package is single-site or multisite
- Upload the package to your Prime Mover backup/export directory.
- Login to WordPress admin or network admin (in case of multisite)
- Go to Prime Mover -> Packages.
- Click Refresh packages button.
- You should be able to see the package listed. Otherwise please check if you have upload the package to the correct path or if it is not corrupted.
- This is how it looks like:
- Take a look under “Package type”. If it is “single-site” , the package is for a single site installation. Otherwise, it will show “multisite” if it is for multisite.
- Any single-site package can only be restored to any single-site environment. It is because a Prime Mover package is BOTH a backup or migration package. As long as the environment is compatible, can be used both.
- A multisite subsite package can only be restored to any multisite subsite as long as the blog ID matches. In multisite, a site is identified in terms of blog ID. A multisite package of blog ID 7 can be restored to any multisite subsite as long as the blog ID is 7 also.
- If you restore a single-site package to a multisite, Prime Mover will block it and shows error.
- If you restore a multisite package to a single site, it will also be block and shows error.
- If you restore a multisite subsite package with blog ID of 8 (for example) to a different multisite subsite of blog ID of 9 (not matched). It will be block and shows error.
Migration Scenarios and Required Package Type
- If you backup a single-site, you will need to create a single-site package so that you can restore it.
- If you migrate a single site to another single site installation, you will need to a single site package also to migrate it.
- If you migrate a single-site to multisite, you will need to create multisite package in your source site single-site installation and provide the target blog ID. Make sure that you know the blog ID of the subsite in advance. In this case the subsite should exist first.
- If you backup a specific multisite subsite, you will need to export as subsite backup so that you can restore it (you don’t need to provide blog ID, Prime Mover assumes you are exporting the same site if you choose this setting).
- If you migrate a multisite subsite to another multisite subsite, you will need to create a multisite package and provide the target blog ID.
- If you migrate multisite to single-site, you will need to create single-site package in your source site multisite installation.
That’s it folks.