Broadband M&A Integration: What Changes When the Deal Closes (and What Can't)

The deal closes on a Tuesday. By Wednesday morning, you're running two companies.

That's not a metaphor. You have two billing systems producing revenue that have to be reconciled. Two NOC (network operations center) teams watching two networks that were never designed to share visibility. Two support queues fielding calls from subscribers who may not know yet that something's changed. Two field teams working from different dispatch tools, different job formats, and different equipment standards. None of it pauses while you work through the integration plan.

This is the part of broadband M&A that is less frequently talked about. The deal content is everywhere: how to find targets, how to structure offers, how to navigate the regulatory filings, how to run due diligence. What happens after the close is a different conversation entirely, and it's one that operators commonly enter without a real plan.

Sonar wrote the M&A Transition Playbook to change that. It's built on the experience of operators who lived it, and it's educational first: the frameworks, timelines, and checklists are designed to be useful whether or not you ever talk to Sonar. Here's the thinking behind it.

The First 90 Days: Where Broadband M&A Integration Often Fails

The risk was never the deal itself. It's the first 90 days after close. Most acquisitions don't fall apart in the boardroom, they wobble in the quarter after close, in the operational details that are easy to underestimate when the finance model looks clean.

Billing is the highest-risk domain. It touches revenue directly, and it produces subscriber-facing consequences the moment it fails. The most dangerous moment in a billing transition isn't the migration itself. It's the stretch when both systems are running at once and revenue is being tracked in two places. Double billing happens. Missed billing happens. Service plans that exist in one system with no clean equivalent in the other create subscribers who fall through the cracks, and those errors surface weeks later as disputes and cancellations.

Churn is the second major risk, and unlike billing, it doesn't spike on day one. It concentrates in a specific window, roughly days 20 to 90 after close, when billing changes reach subscribers, support quality dips as teams absorb higher call volume, and the first migration errors become visible. Subscriber churn that starts in week three and runs for six months isn't a customer service problem. It's a valuation problem.

Network and field operations are the third risk area, and this is where integration problems get physical instead of just financial. An acquiring NOC often has full visibility into its own network and none into the one it just bought, so issues in the new footprint get discovered by subscriber phone calls instead of monitoring alerts. Field operations, frequently the last thing anyone plans for, are often the first thing to break, because crews can't create work orders without accurate address records and equipment templates for the acquired territory.

Why Due Diligence Misses OSS/BSS Risk

Most due diligence is finance-led, and that's a gap. The OSS/BSS (the billing, provisioning, and network management systems that run an ISP) platform a target runs on tells you almost as much about the real risk in a deal as the balance sheet does.

A few questions worth asking:

• Is the subscriber count something you can trust, or is it an estimate dressed up as a fact?
• Is billing clean, or are uncollected balances hiding errors that will surface later as disputes?
• How many disconnected systems is this operator really running to handle billing, network, field ops, and support? That number predicts integration cost more reliably than anything in the org chart.

An operator who struggles to produce clean data under due diligence conditions is telling you, before you've signed anything, what integration is going to feel like.

The 90-Day Framework: Protect, Stabilize, Integrate

It's a sequence, not a scramble. The playbook is organized around a simple principle: protect what touches subscribers first, build infrastructure second, and integrate third. Deviating from that order is the single most common cause of post-acquisition operational problems.

1. Protect (Days 1-30): Continuity, not integration. Every system that worked before close keeps working. Billing reconciles, the NOC has visibility, support knows where calls route, dispatch covers the new territory, and subscribers hear from you at close rather than two weeks later.
2. Stabilize (Days 31-60): Validate the data, build the migration plan with a designated go/no-go owner, and stand up the consolidated financial reporting your board will ask for.
3. Integrate (Days 61-90): Migrate to the system of record, retire legacy on a deliberate timeline, train the acquired team, and run a formal review. Complete legacy retirement is realistic within four to six months for most Tier 2 and Tier 3 acquisitions when preparation starts before close.

The specific dates shift with subscriber count, data quality, and team capacity. The sequence doesn't.

BEAD-Funded Networks and Broadband M&A: What Changes

BEAD (the federal Broadband Equity, Access, and Deployment program) adds a wrinkle worth planning for, because BEAD and M&A are increasingly the same conversation. Operators who've won BEAD awards are expanding, and some of that expansion is acquisition. Operators building BEAD-funded networks are increasingly acquisition targets themselves, since a buyer can pick up a buildout that's already cleared the riskiest part of construction. Running an active BEAD build and an acquisition integration at the same time is genuinely complex: compliance reporting and subscriber migration both need to work off the same clean data, at the same time, without either one blocking the other.

The Legacy Billing Trap: Why Retirement Timelines Slip After a Merger

Here's the most common failure mode in broadband M&A integration, and one of the most avoidable: the integration goes well enough that everyone moves on to the next priority. A year later, 800 subscribers are still on the legacy billing system, still being reconciled by hand every month, because nobody was ever given explicit ownership of finishing the job.

The fix isn't more technology. It's a hard retirement date, treated as a business milestone instead of a technical to-do.

M&A Readiness Check: Is Your OSS/BSS Platform Prepared?

Whether you're the acquirer, the target, or an operator preparing for either, one question sits underneath all of it: is your platform ready to absorb, or be absorbed, without creating operational risk?

Sonar's playbook ends with a readiness check you can score in a few minutes, across billing, network, subscriber data, field operations, risk planning, and audit readiness. It's a diagnostic. Use it before a deal to find the gaps, or during an integration to track what you've resolved and what you're still carrying.

A unified OSS/BSS platform doesn't make an acquisition easy, but it removes an entire category of integration work. When billing, provisioning, network, inventory, and support share one data layer, a subscriber and everything attached to them moves together instead of in separate, error-prone handoffs.

Read the Whole Thing

The full M&A Transition Playbook covers all of this in depth: billing continuity, network consolidation, subscriber experience, field operations, the system of record, BEAD and regulatory considerations, the due diligence audit trail, the consolidation timeline, the failure modes that appear most often, and the readiness checklist.

Get the M&A Transition Playbook →

Book a meeting → if you want to talk through how your current platform stacks up against an acquisition scenario.