You've done three acquisitions in two years. Genuinely, well done - that's real strategic momentum. But now you're staring at the aftermath: five websites, three different CMS platforms, analytics scattered across separate Google accounts nobody fully controls, and a growing sense that the digital estate you've inherited is less "portfolio" and more "archaeological dig."
What I want to say upfront - because it's the thing that gets missed most often - is that this is not primarily a technology problem. It looks like one. It presents like one. Your IT team will absolutely frame it as one. But the reason your consolidation keeps getting deprioritised isn't that the technical work is too complex. It's that every time someone raises it, a partner from the acquired firm pushes back, or a marketing team feels threatened, or someone says "can we just leave it for now?" and everyone quietly agrees because the argument isn't worth having.
We know we need to consolidate. We've been meaning to do it. But every time we try to start, someone objects and the whole thing gets kicked down the road.
Sound familiar? I've watched this exact dynamic play out more times than I can count - and the firms that eventually get it done aren't the ones with the best technology teams. They're the ones that treat the human and political dimensions with the same rigour they apply to the DNS records.
I want to be specific about what "post-acquisition digital mess" actually looks like, because vague descriptions let people pretend their situation isn't that bad.
You've got multiple domains registered with different registrars - possibly some that nobody in the current team even has the login credentials for. Each website is built on a different platform, with no shared design system, no common CMS, and no unified content model. Your analytics are fragmented across separate accounts, which means nobody has a consolidated view of how the combined business is performing online. You've got duplicated content serving the same audiences from different URLs, and neither property is reinforcing the other's SEO value - they're actively competing with each other.
And then there's the human layer. The teams who built or inherited "their" website experience any talk of consolidation as a threat to their identity within the merged organisation. The partner who ran the acquired firm's marketing for six years doesn't want to hear that their site is being "absorbed." The clients of the acquired firm have bookmarked a specific URL, and some of them chose that firm partly because of a specific digital experience.
The M&A research on this is pretty consistent: somewhere between 70% and 90% of acquisitions fail to deliver the expected synergies, and a big chunk of that failure happens post-deal, during integration. Digital consolidation is one of those workstreams that looks straightforward in the deal model and turns into a quagmire in practice - not because the technology is impossible, but because nobody budgeted for the politics.
Seriously, don't skip this bit. Do not make any consolidation decisions until you've completed a proper digital estate audit. Not a quick scan. Not "Dave from IT had a look." A structured, documented assessment of everything you've inherited.
Here's what the audit needs to cover. Every live domain and subdomain - including the ones nobody knows are still running. (There are always some. I was working with an IT services firm that had grown through thirteen acquisitions. When we started the audit, we found legacy domains still resolving to servers that hadn't been patched in two years. The IT director's face when we showed him was something. That's not just messy - that's a live security exposure.) The platform each site runs on and its current licence and support status. Monthly traffic and its sources for each property. The SEO value held by each domain - domain authority, inbound link profiles, ranked search terms. A content inventory for each site and its overlap with other properties. And technical dependencies: integrations, APIs, authentication systems, CRM connections.
This audit takes longer than you expect. It always does. Budget two to three weeks, and treat it as a prerequisite rather than something you run in parallel with the consolidation. The findings will fundamentally change your consolidation plan - I've seen audits reveal that the property everyone assumed was disposable actually held 40% of the combined organic search traffic. Making that decision without the data would have been a disaster.
If you want a structured way to scope this, we've put together a digital estate audit checklist covering all six categories - domains and hosting, platform status, traffic and analytics, SEO value, content inventory, and technical dependencies - with a data collection guide for each. You can use it internally or hand it to your agency as a brief. Either way, it'll save you from the "we forgot to check the subdomains" conversation three months in.
Once the audit is complete, every property in your estate falls into one of three categories. The temptation is to default to a single approach across the board. Resist it.
Consolidate. Merge the content into the primary site, redirect the domain, and preserve as much SEO value as possible through structured 301 redirects. This is the right answer when the acquired brand doesn't have strong independent market recognition and the content overlaps significantly with what already exists on the primary site. Google's own guidance on site migrations is clear that properly implemented redirects can preserve the majority of link equity - but "properly implemented" is doing a lot of heavy lifting in that sentence. Get this wrong and you can destroy organic search value that took years to build. It's recoverable, but recovery takes months, sometimes longer.
Migrate. Move the site to the primary platform while keeping it as a distinct digital property - its own URL, its own brand presence, its own content. This is appropriate when the acquired brand has strong market recognition or serves a distinctly different audience. You get the operational benefits of a single platform (one CMS to maintain, one hosting arrangement, one set of security patches) without losing the brand equity the acquisition was partly paying for.
Retire. Redirect to an appropriate destination on the primary site and archive the content. This is for properties with low traffic, low SEO value, and no audience that would be materially affected. But "no audience that would be materially affected" needs to be validated, not assumed. Even a site with 200 monthly visitors might include three clients who check it regularly.
The decision for each property should be driven by the audit findings. Not by who shouts loudest in the meeting. Though - and this is where it gets real - the communication strategy for each decision absolutely must account for the politics.
The instinct is to rip the plaster off. Consolidate everything in one go, get it over with, move on. I understand the appeal. It feels decisive. It looks efficient on a Gantt chart.
It is a terrible idea.
A parallel consolidation of multiple properties creates maximum disruption to maximum stakeholder groups simultaneously. It multiplies the technical risk. And - this is the bit people forget - it removes your ability to learn from the early phases before applying that learning to the later ones.
Going back to that IT services firm with thirteen websites from thirteen acquisitions: we didn't consolidate all thirteen at once. We started with the property that had the clearest case - lowest traffic, lowest SEO value, least politically sensitive. We consolidated it cleanly, documented the approach, measured the outcomes. Then we used that result as both the template and the evidence for the next phase. And the next. There was a moment about four months in where one of the acquired firm's partners - who'd been sceptical from the start - looked at the traffic data and said "okay, I get it now." That wouldn't have happened if we'd tried to do everything in Sprint One and he'd spent those four months watching his firm's brand disappear into a single migration.
The whole programme took months rather than weeks, but at the end of it, they had zero measurable loss of organic traffic and a 60% increase in SEO visibility across the combined estate.
The sequencing logic is simple: start with the easiest case, demonstrate the approach, build confidence, then tackle the harder ones. Each phase should include clear communication to the organisation about what changed, what the outcome was, and what comes next. Nobody should be surprised by a fait accompli.
This is the part where most consolidation programmes fall over. Not because the redirects were wrong or the platform migration failed, but because someone who mattered felt blindsided.
There are three stakeholder groups, and each needs something different.
The teams whose site is being consolidated. These people built something. Or they inherited it and made it theirs. Telling them it's being "absorbed" is - I'm going to be blunt - a guaranteed way to create enemies you don't need. What they need to understand is that the consolidation is a technical change that should make their work more visible, not less. Involve them in decisions about how their content is represented on the consolidated site. Ask them what matters most. Let them shape the outcome rather than presenting them with a completed migration and a "hope you're okay with this" email.
I was involved in a consolidation where a partner at the acquired firm was genuinely distressed that the URL structure of the new site didn't include their firm's name. On the surface, nuts, right? But it wasn't about the URL. It was about what the URL represented - whether the merger actually valued what their firm brought. We ended up creating a dedicated section that told the story of the combined firm's heritage, including the acquired brand's history. Cost almost nothing. Changed the entire dynamic.
The acquired firms' leadership. They need to see that the consolidation reflects the strategic logic of the merger - that a single, stronger digital presence serves all the firms' clients better than five separate, weaker ones. But they also need to feel that their contribution is being recognised in the consolidated identity, not erased by it. This is a conversation for the CEO or managing partner, not the IT team.
The firms' clients. They need advance notice, a clear explanation of what's changing and why, and explicit confirmation that their relationship and their account are unaffected. A well-managed domain change should produce zero client defections. A poorly communicated one will produce some regardless of how technically perfect the work is. And if you're in a regulated industry - legal, financial services - check whether you have notification obligations around changes to how clients can contact you or access their information. I'm not going to give legal advice here, but I've seen firms get caught out by this, and it's an awkward conversation to have after the fact.
If you're sitting on a post-acquisition digital mess and you've been putting off the consolidation because it feels too big, too political, or too risky - I get it. Genuinely. But the cost of maintaining five websites on three platforms with fragmented analytics and competing SEO profiles is real, even if it doesn't show up on a single line of your P&L. It shows up in the marketing team's inability to report on combined performance. In the developer time spent patching three different CMSs. In the clients who Google your firm and find a confusing patchwork of brands that doesn't reflect who you actually are now.
Start with the audit. Everything else follows from it.
If you want to understand exactly what you've inherited - every domain, every platform, every integration dependency, and where the highest-risk consolidation decisions are - a digital estate audit is the right starting point. Two to three weeks, and you'll have the decision-ready picture you need before any consolidation begins. And if you want to scope it internally first, grab the digital estate audit checklist - it'll give you a structured way to collect what you need before bringing anyone else in.