WordPress multisite migration can move WordPress safely when it matches the source, destination, and risk level. This method is best for moving a full multisite network or carefully separating subsites with domain and upload-path awareness.
Audience: network owners, universities, agencies, SaaS operators, and hosts running WordPress multisite. Before using this path, decide whether the move changes hosts, domains, DNS, email, PHP versions, database versions, cache layers, or business data. Those details matter more than the migration button itself.
Before migration
- Back up network files and the full network database.
- Inventory subsites, domains, mapped domains, plugins, themes, uploads, and sunrise/domain-mapping configuration.
- Lower DNS TTL for every mapped domain.
- Decide whether you are moving the whole network or extracting a subsite.
Migration steps
- Move network files and uploads to the destination.
- Export and import the full network database.
- Update wp-config.php and .htaccess or web-server rules for the network type.
- Run safe URL replacements for main and mapped domains.
- Check domain mapping, SSL, and per-site uploads.
- Test each high-value subsite before DNS cutover.
Post-migration verification
Check network admin, subsite dashboards, mapped domains, uploads, plugins, themes, cron, SSL, cache, and representative pages from each important subsite.
Also check server logs, PHP errors, WordPress Site Health, cache behavior, CDN routing, redirects, robots/indexing state, cron jobs, and whether a new backup job exists on the destination.
Migration risks
- Single-site migration tools can miss multisite tables or uploads.
- Mapped domains need DNS and SSL per domain.
- Extracting one subsite is a different project than moving the whole network.
Rollback and cutover planning
Keep the old site online until the new site is proven. For stores, memberships, bookings, LMS sites, directories, and lead-generation sites, plan a final data freeze or sync so records do not split between servers. Keep DNS rollback notes, old-host access, and a verified backup until traffic and logs are stable.
Fix I.T. Phill recommendation
Use WordPress multisite migration when it gives you the cleanest preview and rollback path. If the site makes money or stores customer records, treat the final cutover as a maintenance window, not a casual copy job.
Related Fix I.T. Phill Guides
- How to Migrate WordPress: Complete Hosting Move Guide
- How to Migrate WordPress by cPanel Full Account Backup
- How to Migrate WordPress by WHM Transfer Tool
- How to Migrate WordPress by Plesk Migrator
- How to Migrate WordPress by Plesk WP Toolkit Clone
- How to Migrate WordPress by Softaculous Clone or Import
- How to Migrate WordPress by Installatron Clone or Import
- How to Migrate WordPress by DirectAdmin Backup and Restore
- How to Back Up WordPress: Complete Methods Guide
- How to Restore WordPress: Complete Recovery Methods Guide
- How to Back Up WooCommerce Without Losing Orders
- How to Restore WooCommerce Without Losing Orders
- How to Test a WordPress Backup Restore Before an Emergency
Sources Checked
- WordPress advanced administration: migrating WordPress
- WP-CLI search-replace documentation
- WordPress database backup documentation
2026 SEO Refresh: WordPress Multisite Migration Checklist
Admin action path: Multisite migration needs network-level evidence, subsite sampling, domain mapping review, and DNS proof before launch.
What to verify before changing production
- Check network tables, uploads, domain mapping, sunrise or mapping files, and subsite ownership.
- Sample multiple subsites before and after cutover.
- Verify DNS, SSL, login, media, REST, sitemap, and canonical behavior for the network.
Source-backed references and next reads
- Official reference: WordPress multisite administration.
- Official reference: WordPress installation handbook.
- Official reference: WP-CLI search-replace command.
- Related FixItPhill guide: host-to-host WordPress migration checklist.
- Related FixItPhill guide: WordPress migration DNS and email cutover.
- Related FixItPhill guide: manual WordPress migration with SFTP and phpMyAdmin.
- Related FixItPhill guide: cPanel WP Toolkit WordPress install checklist.
- Related FixItPhill guide: Plesk WP Toolkit WordPress install checklist.
Ticket evidence should include the method used, backup timestamp, destination URL, DNS or SSL state, mail-delivery result where relevant, and the public verification steps completed after the change.
