Lumen Technologies has selected Amdocs to migrate its business support systems (BSS) to Google Cloud Platform, in a deal that puts a major US telecom operator's charging, billing and customer-management stack on public cloud infrastructure.

The announcement, reported by Telecompaper, names three parties: Lumen as the operator, Amdocs as the migration and BSS partner, and Google Cloud as the destination platform. The engagement covers Lumen's BSS estate — the systems that handle subscriber data, ordering, rating, billing and revenue management for its customer base.

What is actually moving?

The scope is Lumen's BSS layer, not its network infrastructure. Amdocs, a long-standing vendor of BSS/OSS software to communications service providers, will carry out the migration onto Google Cloud Platform. That means Lumen's operational software moves first; transport, fiber and network gear stay where they are.

For a carrier of Lumen's profile — a US provider of fiber, enterprise connectivity and managed services — BSS modernisation is typically the highest-value, highest-risk slice of an IT portfolio. Billing and charging systems sit directly in the revenue path. Any migration in this layer demands tight cutover discipline, and Lumen has handed that work to a specialist rather than attempting it in-house on hyperscaler infrastructure alone.

Why does the partner mix matter?

The deal follows a now-familiar enterprise pattern: the operator contracts one vendor to execute the cloud move while another vendor supplies the underlying platform. Amdocs brings the domain software and systems-integration muscle; Google Cloud supplies the compute, storage and managed services that will host the migrated BSS workloads.

That division of labour signals how large operators now approach public cloud adoption. Rather than a single supplier relationship, Lumen ends up with a three-way dependency — one for the software estate, one for the migration execution, one for the infrastructure. CIOs reading this deal should note the governance implications: multi-party accountability across a revenue-critical system migration requires explicit operational-responsibility boundaries from day one.

What does it signal for telecom IT spending?

A tier-one operator committing its BSS estate to a hyperscaler is a marker of where telecom IT budgets are heading. Carriers across markets have been shifting billing, CRM and charging workloads off legacy on-premise platforms toward public cloud, and Google Cloud has been competing hard for exactly these workloads against AWS and Microsoft Azure.

For Amdocs, winning the Lumen engagement reinforces its positioning as the migration and modernisation partner for operators adopting hyperscaler infrastructure — a role that matters as more carriers decide their legacy BSS platforms have reached end of life.

For Lumen, the move aligns with a broader infrastructure simplification agenda: consolidating fragmented BSS systems onto a managed cloud foundation reduces the operational overhead of maintaining dedicated hardware for revenue-critical software.

What comes next?

The immediate deliverable is the migration itself. Enterprise IT leaders tracking this deal will watch three things:

• Migration sequencing — which BSS components move first, and how Lumen handles parallel running during cutover
• Commercial structure — whether the deal is structured as a fixed-price migration, a managed-service annuity, or a hybrid
• Platform lock-in — which Google Cloud managed services the migrated BSS stack adopts, since that determines future portability

No financial terms, timeline or component-level scope have been disclosed so far. The confirmed facts are the parties and the destination: Lumen's BSS systems, Amdocs as the migration partner, Google Cloud Platform as the target environment.