![]() Migrate content using the Import/export plugin.Install the same plugins and themes as in your old site and activate them.Create the new single-site installation.If you have complex settings, and plugins like an ecommerce plugin, this method is not recommended as you’ll spend a lot of time manually copying all your settings.īut if your site is simple, with a small number of plugins, not much in the way of customization, and not many users, it might be the simplest way to proceed. No settings will be migrated apart from widget settings. ![]() The only users migrated will be users who’ve created content – you’ll have to migrate all other users manually.The benefits of this method are that it’s free and it doesn’t involve any tinkering with the database, so is fairly foolproof. The first option uses the free import/export plugin to migrate your content and another free plugin to migrate widget settings. Using Free Plugins to Migrate a Sub-site Out of a WordPress Multisite Network to a Single Site Let’s take a look at each of these methods in turn. Use a migration plugin to export all data and files.Use free export/import plugins to migrate data, and migrate files manually.So, assuming you haven’t been scared off by what you’ve learned about the process so far, let’s look at the different methods you have for doing this. How to Migrate a Sub-site from WordPress Multisite to a Single Site ✨This step-by-step guide will help you along the way ⬇️ Click to Tweet Take things back to the basics by switching from WordPress Multisite to a single-site installation. And I’ll refer to standalone sites in their own dedicated WordPress installation as ‘single sites’. I’ll use ‘base site’ to refer to the core site in a network, which is the one that was there before Multisite was activated. But when you’re migrating a site out of the network, it makes things more complicated.Īs we go through the process of migrating from WordPress Multisite to a single site in this post, I’ll show you how to deal with each part of the site separately so you can migrate it successfully.Ī note on terminology: in this post, I’ll refer to sites within a Multisite network as ‘sub-sites’. This is one of the major benefits of Multisite because it means you only have to keep themes and plugins updated once. Theme and plugin files are stored once in the network, regardless of how many sites they’re activated on. This means you can’t export the user database tables and migrate them to your new site: you’ll have to migrate users separately. 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. User data is stored in two tables for the entire network. ![]() These are given a prefix including the ID of the site, so wp_12_posts will be the posts table for site 12. 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. ![]() Upload files are stored separately for each site, in WordPress-content/uploads/sites/xx, where xx is the ID of the individual site. CompareĪ Multisite network stores data about each site as follows: See how Kinsta stacks up against the competition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |