WordPress Multisite has many benefits. It lets you create as many websites as you need with just one WordPress installation. It allows for connections between those sites, sharing of data and users, and it gives you a way to make money from your WordPress installation, by selling sites on your network to users.
But sometimes, a single-site WordPress installation might be the best option for your site. Maybe you don’t want to share a database of users with other sites. Maybe your site has become much larger than the other sites in the network and you want to separate it out. Or maybe you want a different hosting environment for that site, or you’re moving out of someone else’s multisite network to your own single installation.
Another possibility is that you’ve been running a small Multisite network but now want to remove all of the sites except one and revert that to a single site installation.
The good news is that you can migrate a sub-site from WordPress Multisite to a single site, or convert a network to a single site. The not so good news is that it’s more complicated than simply migrating a single site to another WordPress installation or another domain.
In this post, I’ll show you how to migrate your WordPress site out of WordPress Multisite to a single site, without losing any data.
Why Migrating from WordPress Multisite to a Single Site Is More Complex Than Migrating a Single Site
Let’s take a look at why migrating a site out of a Multisite network is more complicated than migrating between single-site installations.
The reason for this is the way WordPress Multisite stores your data and files, and the fact that some of the data is stored along with data for the other sites in the network.
A Multisite network stores data about each site as follows:
Upload files are stored separately for each site, in WordPress-content/uploads/sites/xx, where xx is the ID of the individual site.
Most data, including posts, post metadata, taxonomies, and more, is stored separately for each site in dedicated database tables that are created each time a new site is added to the network. These are given a prefix including the ID of the site, so wp_12_posts will be the posts table for site 12.
User data is stored in two tables for the entire network. Instead of becoming a user on one site, a user has an account on the network, which stores metadata about which sites they have access to. This means you can’t export the user database tables and migrate them to your new site: you’ll have to migrate users separately.
Theme and plugin files are stored once in the network, regardless of how many sites they’re activated on. This is one of the major benefits of Multisite because it means you only have to keep themes and plugins updated once. But when you’re migrating a site out of the network, it makes things more complicated.
As we go through the process of migrating from WordPress Multisite to a single site in this post, I’ll show you
This article was written by Rachel McCollin and originally published on Blog – Kinsta Managed WordPress Hosting.