Why is the first quarter after close the risky part?
The value of an acquired ISP is its subscriber base and the revenue it produces. That value is most exposed right after close: invoices change format, phone numbers and portals change, staff are learning new systems, and competitors know it. Every error in the first cycle becomes a call, and some of those calls become cancellations.
Some vendors publish dedicated M&A consolidation playbooks for this phase. Whatever tooling you use, the work falls into the same six areas.
How should billing data be migrated after an acquisition?
Billing is where integration mistakes are most visible: a wrong balance, a missing credit or a duplicated charge lands on every affected subscriber at once. Migrate in a way that can be checked before it goes live.
- 1.Extract subscribers, contracts, plans, balances, credits and installed equipment from the acquired system.
- 2.Verify every record against the live base: counts by plan, balances in total and per account, active services per address.
- 3.Run a parallel cycle: issue one full billing cycle in the new system alongside the old one and compare invoice by invoice.
- 4.Cut over only when the parallel cycle matches, and keep the old system readable for disputes afterward.
Taxes and surcharges deserve their own check. The acquired company may have applied sales tax, USF and E911 differently, and a sudden change on the invoice needs an explanation.
What should subscribers be told, and when?
Subscribers do not need the deal story. They need to know what changes for them and when: the name on the invoice, how and where to pay, the support number and portal, and whether their price or plan changes. Tell them before the first new invoice arrives, repeat it on the invoice itself, and brief support staff with the same script.
If prices or plans will change, separate that news from the ownership change. Two changes landing in the same message read as one bad surprise.
How do you protect the base from churn and support spikes?
Expect support volume to rise around the first new invoice and any portal or payment change. Plan staffing for it, publish answers to the obvious questions, and handle routine cases such as balance questions, password resets and payment links automatically so people are free for real problems.
Watch churn weekly rather than monthly during the transition, by service area and by reason. Early cancellations clustered around one change tell you what to fix while it is still cheap. Structured disconnection reasons make that possible.
| ID | Event | Detail | Status | Value |
|---|---|---|---|---|
| #48201 | Auto-suspend | Past due · 4 days · policy DUNN-04 | Suspended | −1 service |
| #48202 | Auto-reconnect | ACH payment cleared · $74.00 | Reconnected | 2 min |
| #48203 | Cycle invoicing | Taxes, USF and E911 applied · emailed | Issued | 2,418 docs |
| #48204 | Payment reconciled | Paid via reminder link · matched to invoice | Cleared | +$74.00 |
What happens to field operations, inventory and the network?
Field and network work is where two operations physically meet. Technicians from both companies share trucks, warehouses and appointment windows, and a subscriber who sees a missed visit in the first month remembers the new owner for it. The goal for this phase is simple: every piece of equipment accounted for, every appointment confirmed, and suspension and reconnection working the same way on the first day of the new billing rules as they did on the last day of the old ones.
- Inventory reconciliation
- Count equipment by warehouse and truck, and match installed CPE and ONUs to the addresses in the billing records.
- Field scheduling
- Merge technician calendars and appointment windows early, and confirm every appointment during the transition to avoid failed truck rolls.
- Provisioning cutover
- Move RADIUS, TR-069 and OLT/GPON provisioning so suspension and reconnection keep working on the new billing rules.
- Network documentation
- Confirm which subscribers sit behind which sector, tower or OLT before the first outage under new ownership.
What does a 30/60/90-day integration plan look like?
| Window | Billing and data | Subscribers and support | Field and network |
|---|---|---|---|
| Days 1–30 | Extract and verify records; map plans, taxes and surcharges | Announce what changes; brief support; publish FAQs | Inventory count; document network topology |
| Days 31–60 | Parallel billing cycle; fix every mismatch | Watch churn weekly by reason and area; staff for the first invoice | Merge schedules; prepare provisioning cutover |
| Days 61–90 | Cut over billing; keep old system readable | Proactive outreach to at-risk subscribers | Cut over provisioning; confirm suspend and reconnect |
Where does Inerxia fit?
Inerxia migrates subscribers, contracts, balances and equipment, verifies every record against your live base and runs a full cycle in parallel before anything goes live. Four weeks to your first full cycle; migration, training and support are included. The Operating System then runs billing, dunning, inventory, ticketing and provisioning on one subscriber record.
During the transition, the support agent absorbs routine calls and the retention agent flags at-risk subscribers early. Compare platforms on the comparison page.