Skip to main content
CallSprout
2026-11-10

PBX to VoIP migration checklist (2026)

PBX to VoIP migration checklist for 2026, in plain steps: port your numbers, set E911, ready the network, rebuild call flows, and cut over with a rollback plan.

Matte green business headset on a sculpted ivory stand

The hard part of leaving a PBX is not picking a VoIP logo. It is doing the work in an order that keeps the main number ringing.

This checklist is that order. It is for the owner, office manager, or IT lead who will own the project from the first inventory to the week after cutover. If you want the reasoning behind the move, the PBX to VoIP migration guide covers it. If you still need the case for switching, 10 advantages of moving from PBX to VoIP is the shorter read.

Use it when you migrate a PBX to VoIP and replace the phone system. It is not a plan for bolting texting or recording onto the box you already have.

How the ten phases fit together

Work top to bottom. Inventory and the network come before you promise a date. Number porting runs in the background while you rebuild call flows and train people. Cutover is a confirmation, not the day you discover the fax line was never on the list.

  1. Audit the PBX you are leaving
  2. Choose a VoIP provider
  3. Network readiness and QoS
  4. Hardware and desk phones
  5. Auto attendant and call flows
  6. Port your numbers
  7. Set E911 addresses
  8. Train the team
  9. Cutover and rollback
  10. The first week

Phase 1: Audit the PBX you are leaving

You cannot port, price, or rebuild what nobody wrote down. Most surprises in a PBX migration are lines, devices, or call paths that never made the list.

Pull a recent bill before you talk to providers. The account name and service address on that bill are what the current carrier will check later, and a mismatch is a common reason a port gets rejected.

  • [ ] Count every extension, phone number, and device, including spare lines nobody admits to using
  • [ ] Map who answers, where a call goes if they don't, and what happens after hours, on weekends, and on holidays
  • [ ] List every system the phones touch, including a CRM, a scheduling tool, a helpdesk, or a PSA such as ConnectWise PSA
  • [ ] Note analog gear that is easy to forget: fax, alarm panels, elevator phones, door phones, postage meters, and overhead paging
  • [ ] Record a normal day and a busy hour, so you know how many calls can be in progress at once
  • [ ] Copy the account holder name, billing address, account number, and any PIN from a current bill
  • [ ] Check the contract end date and any early termination terms with the current carrier
  • [ ] Name one person to own the migration from this list through the first week

Phase 2: Choose a VoIP provider

Price is the easy comparison. The expensive surprises are usage rounding, emergency calling, and a port the provider expects you to run alone.

Ask the questions out loud and write down the answers. A quote that cannot explain an outage, a port, or an emergency address is not ready to run your main number. Our 10 questions to ask a VoIP provider is a fuller list if you are still comparing.

  • [ ] Ask how an AI voice agent is priced: on the seat, as a separate subscription, or only for the calls it answers, and whether any free time at the start of a call is counted exactly or rounded up to a full minute
  • [ ] Ask what happens to calls when the provider has an outage, and what you are supposed to do
  • [ ] Confirm the system can connect to the CRM, helpdesk, or PSA you listed in the audit
  • [ ] Get a straight answer on who fills out the port paperwork and which documents the carrier will want
  • [ ] Ask what it takes to add or remove a person later
  • [ ] Read the service agreement for the term, renewal, and how seat changes are billed
  • [ ] Ask who registers E911 addresses, how fast a move gets updated, and whether emergency calling is a separate charge
  • [ ] Confirm your current desk phones will register, before anyone orders a new fleet

Phase 3: Network readiness and QoS

Call quality is decided by the network you already have. A new phone system will not fix a congested connection, and you do not want to learn that on cutover morning.

You do not need a perfect lab. You need headroom at the busiest hour, voice treated as more important than a software update, and a plan for the day the office internet dies. Quality of Service only affects equipment you manage. It does not change how the public internet treats your packets.

The reliability page includes a connection test you can run from a computer on the office network. It reports speed, latency, jitter, and packet loss. If a second circuit is part of the plan, a backup line with a new public IP can drop calls in progress when traffic moves. Unbreakable Internet keeps one static IP across two connections so a circuit failure does not have to end the call.

  • [ ] Compare the busiest hour of simultaneous calls with the slower of your upload and download, and leave room for everything else the office does online
  • [ ] Ask the provider what each simultaneous call needs on your connection, then recheck the headroom
  • [ ] Turn on Quality of Service so voice audio is prioritized on your router or switches
  • [ ] Put heavy call desks on Ethernet, not only on Wi-Fi
  • [ ] Ask whether SIP ALG on the router should stay on or come off before you change it. Some routers rewrite voice traffic and cause one-way audio
  • [ ] Ask the provider which ports and addresses the firewall must allow, and apply those rather than guessing
  • [ ] Put the router and the phone switch on a battery backup if the phones have to work through a short power cut
  • [ ] Decide the failover before cutover: a second internet circuit, a mobile app, or a cell phone when the office connection drops

Phase 4: Hardware and desk phones

A PBX migration does not require a pallet of new phones. It does require an honest list of what will still work on Monday.

Standard desk phones that speak VoIP often move. Proprietary PBX phones often do not. People who are rarely at a desk may be better on a computer, a browser, or a cell phone app than on hardware that sits unused. For a buying comparison, see VoIP phones for small businesses and the apps and desk phone options.

Analog devices are the other half of this phase. A fax machine, an alarm, an elevator phone, or a paging amp may need to stay on an analog line, move to an adapter, or be replaced. Do not unplug them because the PBX cabinet is leaving. If fax is part of the move, faxing from a computer is the path that drops the machine.

  • [ ] List the make and model of every desk phone, headset, and sidecard
  • [ ] Mark each one keep, replace, or retire, and confirm the keepers with the new provider
  • [ ] Check Power over Ethernet if the phones draw power from the switch, and confirm the switch has enough ports
  • [ ] Order replacements only after compatibility is confirmed
  • [ ] Decide who will use an app instead of a desk phone, including anyone who works away from the office
  • [ ] Write a plan for each analog device before the old lines are disconnected
  • [ ] Keep a few spare handsets or headsets for the first week, not a closet full of untested phones

Phase 5: Auto attendant and call flows

The menu people complain about does not have to survive the move. Write the new flows from how callers actually ask for help, then test them with someone who does not work there.

Cover the open hours, the lunch gap if you have one, weekends, and holidays. Decide the ring pattern: everyone at once, one after another, or a priority order with overflow. Then decide the failure path. Voicemail, a cell phone, an on-call person, or an AI voice agent are different choices, and after hours can differ from the daytime path.

Build this on the new system before the numbers move, using a test number if you have one. The voice and calling features are the kind of greetings, ring groups, and hours routing you are trying to recreate or simplify. If you are choosing the menu style itself, auto attendant phone systems compares a press-1 tree with a system that listens.

  • [ ] Write the greeting in the words a caller should hear, and keep it short
  • [ ] List the menu choices, who each one rings, and what happens if nobody picks up
  • [ ] Set business hours, holidays, and any lunch or weekend difference
  • [ ] Set overflow and the after-hours path, including voicemail
  • [ ] Confirm voicemail reaches someone as a message or a transcript, not only as a blinking light
  • [ ] If a CRM or PSA match is supposed to change who rings, test that path on the test number
  • [ ] Have a person outside the project call the test number and try to reach sales, support, and a named person

Phase 6: Port your numbers

Porting is how you keep the numbers customers already dial. It is also the step most likely to slip, because your current carrier has to release them.

Submit the port through the new provider. The signer should be someone the current carrier will accept, and the account name and billing address need to match the bill exactly. Have a recent bill or a customer service record ready. Carriers reject ports over small differences: a suite number, an old company name, a missing PIN.

List every number you want to keep, not only the main line. That includes fax, alarm, and any toll-free numbers. Toll-free numbers are a separate port from local numbers. If you are moving only some numbers and the main billing number is one of them, the numbers that stay behind need a new billing number. Keep the old service active until the port is confirmed. Canceling early is how a business ends up with no phones at all. You remain responsible for the old account's balance and any early termination fees.

  • [ ] Sign the letter of authorization the new provider gives you
  • [ ] Match the account holder name and billing address to the current bill, character for character
  • [ ] Include the account number and any PIN the carrier has on file
  • [ ] Attach a recent bill or customer service record
  • [ ] List local numbers and toll-free numbers separately
  • [ ] Choose a full port or a partial port, and if the billing number is leaving, name a new one for what stays
  • [ ] Set a target port date with buffer, and do not publish that date as a promise until the provider accepts it
  • [ ] Tell the staff the target date, and tell them the old system stays up until the port is actually done

Phase 7: Set E911 addresses

On a traditional PBX, 911 often rode the building's phone lines, and the address was the building. On VoIP, each number carries a registered address you have to get right. A dispatchable location is precise enough for responders to find a person: street address, floor, suite, or room.

Register that address before cutover, not after the first real emergency. Update it when a phone moves. A home office, a job site, and a second shop are not the headquarters address. Someone who dials 911 from a laptop at home needs the address where they are, or they need to tell the dispatcher where they are.

Two older expectations still matter, and this is not legal advice. Callers should be able to dial 911 directly, without a 9 or another prefix in front. And someone at the business, such as a front desk or a manager, should know when 911 was dialed so they can meet responders. Whether that is what Kari's Law and RAY BAUM'S Act require of your company is a question for your own advisers.

An internet phone cannot place a 911 call without power and a working connection. Keep a cell phone or another path that does not depend on the office router. Ask the provider how to confirm emergency calling without placing a live 911 call.

  • [ ] Register a dispatchable address for every number before the port date
  • [ ] Include floor, suite, or room where the street address alone is not enough
  • [ ] Separate the plan for people who work away from the registered site
  • [ ] Write down who updates an address when a phone moves, and how fast that update happens
  • [ ] Confirm people can dial 911 directly, with no prefix
  • [ ] Decide who gets notified on site when someone dials 911
  • [ ] Keep another way to reach emergency services when the power or the internet is out
  • [ ] Ask the provider for the test method, and do not place a live 911 call to "see if it works"

Phase 8: Train the team

Training after cutover is how a normal Tuesday becomes a missed call. People need the new habits before the numbers move: how to answer, transfer, hold, park, and check voicemail, and what their cell phone or app will do if the desk set is offline.

Keep it short. A single session and a half-page card at the phone beat a handbook nobody opens. Cover 911 in that same session: the address that goes with the call, and what to do if they are not at that address.

  • [ ] Schedule the session before cutover day, with the people who actually answer
  • [ ] Cover answer, transfer, hold, park, and voicemail on the devices they will use
  • [ ] Show the mobile app or cell failover, and have each person place one test call
  • [ ] Explain what 911 sends, and what to tell a dispatcher if they are away from the registered address
  • [ ] Name who covers the main line on cutover day
  • [ ] Put a short card by each phone: transfer, voicemail, and who to tell if audio is bad
  • [ ] Leave time for a second pass with anyone who missed the first session

Phase 9: Cutover and rollback

Cutover day should be boring. Boring means the port is done, the flows were tested, and someone can stop the switch if the live calls do not match the test.

Pick a low-traffic window. A Monday at 9 a.m. is a poor time to find out the greeting is wrong. The rollback has two shapes, and you should write both down. If the port has not completed, you stay on the old system and you do not tell customers anything has changed. If the port has completed and calls are failing, going back is another port, which takes time. That is why the old hardware stays in place until the first week is clean, and why you do not cancel the old account on the morning of the move.

  • [ ] Confirm the number port has completed before you declare the switch done
  • [ ] Name one person who can halt the cutover
  • [ ] Place live inbound and outbound calls on the main number and on a few extensions
  • [ ] Check outbound caller ID on a cell phone that is not on the new system
  • [ ] Walk the auto attendant, the ring groups, and the after-hours path
  • [ ] Leave a voicemail and confirm it arrives where you expect
  • [ ] Confirm the E911 address on file is the one you registered
  • [ ] Keep the old carrier active, and leave the PBX hardware in place
  • [ ] Tell staff, and tell any customer or vendor who lives on the main line, once the live tests pass

Phase 10: The first week

A clean cutover can still hide a misrouted option, a voicemail greeting in the old voice, or a sync that never started. Look for those before you close the old account.

  • [ ] Review call logs for missed calls and calls that reached the wrong place
  • [ ] Confirm voicemail-to-email or transcription is arriving
  • [ ] Check that records you expected in the CRM or the PSA are showing up
  • [ ] Ask the people who answer what felt clumsy, and fix the card or the flow
  • [ ] Call the main number after hours and on the next holiday setting you can test
  • [ ] Close the old carrier account only after those checks pass, and only once you understand any early termination fees
  • [ ] Retire or repurpose the old PBX hardware after the account is closed, not before

Mistakes this checklist is built to catch

The phone switch itself is rarely the thing that hurts. A fax line nobody inventoried, a port submitted under the wrong legal name, an emergency address that still says the old suite, and a team that meets the new phones on the morning they have to use them: those are the failures. The audit, the port paperwork, the E911 list, and the training session exist so callers are not the ones who find them.

Where CallSprout fits

CallSprout is a cloud business phone system. The move starts with three short forms: an LOA, a user list, and your call routing instructions. From there we pull your current settings, port your numbers, build your call flows, test them, and train your team. Support answers by phone after you go live.

Local number ports typically take 7 to 14 business days. Toll-free ports vary. A signed LOA is valid for 60 days from the day you sign it, so sign it when you are ready to move, not months earlier. We port the numbers your customers already know.

You can keep standard desk phones you already own. The Communicator desktop, web, and mobile apps are included with Contact Center Lite and are a per-seat add-on on Business and Contact Center Pro. The Microsoft Teams integration is included on every plan. If the desk phones go offline, calls can ring the mobile app, or a cell phone through find-me/follow-me, once that path is set up ahead of time. See voice and calling for the phone system those phones and apps sit on.

E911 service is required on every account and is billed as its own line on the quote. Each number has a dispatchable location, such as a street address plus the floor or suite. When someone dials 911, that location goes with the call. Update it when a phone moves. Like any internet phone service, 911 needs power and an internet connection at the phone, so keep another way to reach emergency services.

Sage, our AI voice agent, is available on every CallSprout plan, with the first 30 seconds of each call free and the rest billed by the second ($0.39/min). You can leave Sage off, or turn it on for one user, a department, a ring group, a queue, or a single number. You pay for Sage only where it answers. AI Transcription of calls is $0.0198 per minute. Voicemail transcription is free.

Business, Contact Center Lite, and Contact Center Pro are published as monthly rates and as lower annual rates. Add-ons, including E911, fax, and extra numbers, are listed on the same page. See pricing for the current numbers.

If you want the office connection checked before the phones move, CallSprout offers a network assessment. Contact us and start with the audit, or go straight to pricing if you already know the team size.

Frequently asked questions

What is a PBX to VoIP migration?

A PBX to VoIP migration replaces the on-site phone system with a cloud phone system. You inventory extensions and call flows, prepare the network, decide which phones stay, rebuild menus and routing, port the numbers, register emergency addresses, train the people who answer, and cut over with a written way to roll back.

Is this checklist enough to complete a full VoIP implementation on my own?

For a small business, yes, if one person owns the project and the provider helps with the port and the cutover. A company with several sites should still name that owner. The phases here are the work a full replacement needs.

What is the difference between a PBX replacement and a partial upgrade?

A PBX replacement moves call routing, voicemail, menus, and the phone numbers onto the cloud system. A partial upgrade keeps the PBX and adds something beside it, such as texting or call recording. This checklist is for a full replacement.

Do I need new desk phones to migrate from a PBX to VoIP?

Not always. Many businesses keep standard desk phones that already work on VoIP, and some skip desk phones for a computer, a browser, or a cell phone app. Confirm compatibility before you buy hardware, and plan separately for analog devices such as fax machines, alarms, elevators, and overhead paging.

What should I check on the network before a VoIP migration?

Confirm the connection can carry your busiest hour of calls on top of normal office traffic, using the slower of upload and download. Prioritize voice on the router and switches you control. Use wired connections at desks that live on the phone, and ask the provider whether SIP ALG should stay on before you change it. Have a second internet path or a mobile failover before cutover day.

What does E911 mean for a VoIP migration?

E911 sends a dispatchable location with a 911 call, such as a street address plus a floor or suite, so responders know where to go. Register that address for each number and update it when a phone moves, including when someone works from home. A 911 call on an internet phone also needs power and a working connection, so keep another way to reach emergency services. This is not legal advice, and whether your setup meets Kari's Law or RAY BAUM'S Act is a question for your own advisers.

How do I roll back a VoIP cutover if something goes wrong?

Write the rollback before cutover day and name one person who can halt the switch. Keep the old carrier active until the port is confirmed, and do not cancel that account on the morning of the move. If the port has not completed, rollback means staying on the old system. If the port has completed, going back means a new port, which is why you test call flows before you commit the date and why you leave the old hardware in place until the first week checks out.

What should a VoIP migration checklist include?

It should cover the ten phases in this article: a PBX audit, provider selection, network readiness and QoS, hardware and desk phones, auto attendant and call flows, number porting, E911 addresses, training, cutover with a rollback plan, and a first-week check.

How long does a PBX to VoIP migration take?

There is no single timeline that fits every provider. Start the audit before you pick a cutover date, begin number porting early, and add buffer around the target date because your current carrier controls part of the clock. On CallSprout, local number ports typically take 7 to 14 business days, and toll-free ports vary. Keep checking the system through the first week before you close the old account.

Can I keep my phone numbers when migrating from PBX to VoIP?

You can keep them by porting. Submit the port through the new provider, match the account name and billing address to the current carrier's bill, and keep the old service active until the port is confirmed. Do not cancel the old account until you have placed live test calls on the new system.

See CallSprout in action.

Start a free trial or talk to Sage, our AI agent.

Get a live call from our AI agent in about 10 seconds.