To migrate subsites in WordPress multi-site to a single site, you need to perform the following steps in turn: 1. Use WordPress's own export tool to export articles, pages, etc.; 2. Export the table with the corresponding prefix from the database and rename it to a single-site format, while replacing the old domain name; 3. Manually migrate media files and repair paths; 4. Configure the themes, plug-ins and settings of the new site and conduct testing. The entire process requires attention to data cleaning, URL replacement and plug-in compatibility to ensure normal functions after migration.
Migrating a subsite in a WordPress multisite to a single site is actually a relatively common but operational care. Because the data structure of multi-site is slightly different from that of single-site, there may be problems with copying files or databases directly. The focus is on extracting the data of the target substation and rebuilding it correctly in the new environment.
Here are some key steps and precautions to help you complete the migration smoothly.
1. Export subsite content
WordPress's own "Export" tool (Tools > Export) can be used to export articles, pages, comments, custom fields and other content. While it can't export everything (like theme settings, plugin data, etc.), it's enough for basic content migration.
- Log in to the backend of the subsite you want to migrate
- Go to Tools > Export
- Select "All" or select a specific content type as needed
- Download the generated
.xml
file
This method is suitable for migrating basic content such as articles, pages, media libraries, etc. If your theme or plugin depends on a lot of settings, it may need to be handled manually.
2. Export and organize the database
Each subsite in a multi-site has its own prefix table (such as wp_2_posts
, wp_2_options
, etc.). To migrate this data to a single site environment, you need:
- Use phpMyAdmin or other database management tools
- Find the database table for the corresponding subsite (for example, start with
wp_2_
) - Export data from these tables
- Change the table name to a single site format (such as
wp_posts
,wp_options
)
It should be noted that it is best to clean up unnecessary data before importing, such as temporary options, logging, etc. Also, make sure to replace the old domain name information, otherwise the link will point to the original multi-site address.
You can use SQL replacement statements to update the URL:
UPDATE wp_options SET option_value = replace(option_value, 'http://oldsite.com', 'http://newsite.com') WHERE option_name = 'home' OR option_name = 'siteurl';
3. Migrate media files and other resources
When exporting XML, you can choose whether to include attachments, but sometimes it fails or misses. A safer way is:
- Copy files directly from
/wp-content/uploads/sites/2/
of the server - Paste in new single site
/wp-content/uploads/
path - Then update the GUID and file path through the "Media Library Repair Plugin" or SQL
This ensures that the pictures, videos and other resources can be displayed normally.
4. Set up a new site environment
After the migration is complete, don't forget to adjust some key settings for the new site:
- Check if the permalinks settings are consistent
- Replace the appropriate theme and restore the appearance settings
- Install the necessary plug-ins and import relevant configurations
- Test whether the front desk and background functions are normal
Some plug-ins will use different loading methods in multi-site environments, and may fail after migration to a single site. At this time, you need to reconfigure or replace the plug-in.
Basically that's it. The whole process is not too complicated, but details are easy to ignore, such as incomplete URL replacement, permission issues, or some plug-in dependencies are not handled. As long as you take it step by step, most situations can be solved smoothly.
The above is the detailed content of How to migrate a multisite site to a single site. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To roll back the WordPress version, you can use the plug-in or manually replace the core file and disable automatic updates. 1. Use WPDowngrade and other plug-ins to enter the target version number to automatically download and replace; 2. Manually download the old version of WordPress and replace wp-includes, wp-admin and other files through FTP, but retain wp-config.php and wp-content; 3. Add code in wp-config.php or use filters to disable core automatic updates to prevent further upgrades. Be sure to back up the website and database before operation to ensure safety and reliability. It is recommended to keep the latest version for security and functional support in the long term.

The steps to create a custom shortcode in WordPress are as follows: 1. Write a PHP function through functions.php file or custom plug-in; 2. Use add_shortcode() to bind the function to the shortcode tag; 3. Process parameters in the function and return the output content. For example, when creating button shortcodes, you can define color and link parameters for flexible configuration. When using it, you can insert a tag like [buttoncolor="red"url="https://example.com"] in the editor, and you can use do_shortcode() to model it

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

Object cache assists persistent storage, suitable for high access and low updates, tolerating short-term lost data. 1. Data suitable for "persistence" in cache includes user configuration, popular product information, etc., which can be restored from the database but can be accelerated by using cache. 2. Select a cache backend that supports persistence such as Redis, enable RDB or AOF mode, and configure a reasonable expiration policy, but it cannot replace the main database. 3. Set long TTL or never expired keys, adopt clear key name structure such as user:1001:profile, and update the cache synchronously when modifying data. 4. It can combine local and distributed caches to store small data locally and big data Redis to store big data and use it for recovery after restart, while paying attention to consistency and resource usage issues.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website
