Title: Database imports for multisite environments
Author: WordPress VIP Documentation
Published: August 31, 2023
Last modified: September 30, 2025

---

 1. [Databases](https://docs.wpvip.com/databases/)
 2. [Import database files](https://docs.wpvip.com/databases/import/)
 3. Database imports for multisite environments

#  Database imports for multisite environments

[Database structure for a WordPress multisite](https://docs.wpvip.com/multisite-database-structure/)
differs from the database structure of WordPress single site. In order to import
a database to a VIP WordPress multisite network, the database file for import must
be exported from a WordPress multisite.

A [VIP Local Development Environment](https://docs.wpvip.com/vip-local-development-environment/)
configured as a multisite can be a useful tool for testing the database import process.

**Note**

If the multisite environment is in an “[Unlaunched](https://docs.wpvip.com/launch-a-site/unlaunched/)”
state, all sites on the network will go into maintenance mode during a SQL import.
The “Launched” or “Unlaunched” state of an environment can be referenced in the 
VIP Dashboard or with [the VIP-CLI command `vip app`](https://docs.wpvip.com/vip-cli/commands/app/).

## Requirements

 * The database file for import must have been exported from a WordPress multisite.
    - If the origin site of the database is a [WordPress single site](https://docs.wpvip.com/wordpress-single-site/),
      the database will need to be converted to a multisite database prior to import.
    - A WordPress.org article provides helpful instructions for [migrating WordPress single sites into a multisite install](https://wordpress.org/support/article/migrating-multiple-blogs-into-wordpress-multisite/).
 * If importing the database for an entire multisite network, ensure that the export
   has all tables listed in [network-level tables shared by all sites](https://docs.wpvip.com/multisite-database-structure/).
 * If importing tables for a specific site, ensure the table prefixes match the 
   intended destination site ID (e.g. tables prefixed `wp_3_` will be imported to
   site ID 3). Table prefix values will be visible in the confirmation output of
   the import command.
 * If importing a selection of tables for one or more sites, the database export
   should include _only_ the tables for those sites.
 * If the SQL file being imported includes tables for the main site (ID 1), and 
   the domain value in the file for site ID 1 does not match a [domain that has been mapped](https://docs.wpvip.com/map-a-domain/)
   to the environment for import, the import will fail. To prevent this issue, [update domain values either before or during the import](https://docs.wpvip.com/databases/import/updating-values/),
   and update the domain value for site ID 1 with a domain that is mapped to that
   environment.

![](https://docs.wpvip.com/wp-content/uploads/sites/2/2021/10/import-output.png)

Screenshot of returned messages and warnings when running a database import to a
WordPress multisite

Last updated: September 30, 2025