WordPress multisite lets you run dozens of sites from a single installation. Shared users, shared themes, one-click plugin updates across the network. It sounds like the dream infrastructure for anyone running multiple content projects.
Until you try to install a plugin on site #4 that breaks checkout on site #9. Or your host tells you multisite counts as one site for billing—but throttles CPU after 50,000 monthly visits total. Or you want to sell one project and realise you can’t extract it without a database surgeon.
Multisite makes sense in specific scenarios. Outside those scenarios, it creates more problems than it solves.
When multisite works
Multisite shines when you’re running a fleet of near-identical sites that share the same stack and never diverge.
University department sites. Same theme, same plugins, same user roles. Central IT pushes updates; individual departments edit pages. No custom functionality per site.
Franchise or multi-location businesses. Twenty gym locations, one brand, one CMS. Each location gets its own subdomain, but the plugin set, design, and functionality stay identical.
Internal documentation or staging networks. You’re running test environments for client work and want to spin up isolated WordPress instances fast without separate hosting accounts.
The common thread: low divergence. The moment one site needs WooCommerce, another needs a membership plugin, and a third runs a job board, multisite becomes a liability.
Where it breaks
Plugin conflicts cascade across the network. Activate a caching plugin on the network level, and it applies to every site—even the ones where it breaks the login flow or conflicts with another plugin active on a single sub-site.
You can activate plugins per-site, but troubleshooting gets messy. Is the issue the network-activated SEO plugin, the site-specific form builder, or the theme? Multiply that across twelve sites and you’re spending more time debugging than publishing.
Performance caps hit faster. Most managed WordPress hosts treat multisite as a single site for billing purposes—but apply the resource limits globally. If your plan includes 100,000 visits per month, that’s across all subsites combined. Three sites doing well means the rest get throttled.
BigScoots and a handful of other hosts meter multisite by total resource usage rather than visit counts, but you’ll still hit I/O limits or MySQL connection caps faster than you expect when you’re sharing a database across ten active sites.
You can’t sell or migrate one site cleanly. Each subsite lives in the same database with shared user tables and a shared uploads directory (unless you’ve rewritten the media handling). Extracting one site means exporting specific tables, rewriting URLs, and recreating users. It’s possible, but it’s never one-click.
The split-or-merge decision tree
Start with separate WordPress installs if:
- Each project might need different plugins, especially anything that touches checkout, membership, or user roles
- You plan to sell, transfer, or shut down individual sites
- Traffic is uneven—one site gets 80% of visits and you want isolated performance
- You’re working with different developers or agencies per project
Go multisite if:
- You’re running 5+ sites with identical functionality
- Central control matters more than per-site flexibility
- You’ll never migrate or sell individual sites
- You have in-house WordPress expertise to manage network-level issues
One middle path: use separate installs but centralize management with something like MainWP or ManageWP. You get one dashboard for updates and backups without the database coupling.
Migrating out of multisite
If you’re already on multisite and it’s not working, extraction is possible but manual.
You’ll export the subsite’s tables (usually prefixed with wp_2_, wp_3_, etc.), rename them back to the standard wp_ prefix, search-replace the domain in the database, and move the /wp-content/uploads/sites/2/ folder into a new install’s /uploads/ directory.
Budget four to six hours for the first one. After that, you’ll have a checklist and can move faster.
Some hosts offer multisite-to-single-site migration as a service—expect to pay $150–$300 per site, and confirm they’ll handle user table merges and media-path rewrites.
Want more infrastructure breakdowns like this? Subscribe to One Two Three Send and get one operator-focused deep-dive every day.