Scope: Prime Mover Free / Pro version

Background

Prime Mover has its own naming conventions for the packages. By default, the zip 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.zip

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

It is really easy to identify if the zip package is for multisite or single-site:

  • Double click the zip without extracting it.
  • Double click inside the folder until you see a file called blogid.txt
  • Double click to open this text file.
  • The content of this file is the target ID of the site. It should be an integer.
  • If the blog ID is 1, then the package is a single-site package.
  • If the blog ID is greater than 1, then the package is for a multisite.

Compatibility

  • A single-site package can only be restored to a single-site environment.
  • A multisite package can only be restored to a multisite.
  • 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, it will also be block and shows error.

Creating single-site or multisite package

  • By default, single-site installation will produce single-site packages.
  • To create multisite packages in WordPress single-site installation, user needs to check “Export to multisite format” and then provide blog ID.
  • By default, multisite installation will produce multisite packages.
  • To create single-site packages in WordPress multisite installation, user needs to check “Export to single-site format“.

Migration Scenarios and Required Package Type

  • If you migrate or backup single-site to single-site, you will need to create single-site package. (default)
  • If you migrate or backup single-site to multisite, you will need to create multisite package in a single-site installation.
  • If you migrate or backup multisite to multisite, you will need to create multisite package (default)
  • If you migrate or backup multisite to single-site, you will need to create single-site package in multisite installation.

That’s it folks.

Was this article helpful?
YesNo