You have completed three acquisitions in two years. That is real strategic momentum. Now you are staring at the aftermath: five websites, three CMS platforms, analytics scattered across accounts nobody fully controls, and a digital estate that feels less like a portfolio and more like an archaeological dig.
This is partly a technology problem. It is also a brand, client, operating and political problem. A consolidation stalls when a partner from an acquired firm fears erasure, a marketing team sees a loss of autonomy or everybody agrees to leave the difficult decision for another quarter.
The firms that make progress apply the same rigour to identity, ownership and communication that they apply to DNS records.
Name the estate before choosing its future
"Several legacy websites" is too vague for a decision.
Domains may sit with different registrars, agencies or former employees. Sites may run on unsupported software or duplicate services for the same audience. Analytics and consent configurations may differ. Content can overlap, conflict or remain valuable to a specialist market. Forms may send client information into inboxes and systems that the combined firm no longer governs consistently.
Then there is the human layer. The people who built or inherited a website may experience consolidation as a verdict on their firm's history and influence. Clients may recognise the acquired name or have bookmarked a route they still use. "Absorb the old site" is an architectural instruction carrying an organisational message.
Treat the estate as part of post-deal integration, rather than an untidy marketing asset. The objective is not necessarily one website. It is a coherent, governable digital presence that supports the acquisition strategy and the people it serves.
Audit before you consolidate
Do not choose the destination from a quick scan. Build a documented view of what the firm owns, depends on and risks losing.
Domains, infrastructure and control
Record every live domain, subdomain and relevant redirect. Confirm registrant, registrar, renewal, DNS, certificates, hosting, administrative access and recovery routes. Look for staging sites, old campaign domains and services that do not appear in the main navigation.
On an estate assembled through thirteen acquisitions, we found legacy domains still pointing to infrastructure that had missed security maintenance. It exposed a direct control question: can the current firm identify and administer every public property that carries its name?
Platform and supplier position
Identify each CMS, version, licence, support status, plugins, themes, hosting service, agency and contract. Record who can deploy, update and restore it. Include monitoring, backups, incident response and expected end-of-support dates.
Calculate ownership cost across licences, hosting, suppliers and internal time. A low invoice can conceal a site maintained through fragile knowledge or unmanaged risk.
Users, traffic and search
Reconcile analytics access and definitions. Review traffic sources, important landing pages, conversions, device use and seasonal patterns. Use Search Console and backlink information to understand how people and search engines find each property.
Avoid reducing search value to one third-party "domain authority" score. Examine queries, useful pages, external links, indexed URLs and business relevance. A low-volume specialist site may support a small number of valuable relationships.
Content, brand and journeys
Inventory content at a level suited to the estate. Mark duplication, contradiction, age, ownership, audience, legal or regulatory retention, and content with distinctive search or client value. Include people profiles, cases, downloads, policies and structured data alongside ordinary pages.
Map the journeys that cross properties. A user might start on an acquired brand, move to the group site and submit a form to a third system. The migration decision needs to preserve or deliberately redesign that route.
Data, integrations and compliance
Trace forms, cookies, analytics tags, CRM connections, authentication, APIs, feeds and data exports. Identify personal and confidential information, processor relationships, retention and deletion. Check accessibility, privacy and sector-specific obligations with the appropriate specialists.
The output is a decision register, rather than a prettier spreadsheet. Each property should have an owner, evidence, risks, dependencies and a proposed future state. The audit duration depends on estate size, access and documentation; do not promise that every acquisition estate can be made decision-ready in an arbitrary number of weeks.
If you need a structure, download the digital estate audit checklist below. It covers the principal evidence categories and can be used internally or as a brief for a partner.
Choose a future for each property
Three common treatments are useful, although the same answer need not apply to the whole estate.
Consolidate. Move useful content and journeys into a primary property, then redirect corresponding old URLs. This can suit an acquired brand with limited need for an independent digital presence and substantial audience or content overlap.
Migrate and retain. Move the property onto a shared platform or operating model while keeping a distinct brand, domain or experience. This can reduce duplicated technology without discarding recognition that still supports the deal strategy.
Retire. Archive what must be retained, remove what no longer has a purpose and direct users to relevant live destinations. Low traffic alone does not prove there is no affected audience.
Some firms will deliberately retain a property on its current platform for a defined period. Treat that as a fourth, time-bound decision with an owner, cost, risk and review trigger. "Leave it for now" should not be an unrecorded default.
Score options against acquisition intent, client journeys, brand value, content and search evidence, operational cost, risk, technical dependencies and future change. Record who has been consulted and which evidence could change the decision.
Protect users and search signals during a move
A domain move is a product and service change as well as a technical release.
Build an old-to-new URL map at page level. Redirect each valuable old URL to the most relevant new destination, rather than sending everything to a homepage. Update internal links, sitemaps, canonical references, campaign links and important external profiles. Preserve access to content that clients still need.
Google's current site-move guidance recommends careful URL mapping, permanent server-side redirects, Search Console use and monitoring of both old and new URLs. It also advises changing one major thing at a time where possible and warns that rankings can fluctuate while pages are recrawled and reindexed. Google says permanent redirects do not themselves cause a loss of PageRank. A wider consolidation can still change traffic and rankings.
Test forms, search, downloads, consent, analytics, accessibility and integrations across the new journey. Monitor search visibility, traffic, errors, redirects and business outcomes after launch. Keep redirects for as long as practical; Google's guidance says generally at least a year and notes that users may benefit from longer.
Decide what "preserved" means before the move. It might include access to important client resources, qualified enquiries, relevant search visibility, task completion and the absence of material security or compliance regression. Aggregate traffic alone can hide the loss of a small, valuable audience.
Sequence for learning and risk
Moving every property in parallel maximises the number of simultaneous dependencies and stakeholder groups. It also makes failures harder to diagnose.
A phased sequence is often stronger. Choose an initial property or section that is representative enough to teach the team something, bounded enough to recover and appropriate for the risk. The least politically sensitive site may be a good start, but an obscure site with no important integrations may teach little about the harder moves.
Google also recommends splitting a large move into smaller steps when that makes sense, while warning that a test section may not represent the whole site. Use the first phase to validate the process, tools, roles and measures. Do not assume one successful migration proves every later brand and journey decision.
On the thirteen-acquisition estate, the programme began with a lower-risk property, documented the approach and used observed results to build confidence for later decisions. The team could challenge its process before attempting the more consequential migrations.
After each phase, communicate what changed, what happened and what the next decision is. A migration programme should accumulate evidence and organisational confidence, rather than simply repeat a technical recipe.
Communication is part of the control environment
Consolidation programmes fail when people who hold critical knowledge or influence feel blindsided.
Teams behind an acquired property
These colleagues built something or inherited responsibility for it. Involve them in the inventory, the decision criteria and how their expertise and content will appear. Explain which work becomes easier and which autonomy changes. A completed migration followed by a reassurance email invites resistance and loses useful knowledge.
In one consolidation, a partner was distressed that the new URL structure did not carry the acquired firm's name. The apparent URL objection was really a question about whether the merger valued what that firm brought. A section explaining the combined firm's heritage helped resolve the issue. Small design choices can carry disproportionate symbolic weight.
Leadership across the combined firm
Leadership needs to connect digital decisions to the acquisition thesis: stronger reach, clearer services, shared capability or an intentionally differentiated portfolio. Recognition of an acquired firm's contribution should be explicit where it is true. This is a leadership conversation, rather than a message delegated entirely to IT.
Clients and other users
Identify who needs advance notice, what action they must take and which channels they trust. Explain changes to domains, contacts, logins, saved links and access to information. Confirm what remains the same. Give support teams scripts and escalation routes for confusion or fraud concerns.
In regulated or high-trust services, involve legal, compliance, privacy and security owners early to determine contractual or notification duties. A domain or login change can also create an opportunity for impersonation, so coordinate security messaging and monitoring.
Where to start
Maintaining five sites on three platforms creates costs even when they do not appear on one budget line. Marketing cannot see combined performance. Technology teams patch several estates. Clients and prospects encounter brands that may no longer explain the firm they are dealing with.
Start with the audit, then turn its findings into explicit property decisions and a risk-based sequence.
If you want to understand what you have inherited, a digital estate audit is the right starting point. It should give you a decision-ready picture of domains, platforms, journeys, content, data and dependencies before consolidation begins. If you want to scope that work internally, download the digital estate audit checklist below and use it to expose what the organisation knows, assumes and still needs to find.
