We set up a new WordPress multisite network from an existing single-site installation, converting it into the network’s main site and configuring the underlying architecture correctly — a foundational, structural change that affects how the entire installation works going forward, not something to undertake without understanding the trade-offs involved.
Multisite network setup & configuration
An existing single site converted into a multisite network, with the trade-offs discussed upfront.
- 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
- Confirmation of your intended network structure (subdomains or subdirectories for subsites)
- FTP and database access, since this involves core configuration file and database changes
- A recent backup, or agreement to take one before proceeding, given the scope of this change
This or something else?
| You want to convert your existing single WordPress site into a multisite network | This fix covers it |
| You already have a multisite network and need a configuration error fixed | Multisite network configuration errors, in the Configuration & Environment category, the diagnostic version |
| You want a subsite added to an already-existing network, not the network itself created | Subsite creation & template cloning |
| You’re not sure multisite is actually the right approach for your situation | Worth discussing directly — multisite fits specific use cases, and isn’t always the best structural choice |
What we do
- Confirm your intended network structure and requirements
- Configure wp-config.php and .htaccess for multisite
- Convert the existing site into the network’s main site
- Verify the network dashboard and core multisite functions work correctly
- Test creating an initial subsite to confirm the setup functions end to end
- Document the network structure and configuration for future reference
What is included
- A working multisite network converted from your existing single site
- Verified core network functionality
- A tested initial subsite confirming end-to-end function
- The pre-conversion backup, kept for 30 days
Not included
- Creating additional subsites beyond the initial test — a separate, related fix for each
- Domain mapping for custom subsite domains, a separate, related fix if needed
- Migrating existing content into a specific subsite structure beyond the conversion itself
- Ongoing network administration as a standing service
Questions about this fix
Is multisite the right choice for what I'm trying to do?
It depends on your specific situation — multisite suits managing several related sites with shared users or plugins efficiently, but it's a genuine structural commitment with its own complexities, worth discussing directly if you're not already confident it's the right fit.
Can I undo this and go back to a single site if I change my mind?
It's technically possible but involves its own significant, careful process rather than a simple toggle — this is why we'd recommend being confident in the decision before converting, rather than treating it as an easily reversible experiment.
Will my existing site's content and settings be preserved during this conversion?
Yes, your existing site becomes the network's main site, retaining its content — we verify this specifically as part of the conversion process.
Should I choose subdomains or subdirectories for my subsites?
This depends on factors like your DNS setup and preferences — subdomains require additional DNS configuration, while subdirectories don't, and we can help you weigh the practical trade-offs for your specific situation.
What happens to my existing plugins during this conversion?
We verify plugin compatibility as part of testing, since not every plugin is built with multisite in mind — a plugin working fine on a single site doesn't automatically guarantee identical behaviour across a network.
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.