The five-year hold and the platform nobody replaced

A third of private equity portfolio companies are now held past five years, and buyers are pricing the gap. An end-of-support core system is one of the few valuation discounts a seller can remove on a known schedule.

As of March 2026, private equity globally held 32,979 portfolio companies, essentially unchanged from the end of 2025. What changed is their age: 34 percent had been held for more than five years, up from 28 percent a year earlier.1 Seventy percent of sponsors surveyed by L.E.K. expect to exit less than a fifth of their portfolio in the next twelve months, and more than half have considered dividend recapitalizations or continuation vehicles to return capital in the meantime.2

In the middle market specifically, PwC describes the first half of 2026 as one of hesitation, driven by valuation gaps that neither buyers nor sellers are willing to bridge.3

This is not about where valuations settle. It is about one contributor to the gap that sellers tend to underweight, because it does not appear in the financials until a buyer's diligence team finds it.

A company acquired in 2020 or 2021 was, in many cases, running a core system chosen years before that. Five or six years of hold is long enough for that system to cross its vendor's end of support, or to be within a year of doing so. The pattern we see most often: an ERP or CRM whose vendor stopped selling it, then stopped enhancing it, then set a date after which it will not be patched; a virtualization layer whose licensing terms changed under new ownership; a field-service or warehouse platform whose integrator has moved on to other products.

None of this shows up in the quality-of-earnings report. All of it shows up in technology diligence, and it shows up as a number: the estimated cost and duration of a replacement the buyer will have to fund in year one. A buyer who expects to spend $2 million and eighteen months of management attention replacing a core platform will price that in, and will also price in the risk that the estimate is low. Sponsors have already become more cautious about targets where the technology picture is unclear; PwC notes that concern about how AI will reprice software has made buyers more careful across service-led sectors as well.1

The seller's position is weak at that point. The system cannot be replaced before close. The only argument left is that the buyer's estimate is too high, which is not an argument a seller wins.

The published end-of-support date is not the deadline. The deadline is the date by which selection and implementation must begin so that the replacement is live and stable before the process starts. We call this the Start Engagement By date, and it is what the EOL Radar is built to calculate.

For a mid-market ERP, a realistic runway is three to six months of selection and nine to fifteen months of implementation, followed by a quarter of stabilization. Call it eighteen to twenty-four months. A sponsor planning a process for the second half of 2028 would therefore need the decision made by the end of 2026 to present a buyer with a modern, stable platform and a clean integration story. A sponsor planning for 2027 has, in most cases, already missed the window for a replacement and should be planning for a different conversation: a documented, costed, partially executed transition that the buyer can see and underwrite.

That second option is worth more than sellers assume. A buyer will discount an unaddressed problem heavily because the range of outcomes is wide. A buyer will discount a documented plan with a signed vendor contract and a phase already live much less, because the range has narrowed.

• Run every core platform against its vendor's own lifecycle page and record the end-of-support date. Not the reseller's summary; the vendor's page.
• Back out the runway. Any platform whose Start Engagement By date falls before the planned process is a diligence finding waiting to happen.
• For each such platform, choose one of three positions and document it: replace before the process, begin replacement and present the plan, or accept the discount consciously. All three are legitimate. Silence is not.
• Have the integration map drawn. The most common finding in technology diligence is not the old system itself but the undocumented links between it and everything else. A one-page diagram removes more uncertainty than most memos.
• Separate the security findings from the platform findings. An unsupported system with no exposed vulnerabilities and a tested backup is a cost item. The same system exposed to the internet is a risk item, and buyers treat those differently.

There are portfolio companies for which replacement before exit is the wrong answer. If the hold is likely to extend for reasons unrelated to technology, a rushed implementation timed to a process that then slips is the worst of both outcomes: disruption during the hold and no credit at exit. If the platform is stable, isolated, and well understood, and the buyer universe is strategic acquirers who will consolidate onto their own systems regardless, the money is better spent elsewhere.

The mistake is not choosing to wait. The mistake is waiting without having done the arithmetic, so that the choice is made by the calendar rather than by the sponsor.

The exercise above takes a few days per company and can be run across a portfolio in a quarter. It tends to surface two or three companies where the timing is urgent and a longer list where it is not. That is a better use of an operating partner's attention than discovering the urgent ones in a data room.

The EOL Radar is free and covers the platforms mid-market companies most commonly run. If a portfolio company's situation raises questions the radar cannot answer, start a conversation and we will help you work through the timing.