Blog / VoIP Setup And Troubleshooting

How to Switch to VoIP in 14 Days Without Downtime

A day-by-day plan to switch to VoIP in 14 days. It covers submitting your number port early, running both systems side by side, testing every call path and keeping a rollback ready for cutover day.

To switch to VoIP without dropped calls, submit your number port in the first two days, build and test the new system on temporary numbers while the old one keeps running, cut over mid-week in the morning, and cancel the old carrier only after every number is confirmed moved. This guide gives you a 14-day plan with a day-by-day schedule, a porting checklist, a call flow test script and a rollback plan. It is written for US businesses that want to change business phone provider or leave a landline or old PBX behind.

Key takeaways

  • FCC rules require simple number ports, including ports to interconnected VoIP, to be completed within one business day, and non-simple ports within four business days, once the port is confirmed (Kelley Drye).
  • The FOC (Firm Order Commitment) date from your old carrier controls the whole VoIP migration schedule. Every task after Day 8 moves if the FOC date moves.
  • Never cancel your old phone service before the port completes. Cancelling early can release your numbers for good.
  • By June 30, 2025, the US had 63 million interconnected VoIP subscriptions against 15 million switched access lines, which were falling at 17.9% a year (FCC).
  • A VoIP rollback means rerouting calls (forwarding, reverting routing), not reversing the port. Agree on triggers, such as a main line failing inbound for more than 15 minutes, before cutover day.

How do you switch to VoIP in 14 days without downtime?

You switch to VoIP in 14 days without downtime by porting early, building in parallel, testing every call path and keeping a rollback ready. Submit the port request on Day 2, build the new phone system on temporary numbers, forward the old main line during a parallel run, then cut over on a Tuesday to Thursday morning.

The 4 rules: port early, build in parallel, test every call path, keep a rollback

  1. Inventory every number and line, including fax, alarm and card terminals.
  2. Pull your Customer Service Record (CSR) and latest bill from the current carrier.
  3. Test your network for bandwidth, jitter and packet loss.
  4. Submit the port on Day 2 and start text messaging (10DLC) registration the same day.
  5. Build users, menus, queues and voicemail on temporary numbers.
  6. Run both systems in parallel by forwarding the old main line to the new system.
  7. Run the full call flow test script before the port date.
  8. Cut over, monitor, then cancel the old service in writing.

What 14 days assumes (under 50 users, local numbers, one to three sites)

The plan assumes under 50 users, mostly local numbers, one to three sites, and a carrier that accepts the port on the first try. Toll-free numbers, multi-site PBX replacements or rejected ports can add a week or more.

DayTaskOwnerDone when
0Readiness checklist, CSR requestedInternal leadCSR and bill in hand
1Kickoff, inventory sign-off, target cutover dateInternal leadNumber list signed off
2Submit port (LOA, CSR, PIN), start 10DLCInternal lead + new providerPort ID and 10DLC submission received
3-4Build users, IVR, queues, voicemail on temp numbersNew provider + internal leadConfig matches call flow map
5E911 locations, outbound caller IDInternal leadEvery user has a dispatchable location
6-7Pilot group live, CRM syncPilot teamPilot makes and takes real calls
8FOC date confirmedOld carrier / new providerWritten FOC date and time
9-10Parallel run, full staff trainingInternal leadAll staff log in and complete a test call
11Full call flow test scriptTestersEvery test passes
12Port cutover, go/no-goAll threeInbound works on every number
13HypercareInternal lead + new providerNo open critical issues
14Verify, cancel old service in writingInternal leadCancellation confirmed

Why are US businesses switching to VoIP now?

US businesses are switching to VoIP now because copper landlines are being retired, landline prices keep rising as carriers shrink those networks, and cloud phone systems support remote work and CRM integration. A March 2026 FCC order also lets carriers retire copper phone lines faster, so many businesses are being pushed to move.

Copper/POTS retirement and the 2026 FCC order

POTS (plain old telephone service) is the traditional copper landline. On March 26, 2026, the FCC unanimously adopted an order (FCC 26-19) that speeds up copper retirement. Under the order, carriers can grandfather legacy lines (stop new sales), discontinue them faster, and refuse to move a grandfathered line to a new address. If you plan to relocate, your landline may not come with you. UK content about the 2027 BT/Openreach switch-off does not apply to US businesses.

Landline vs. VoIP: what the FCC numbers show

The FCC's Voice Telephone Services report counted 15 million switched access lines against 63 million interconnected VoIP subscriptions as of June 30, 2025. Switched access lines are declining at a compound annual rate of 17.9%.

Cost, remote work and CRM integration

Cloud phone systems run in a browser or mobile app, so remote and hybrid staff use the same business number from anywhere. Features like call recording, texting and CRM logging come with the system. If you are still choosing a platform, our guide to choosing a VoIP phone system for business compares features, contracts and support.

What do you need before you switch to VoIP?

Before you switch to VoIP you need a complete number inventory, your Customer Service Record (CSR) and latest bill, a map of current call flows, a passing network test, a device plan and named owners. Missing any of these is the most common reason a VoIP migration slips past 14 days.

Number inventory: main line, DIDs, toll-free, fax, alarm, elevator, card terminals

A DID (direct inward dial) number rings a specific person or team. List every number with its purpose: main line, DIDs, toll-free, fax, alarm panels, elevator phones, postage meters and credit card terminals. The last five are the lines businesses most often forget. Plan an ATA adapter, online fax, a cellular communicator or a POTS replacement for each one before you port.

Get your Customer Service Record (CSR) and latest bill

The CSR is your carrier's official record of your account: legal name, service address, billing telephone number (BTN) and every number on the account. Your port request must match it exactly. A mismatch in name, address or BTN is the top cause of port rejections, so request the CSR on Day 0.

Map current call flows and hours

Write down what happens when someone calls each number today: who rings, after how many seconds, what the menu says, where calls go after hours and on holidays, and where voicemail lands.

Network readiness test: bandwidth, jitter, packet loss, SIP ALG, QoS

A common vendor rule of thumb is about 100 kbps per concurrent call, up and down, or roughly 2 Mbps for 20 simultaneous calls. Treat that as a starting estimate, not a standard. Also check:

  • Latency under 150 ms, jitter under 30 ms, packet loss under 1% (common targets).
  • SIP ALG off on the router. SIP ALG is a router feature that rewrites call signaling and often breaks VoIP audio.
  • QoS (Quality of Service) set to prioritize voice traffic, plus a voice VLAN if you use desk phones.
  • PoE switches if desk phones draw power from the network.
  • A failover connection, such as a second ISP or cellular backup.

Use our VoIP bandwidth calculator and network test to size your connection.

Device plan: browser/softphone, desk phones, ATAs

A softphone is a phone app on a computer or mobile device. Decide who gets a browser or desktop app with a headset, who needs a desk phone, and which analog lines need an ATA (analog telephone adapter).

Assign owners: internal lead, new provider, old carrier contact

Name one internal lead with authority to sign the LOA. Record your new provider's onboarding contact and your old carrier's porting or repair line, with account number and PIN.

What is the 14-day VoIP migration plan, day by day?

The 14-day VoIP migration plan submits the number port on Day 2, builds and pilots the new system on temporary numbers through Day 7, confirms the FOC date on Day 8, runs both systems in parallel on Days 9 to 11, and cuts over on Day 12. If the carrier sets a later FOC date, shift Days 9 to 14 and keep forwarding in place.

Day 1: Kickoff, inventory sign-off, choose cutover date

Owner: internal lead. Confirm the number list, which numbers port and which are retired, and a target cutover day. Pick a Tuesday, Wednesday or Thursday. Avoid Fridays, month-end and your busiest season. Done when: the inventory is signed off.

Day 2: Submit port request (LOA, CSR, PIN) and start 10DLC registration

Owner: internal lead with new provider. Sign the LOA (letter of authorization), attach the latest bill and CSR, and include the account number and port-out PIN. Start A2P 10DLC brand and campaign registration the same day if you will text customers. Done when: you have a port request ID and a 10DLC submission confirmation.

Days 3-4: Build users, numbers, IVR, queues, voicemail on temporary numbers

Owner: new provider and internal lead. Assign temporary numbers, create users, and rebuild the auto attendant, ring groups, queues, business hours, holiday schedule and voicemail from your call flow map. Tools like IVR phone menus and call routing let you build all of this before a single number ports. Done when: every call path on the map exists in the new system.

Day 5: Configure E911 dispatchable locations and caller ID

Owner: internal lead. Enter a street address, plus floor or suite, for every user and device, including remote workers. Set outbound caller ID per user or team. Done when: no user lacks an emergency location.

Days 6-7: Pilot group goes live on temp numbers; CRM/HubSpot sync

Owner: pilot team of three to five people. They make real outbound calls, take test inbound calls and confirm that calls log to the CRM. Done when: the pilot reports no blocking issues.

Day 8: FOC date confirmed; lock the cutover window

Owner: new provider and old carrier. Get the FOC date and time in writing. Done when: cutover is on the calendar and all staff know.

Days 9-10: Parallel run: forward old main line to new system, train all staff

Owner: internal lead. Forward the old main number to its temporary number on the new system so real customer calls hit the new call flows. Train every user on answering, transferring, voicemail and the mobile app. Done when: every user has logged in and completed a live call.

Day 11: Full call flow test script

Owner: testers. Run every test in the script below and fix failures. Done when: all tests pass.

Day 12: Port cutover (morning, mid-week) and go/no-go

Owner: all three parties. Hold a go/no-go check at 8 a.m. When the port activates, test inbound on every number from an outside mobile phone. Done when: every ported number rings the new system.

Day 13: Hypercare and monitoring

Owner: internal lead and new provider. Watch call logs, missed calls and quality reports, and fix routing gaps as staff report them. Done when: no critical issues remain open.

Day 14: Verify all numbers, then cancel old service in writing

Owner: internal lead. Confirm every number shows as ported, remove forwarding, then cancel the old account in writing. Done when: you have cancellation confirmation and a final bill date.

How does number porting work, and what causes delays?

Number porting moves your existing phone numbers from your old carrier to the new provider under FCC rules. Porting delays usually come from paperwork mismatches against the CSR, not from the switch itself. Once the port is accepted, the FCC sets maximum completion times, but review and rejections can stretch a VoIP port to one or two weeks.

Simple vs. non-simple ports (FCC 1 vs. 4 business days)

A simple port is a basic port of a few numbers with no complex services attached. FCC rules require simple wireline and intermodal ports, including ports to interconnected VoIP, within one business day, and non-simple ports within four business days unless the customer or new provider asks for longer (Kelley Drye). The FCC cut the simple-port interval from four days to one in 2009, with most providers required to comply by August 2, 2010 (Davis Wright Tremaine). Those clocks start after the port is validated, so plan for 5 to 10 business days end to end.

LOA, CSR, BTN and account PIN

The LOA is a signed form authorizing the new provider to move your numbers. It must match the CSR on business name, service address and BTN, and include the account number and any port-out PIN. Our walkthrough on how to port a business phone number to VoIP covers each field.

Partial ports and keeping the BTN

A partial port moves some numbers and leaves others on the account. If the BTN stays behind, the old carrier needs a new BTN assigned or the port may be rejected. Ask your carrier first.

Toll-free (RespOrg) and wireless numbers

Toll-free numbers port through a RespOrg (Responsible Organization), the entity that manages toll-free routing, and often take longer than local numbers. Wireless numbers need the account number and a port-out PIN from the mobile carrier. Local numbers can also be limited by rate center coverage, so confirm the new provider serves your area codes.

What the FOC date is and why you must not cancel early

The FOC date is the carrier's confirmed date and time for the port. Until then, the old carrier still routes your calls.

Do not cancel your old service until every number shows as ported. Cancelling first can release your numbers before the port completes.

A number porting service that tracks status per number makes the final check simple.

How do you run a parallel system for zero-downtime cutover?

A parallel system means the new VoIP phone system runs live on temporary numbers while the old carrier still owns your real numbers. Call forwarding from the old line sends real traffic to the new system before the port, so the phone system cutover becomes a routing change instead of a leap of faith.

Temporary numbers and call forwarding

Forwarding the old main line to its temporary number tests the new call flows with real callers. Forwarding also hides the gap when a port has only partly propagated: callers reach the new system either way. Two limits apply. Forwarded calls may use old-carrier minutes, and caller ID may show differently on forwarded calls.

Simultaneous ring during the port window

If forwarding is not available, set key old-system extensions to also ring mobile phones or the new app during the port window, so no call rings unanswered.

Porting secondary numbers first as a canary

Port a low-risk DID or fax number a few days before the main line. If that port completes cleanly, the main port is unlikely to fail on paperwork.

How do you test call flows before going live?

You test call flows by calling every number and every menu path from an outside phone, at every time condition, and recording a pass or fail for each. Run the full script on Day 11 against temporary numbers, then repeat the inbound tests on Day 12 against ported numbers.

TestExpected resultPass/FailTester
Call each number from an outside mobileRings correct user, group or menu
Call during business hoursMain greeting plays
Call after hoursAfter-hours greeting and routing
Enable holiday mode, callHoliday message plays
Press each IVR optionReaches the right team
Let a queue ring with no agentsOverflows to voicemail or backup
Leave voicemailEmail with audio and transcript arrives
Check AI summary on a test callSummary appears on the call record
Place outbound call to a mobileCorrect caller ID shows, not "Spam Risk"
Send and receive a textDelivered both ways
Warm and cold transferCaller lands on the right person
Mobile app, browser, desk phoneEach places and receives calls
CRM loggingCall and recording appear on the contact
933 test (if your provider supports it) or a scheduled, non-emergency 911 testAddress read back is correct

Never place a live 911 test call without first contacting the local emergency center's non-emergency line. If audio breaks up during testing, the VoIP choppy audio fix guide maps symptoms to causes.

What should you do if the VoIP cutover goes wrong?

If the VoIP cutover goes wrong, reroute calls rather than trying to undo the port, because a completed port cannot easily be reversed. A rollback plan defines go/no-go criteria, specific failure triggers, the actions each trigger starts, and who calls whom. Collect every escalation contact before Day 12.

Go/no-go criteria

Go only if the Day 11 test script passed, the FOC is confirmed in writing, all staff can log in, and both provider and old carrier support lines are staffed during the window.

Rollback triggers (e.g., main line inbound failure > 15 min)

  • Main number receives no inbound calls for more than 15 minutes.
  • More than one IVR path fails.
  • Outbound calls fail for a whole team.
  • 911 location test reads back the wrong address.

Rollback actions: forwarding, reverting routing, carrier escalation

  1. Point the affected number to a working destination, such as a mobile phone or backup group.
  2. Revert the new system's routing to the last known good configuration.
  3. Escalate to the new provider's porting team with the port ID, and ask the old carrier's repair line to confirm the port status.
  4. If the port has not activated, ask both parties to reschedule the FOC rather than proceed.

Customer and staff communication templates

Customer greeting: "Thanks for calling [Company]. We're upgrading our phone system today. If you can't reach us, text or call [backup number] or email [address] and we'll respond within [time]."

Staff message: "Cutover issue on [number] since [time]. Calls are routed to [destination]. Next update at [time]. Don't restart phones or change settings."

What compliance rules apply when you switch to VoIP?

When you switch to VoIP, three compliance areas matter most: E911 under Kari's Law and RAY BAUM'S Act, A2P 10DLC registration for business texting, and outbound caller ID reputation. Skipping any of them can mean emergency calls without a location, blocked texts or sales calls flagged as spam.

Kari's Law and RAY BAUM'S Act dispatchable location

Under Kari's Law and Section 506 of RAY BAUM'S Act, multi-line phone systems must allow 911 dialing without a prefix like 9, notify a central point such as a front desk when 911 is dialed, and send a dispatchable location with the call. Interconnected VoIP is covered (Kelley Drye). A dispatchable location is a street address plus details like floor or suite. Update it whenever someone moves desks or works from home.

A2P 10DLC registration for business texting

A2P 10DLC is the US registration system for business texts sent from 10-digit local numbers. You register a brand and campaign through The Campaign Registry, and carriers now block unregistered traffic. Start on Day 2 because approval can take days. See our business texting compliance checklist.

Caller ID reputation for outbound sales teams

STIR/SHAKEN is the US framework that digitally signs outbound calls so carriers can verify the caller ID is legitimate. New numbers have no reputation yet. Ask your provider what attestation level your calls receive, keep outbound volume per number reasonable in the first weeks, and test caller ID display on the major mobile carriers.

What should you do in the first 30 days after the switch?

In the first 30 days after you switch to VoIP, monitor call quality, close out old contracts and tune routing based on real call data. These three tasks catch the problems that testing misses, such as a congested afternoon network or a queue that overflows at lunch.

Call quality monitoring (MOS, jitter)

MOS (Mean Opinion Score) rates call quality from 1 to 5. Review MOS, jitter and packet loss reports weekly and investigate any site or user with repeated poor scores.

Clean up old devices, lines and contracts

Collect old handsets, return carrier equipment, and check the final bill for early termination fees and lines that stayed active by mistake, such as an unported fax line.

Review analytics and tune queues

Check missed calls by hour, queue wait times and abandoned calls. Adjust ring times, overflow rules and staffing to match.

How does Voicalyst make the 14-day switch easier?

Voicalyst is a browser-based business phone system for US sales and support teams, so most of the 14-day plan happens in software rather than hardware. Teams can build phone menus, queues and voicemail on temporary numbers before porting, then move numbers when the setup has been tested.

  • No desk phones required: staff call from a browser or mobile app with a headset.
  • Built before porting: menus, queues and voicemail transcription are configured and tested on temporary numbers.
  • Day-one workflow: the HubSpot calling integration, power dialer, business texting and AI call summaries are available from the first call.

To plan your migration with our team, book a demo at Voicalyst.

Frequently Asked Questions

How long does it take to switch to VoIP?

Most US businesses with under 50 users, local numbers and one to three sites can switch to VoIP in about 14 days. The number port sets the pace. FCC rules require simple ports to finish within one business day once confirmed, but paperwork review usually stretches the full process to one or two weeks.

Can I keep my business phone number when I switch to VoIP?

Yes. FCC number portability rules let you move local, toll-free and most wireless business numbers to a VoIP provider. You sign a letter of authorization (LOA), and the name, service address, billing telephone number and account details must match your current carrier's records exactly, or the port can be rejected.

Will I lose phone service during number porting?

You should not lose service if you keep the old account active and build the new system before the port. Calls keep ringing on the old carrier until the port completes on the FOC date. Forwarding the old main line to a temporary number on the new system covers the short gap while routing updates.

Can I use my existing phones with VoIP?

Sometimes. Analog desk phones need an ATA adapter, and older PBX handsets usually will not work with a cloud system. Many SIP desk phones can be reprovisioned if the new provider supports the model. Browser and mobile apps with a USB headset often replace desk phones entirely and remove hardware cost.

What happens to fax and alarm lines when switching to VoIP?

Fax, alarm panel, elevator and some credit card terminal lines need a separate plan because they often run on copper POTS lines. Options include an ATA adapter, online fax, a cellular alarm communicator or a dedicated POTS replacement service. Check with your alarm company and elevator vendor before porting those numbers.

Should I cancel my old phone provider before porting?

No. Cancelling first can release your numbers and make them impossible to port. Keep the old account active until every number shows as ported and you have tested inbound calls on each one. Then cancel in writing, request a final bill and check for early termination fees or charges on lines that stayed behind.

Put this into practice with Voicalyst

Voicalyst is the cloud phone system US sales and support teams set up in minutes: a business phone system with cloud telephony, AI call summaries and texting.

Start free trialBook a demo
VE

Voicalyst Editorial Team

Guides and research from the team building Voicalyst.