Extracting one site from a WordPress multisite network into its own standalone installation means separating shared tables, shared plugins, and shared media from everything specific to just that one site — a genuinely more involved job than a normal migration, since multisite’s database structure isn’t designed to be easily split apart.
Multisite to single site extraction
One site carefully extracted from a multisite network into its own standalone install.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Admin access to the multisite network and the specific site being extracted
- Your target hosting environment for the standalone site
- Confirmation of which plugins and media are genuinely specific to this site, versus shared network-wide
This or something else?
| You want one specific site pulled out of a multisite network into its own standalone WordPress installation | This fix covers it |
| You’re moving a standalone site to a new host, not extracting from multisite | Host-to-host migration – single site |
| You want the whole multisite network moved, not one site extracted from it | A different, larger project — worth discussing directly |
| You want a staging copy of the multisite network, not an actual extraction | Staging environment creation & sync |
What we do
- Identify exactly what content, media, and settings belong specifically to the site being extracted
- Separate that site’s data from the shared multisite database tables
- Reconstruct it as a standalone WordPress installation on the target hosting
- Reinstall and reconfigure any plugins that were previously shared network-wide
- Verify all content, media, and functionality transferred correctly
- Test the standalone site thoroughly before final DNS cutover
What is included
- A complete, standalone WordPress installation extracted from the multisite network
- All site-specific content, media, and settings preserved
- Plugins reinstalled and reconfigured for standalone use
- Thorough testing before cutover, and the pre-extraction multisite state left untouched
Not included
- Changes to the remaining multisite network itself, beyond removing the extracted site if requested
- Purchasing new hosting for the standalone site, unless already arranged
- Ongoing management of either the standalone site or the remaining network after extraction
- Recovering shared content that genuinely can’t be attributed to a single site
Questions about this fix
Will extracting my site affect the rest of the multisite network?
We aim to leave the remaining network untouched by this process, extracting only the specified site's data — removing it from the network afterward, if you want that done too, is a distinct, additional step worth confirming.
What happens to content that was shared across the whole network, not specific to my site?
Genuinely shared, network-wide content doesn't belong to any one site by definition, so it isn't something that transfers with the extraction — we'll flag anything ambiguous for your decision.
Is this more complicated than a normal site migration?
Yes, meaningfully — multisite's database structure interleaves shared and site-specific data in ways a standalone WordPress installation doesn't, which is why this requires more careful separation than a typical host-to-host move.
Will my plugins still work the same way after extraction?
Network-activated plugins need to be reinstalled and reconfigured as standalone plugins on the new site, which we handle, though some network-specific plugin behaviour may need adjusting for a non-multisite context.
Can I extract more than one site from the same network at once?
Yes, though each site is effectively its own extraction project — we'd scope and quote multiple extractions based on how many sites and how much shared complexity is involved.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.