The Complete Guide to WordPress Multisite Migration: Secure Transfer and Zero Data Loss Solution

WordPress MultisiteNetwork, compared with the ordinary WordPress site, multi-site network contains interrelated sub-site database, shared media library and complex user rights system, any operational errors may lead to permanent data loss. Now based on actual cases, systematic combing of multi-sitemigrationKey risk points in the process and response options.

Specificity of the database structure

multisite networkcomprehensive databaseContains several special data tables. Among themwp_blogsRecord basic information for all sub-sites.wp_siterespond in singingwp_sitemetastore network-level settings, and each sub-site has a separate data table group (e.g., thewp_2_posts). Testing revealed that direct replication of a single-site database resulted in broken sub-site associations.

In practice, the SQL file containing all prefixed data tables must be exported in its entirety. Use thephpMyAdminTo export, you need to check the "Custom" format and select the "Full Insert" option to avoid data truncation.

Command line export is more reliable:

bash
mysqldump -u username -p database name > multisite_backup.sql

Media File Handling Essentials

The multisite network defaults to a shared upload directory structure, with media files from all subsites stored in the/wp-content/uploads/sites/within the subfolder. A common error is to migrate only the main site files, resulting in broken images in the sub-sites.

The reliable solution is to synchronize the entire upload directory using the rsync command:

bash
rsync -avz /old server path /wp-content/uploads/ new server:/wp-content/uploads/

simultaneous check.htaccessfile permissions to prevent403 Denial of AccessError.

Domain name and path configuration

multisite networkwp-config.phpincorporateDOMAIN_CURRENT_SITEdefinitions, while the databasewp_optionstable (primary site) andwp_#_optionsThe table (sub-site) stores the absolute URL path. When migrating to a new domain, there are four steps of adjustments to perform:

• existwp-config.phpupdateDOMAIN_CURRENT_SITE(be) worth

• Bulk replacement of old domains using SQL:

sql
UPDATE wp_options SET option_value = REPLACE(option_value, 'old domain name', 'new domain name');
UPDATE wp_#_options SET option_value = REPLACE(option_value, 'old domain name', 'new domain name');;

• Clear all cached plugin data

• Reset fixed link structure

Synchronization of user rights

Multi-site user data is stored in thewp_usersrespond in singingwp_usermetatable, while sub-site permissions are recorded in thewp_#_capabilitiesetc. in the metadata. Tests have shown that directly importing the user table may break role assignments.

Recommendation Process:

1. Keep all user IDs intact when exporting
2. After migration use "network administrator→subscribers→Redistribution of articles"Functions
3. probewp_user_rolesWhether the option is a complete migration

Validation and Test Checklist

The following checks must be performed after completing the migration:

• All sub-site home pages load properly
• Can administrators switch between different sub-site backends
• Whether the media library image is displayed in full
• Whether the user logs in with the correct permissions
• Whether the plugin remains active at the subsite

Sub-sites appear404 errorWhen you do, you need to check thewp_#_optionstabulatedsiteurlrespond in singinghomevalues and resave the fixed link settings. Database connection problems usually stem fromwp-config.phphit the nail on the head$table_prefixMismatch with the actual database prefix.

Emergency Recovery Program

Preparing two recovery plans minimizes risk:

1. database snapshot: Create database point-in-time recovery markers before migration
2. File Backup: Retention of the fullwp-contentCatalog Zip

Practical examples show that when the subsite data is abnormal, separate recoverywp_#_optionstable is often more efficient than a full library rollback. Using theWP-CLI(used form a nominal expression)search-replacecommand is more secure than manual SQL replacement:

bash
wp search-replace 'old domain' 'new domain' --network --dry-run

The complexity of multi-site migrations stems primarily from data correlation.Understanding Table Structure Relationships,Adoption of incremental operation,Establishment of a complete rollback mechanismThese three elements are effective in controlling risk. For hyperscale networks, it is recommended thatMigration of sub-sites in batches, validate core functionality immediately after each migration to avoid systemic failures.

Contact Us
Can't read the tutorial? Contact us for a free answer! Free help for personal, small business sites!	Customer Service
① Tel: 020-2206-9892
② QQ咨询：1025174874
(iii) E-mail: info@361sale.com
④ Working hours: Monday to Friday, 9:30-18:30, holidays off