A telecom carrier switch is not a simple plug-and-play migration. It's a complex orchestration involving number porting authorities, circuit provisioning timelines, contract termination logistics, and dozens of moving pieces that can fail independently. We've managed over 200 carrier migrations. In nearly every one, something tried to go wrong. Most of the time, because we had a plan.

The companies that suffer the worst outages during carrier switches are not the ones lacking technical skill. They're the ones who underestimated the number of dependencies woven through their telecom infrastructure. They unplugged the old service before confirming everything actually moved. They missed that their elevator system was tied to an old dedicated line. They discovered mid-switch that an auto-renewal clause was still active on a contract they thought they were exiting.

This guide walks you through every stage: how to audit your current footprint, how to navigate the porting process, how to run old and new services in parallel, and how to execute a cutover with minimal risk. The stakes are high—a botched carrier switch can take out phone service for your entire organization for hours or days. This playbook exists so that doesn't happen to you.

Why Carrier Switches Fail

Most carrier switch failures fall into one of several categories. Understanding these failure modes is the first step toward avoiding them.

Number porting failures. A number port is not a one-step process. It's a multi-week dance between your old carrier (the losing carrier), your new carrier (the gaining carrier), and the regulatory authority (the local number portability administrator). Here's where it breaks: The Letter of Authorization has a typo in a phone number field. The account holder's signature on the LOA doesn't match the name on the account. The port-out date changes at the last minute because the old carrier disputes the request. The new carrier's back-office system doesn't recognize the toll-free routing instructions. You request a port-out before signing a contract with the new carrier, so the new carrier cancels the port-in order and your numbers snap back to the old carrier. You discover on cutover morning that the FOC (Firm Order Commitment) date the new carrier gave you was aspirational, not firm.

Installation delays. The new circuits don't show up on time. The fiber installer is backed up. The local exchange carrier hasn't provisioned the loop. The new carrier scheduled the installation in a two-hour window that falls during your maintenance window but across two different time zones—and "maintenance window" means something different to the installer than it does to you. You discover on day 14 that the circuit is still "pending activation."

Forgotten dependencies. Your elevator system uses a dedicated POTS line on the old carrier. Your alarm company's monitoring service is tied to an old analog line. Your fax server runs on a different circuit than your main phone trunk. Your credit card terminal dials out over the old carrier's network. None of these got migrated because no one documented that they existed. You disconnect the old service and find out when the elevator gets stuck or the alarm stops reporting.

Contract and billing traps. Your three-year contract with the old carrier doesn't actually end when you think it does—there's a 12-month auto-renewal clause you missed. You pay an early termination fee you didn't budget for. Or the opposite: you go dormant on the old contract without formally terminating, and six months later you're being billed for minimum commitments on a line you haven't used in months.

Miscommunicated cutover windows. Everyone agrees on a cutover plan, but "9 a.m. Pacific" gets misinterpreted as 9 a.m. in the carrier's home time zone. The old carrier disconnects the service at 9 a.m. Eastern while you're still testing. The new circuit isn't ready yet. Thirty minutes of downtime nobody planned for.

Pre-Switch Audit: Know Your Footprint

Before you talk to a new carrier, you need to know exactly what you're moving. Pull your last 12 months of bills from your current carrier. Print them. Go line by line.

Inventory every service. List every phone number, every circuit, every trunk line, every add-on service. Not the summary page—the detailed billing section. Document:

Identify what can't port. Some services don't port cleanly. Dedicated circuits from the local exchange carrier (LEC) physically tied to the old carrier's infrastructure may need to be rebuilt. Certain business services packages are carrier-proprietary and require a redesign on the new carrier. Specialized services like managed call recording or unified communications features may not exist on the new carrier in the same form.

For each of these, determine: Can this service migrate at all? If yes, does it require new hardware or configuration? Does it require a separate implementation project? Will there be a gap in service during the migration?

Check all contract dates. Don't rely on what the salesperson told you. Pull the actual contract for your current service. Look for:

This audit typically takes 4–6 weeks depending on the complexity of your service footprint. It's not optional. Organizations that skip this step invariably discover something critical during the cutover.

Number Porting: The Technical Reality

Number porting is regulated at both the federal and state level. The process is standardized, but the details matter intensely because small errors cause the entire port to fail.

The Letter of Authorization (LOA). This is the legal document that authorizes the new carrier to request the port from the old carrier. It's not a casual form. Here are the fields that cause the most rejections:

A single error in the LOA sends it back to you for correction, adding 3–5 business days to the timeline.

Firm Order Commitment (FOC) date. This is the date the new carrier promises to be ready to accept the port. It's called "firm," but it's actually aspirational. Carriers miss FOC dates regularly. The realistic FOC is 7–21 business days after the new carrier submits the LOA to the old carrier, depending on your local regulatory body and call volume. The old carrier has five business days to object or accept the port. If they object, they must provide a reason, and you have a window to dispute or correct it. If they don't respond within five business days, the port proceeds by default.

The porting window. On the FOC date, the actual port happens during a specific window, usually 6 a.m. to 10 a.m. in your local time zone. This window is when the numbers are pulled from the old carrier's infrastructure and provisioned on the new carrier's. During this window, calls to those numbers may fail, ring to the wrong place, or behave unpredictably. This is why you must have an active alternative (like a call forwarding to a mobile number or a second carrier) in place before the porting window.

Port failures and snap-back. A port can fail for several reasons: the old carrier didn't release the numbers, the new carrier didn't accept them, or the routing didn't activate properly. If a port fails, the numbers snap back to the old carrier automatically within a few hours. You discover this when calls don't reach the new system. At that point, you have to troubleshoot with the old carrier to understand why they didn't release the numbers, correct the issue, and request a new FOC date. This adds 7–21 more business days to the timeline.

Toll-free vs. local porting. Toll-free numbers (800, 888, 877, etc.) port differently than local numbers. Toll-free ports use NPAC (Number Portability Administration Center) and typically take 7–10 business days. Local number ports use state-specific LNP administrators and can take 14–21 business days. If you have both, you're coordinating two separate porting processes with potentially different timelines.

Plan for the worst case: 21 business days, a failed port requiring a re-do, and a second round of porting. That's 42 business days—nearly three months. Many organizations don't allow for this in their cutover planning and get caught without an active alternative service.

Parallel Running: Old and New Service Simultaneously

The safest carrier switch runs old and new service in parallel for 2–4 weeks before the cutover. This gives you time to test the new system, validate that all numbers ring through, and confirm that all integrated services work.

What can run in parallel. Generally, you can have active service on both carriers as long as the numbers aren't in conflict. If the old carrier has your main DID block (555-0100 to 555-0199) and the new carrier will have the same block, you can't have both active simultaneously—the phone system won't know which carrier to send a call to.

Instead, run parallel like this: Weeks 1–2, port a subset of your numbers (maybe your main number, plus a test block) to the new carrier. Keep them active on the new carrier's system while the old numbers remain on the old carrier. Route calls to the new numbers to the new phone system. Route the old numbers to a forwarding system that bridges to the new system. This way, your external contacts can call your new numbers (which are live on the new carrier and ring to the new system), and callers reaching the old numbers get forwarded seamlessly.

As you validate that the new system works, gradually migrate more services. During this time, you're not at risk of total outage—if something fails, the old carrier is still live.

What can't run in parallel. You can't have the same DID on two carriers at once. You can't have a trunk group split across both carriers unless your phone system is specifically designed to do dual-carrier trunking (most aren't). If you have dedicated circuits tied to specific carriers, those circuits are by definition dedicated and can't exist on both carriers.

For services that can't parallel-run, your options are: (1) implement them fresh on the new carrier before the cutover and test them thoroughly, or (2) accept a brief gap in service during the cutover and have a rollback plan if something fails.

Cutover Day: Execution and Monitoring

The day you flip the switch from the old carrier to the new carrier needs to be orchestrated like a surgical procedure. Here's the checklist:

Who needs to be in the room (or on the call). You need at minimum:

Pre-cutover testing checklist (run 24 hours before cutover).

The actual cutover (hour 0). At the predetermined cutover time:

  1. Notify all stakeholders (especially anyone with external responsibilities) that the cutover is beginning
  2. Reprogram your phone system's trunk configuration to use the new carrier's trunks as primary
  3. Update DNS and SIP routing if applicable
  4. Verify that inbound calls are routing to the new carrier
  5. Make a test call inbound and outbound
  6. Do NOT disconnect the old carrier at this point

Monitoring windows (hours 0–2 post-cutover). For the first two hours after cutover, you are actively monitoring for failures. Someone should be making and receiving calls on multiple phone system extensions. Someone should be checking call logs and quality metrics. If the new carrier has a dashboard, watch it in real-time. If you notice a pattern of failed calls, a specific trunk is failing, or an integrated service is down, you have a decision point: troubleshoot live (risky) or roll back to the old carrier and troubleshoot offline.

Rollback trigger criteria. Decide in advance what triggers a rollback. Examples: "More than 10% of calls failing," "All inbound calls failing for more than 15 minutes," "A mission-critical system (like a call center or receptionist) is non-functional." If you hit a trigger, you reprioritize away from debugging and toward getting back on the old carrier. The old carrier remains active for exactly this reason.

Post-Switch: Cleanup and Validation

After the cutover, your work isn't done. There's a critical 30-day window where you validate that everything actually works and handle the business-end tasks.

When to disconnect the old service. Do not disconnect the old carrier's service until at minimum day 30 post-cutover. At day 30, you've had time to discover any lingering issues, any services that didn't migrate, and any billing surprises. At day 30, you verify: all numbers are ringing on the new system, all integrated services are working, no calls are routing to the old system. Only then, after you've confirmed visually that nothing is broken, do you request disconnection of the old service.

Before you disconnect, notify the old carrier in writing (email to their account team) with 14 days' notice. Verify they've acknowledged. On the disconnect date, have someone confirm that the lines are physically disconnected and that the old carrier no longer has service active. This prevents surprise bills for services you thought were disconnected.

Final billing reconciliation. The first bill from the new carrier will often be wrong. It's not malice—it's the complexity of a mid-month cutover. You may be charged for partial service days at rates that don't align with your contract. You may see duplicate charges for services that straddled both carriers. You may see line items for things you thought were included in your base rate.

Pull the quote the new carrier gave you and compare it line-by-line to the first bill. Every discrepancy gets escalated to the new carrier's account team. Send them the quote and ask them to explain the variance. Most overages can be credited if you catch them in the first 30 days.

Validating the new bill against the contract. Keep the original quote and contract. For at least the first three months, compare each bill to the original quote. Carriers sometimes add services or features during implementation that weren't in the contract, and then bill you for them. Catching this early saves you thousands in unexpected charges.

Frequently Asked Questions

How long does number porting actually take?

The standard timeline is 7–21 business days from when the new carrier submits the Letter of Authorization (LOA) to the old carrier. In ideal conditions (correct LOA, no disputes, no delays), you're looking at 7–10 business days. In challenging conditions (LOA rejected once, port fails on first attempt, state-level delays), you're at 21 days or more. Plan for 21 days as your baseline and treat anything faster as a win. If you have both local and toll-free numbers, you're coordinating two separate porting processes, which can extend the overall timeline.

What happens if a port fails?

If a port fails—meaning the old carrier didn't release the numbers or the new carrier didn't accept them—the numbers automatically snap back to the old carrier within a few hours. You discover this when calls to those numbers stop reaching the new system. At that point, you work with both carriers to determine why the port failed (most often: an LOA issue, a billing dispute with the old carrier, or a routing configuration error). You correct the root cause and request a new FOC date, which restarts the 7–21 day timeline. A failed port can add 2–3 weeks to your cutover schedule, which is why parallel running and having a rollback plan are essential.

Can we run both carriers at once during the switch?

Yes, but with important constraints. You can have both carriers active simultaneously as long as there are no conflicting phone numbers. The typical approach is to port a subset of numbers to the new carrier (your main DID block plus a test block) and run them both active. External callers can dial the new numbers (which route to the new system), while old numbers forward to the new system. This gives you a live testing period where both systems are active but non-conflicting. As you gain confidence, you gradually migrate more numbers. However, you cannot have the same DID on both carriers at once, and you cannot split a trunk group across both carriers unless your phone system specifically supports dual-carrier trunking.

What exactly is a Letter of Authorization (LOA), and why do they get rejected?

The LOA is the legal document that authorizes the new carrier to request a port from the old carrier on your behalf. It contains your account information, the numbers being ported, and an authorized signature. The most common rejection reasons: (1) The account holder name doesn't match the old carrier's records exactly (spelling, middle initials, Jr./Sr. designations all matter). (2) The service address is wrong or doesn't match the account. (3) The billing phone number is incorrect. (4) The signature is illegible or doesn't match the authorized signatory on file with the old carrier. (5) Required fields are blank. Many of these rejections are easily correctable—you amend the LOA and resubmit—but each rejection adds 3–5 business days. That's why verification is critical before you submit the LOA.

What's the risk of switching mid-contract?

The primary risk is an early termination fee (ETF) from your old carrier. Most business telecom contracts have ETFs calculated as "remaining contract value" (total monthly spend × remaining months). A three-year contract at $5,000/month with 18 months remaining could carry an ETF of $90,000. However, many carriers will negotiate or waive ETFs if you're willing to commit to a longer contract with the new carrier, or if the old carrier is in breach (service issues, quality problems). The secondary risk is hidden renewal clauses—if your contract has a 12-month auto-renewal and you don't formally cancel, you may lock in for an additional year. Always pull the actual contract and review for ETF and renewal clauses before you negotiate the exit.

Watch Out

The single most dangerous mistake in a carrier switch is disconnecting the old service before you've confirmed with absolute certainty that all numbers have ported successfully and are ringing on the new carrier's system. We've seen organizations disconnect the old service on day 2 post-cutover, discover on day 3 that a port failed for a subset of numbers, and have to scramble to get those numbers back on the old carrier while calls are failing. The cost of waiting 30 days to disconnect is negligible compared to the cost of even one hour of downtime. Wait the full 30 days. Verify visually that every number works. Only then request disconnection.

The ITG Perspective

We've managed over 200 carrier migrations, and the single most important factor in success is having a neutral third party own the project plan. When your internal telecom team is managing the switch while also supporting your current carrier and troubleshooting issues, priorities get confused and critical tasks slip. A dedicated project manager—ideally someone from outside your organization who has no allegiance to either carrier—can push for clarity on timelines, insist on proper testing, and call a rollback when conditions warrant it without internal political complications. ITG serves this role for many organizations. We don't benefit if you stay with your current carrier, and we don't benefit if you switch to a particular new carrier. We benefit only if the migration succeeds without downtime and your final bill matches the quote. That's the perspective that leads to success.

Conclusion

A successful carrier switch requires four things: a complete audit of your current footprint, meticulous attention to the porting process, a parallel-run period where you validate the new system, and disciplined execution on cutover day with a clear rollback plan. None of these steps is optional. Organizations that skip any of them invariably suffer unnecessary complications.

The playbook in this guide is based on what works. Follow it, and your carrier switch will be clean. The operational risk is real—a failed carrier switch can take out phone service for your entire organization. But the technical solution is straightforward: careful planning, detailed testing, and the discipline to wait 30 days before you celebrate.