Lumen Is Exiting Voice: What It Means for Your Business and How to Plan the Move

Lumen is exiting voice. It has stopped selling new voice services, and as of August 1 its partners can no longer sell or renew Lumen voice at all. Existing contracts run to term, but when they end there is nothing to renew into. If any part of your phone system runs on Lumen, you now have a fixed window to move, and the best time to start is before your renewal date makes the decision for you.

What's changing

The affected portfolio includes services such as Voice Complete, SIP trunking, PRI, POTS lines, and toll-free, along with hosted voice and UCaaS that Lumen resells. Lumen has framed the change as retiring legacy products in favor of newer ones, and it hasn't published a full list, so confirm which of your services are affected. The move is part of a broader shift toward fiber, network-as-a-service, and security, which we cover in our 2026 State of Connectivity report. It isn't a decision Lumen is likely to reverse.

What it means for you

The date that matters to you isn't Lumen's August 1 cutoff but your own contract's term-end, and that's the one that's easy to lose track of until a renewal notice lands. Pull it up now, because once service rolls month-to-month past that point, you inherit end-of-life pricing on a line Lumen no longer wants to run, with none of the leverage you'd have by negotiating ahead of time.

Two things make the timing tighter than it looks. First, porting is controlled by the carrier you're leaving: they set the cutover date, and a multi-site move is a project port that can run two to three weeks, longer when records don't match. That process now runs through a leaner Lumen support organization, so plan for it to take longer than your last port did. Second, be wary of the incumbent's upsell: the "just move to our newer product" offer usually beats your legacy rate while still sitting above market, and it quietly re-locks you to one carrier.

How big a project this is depends on what you run. A handful of POTS lines or a single SIP trunk is a straightforward swap. A contact center, a spread of DIDs, or 911 across multiple sites is where the real work lives, in the porting and testing, and where starting early pays off most.

You don't have to replace your phone system

A carrier leaving voice is not the same as your phone system breaking. Lumen is stepping back from one layer, the SIP and PSTN connectivity underneath your phones. Everything above it can stay: your PBX, your Microsoft Teams, Webex, or Zoom setup, and your phone numbers. Done well, this is a change your users barely notice.

The priority through all of this is continuity. Your main lines, toll-free, 911, and contact center have to keep working through the cutover, which is the real reason to start early. The safe approach is to stand up the new connectivity and run it alongside the old before you switch, and to keep the Lumen service in place until the new one is ported and tested. That sequencing is why the work needs to begin months before your term-end date, not in the final stretch.

What to do next

Use this checklist to get ahead of the change, whether you run it yourself or hand it to a partner:

• Inventory your Lumen voice services. List every Lumen voice product and location: main lines, SIP trunks, PRI, POTS, toll-free, and any hosted or UCaaS seats, with a note on what each one supports.

• Map the dependencies. Document how services, numbers, hardware, locations, and platforms connect so the transition can be planned as one coordinated program.

• Decide what stays and what changes. Preserve the hardware and architecture that still work, and change only what improves cost, flexibility, or resilience. Avoid replacing one form of carrier lock-in with another.

• Source quotes. Compare qualified providers on pricing, technical fit, implementation support, and contract terms rather than defaulting to the incumbent’s proposed replacement.

• Build the migration plan. Sequence porting, installation, testing, and cutover across the full environment, with clear ownership and a fallback path if anything goes wrong.

How Lightyear helps

That checklist is the work, and it's what Lightyear takes off your plate. We've managed telecom sourcing for more than 400 enterprises, and because we're independent and vendor-neutral, our recommendation comes down to your price and fit rather than any carrier relationship. Here's how we'd run your transition:

1. Audit what you have. Our engineers map your current voice environment and identify every affected service, piece of hardware, and location, so nothing surfaces late.

2. Design the right replacement. We support a like-for-like solution that rides your existing hardware, or a move to a more flexible, cloud-based setup, whichever better fits your environment and budget.

3. Source the best available pricing. We run a competitive bid across more than 1,200 qualified providers and price every option against our dataset of 100,000-plus RFPs and more than a million quotes, so you see the whole market rather than a shortlist.

4. Plan and manage the migration. We project-manage the cutover to keep downtime near zero and your main lines, toll-free, 911, and contact center live throughout.

After go-live, you keep the Lightyear platform to track inventory, spend, and renewals in one place, so the next product sunset or contract deadline reaches you early instead of as a surprise notice.

What this looks like in practice

One of Lightyear's enterprise customers caught its Lumen exposure on a routine monthly sync with their Lightyear team. Lightyear mapped the full call path in a single 30-minute session: SIP trunks over dedicated circuits into the customer's data centers, on-premise SBCs, and routing out to the cloud contact center, Teams, e-fax, and offshore partners.

Rather than just replacing the SIP trunks, Lightyear reframed the work as an architecture decision and captured the customer's target state: no customer-owned SBCs, DID pools kept intact, and carrier-side integration straight into the contact center and Teams. Lightyear recommended a shortlist of qualified service providers and each candidate was asked to price two designs, the target state and a like-for-like replacement, for a defensible cost-and-risk comparison instead of one vendor's pitch. 

Among the recommendations were a voice platform that large global carriers are themselves adopting and a provider that already underpins some of the customer's existing voice services. The low-volume edge cases, analog and specialty lines, went to specialists so they wouldn't hold up the core cutover.

The migration is a multi-month effort, sequenced on the customer's own timeline, with number porting planned ahead to minimize disruption.

Making it a planned move

Lumen's exit wasn't your choice, but it's a reasonable moment to move off legacy voice on your own terms, often at a better rate than you're paying today. The organizations that handle it best are the ones that start while they still have runway. If Lumen is anywhere in your voice environment, schedule a review with our team and we'll map what's affected and walk you through your options.