How to Migrate a WordPress Multisite Network

admin

7 hours ago

How to Migrate a WordPress Multisite Network migration tutorial showing backup, transfer, verification, and DNS cutover checks

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.