An incompatible restore package causes this. For example, you can restore a single-site package to a multisite server or vice versa, or you can restore a multisite package intended for another sub-site blog ID.

To fix this issue, make sure that:

  • If you want to migrate to a WordPress single-site, create a single-site export and restore that single-site package to any WordPress single-site only. For example, make sure this is checked during export:

Then, restore this package ONLY to the single site.

  • If you want to migrate to a WordPress multisite subsite with blog ID (e.g., 7), create a multisite package targeting blog ID 7. Restore that multisite package to only the subsite blog ID 7. For example, you need to check export to multisite format and provide seven as the blog ID, e.g.

Then, this package will be restored only to the multisite sub-site with blog ID 7.

It does not matter whether you create these packages at a single site or a multisite. The only important thing is that you make the correct package for your target destination (by providing the correct export type) (single site package for single site destination or multisite package for multisite destination)

Last updated: August 27, 2025

Was this article helpful?
YesNo