Many organizations do not have one website. They have dozens or hundreds, built over the years on whatever platform made sense at the time: a homegrown CMS, a vendor's proprietary system, older versions of open source tools and a few WordPress installs. Each one needs its own updates, hosting and expertise. Consolidating them into a single WordPress Multisite network is one of the highest leverage projects an IT or digital team can take on.
I have led several large consolidations, including the LexisNexis LawLinks move of nearly 3,000 law firm sites from a legacy CMS into WordPress Multisite, the Microsoft News Center network of 38 sites in 16 languages and the DrugFree.org platform consolidation. Here is the playbook.
Why consolidate
The benefits compound with every site you bring in:
- One codebase to secure and update
- One design system and component library
- Shared features built once and used everywhere
- One hosting platform, one monitoring setup and one support process
- Editors learn one tool, and staff can move between sites easily
Legacy and proprietary platforms are the hard part
Homegrown and proprietary systems rarely have clean export tools. Content may sit in unusual database structures, be stored as raw HTML, or be locked behind a vendor's interface. We treat extraction as an engineering problem:
- Read directly from the database or vendor export files when available
- Use APIs where the platform offers them
- Crawl the published site when nothing else exists, as we did for Newark's Schoolwires sites in the Newark Public Schools migration
- Normalize everything into a common intermediate format before importing
Automate the pipeline
At scale, manual migration is impossible. For LawLinks, an automated pipeline turned each legacy database export into a finished site on the network, including a child theme recreated from the firm's live site so clients kept their look. The principle applies broadly: build a pipeline that takes a source site and produces a WordPress site, then run it again and again until the output is right. Repeatability is what makes hundreds of sites manageable.
Design for variation within a system
Consolidated sites rarely look identical. We use one parent theme or block theme with controlled variations, such as style variations, child themes or per site settings, so each site keeps its identity while sharing the same code. That balance protects brand consistency and still lets each site feel like its own.
Users, roles and authentication
Users from many systems become one network user base. We deduplicate accounts by email, map legacy roles to WordPress roles per site and connect the network to single sign on where possible so access is managed in one place.
Redirects for every site
Each source site has its own URL patterns, and many have their own domains. We map every URL, set 301 redirects and use domain mapping so sites keep their addresses. The details are in our migration SEO guide.
Roll out in waves
We never migrate everything at once. A pilot group of sites proves the pipeline and the design system. Later waves move faster as the process matures. Each wave includes content review, editor training and a launch window that fits the owners' schedules.
Hosting the consolidated platform
A large network needs hosting built for it: object caching, a CDN, room for traffic spikes and isolated staging. We host networks like these under our managed hosting service.
Measuring the payoff
Consolidation is a large investment, so measure it. Before the project, record the number of platforms, hosting bills, license fees, vendor contracts and hours spent on updates and support. After each wave, record the same. Many organizations also track editor satisfaction and the time it takes to launch a new site, which typically drops sharply once a network and design system are in place. Clear before and after numbers help justify the next wave and give leadership a concrete story to tell about why the work mattered.
Consolidation checklist
- Inventory all sites, platforms, owners and URLs
- Common content model and intermediate format
- Automated, repeatable migration pipeline
- Parent theme with controlled per site variations
- Deduplicated users, mapped roles and SSO
- Redirects and domain mapping for every site
- Pilot first, then waves
- Hosting sized for the combined network
Frequently asked questions
How many sites can one network hold?
Networks with thousands of sites run successfully on WordPress Multisite when the hosting and database are planned for it.
What if some sites need unique features?
Features can be enabled per site, and truly different sites can stay separate installs on the same hosting platform.
How long does consolidation take?
It depends on the number of sources and how clean they are. The pilot sets the pace for the rest.
Start with our platform migrations service or WordPress Multisite services.
