Firms that grow through acquisition often inherit several websites, content systems, hosting arrangements, analytics accounts and versions of the brand. Consolidation promises lower operating effort and a coherent market presence. It can also remove useful content, damage search visibility and alienate people whose identity is tied to an acquired business.
The first task is therefore not migration. It is establishing what each part of the estate does, who depends on it and what value must survive.
An apparently dormant site may still attract relevant demand or hold valuable links. A page described as critical may receive almost no use. Similar service descriptions may have diverged until they make conflicting promises. Audit before deciding anything.
Treat the audit as decision work
Create a complete estate inventory covering domains, subdomains, CMSs, hosting, certificates, analytics, search properties, forms, integrations, accounts, suppliers and renewals. Confirm ownership and protected access. Acquisitions often leave important assets registered to former staff or agencies.
At page and content-set level, collect:
- purpose, audience and owner;
- traffic and meaningful actions;
- organic queries, indexed status and inbound links;
- content quality, accuracy and currency;
- duplication and conflicting claims;
- regulatory, contractual or records significance;
- linked assets, forms and integrations;
- accessibility and technical condition;
- future relevance to the combined organisation.
Analytics are evidence with limitations. Missing tags or short retention can make a useful site look inactive. Search data may not capture referral, direct, offline or existing-client value. Combine data with stakeholder and user evidence.
Do not let a business owner decide the fate of pages from memory alone. Equally, traffic does not make content strategically correct. The audit creates the basis for an explicit retain, combine, rewrite, archive, redirect or remove decision.
Decide the future organisation before moving pages
Consolidation is not the act of placing several old navigation trees beneath one logo. Define the future firm’s services, audiences, propositions and operating model.
Research how clients understand the combined offer and where acquired strengths need to remain visible. Resolve terminology and conflicting descriptions with accountable subject specialists. Decide whether any brand, jurisdiction or service genuinely requires a distinct experience.
Create a target content model and information architecture. Map each source item to a destination or retirement decision. Record rationale, owner and required action. This prevents migration volume from becoming the measure of progress.
Content quality decisions take time. Similar pages may each contain useful passages, evidence or search value. Preserve the strongest current material while removing contradiction and repetition. The editing process should involve people who understand the acquired business without giving every historic page an automatic right to survive.
Preserve search value deliberately
Domain consolidation changes how search engines and people reach content. Build a URL-level redirect plan from the final content decisions. Map each retired URL to the closest relevant destination; avoid sending everything to the homepage.
Capture current URLs, canonical signals, metadata, internal links, structured data, robots rules, sitemaps and significant backlinks. Check protocol, hostname, case, parameters and historic paths. Crawl the proposed redirects to find loops, chains and broken destinations.
Search specialists should review material decisions, especially where several pages compete for the same subject or a strong page will be combined. No migration can guarantee zero traffic movement. Establish baselines, expected volatility, monitoring and recovery authority.
Keep redirects for as long as users and external references may reasonably rely on them. Do not describe their work as an afternoon task merely because implementation can be automated. The difficult part is the content and destination judgement.
Consolidate analytics without losing history
One measurement model can give leadership a coherent view, provided legacy context survives. Before changing accounts or tags, export key historical data, definitions, annotations and known quality issues.
Design the new measurement plan around decisions and outcomes. Standardise event names, consent handling, referral exclusions and CRM attribution. Mark the migration date and avoid comparing periods as if tracking remained identical.
Maintain an archive linking old properties and definitions to the new model. A single dashboard is useful only if it does not erase the conditions behind the numbers.
Phase by risk and learning
A phased migration limits blast radius and lets the team improve its method. Starting with a simpler, lower-consequence site can be sensible when it still tests representative content, redirects, analytics, deployment and governance.
Do not automatically leave the highest-risk unsupported site until last. Sequence using value, urgency, dependency, technical risk and learning. A pilot phase should exercise enough of the real problem to inform later work.
For each wave:
- confirm content and redirect decisions;
- migrate using a repeatable, version-controlled process;
- review content, accessibility, security and performance;
- test forms, integrations, consent and analytics;
- rehearse release and rollback;
- monitor errors, search, user behaviour and support;
- capture learning before the next wave.
Avoid a big-bang release merely to create a clean brand moment. Equally, do not let phases extend so long that the estate continues diverging faster than it consolidates.
Design for the next acquisition
The target platform should make future integration of an acquired site more predictable. Define a playbook covering estate discovery, access, risk triage, brand decision, content model, redirects, data, governance and transition.
This does not mean forcing every future business into identical pages. Create governed flexibility for valid service, sector or regional differences. A shared design system, content model and platform can support variation without recreating independent estates.
Include operating cost and skills. A technically elegant platform that only one agency can change may reproduce dependency in a different form. Test whether internal teams can publish, measure and govern the combined service.
Treat identity as programme work
Retiring a website can feel like erasing the work and status of an acquired team. Brand logic and reduced hosting cost will not answer that concern.
Involve acquired colleagues in identifying content, client expectations, terminology and evidence worth preserving. Explain decision criteria and show where their contribution appears in the future service. Give them influence over the knowledge they hold while maintaining clear authority for the final architecture.
Plan client, employee and partner communication. Some audiences need advance notice, changed contact routes or reassurance about continuity. Redirects alone do not manage organisational change.
Measure the outcome, not the site count
Track more than the number of platforms retired. Relevant evidence may include:
- total ownership and support effort;
- security and accessibility exposure;
- publishing time and content quality;
- search visibility and qualified demand;
- journey completion and enquiry routing;
- data consistency and reporting effort;
- colleague adoption and future acquisition readiness.
Use baseline, period and definitions. Do not publish a support-cost or search-improvement percentage without approved evidence, the calculation and a suitable comparison.
The strongest consolidation creates a governable digital service, not merely one website. Audit the estate, make content and search decisions before migration, phase around real risk and give acquired teams a meaningful role in shaping what survives.
Distinction’s digital-estate consolidation assessment can help establish likely scope, dependencies, cost and programme risk before commitment. A first conversation can also test whether full consolidation, selective integration or a different target model is more appropriate.
