Blog
Buying a Fiber Network? Here's What You Actually Inherit
What you actually inherit when you buy a fiber network.
You inherited their hardware, their processes and their data. You should not have to standardize all three before the deal starts paying for itself.
The deal closed. The integration didn't.
The clock on the synergies you underwrote starts ticking before any of it is sorted out. The usual options are both bad: run parallel stacks and pay for two operations, or run a replatform project and push revenue synergies eighteen months out.
The answer: AEX is multi-vendor at its foundations, with Nokia, Calix, ZTE, Zhone, Huawei, Ubiquiti and eero, plus any TR-069 device, built on per-vendor activation knowledge from more than a decade of running networks.
Each estate runs different hardware.
Thousands of devices you didn't choose.
Two ways of charging the same subscriber.
The biggest hidden cost in the deal.
What that means in practice
Provision across mixed hardware in real time, layer 2 and layer 3, with automatic rollback.
AEX Software
Bring acquired subscribers onto one engine covering recurring, prepaid, postpaid and wholesale.
AEX Software
Run both estates the same way without forcing either onto the other's processes.
AEX Software + Field Service
You are never locked to one OEM by your OSS.
AEX Software
The onboarding question
Data migration
Moving an acquisition's non-normalized data is the highest hidden cost in any deal like this. AEX is investing in data transformation and onboarding orchestration to turn migration from a project into a process.
Commercial
Per-active-subscriber pricing means the cost of an acquired base tracks the base itself, so integration doesn't carry a fixed platform penalty before the synergies land.
Keeping your equipment
Yes, if your OSS/BSS can provision and monitor the equipment already in service. Start by checking the exact models and firmware in the acquired network. Then test a small group of subscribers before migrating the rest. Where equipment isn't supported, plan a targeted upgrade or keep the existing management system in place during the transition.
Record OLT and ONT models, firmware, and provisioning methods. Ask the platform vendor to demonstrate activation and rollback on the models you actually run.
Match service addresses, accounts, plans, and devices before importing data. Resolve duplicates and mismatches before they affect live orders.
Use a pilot group to verify that existing service stays active, new orders provision correctly, and the first invoice reflects the right plan, balance, and billing date.
Compare activation failures, support tickets, and invoice exceptions after each batch. Agree in advance on what would trigger a pause or rollback.
Use what you need
Each works on its own alongside the vendors you already have.
Run the business
One OSS/BSS for both estates, with billing that handles every model you inherited.
Get crews there
One scheduling and mobile workflow for every crew, old and new.
Run the network
NOC, helpdesk and equipment coverage across the combined footprint.
Where you are
New network
Get to your first invoice without assembling a stack first.
Growing fast
Close the gaps between systems without a rip-and-replace.
Shared infrastructure
Run every ISP on your network through one interface.
Blog
What you actually inherit when you buy a fiber network.
Read the blog →
Blog
How connected OSS/BSS takes an order through to cash.
Read the blog →
Blog
Carrier services every fiber operator needs to plan for.
Read the blog →Yes, if your OSS/BSS can provision and monitor the equipment already in service. Start by checking the exact models and firmware in the acquired network. Then test a small group of subscribers before migrating the rest. Where equipment isn't supported, plan a targeted upgrade or keep the existing management system in place during the transition.
Usually a mix of OLTs and ONTs from different vendors, subscriber and billing records in another system, its own provisioning methods, and support processes built around them. Knowing exactly what you've inherited, down to models, firmware and data quality, is the first step in planning the integration.
Not on day one. Many operators keep the acquired billing running during the transition, then move subscribers in batches. AEX Software bills recurring, prepaid, postpaid and wholesale services from one engine, so acquired plans can be brought across without rebuilding them.
Pilot first, then migrate in batches. Confirm that existing service stays active, new orders provision correctly and the first invoice is right for the pilot group, and agree in advance what would trigger a pause or rollback. AEX provisions across mixed hardware with automatic rollback.
It depends on the size of the base, the equipment you've inherited and the state of the subscriber data. Migrating in batches lets you start running acquired subscribers on your own systems early, rather than waiting for one big cutover.
Yes. AEX Network Services provides NOC monitoring and a subscriber helpdesk that can cover the acquired network while it's being integrated, either alongside AEX Software or on its own.