Leaving Lumen Voice? Minimize disruption and maximize benefits
Planning a Lumen voice migration? Infobip’s simple five-step process keeps every number, site, and 911 address working. Our detailed guide will help you keep the conversations going.
Your Lumen voice contract has an end date, and that date is now the deadline for your next carrier decision. Whether you are looking for a Lumen voice alternative for one site or two hundred, the goal is the same – move your numbers, your SIP trunks and your emergency addresses with a planned approach that minimizes disruption to your customer communication.
This guide explains what changed, then walks through Infobip’s five-step migration framework – assess, provision, parallel run, port and optimize. We also consider the unique migration requirements of enterprises, mid-market businesses, and wholesale carriers.
What has Lumen announced about its voice services?
Lumen has stopped selling new enterprise voice services, although it is continuing to honor existing contracts. There won’t be a formal switch of their service, but contracts that would previously have been renewed will now have a natural end. Teams can use this date as the end point of their voice migration to a new carrier that is investing for the long term.
Why is your contract end date your deadline?
Work backwards from the date your Lumen contract ends. Every phase of a safe migration needs time, and you want to finish before you are paying for two systems longer than necessary, or before you are left without a contract at all.
A simple way to plan:
- Find your end date for each contract, including inbound/outbound, toll-free or 10dlc and any hosted Microsoft Teams service.
- Count back the time each phase needs, with extra room for number porting, depending on port out and port in supplier.
- Avoid busy periods. Do not schedule cutover during seasonal peaks, major campaigns or fiscal close.
- Start the assessment now, even if your end date is 12 to 18 months away. Starting early costs nothing. Waiting until the renewal notice arrives usually costs a month-to-month contract.
How do you migrate voice with mininal disruption?
Infobip’s migration follows five steps. Each one limits how many calls are at risk if something goes wrong.
| Step | What happpens | You move on when |
|---|---|---|
| 1. Assess | Map numbers, trunks, volumes and dependencies | You have a complete inventory and a timeline |
| 2. Provision | Build the new environment alongside the old | Trunks, routing and integrations are ready |
| 3. Parallel run | Old and new run side by side | Call flows and failover test cleanly |
| 4. Port | Move numbers in planned waves | Every number is live and validated |
| 5. Optimize | Improve and expand on the new platform | Ongoing |
Step 1: Assess the environment before you move it
Every successful migration starts with visibility. Before any number is ported or any route changes, map the current setup:
- Number inventory, including toll-free
- Call volumes and capacity requirements
- SIP trunking and routing setup
- PSTN dependencies, such as alarms, fax lines, and payment terminals
- Geographic footprint and sites
- Contract terms and end dates
- Operational workflows and future growth plans
Most other voice migration guides start at the pilot. Starting with the inventory and the contract review is what makes the later steps predictable.
If you want help with this step, Infobip offers a migration assessment.
Step 2: Provision the new environment in parallel
Next, prepare the destination before any traffic moves. Provision SIP trunks, PSTN connectivity, routing logic, and resiliency and failover plans. Confirm that your existing platforms are ready to connect.
Most enterprises do not need to replace the platform on top. Infobip’s US voice network, formerly Peerless Network, supports Operator Connect for Microsoft Teams, bring your own carrier (BYOC) for Genesys Cloud CX and Talkdesk, and Cloud Connect for Webex Calling. Teams, Webex or Genesys keeps running. Only the carrier underneath changes.
Building in parallel also lets you validate the setup before anything depends on it.
Step 3: Run in parallel and test before you switch
In a parallel run, the existing and new environments run side by side, so you can test real call flows with real conditions.
Confirm:
- Inbound call routing
- Outbound calling
- Toll-free traffic
- Call quality
- Failover behavior
- Number reachability
- Business-critical workflows
If something breaks, calls fall back to the old path instead of failing. A parallel run turns a migration from a plan into proof, and it removes the biggest objection to switching – the fear of committing before you know it works.
Step 4: Port numbers in planned waves
Porting is the is the most important part of the migration and needs the most coordination. Move numbers in waves, by site, region, branch, or business unit, whichever fits your operating model.
A well-managed port includes:
- Milestone tracking
- Port order management
- Reject resolution
- Carrier coordination
- Customer communication
- Post-port validation
Check emergency calling at the same time. Every number needs an accurate 911 location on the new platform, and each site needs its own address. Confirm in advance how locations are managed for remote and hybrid workers. Keep your rollback plan ready until every number is live and tested.
Typical timelines vary by number type and volume.
Step 5: Optimize so the new setup is better than the old one
Use these five questions to compare providers on the same footing:
| Question | What it is important |
|---|---|
| Do you start with an inventory and contract review? | Plans built on an inventory hold up better than plans built on estimates |
| Can I test in parallel before I commit? | Proof beats promises |
| Who handles the port, and how? | Porting is where migrations often stall |
| How do you manage emergency addresses per site? | It affects safety and compliance |
| What happens to my platform and my numbers? | You want to keep Teams, Webex or Genesys and every number |
If you are comparing Infobip with other providers, ask the same questions of us. Read more about how Infobip SIP trunking connects an existing phone system to a global network.
How do you get the most from voice after the move?
Moving carriers should not be the end of the project if you want to benefit from a platform that enable you to integrate your voice communication so that it works together with your messaging, WhatsApp calling, and Voice AI.
- Voice over messaging: WhatsApp Business Calling and Viber Business Calls bring conversations to channels your customers already use. Viber outbound calling needs case-by-case review.
- Voice AI agents: Voice AI agents extend IVR into natural conversations with handoff to live agents. They are currently in Early Access, so confirm availability for your markets.
- One customer view: On AgentOS, voice shares customer profiles and analytics with SMS, WhatsApp, RCS and chat.
Voice is a core product at Infobip and we are continuing to invest and expand our offering – so you can be assured that migrations headaches will be a thing of the past.
Which migration path fits your organization?
The overall migration framework remains the same, but there are considerations that depend on the size of your business and your specific requirements.
1. Enterprise: Keep your platform and move site by site
The challenge: Many sites, several platforms, and compliance requirements all change at once.
The approach: Keep Teams, Webex or Genesys. Port in waves by site, with emergency addresses set for each location, clear governance and a rollback plan for every wave.
Next step: Book a migration assessment with the Infobip team.
2. Mid-market: A short sequence without hiring specialists
The challenge: You have a small team and no time to learn a carrier change from scratch.
The approach: Follow the five steps in order, with portal-based setup through the Infobip Voice US Portal and a team that handles the port. You get a predictable timeline instead of an open-ended project.
Next step: Request a number inventory and timeline review.
3. Wholesale: Protect your customer base
The challenge: If you are a carrier, UCaaS or CCaaS provider, or channel partner with Lumen voice customers, you risk losing both the customers and the revenue when contracts end.
The approach: Infobip Voice US offers carrier services including local transit, toll-free, DIDs, telephone numbers, long distance and switched access, with portal and API provisioning and a partner program.
Next step: Talk to the Infobip carrier and partner team.
FAQ
Your contract end date sets your timeline. Lumen has stopped selling new enterprise voice services and is honoring existing contracts, without a final termination date announced. We recommend starting with an assessment 12 to 18 months before your contract ends.
Yes. A carrier change does not require a platform change. Infobip’s US voice network connects to Teams through Operator Connect, Genesys Cloud CX and Talkdesk through BYOC, and Webex Calling through Cloud Connect.
No, if you port them. Numbers move in planned waves, with each wave validated before the next begins. Confirm timelines early, because porting is the longest part of the project.
Your old and new voice environments run side by side while you shift traffic in steps, such as one site or number range at a time. If something fails, calls fall back to the original path. You move on when your call quality and routing checks hold steady.
Every number needs an accurate emergency address on the new platform. Check each site during the port, and confirm how remote and hybrid workers are handled.
Voice is a core product at Infobip, available through APIs and as part of AgentOS alongside messaging channels. We are continuing to invest in and enhance our voice offering.