Switching phone providers is not complicated. It just has a lot of moving parts.
Six weeks is the right amount of time. Less than that and things get rushed. More than that and momentum dies. This is the plan we run with customers moving to Vocatech. It works for any provider. Use it.
Each week has a focus and a short checklist. Do the work each week and port day is boring, which is exactly what you want.
Week 1. Inventory
You cannot move what you have not counted. Week one is entirely about writing down what exists today.
Most businesses discover at this step that they are paying for more than they thought, or they are missing things they assumed were in place. Both findings are useful.
Checklist for week 1.
- Count every extension in use. Who owns it, what phone do they use, do they still work here.
- List every DID (direct inward dial number) on the account. Main line, department lines, fax lines, vanity numbers.
- List every integration. CRM, ticketing, calendar, Teams or Webex, recording storage, analytics tools.
- Document your auto attendant flow. What options play, what they route to, what the after-hours message says.
- Document your hunt groups and ring rules. Who rings first, who rings second, how long before voicemail.
- Write down your business hours and holiday schedule exactly as configured on the current system.
- Check recording retention requirements. Are you under HIPAA, FINRA, or any other rule that mandates a specific retention period.
- Pull your last three months of phone bills. Note total cost, line items, and any fees you do not recognize.
By end of week 1 you have a single document describing your current system. Save it. This becomes the spec for the new provider.
Week 2. Provider Selection
Week two is about choosing who you will move to. If you already know, great. Spend the week verifying the choice.
The right questions to ask any provider.
- What is the full price at my seat count, including all fees. Not the advertised price. The invoice price.
- Is the contract month-to-month, or is there a minimum term. Ask for the contract in writing before you commit.
- What infrastructure do you run on. BroadWorks, Asterisk, custom stack. Each has tradeoffs.
- Is there a free trial, and what does it include. A real trial means full platform access, not a demo.
- When I call support, who picks up. Ask directly. Get a name if you can.
- Do you offer a HIPAA BAA if I need one. Ask even if you are not sure, because you might be.
- How long does a port take, and who handles it. The right answer is that the provider handles it.
- If I need a custom integration you do not have, what happens. Is there a workshop, or is the answer no.
Call the support number before you sign anything. A real human picking up on a business day at 2pm is a better signal than any marketing page. If the answer is a voice menu, a callback form, or an offshore ticket queue, you have your answer.
Week 3. Account Provisioning
By the end of week two you have picked a provider and signed. Week three is setup.
Good providers do most of this for you. You approve decisions and test. Bad providers hand you a portal and a tutorial video. If the answer is self-service for a 20-seat business, reconsider the choice.
Checklist for week 3.
- Create every user in the system. Name, email, extension, role.
- Build the auto attendant. Match your existing flow. Record greetings.
- Configure hunt groups. Same members, same ring order, same fallback.
- Set business hours and holiday schedule.
- Create voicemail boxes for each user. Configure notification preferences.
- Configure after-hours routing. Where do calls go at 6pm, on Saturday, on a holiday.
- Assign temporary test numbers so you can dial the new system before the port.
By end of week 3 the new system is ready to receive calls. The only thing missing is your actual phone numbers.
Week 4. Integrations and Devices
Week four is the glue. The phone system has to connect to everything else you use.
This week is usually where projects slip, because integrations reveal surprises. A CRM field that was custom. A ticketing tool that was connected five years ago and nobody remembers how. A Teams calling policy that is going to break when you change carriers.
Checklist for week 4.
- Wire up the CRM integration. Confirm caller context pops correctly on a test call.
- Configure any Teams or Webex integration. Test calling out, receiving in, presence sync.
- Order phones if you are using physical desk phones. Allow one week for shipping.
- Order headsets for desk users who prefer them.
- Install the softphone or desktop app on every user machine. Test login.
- Install the mobile app on every user phone. Test calls in and out.
- Configure call recording storage and retention. Confirm compliance requirements are met.
- Set up Callpop or equivalent desktop caller context if included.
By end of week 4, your users can receive calls on the new platform through the temporary numbers. Everything that will work after the port is working now, minus the real numbers.
Week 5. Pilot and Training
Week five is where you find out what is broken. Better to find out now than on port day.
Pick three users. Ideally one from each key role. A front desk person who takes a lot of inbound calls. A salesperson who makes a lot of outbound. A manager who uses analytics. Give them the new platform as their primary phone for the week, running in parallel with the old one.
They will find things. Wrong extension on a transfer. CRM pop showing the wrong contact. A ring rule that was meant to fire after three rings firing after five. Every issue they find this week is an issue you do not have to handle on port day.
Checklist for week 5.
- Run a 45-minute training session for all users. Live, not a recorded video.
- Distribute a one-page cheat sheet. Top ten things users do, in screenshots.
- Run the three-user pilot for the full week.
- Track every issue in a shared list. Fix or explain each one before week 6.
- Confirm with the new provider that the firm-order commitment date is scheduled.
- Notify customers and vendors of the upcoming port date (usually not required, but sometimes helpful).
- Back up any voicemail messages from the old system that matter. They do not transfer.
By end of week 5 you have a system that works for real users doing real work. You also have a date for port day.
Week 6. Cutover
The last week. Most of it is waiting.
The port itself happens on a scheduled morning, usually very early, sometimes over a weekend. Calls stop going to the old carrier and start going to the new one. The whole event takes minutes once it starts. The lead-up is where all the work lives.
The night before port day.
- Confirm the firm-order commitment time with the new provider.
- Keep the old system live and paid. Do not cancel yet.
- Have the emergency contact number for your new provider visible and tested.
- Send a final internal note to staff so they know when the switch will happen.
Port day.
- Test inbound calls from at least three external lines in the first thirty minutes.
- Test outbound calls including one long-distance and one toll-free.
- Confirm voicemail delivery.
- Verify the auto attendant plays correctly.
- Verify hunt groups ring correctly.
- Verify CRM pop is firing with correct caller identification.
- Watch for cached calls still hitting the old system for up to 24 hours. Forward any that arrive.
The week after.
- Leave the old service active for seven full days after the port. Then cancel in writing.
- Review the final invoice from the old provider. Dispute any overages.
- Send any missed voicemail or forwarded calls back into the new system.
- Check analytics on the new system. Volume, average handle time, abandoned calls. Compare to week 5.
By end of week 6, the switch is done. You should not have missed a business call. Your users should be working on the new system as if they had always been.
Red Flags to Watch For in a Provider
Before we close. A few signals that you are about to hire the wrong provider. If any of these show up in the sales process, slow down.
A rep who will not put the price in writing. If the number keeps shifting, or you get quoted one price verbally and a different one on the paperwork, walk away. The final invoice will do the same thing.
No phone support. Some providers run support entirely through chat, email, or tickets. For your email or your Netflix account, that is fine. For your phone system, that is a disqualifier. When phones are down, you need a human now.
No trial period. Any provider who will not let you try the product before you sign a contract does not believe the product is good enough to sell on its own merits.
Multi-year contract required. If the only way to get acceptable pricing is a three-year commitment, the pricing is designed to trap you, not to serve you. Month-to-month exists. Demand it.
Vague answers about fees on invoice. Ask directly what regulatory, compliance, or recovery fees will appear on your invoice. A straight answer means transparent pricing. An evasive answer means you will find out by opening your first bill.
An offshore support team with no U.S. escalation. Offshore tier-one support is fine for scale. The problem is when there is no path to a U.S. engineer when something real breaks. Confirm there is one before you sign.
Refusing to name their infrastructure. A serious provider will tell you what they run on. BroadWorks, Asterisk, FreeSWITCH, custom. If the answer is marketing fog about a proprietary platform, the platform is probably duct tape.
The Last Thing
The biggest predictor of a smooth migration is the provider doing the migration, not you. If you find yourself doing the provisioning, running the port paperwork, and debugging the integration on your own, you picked the wrong team.
A good provider runs the port. You approve the date. You test the output. That is it.
Six weeks. One focused week at a time. No drama on port day.
About Vocatech
Vocatech is a business phone service founded in Brooklyn in 2008. Built on Cisco BroadWorks with our own platform on top. Callpop, Reports with AI transcription and summaries on our own GPUs, Textdock for SMS and WhatsApp inside Cisco Webex, a Portal for admins, and a custom integrations team.
$29.95 per seat flat. Month to month. Everything included. Free port-in. Free trial through the end of the month. HIPAA BAA available. The engineers who built the product pick up the phone when you call.
Over a thousand businesses. 97% retention. Eighteen years.
Start a trial at vocatech.com/contact, see pricing at vocatech.com/pricing, or compare at vocatech.com/compare.