A roll-up can put several businesses under one owner without giving their customers the same needs. Portfolio company website consolidation should start with a buyer and brand decision, not a deadline to put every acquired site on one domain.
Aim for one website only when one buying experience makes sense. Otherwise, consider shared technology behind distinct sites, or a staged move that keeps an acquired brand visible while the business integrates.
What is portfolio company website consolidation?
It is the deliberate decision to combine or coordinate websites after acquisitions. The work includes choosing which brands and domains stay, mapping content, planning any migration, and assigning ownership of leads and measurement. Merge the customer experience only where it fits; sharing a platform does not require retiring every brand.
Why make this decision before starting a redesign?
The point of portfolio company website consolidation is not fewer URLs. It is a clearer path from customer need to the right business, paired with a website estate the team can manage.
Write the value creation goal before choosing the architecture: a shared sales offer, simpler publishing, less duplicated maintenance, or better reporting. Treat each as a goal to test, not an automatic benefit of the deal.
If the wider plan is still unsettled, align this decision with your marketing for portfolio companies. A website project should support the commercial plan rather than decide it by default.
Should you merge, migrate or keep brands separate?
For portfolio company website consolidation, separate three choices: the public brand, the domain structure, and the technology stack. Decide each on its own merits.
| Option | Consider it when | Resolve before committing |
|---|---|---|
| Merge into one website | The intended offer, audience and sales ownership are shared. | Can one site explain each service clearly and route each inquiry to the right team? |
| Migrate to a shared platform | You want common technology while keeping distinct brands or domains. | Can the platform support separate content, permissions, tracking and customer journeys? |
| Keep separate websites | Brands serve different buyers, regions or specialist needs. | Who owns each site, which standards are shared, and what would trigger a later change? |
A parent website can also serve as a directory while operating brands keep their own sites. Use that model when the parent explains the group but each company still sells a distinct offer.
What should website due diligence cover?
Before approving portfolio company website consolidation, ask for an inventory that ties each site to its business role. Give every item an owner and a recorded disposition.
- Business role: audience, services, region, brand owner, and support needs.
- Performance: landing pages that bring qualified inquiries, branded searches, and current sales outcomes.
- Content: service pages, location pages, useful resources, downloads, and material with legal restrictions.
- Access: domain registrar, hosting, CMS, analytics, search accounts, and lead-routing systems.
- Dependencies: forms, portals, integrations, email settings, paid campaigns, and links used by customers.
Use actual performance records and customer input. Do not treat a brand name, page count, or a vendor presentation as evidence that a site is safe to retire.
How should the transition work?
1. Define the future buying experience
Start portfolio company website consolidation with the customer path. Which business should answer each service request? Where should existing customers get support? Show those routes in a simple page plan before selecting a CMS.
Name one sponsor who can resolve brand and commercial disputes. Assign separate owners for content, engineering, search, analytics, and sales routing.
2. Map each old page to a decision
Mark each page keep, combine, rewrite, or retire. Map retained material to a relevant destination, not simply the new homepage. Include downloadable files and campaign landing pages. Keep a record of the old address, planned destination, responsible owner, and reason for the choice.
Use that inventory to guide your content strategy for portfolio companies, especially where several brands describe similar services.
3. Build and test the migration
The technical plan for portfolio company website consolidation should cover redirects, internal links, canonical URLs, sitemaps, tracking, forms, and access to the old domains. Test representative old links and complete the lead journey on the new site.
Agree on pass or fail checks before launch. Test mobile layouts, keyboard access, downloads, customer support paths, and delivery of a test inquiry to the correct team.
4. Release in a controlled sequence
Keep the brand change, platform change, and content rewrite separable where practical. Pick the sequence around business constraints, not an arbitrary acquisition anniversary.
Record a fallback plan, launch owner, issue escalation route, and access needed for fixes. Avoid closing old accounts before the team can verify the new setup.
5. Monitor before closing the project
Treat portfolio company website consolidation as unfinished until the buyer journeys and reporting work in production. Check priority pages, old links, tracking, and inquiry routing after release. Keep responsibility for legacy domains explicit.
What if the brands should remain separate?
Keeping brands separate is a valid portfolio company website consolidation outcome. Set shared standards for access, security review, measurement, accessibility, and publishing while leaving the customer experience distinct.
Use group-level reporting to compare performance without forcing every company into identical targets. Document who owns each site and how a future acquisition enters the system. Shared governance should not erase a useful local or specialist offer.
Which mistakes should companies avoid?
Do not treat every acquired site as duplicate inventory during portfolio company website consolidation. Review these decisions before approving retirement:
- Sending every old URL to the homepage. Require a destination that matches the old page, or a documented reason to retire it.
- Replacing specific service content with a broad group pitch. Keep answers that help the right buyer choose.
- Changing tracking without a baseline. Preserve old reports and annotate the release so comparisons have context.
- Launching before lead ownership is clear. Send test inquiries through each brand, region, and service route.
What should it cost, and how long should it take?
Scope portfolio company website consolidation before asking for a price or date. Request estimates against the actual domain inventory, content decisions, integrations, brand work, testing requirements, and internal review capacity.
Separate one-time migration work from ongoing hosting, licenses, maintenance, and publishing. Ask each vendor to state assumptions, exclusions, dependencies, and post-launch responsibilities. Compare proposals against the same scope; do not compare a platform-only move with a full rebrand as if they were equivalent projects.
How should success be measured?
Measure portfolio company website consolidation against the original business goal, with a baseline from each legacy site. Keep brand-level views alongside the group total so leadership can see where results differ.
Track four areas:
- Commercial: qualified inquiries, correct routing, sales acceptance, and resulting opportunities.
- Search: branded and nonbranded discovery, priority landing pages, and old-to-new page coverage.
- Customer experience: completed tasks, support access, form completion, and reported problems.
- Operations: publishing effort, maintenance spend, access ownership, and unresolved migration issues.
Agree on review intervals and escalation thresholds before release. Investigate differences by brand, service, region, and channel rather than relying on the group total alone. The final test is whether the chosen structure serves buyers and the operating plan—not whether every acquired website disappeared.
About the author
Bob Generale is President of Percepture.
