Legacy System Risk in M&A: What Technology Due Diligence Reveals

 

Legacy systems are rarely described as such in an information memorandum. They are “stable, proven platforms” with “a loyal customer base built over many years.” The architecture is “well-understood by the team.” The migration has been “considered and carefully deprioritised.”

By the time technology due diligence examines these platforms directly, a different picture frequently emerges. The stability is real — but it is the stability of a system nobody dares to touch. The team’s understanding of the architecture is concentrated in one or two people who have been there since the beginning. The deprioritised migration has accumulated a cost that grows every quarter it remains unaddressed.

Legacy system risk is one of the most consistent sources of post-acquisition surprise in software-intensive M&A. It is also one of the most assessable — if the diligence is scoped and timed correctly.


What “legacy” actually means in a due diligence context

The term is frequently misused. A platform built five years ago on a modern stack is not legacy. A platform built fifteen years ago on a framework that is still actively maintained and well-structured may not be either.

In a due diligence context, “legacy” refers to a specific combination of characteristics: technology that is difficult or expensive to change, that carries significant operational risk when modified, and that is structurally misaligned with the direction the business needs to move. Age is a contributing factor, not the definition.

The assessment question is not “how old is this platform?” It is: “what would it cost to change it, what are the risks of doing so, and what is the cost of not doing so at the scale implied by the investment thesis?”


What due diligence consistently finds in legacy platforms

Undocumented dependencies and tribal knowledge. Legacy platforms accumulate implicit knowledge over time — decisions made years ago whose rationale was never recorded, integrations built to solve a specific problem and never revisited, configuration choices that turned out to matter but whose significance was only discovered when something broke. In a healthy engineering organisation, this knowledge is externalised into documentation, tests, and code comments. In a legacy platform, it frequently lives in the heads of a small number of long-tenured engineers.

The due diligence implication is direct: the departure of one or two key individuals post-close can render significant portions of the platform opaque. This is a retention risk and a continuity risk simultaneously, and it should be reflected in deal structure.

Technical debt that has compounded beyond the team’s capacity to address it. Most engineering teams are aware of their technical debt. What they often underestimate is the rate at which it compounds. Features built on top of a weak foundation require more workarounds. Workarounds create new dependencies. New dependencies constrain future changes. By the time an acquirer commissions a TDD, the team may be spending a significant proportion of its development capacity maintaining existing workarounds rather than building new capability.

A diligence assessment quantifies this by examining deployment frequency, change failure rates, and the ratio of maintenance to development work. These metrics tell the story more reliably than any management team’s characterisation of the debt backlog.

Security posture that reflects the threat landscape of a different era. Legacy platforms were typically designed when the security threat landscape was materially different — before cloud-native attack surfaces, before the industrialisation of ransomware, before API security became a primary concern. Authentication models, session management, and data handling practices that were adequate ten years ago are frequently inadequate today.

This is not merely a theoretical risk. Legacy platforms are disproportionately represented in breach statistics, in part because their age correlates with known vulnerabilities and in part because their complexity makes them harder to patch. For an acquirer integrating a legacy platform into a broader portfolio, the security risk is not contained to the acquired business — it is a potential entry point for the whole.

Incompatibility with AI-enabled roadmaps. A growing number of acquisition theses are predicated on augmenting or extending the acquired platform with AI capability — AI-assisted features, automation of manual processes, or integration of AI tooling into the product roadmap. Legacy platforms are frequently incompatible with these plans in ways that are not obvious until the integration is attempted.

The underlying problem is structural: AI capability requires clean, accessible data, modern API interfaces, and an architecture that can accommodate new processing layers. Legacy platforms often have none of these. Data is fragmented across siloed databases with inconsistent schemas. APIs either do not exist or were designed for a specific integration use case. Adding an AI layer to a legacy architecture frequently requires rebuilding the foundation before the AI work can begin — a cost that is rarely in the investment thesis.


What the assessment actually looks at

A technology due diligence assessment of a legacy platform covers several specific areas that standard IT reviews typically miss.

Modernisation cost and sequencing. Not all modernisation is equal in cost or risk. A well-structured assessment identifies which components can be replaced incrementally, which require a wholesale rebuild, and what the sequencing constraints are — which changes must precede others to avoid breaking what currently works.

Migration risk. The transition from a legacy platform to a modern one carries its own operational risk, independent of the destination architecture’s merits. Data migration, customer continuity, and the period of parallel running all carry costs that need to be scoped and factored into the acquisition model.

The cost of staying. Modernisation is expensive. Staying on a legacy platform is also expensive — in security risk, in development velocity foregone, and in the increasing cost of skilled engineers willing to maintain ageing technology. A complete assessment models both paths, so the acquirer is making a decision between quantified options rather than a vague trade-off.


Legacy system risk is not a reason to avoid an acquisition. Many excellent businesses run on platforms that need modernisation. What it requires is accurate assessment — of the cost, the sequencing, the security exposure, and the implications for the investment thesis — so that the price paid and the structure of the deal reflect the actual risk being assumed.

At VeryDiligent, legacy platform assessments are a core part of our technology due diligence practice. We assess modernisation cost, security posture, and AI-readiness compatibility as standard scope — not supplementary items. If you are evaluating a business that may carry legacy system risk, we would be glad to discuss what a proportionate assessment looks like.


Related reading: When Due Diligence Comes Too Late: A Cautionary Tale | What PE Firms Should Demand from Technology Due Diligence | Scoring Technical Maturity: A Practical Model

Leave A Comment

Your email address will not be published. Required fields are marked *