Vol. III · No. 128 Independent LegalTech Analysis Wednesday, June 17, 2026

The Legal Stack

← Analysis Analysis · Legal Operations

Why Law Firm Mergers Keep Failing (And What Tech Has to Do With It)

The legal press loves a merger announcement. Two firms shake hands, issue a joint statement about "complementary practices and shared culture," and promise seamless service continuity for clients. Then, eighteen months later, partners are quietly lateraling out, billing rates are a mess, and nobody can...

The legal press loves a merger announcement. Two firms shake hands, issue a joint statement about "complementary practices and shared culture," and promise seamless service continuity for clients. Then, eighteen months later, partners are quietly lateraling out, billing rates are a mess, and nobody can pull a unified client report. The merger hasn't failed yet, officially. But it's failing.

Technology is rarely named as the culprit. It should be.

The Practice Management Problem Nobody Wants to Solve

When Dentons absorbed another mid-market firm in its relentless global expansion, the operational integration challenge wasn't philosophical — it was infrastructural. Getting two firms onto a single practice management system is genuinely hard, expensive, and politically loaded. Partners who have used Elite Enterprise for fifteen years don't quietly migrate to Aderant because someone in New York decided it was time.

The core incompatibility problem runs deeper than software preference. Practice management systems encode the operational DNA of a firm. Billing structures, matter numbering conventions, timekeeper hierarchies, rate card logic — these aren't just settings you export and import. They reflect fundamental decisions about how work gets organized and how revenue gets recognized. When Hogan Lovells merged with Lovells and legacy Baker & McKenzie in successive waves of growth, the billing system harmonization reportedly took years and consumed resources that were never budgeted in the original deal economics.

The modern stack has made this worse, not better. Firms are no longer running a single monolithic system. They're running a practice management platform integrated with document management (often iManage or NetDocuments), e-billing (TyMetrix, Passport), CRM (InterAction or its competitors), matter budgeting tools, and increasingly, AI-powered contract review and knowledge management systems. Each integration point is a custom-built bridge. When you merge two firms, you don't just merge two practice management systems — you merge two ecosystems of brittle integrations, and most of them break on contact.

Client Data Portability Is a Liability, Not Just a Logistics Issue

Here's the problem that should be keeping general counsel up at night during merger negotiations: client data portability exposes both legacy firms to liability that nobody is formally pricing into the deal.

Under the ABA Model Rules, specifically Rule 1.6 on confidentiality and the portability principles embedded in Rule 1.16, clients have rights over their data that don't bend to accommodate merger convenience. When two firms consolidate their document management environments, they are necessarily commingling data sets across matters, clients, and timeframes. The conflict check database alone is a minefield. Client A may have been adverse to Client B in litigation handled by the firm you just absorbed. You now represent both. The technical merge surfaced the conflict; the question is whether your systems caught it before a partner took a call.

GDPR adds an international dimension that US-headquartered firms consistently underweight. If either legacy firm has handled matters for EU-based clients — and at AmLaw 100 scale, they almost certainly have — the merger triggers data transfer obligations under Articles 44-49 of the GDPR. A merger isn't a simple "business continuation" event for purposes of lawful data processing. The new entity needs to establish its own lawful basis for holding that client data. Firms that haven't mapped this exposure before signing are creating regulatory liability from day one of integration.

The California Consumer Privacy Act creates parallel obligations for California-based clients and any firm with California operations — which is to say, virtually every major firm.

Due Diligence on Tech Assets Is Still an Afterthought

The transactional due diligence in a law firm merger would embarrass a first-year associate if applied to a client M&A deal. Firms scrutinize lateral partner books of business, real estate obligations, and malpractice tail coverage. Technology asset due diligence? It gets a checklist item and a phone call with the IT director.

This is structurally backwards. The technology estate of a modern law firm is a significant liability, not just an asset. Software licensing agreements frequently contain change-of-control provisions that void enterprise pricing or require renegotiation upon merger. A firm running iManage or Relativity under an enterprise license negotiated three years ago may find that agreement technically terminated by the merger transaction. Vendors know this. The renegotiation leverage shifts entirely to them the moment a merger is announced publicly.

Cybersecurity posture deserves its own diligence track. The FBI and CISA have both documented law firms as high-value targets for ransomware and state-sponsored intrusion, precisely because they hold sensitive client data with historically weak perimeter security. When Campbell Conroy & O'Neil suffered a ransomware attack in 2021, it demonstrated that even firms representing Fortune 500 companies can have exploitable gaps. Merging two firms means merging two attack surfaces before you've merged two security programs. That window of vulnerability — when systems are connected but not yet unified — is exactly when threat actors probe.

What Actually Works

The firms that navigate technology integration successfully share one characteristic: they make a hard decision early and enforce it. Decide which practice management system survives, which document platform is primary, and which CRM wins. Then fund the migration properly, hire a dedicated integration project management office, and give it a realistic 24-month runway rather than a 90-day press release timeline.

Eversheds Sutherland's integration after the 2017 merger between Eversheds and Sutherland Asbill & Brennan drew praise in legal operations circles precisely because the combined firm made firm architectural decisions and communicated them clearly, rather than running parallel systems indefinitely as a political compromise.

The Honest Conclusion

Law firm mergers fail — or quietly underperform for years — because partners talk about culture and clients while ignoring the operational machinery that makes client service actually work. Technology isn't a back-office concern you hand to the CIO after the ink dries. It's a strategic due diligence item, a liability exposure category, and a post-merger execution risk that deserves senior leadership attention from the first conversation.

The next firm that treats its technology stack with the same rigor it applies to lateral compensation negotiations will be the one that actually delivers on the integration promise. The others will keep issuing press releases and losing partners.