Multisite migration
WordPress Multisite Migration: The Complete Guide
How to move a whole network, a single subsite, or several single sites in or out of WordPress Multisite, and which method fits which job.
Short answer
A Multisite migration is never just a copy of wp-content. A network shares one set of core files, one wp-config.php with the multisite constants, network tables (wp_site, wp_sitemeta, wp_blogs), and one users table for every site. Each subsite adds its own tables (wp_2_posts, wp_2_options …) and its own uploads folder under uploads/sites/2/.
So first decide what you are moving: the whole network, one subsite, or single sites that should join or leave a network. Each of those is a different job with its own risks, mostly around URLs, shared users and media paths. The six how-tos below cover the common cases step by step.
Before you start
- A complete, recent backup of the source you can restore. Test the restore before you need it.
- Know your network type: subdomain (
site.example.com) or subdirectory (example.com/site/). A full-network restore needs the same type on the destination. - Network Admin access on every network involved, and SFTP or file manager access on the hosts.
- DNS access for any domain that changes, and a lower TTL a day before you switch.
Which migration do you need?
Moving the whole network to another server, with or without a new domain: see moving a Multisite to a new host and changing the Multisite domain.
Moving one subsite to another network: export that subsite and import it as a new site on the destination network.
Turning one subsite into its own WordPress install: extract it from a network backup. Doing this for every site is a network split.
Bringing separate WordPress sites into one network: import each single-site backup as a new subsite and merge its users into the shared users table.
What makes Multisite migrations break
URLs are stored in many places: wp_site, wp_blogs, each site's options, post content, widgets and serialized plugin settings. A plain SQL find-and-replace breaks serialized data, so use a tool that rewrites serialized values safely.
Users are shared. When a site moves into another network, its user IDs almost never match the destination, so authors and user-linked data such as WooCommerce customers must be remapped, not overwritten.
Media paths differ: subsites keep uploads under uploads/sites/N/, but the main site (blog 1) usually uses uploads/ directly.
wp-config.php holds DOMAIN_CURRENT_SITE, PATH_CURRENT_SITE and SUBDOMAIN_INSTALL. After a domain or host change they must match the new setup, or logins and redirects fail.
Which Multisite Migrate plan covers what
Free: full network backups from Network Admin, backups of selected subsites, upload-import of an archive, and restore with URL rewriting (including serialized data) when the site moves to a new address.
Plus: off-site copies to your own cloud storage and cloud backup schedules.
Pro: import directly from cloud storage or a URL, direct site-to-site Push and Pull, the empty-server installer, importing a site into an existing network with shared users merge, extracting one site as standalone, splitting a network, leftover-URL verification and WP-CLI.
Steps
- Back up and test
Run a full network backup and restore it once on a test install, so you know the archive is complete. - Pick the scenario
Whole network, one subsite, a split, or a merge. Each how-to below lists the exact options to choose. - Prepare the destination
Same PHP and MySQL major versions or newer, enough disk for the archive plus the extracted files, and DNS and SSL ready for every domain that will be used. - Restore with URL mapping
Map each old URL to its new one during the restore so serialized data is rewritten correctly. - Verify, then switch
Log in, check Network Admin → Sites, re-save permalinks, spot-check media and forms, search for leftover old URLs, and only then point DNS to the new server.
Troubleshooting
Frequently asked questions
Can I migrate a Multisite network with the free plugin?
Yes. A full network backup, upload-import on the new install and a restore with URL rewriting are included in Free. Pro adds import from cloud or URL, the empty-server installer and the topology options for moving single sites in or out of a network.
Do I need the same network type on the destination?
For a full-network restore, yes: a subdirectory network restores onto a subdirectory network, and a subdomain network onto a subdomain network.
What about the users table?
A full-network restore replaces the users table with the archive's. When a single site joins an existing network, Pro's shared users merge matches users by login or email and remaps authors instead of overwriting accounts.
How long does the migration take?
It depends on database size, media volume and the host's limits. Backups and restores run in chunks, so short PHP time limits slow the job down rather than stopping it.
Sources
Related guides and comparisons
Articles on this topic
-
Topic: Cloud storage & costs
Egress fees for WordPress backups: what a restore really costs in 2026
We priced a 20 GB and an 80 GB WordPress Multisite backup at Amazon S3, Wasabi, Backblaze B2, Cloudflare R2 and Hetzner, and counted the requests our own backup plugin sends for each archive.
-
Topic: Hosting & PHP
max_execution_time on shared hosting: measured limits for Multisite backups
We timed PHP's execution limit on Linux and Windows, collected the documented limits of five hosts and traced which timeout actually ends a long WordPress Multisite backup request.
Make your first restorable network backup for free.