For the BroadWorks Head of Product

If you are deciding whether to stay on BroadWorks or migrate, the biggest risk is not the destination. The real risk is what you cannot see in your estate today, because the gaps you miss now surface mid-migration, where they cost the most to fix.

Most modernization programs do not stall because the strategy is wrong. They stall because of the complexity that builds up in a portfolio over years: the devices, features, and configurations no plan accounts for, because none of them are visible from the platform-level view. Device condition, license fit, and configuration complexity are what actually decide whether you stay or move, and most providers are making that call without the facts in front of them. The point of this piece is simple. You can put those facts in front of you, enterprise by enterprise, before you commit to a plan or a date.

When TekVizion ran EZDiscovery against a Tier 1 service provider’s BroadWorks estate, we surfaced device, feature, licensing, and configuration detail in minutes. The same picture would have taken months to rebuild by hand across multiple systems, if it could be rebuilt accurately at all.

“Every migration conversation we walk into starts with the same gap: the service provider and the platform do not share a common language for the estate. Our job is to give them one.”

No two service providers are configured the same way

A decade and more of provisioning decisions produces an estate that is one of a kind. No two BroadWorks service providers are configured alike, and the reasons are usually buried in choices made years, even decades, ago. Hierarchies were built differently. Some never adopted the enterprise or department structure at all. Features were turned on case by case. Each choice was reasonable at the time. Together they mean a migration is never a clean lift and shift. It is a reprovisioning exercise, and you cannot see its shape until the estate is mapped.

What surfaces when you map the estate

When you map a BroadWorks estate before a migration, this is what tends to surface:

• End-of-life and end-of-support devices
• Features that cannot carry across to the target platform
• Devices that cannot be reused on the target platform
• Features actually in use, versus what was provisioned
• Licenses that no longer match real usage
• Fragmented or over-complex call flows, and trunk complexity
• Undiscovered analog endpoints

Devices sit at the top of that list, but not for the reason most plans assume. End of life on its own rarely forces a decision. An end-of-life phone still registers and still makes calls, which is why a commercial buyer asks why change now. What actually shapes a migration is narrower: devices that are past end of support, no longer receiving firmware or security updates, and devices that will not meet the target platform’s security requirements. Those are what trigger truck rolls, the on-site engineer visits that are the biggest cost and the most visible disruption to your customers. In one BroadWorks estate of around 40,000 devices across several hundred enterprises, more than a quarter were at or past end of life, and the share that genuinely affects a migration is the set that is also out of support or carries a security risk.

Feature usage sits right behind devices. A migration breaks when a capability a customer relies on every day does not carry across. Knowing what each enterprise actually uses, rather than what was provisioned years ago, is what keeps your customers working the way they expect through the move.

What this gives you

Once you can see the full picture, enterprise by enterprise, the estate stops being the unknown in the room. You can weigh cap-and-grow against migrate on evidence, decide which enterprises are ready and which need work first, and see what will not carry across before it derails a cutover, rather than after. The picture informs the decision. You still make the call.

Making the estate legible

Modernization, at its core, is less a migration problem than a question of how well the estate is understood. EZDiscovery connects read-only to a BroadWorks environment and returns an enterprise-by-enterprise picture of how the platform is actually configured and used: which devices are end of life or out of support, where licenses no longer match real usage, which call flows have grown more complex than they need to be, and which features and devices will not carry to the target platform. That picture turns a migration from a guess into a sequenced plan, and it lets you move without putting production at risk.

Service providers think in customers, services, and revenue. Platforms think in users, features, and configurations. Modernization only happens at scale when both sides share a common language for the estate, and closing that gap is what EZDiscovery is built to do.

See what EZDiscovery surfaces in your portfolio

Service Provider Annual Subscription with a 90-day risk-free deployment. Built for carriers running continuous discovery across the book.

Contact: sales@tekvizion.com