Nobody budgets for the second system

Every merger model accounts for synergy. Almost none accounts for the fact that the losing platform doesn’t actually go away — it just goes quiet, and stays on the invoice.

Most post-merger IT reviews start the same way — with a slide that says the integration is “complete,” followed by a budget conversation that quietly proves it isn’t.

The deal team did its job. The org chart is unified, the go-forward platform is chosen, the press release went out. But somewhere in a cost center nobody’s watching closely, a second ERP is still running. A second CRM. A second HR system nobody logs into except payroll, twice a month, because three years of employee records are still sitting in it.

Nobody planned to keep paying for it. It just never got turned off.

The synergy model has a blind spot

The pattern is consistent across industries. The synergy case in the deal model assumed clean consolidation — one platform wins, the other is decommissioned, the savings hit the P&L on schedule. In practice, decommissioning stalls almost every time, and it stalls for reasons that have nothing to do with technical difficulty.

• Legal hold on records tied to active litigation or investigations
• Regulatory retention windows that run years, sometimes decades, past the deal close
• A handful of business users who still need occasional lookup access to old orders, claims, or invoices
• The person who owned the application left the company during the integration and nobody re-assigned the decision
• Nobody can fully map the downstream reports and integrations quietly still pulling from it

None of these are good reasons to keep an entire production environment running. But each one, individually, is a good enough reason for whoever’s in the room to say “let’s revisit this next quarter.” And next quarter becomes next year.

“We completed integration two years ago. We still support 47 applications from the acquired company.”

It’s a familiar refrain across post-merger IT organizations, regardless of industry. Two years post-close. Dozens of applications. Every one of them technically retirable. None of them actually retired — because retiring the application feels riskier than paying to keep it breathing.

The real question isn’t “which platform wins”

That decision gets made fast, usually inside the first six months. The harder question is what happens to the historical data sitting inside the platform that lost. Auditors still need to find it. Legal still needs to produce it on request. A few business users still need to look something up from three systems ago.

Most organizations solve this the expensive way: keep the whole environment alive — licenses, infrastructure, specialized support contracts, the works — just to preserve access to a shrinking sliver of records that actually get touched. It’s a wildly inefficient trade. Full production costs, to protect maybe 2% of the data anyone will ever look at again.

The more effective approach separates the two problems entirely. Archive the historical data on its own, with full compliance and legal-hold intact, keep it instantly accessible to the people who need it, and retire the application underneath it. The record survives. The cost doesn’t.

Why this is the fastest synergy win available

Of everything on a post-merger IT roadmap, application retirement is unusual in one specific way: it doesn’t require changing how anyone works. You’re not migrating users to a new system, retraining anyone, or touching an active business process. The decision about which platform survives has already been made. The only remaining work is preserving what’s left behind — which is a data problem, not a transformation problem.

That’s exactly why it tends to move faster than anything else on the integration roadmap, and why finance teams like it: the ROI case is concrete and provable within a single fiscal quarter, not a multi-year transformation program.

What actually breaks the inertia

The organizations that make progress tend to start the same way: pick one application. Not the biggest, not the most political — the one where the model can be proven cleanly. Archive it, retire it, show the number on a slide. That single proof point does more to unlock the next twenty applications than any amount of top-down mandate. Once finance sees a real dollar figure attached to a retired system, the rest of the portfolio review gets a lot easier to schedule.

The applications aren’t the hard part. The inertia is. And inertia is beatable with one good example.

DISCLAIMER: THE CONTENT, VIEWS, AND OPINIONS EXPRESSED IN THIS BLOG ARE SOLELY THOSE OF THE AUTHOR(S) AND DO NOT REFLECT THE OFFICIAL POLICY OR POSITION OF SOLIX TECHNOLOGIES, INC., ITS AFFILIATES, OR PARTNERS. THIS BLOG IS OPERATED INDEPENDENTLY AND IS NOT REVIEWED OR ENDORSED BY SOLIX TECHNOLOGIES, INC. IN AN OFFICIAL CAPACITY. ALL THIRD-PARTY TRADEMARKS, LOGOS, AND COPYRIGHTED MATERIALS REFERENCED HEREIN ARE THE PROPERTY OF THEIR RESPECTIVE OWNERS. ANY USE IS STRICTLY FOR IDENTIFICATION, COMMENTARY, OR EDUCATIONAL PURPOSES UNDER THE DOCTRINE OF FAIR USE (U.S. COPYRIGHT ACT § 107 AND INTERNATIONAL EQUIVALENTS). NO SPONSORSHIP, ENDORSEMENT, OR AFFILIATION WITH SOLIX TECHNOLOGIES, INC. IS IMPLIED. CONTENT IS PROVIDED "AS-IS" WITHOUT WARRANTIES OF ACCURACY, COMPLETENESS, OR FITNESS FOR ANY PURPOSE. SOLIX TECHNOLOGIES, INC. DISCLAIMS ALL LIABILITY FOR ACTIONS TAKEN BASED ON THIS MATERIAL. READERS ASSUME FULL RESPONSIBILITY FOR THEIR USE OF THIS INFORMATION. SOLIX RESPECTS INTELLECTUAL PROPERTY RIGHTS. TO SUBMIT A DMCA TAKEDOWN REQUEST, EMAIL INFO@SOLIX.COM WITH: (1) IDENTIFICATION OF THE WORK, (2) THE INFRINGING MATERIAL’S URL, (3) YOUR CONTACT DETAILS, AND (4) A STATEMENT OF GOOD FAITH. VALID CLAIMS WILL RECEIVE PROMPT ATTENTION. BY ACCESSING THIS BLOG, YOU AGREE TO THIS DISCLAIMER AND OUR TERMS OF USE. THIS AGREEMENT IS GOVERNED BY THE LAWS OF CALIFORNIA.