Dividing a WordPress multi site network into a single WordPress site is very difficult and completely crude So far! Shipper can easily move websites from the WordPress multi site network to a single WordPress installation hosted in its own domain. Running a multi site network has many advantages and benefits. However, you may want to import sites from multiple site networks and set them up as a single WordPress site in your domain. In this post, you will see: Why split sites on a multi site network? How to migrate a WordPress multi site sub site to a single WordPress installation? Why split sub sites in a multi site network? Here are a few reasons to import a site from a multi site network and set it up as a single word press installation: The
The site may go beyond the network and need its own space or ID. I want to install plug-ins, themes, or third-party applications that may require more site control and cannot be added to multiple sites or their own servers. The performance of the site is not as good as expected. Instead, we want to improve the performance. Online search allows you to find multiple articles and tutorials to demonstrate to multi site administrators how to migrate a child site to a single site. They usually include several steps, such as rough, creating backups, importing XML files, renaming database tables, changing searches through wp-cli or plug-ins, and so on. The
If you want to move a single word press site to a multi site network, this may work well. However, in a multi site environment, it is difficult to separate sub sites and migrate the entire site to the opposite direction of a single word press installation hosted in your domain Is there a simpler and easier way to automate this process? All you need to do is click the button once or twice. Sure! Word press calls it a \
Let’s take a step-by-step look at the migration process and show you how easy it is for shipper to migrate Initial setup – it is easy to migrate the site to the pre migration checklist shipper. Shippers work with all hosts. Set up the destination site and ensure that the shipper plug-in is installed on the source site (i.e. multi site installation) and the destination site. Note: you do not need to back up the source site. Our migration method is 100% secure for the source site (i.e. multi site installation). However, it is recommended that you perform a full backup of the target site to prevent problems when the system overwrites files, folders, and databases on the target site. If you are a wpmu dev member, you can use snapshot pro to automatically back up the entire site to secure cloud storage. If necessary, you can click once to restore the site. This tutorial uses cPanel and softaculous to set up a demo multi site network with three subdirectories on a dedicated server. The
Male WordPress multi site demo website. Suppose you want to detach site 2 from a multi site environment and migrate the entire site to a single word press installation in your domain. The demo site includes: Male this is word press to be split on a multi site network
Sub site presentation. Demo site 2 includes posts, pages, comments, categories, labels, plug-ins, themes, media, etc. All of these will be migrated to a single word press installation. Migrate all content contained in all content, media, plug-ins, themes and other subsites. Here is our new single word press installation. The
Male install our new word press – this is the target site. Here is also our new WordPress single site dashboard. Male new word press installation dashboard. You are now ready to begin the migration process. Use shipper to migrate WordPress multi site sub sites to a single WordPress installation. By using shipper’s multi site migration to a single site function, you can use the following methods to migrate sub sites from a multi site network to a single site installation: The
Package migration sender dashboard – package migration. Using this method, the web site is packaged with the installer into a file, so you can use SFTP to the site and send it to the new server. Package migration allows you to create a package across the network or sub sites. If you create a child site as a package and then install it on the server, install it as a single site. API migration malesender dashboard – API migration. This method provides one click automatic export \/ import through secure inter server communication. The
API migration allows you to export and import child sites from the network to a single site. For detailed steps on how to use the above method to migrate a site, please refer to the shipper’s plug-in documentation. Time to migrate the sub site… Now that all the preparation steps have been completed, let’s migrate the sub site to the new single WordPress installation. According to the previous pre migration checklist, you must connect the source and target sites to the hub. Please ensure that both the source and target websites are connected to the hub. In addition, shippers must already be installed at both sites. The
In the WordPress multisite installation, navigate to the shipper menu. ‹ WordPress multisite – distribution enterprise menu. method Before migrating packages, let’s take a look at how to migrate packages. You can select this method on the dashboard of the plug-in, or navigate to sender > package migration, and then click the create package button. Move subsites using package migration. On the create package screen, specify a name for the package, then select a child site as the package type as a single site, and then select the child site to migrate from the select child site drop-down menu. The
In this example, select site 2 as the child site to be migrated. Select a subsite from the drop-down menu. Select the child site to be migrated, then select whether to use password protection package, and then click the Continue button. If you do not want to use filters to exclude specific files, folders, or database tables, click the package build button in the next schema window. You can exclude files, folders, or database files from the package, or you can export the entire child site. The shipper will perform a comprehensive \
In the process of waiting for the construction of the male package, please join the one eyed captain to win the exam competition without blinking an eye. When the software package is ready, both the package archive file and the installer file to the hard disk. The migration package has arrived! Second, use an FTP client (such as FileZilla)
Upload all the package archive files and setup files to the root directory of the site server via FTP (for example, a single word press installation). Upload archive files and installation program files to a single WP installation root directory. Note: FTP login details must be obtained from the host. If the site is hosted with wpmu dev, you can select the target site and click the hosting > sftp\/ssh tab to obtain SFTP login details from the hub. Male hub gets SFTP login details. Upload the package archive and setup files to the root directory of a single word press installation, and then in the browser https:\/\/yourdomain.com\/installer.php Navigate to and follow the instructions of the Migration Wizard to complete the migration process. Follow the wizard to complete the migration. You can create a new database on a single target site or overwrite an existing word press installation. If you choose to overwrite the target site, it is recommended that you enable the get database credentials from profile option. Because there is a target site, WP config. Automatically obtain database credentials from PHP files. Select the option, and then click the button to test the connection and distribute the migration. Create a new database or overwrite an existing database on the target site. The Migration Wizard will automatically run the deployment and installation process and ask to view and update the details of the new site. The last step… After the process is completed, the system will prompt the user to log in to the newly migrated website to confirm that everything is normal. Log in with the details of the source site. If everything is OK, run the cleanup script to delete the migration files from the server. All completed! Now is the time to organize and enjoy the new website! Now you must copy all the items from the source multi site sub site to the new single WordPress site. Newly migrated to a site in a single word press installation, all items in the original site are copied. Now let’s look at how to use the package migration method to migrate a child site to a single site. method You can select an API method on the dashboard of the API migration plug-in, or navigate to shippers >api migration. This method allows you to export a site to another server or import another site into a working site. Male API migration can export and import websites. This guide exports a child site of a multi site installation to a previously set up single word press installation. Click the Export button to start the process (if on the dashboard screen of the plug-in, click export > start migration). Select a child site as a migration type to a single site, select the child site to migrate from the child site drop-down menu, and then click next to continue. Male select the subsite to export. After confirming the password, shipper will perform some operations in the background and ask you to select the target site. Select the site from the drop-down menu where you want to export the child site, and then click the blue arrow button to continue. Male select the destination website. When the file is ready, shipper displays the migration filter window. As mentioned earlier, you can exclude files, folders, or databases that you do not want to export. Use a filter to exclude items or skip this step to migrate the entire child site, and then click next. Use the migration filter window to exclude files, folders, or databases from migration. The shipper will perform extensive pre flight inspections and notify you if problems are detected. \
A problem displayed as indicates an error that does not allow the migration to complete successfully. The shipper must resolve these issues before proceeding with your export. If there is no red problem, you can ignore the yellow alarm and continue. The distribution enterprise will tell you whether there are problems to be solved before the website is migrated. A schema window appears asking you to select the destination database prefix. You can use the database prefix of the source site, the existing database prefix of the target site, or create a custom database prefix. Male select the destination database prefix. The shipper calculates the package size and estimates the time required for migration. Click Start migration to continue. Everything is ready for the distribution enterprise! Start moving the site from the shipper and send an email after all operations are completed. The migration is in progress. After the migration is completed successfully, you can log in to the target site, view the server, and view the exported content, files, folders, databases, etc. Your subsite was successfully migrated. Effie API Oh! Note: there is a problem using the API migration method (for example, if the sender stops during file export \/ import, or takes a long time, you can cancel the migration process, use the package migration method described above, or consult the support team. Expert help is required. If there is a problem, you can cancel the migration.) After the migration, migrate the checklist multi site sub site to a single WordPress site, and then take some time to review the new site to ensure that everything is successfully migrated. Confirm: bid farewell to the post, customize the post type and page media attachment plug-in subject comment settings (such as permer link) folders and files (server) WordPress database (server) rough migration, and change the WordPress website from a single site to a multi site, If you are migrating from multiple sites to a single site or from a single site to multiple sites, shipper will make the process easier. When migrating multi site sub sites to a single WP installation, there is no need to manually export or import files, migrate SQL databases, change WP prefixes, rename database tables, change search, etc. Shipper handles all this. Shippers work with all hosts. However, it is best to be hosted by wpmu dev’s managed word press hosting service, use a hub to manage the site, and access a dedicated team of 24×7 support experts for trouble free site migration. If you need to use the wpmu dev dashboard plug-in to help connect a site to a hub, review the documentation on how to add a site to a hub. If you need a step-by-step exercise of the complete multi site to single site migration process, please refer to the shipper plug-in documentation. Also, check out the roadmap for the upcoming New Shipper feature. Have you ever tried using shipper to migrate a child site of a multi site network to a single word press installation? In the comments below, use shipper to share ideas and experiences.
