A VoIP migration checklist keeps a phone-system change from becoming a rushed porting event. Before a Florida business moves its main number, it should document every number, rebuild call flows, configure emergency locations, prepare users and decide what happens if the office internet fails. The migration should be tested before customers are sent to the new system.
1. Inventory Every Phone Number
Start with the current carrier bill and phone-system records.
List:
- Main number
- Direct numbers
- Department numbers
- Fax numbers
- Toll-free numbers
- Numbers used for SMS
- Marketing numbers
- Alarm or specialty lines
Do not assume a number is unused because nobody recognizes it immediately.
Some numbers may still be published online or tied to a vendor.
2. Confirm Porting Information
For each number, document:
- Current carrier
- Account number
- Authorized business name
- Service address
- Billing telephone number
- Porting PIN if required
The FCC says customers can often keep an existing phone number when switching providers, including between wireline, IP and wireless services. See the FCC's number-portability guidance.
Do not disconnect the old service before the port completes.
3. Map the Existing Call Flow
Write down what happens when someone calls.
Document:
- Greeting
- Auto attendant
- Department options
- Ring groups
- Queues
- Timeout behavior
- Voicemail
- Business hours
- Holidays
- After-hours forwarding
- On-call routing
This is the time to remove old complexity.
Do not automatically reproduce a ten-year-old phone tree if customers no longer need it.
4. Decide What Should Improve
A migration is an opportunity to fix workflow problems.
Ask:
- Should calls ring multiple locations?
- Do employees need mobile apps?
- Should voicemail go to email?
- Is bilingual routing needed?
- Which users need SMS?
- Should missed calls overflow to another team?
- Can after-hours routing be simpler?
FLTECHS uses FlowPBX for business phone systems, call routing, SMS/MMS and integrations and lists English and Spanish support.
5. Prepare the Network
VoIP depends on networking.
Before cutover, test:
- Internet stability
- Firewall
- Switches
- Cabling
- Wi-Fi where softphones are used
- Power over Ethernet
- UPS backup
If call quality is poor during testing, investigate the network before moving the main number.
6. Decide How to Handle Internet Failure
Document the failover plan.
Options may include:
- Mobile apps
- Another office
- Alternate numbers
- Cellular internet failover
- Remote call-routing changes
Ready.gov says business preparedness should include communications, IT recovery and continuity planning. See Ready.gov's emergency plan guidance.
For Florida companies, test this before hurricane season.
7. Configure Emergency-Calling Locations
Emergency calling is not an afterthought.
FCC rules for interconnected VoIP address location information for 911 calls, including dispatchable or registered location depending on the type of service. See the FCC's 911 location requirements for interconnected VoIP.
For every office and remote user, understand:
- What location is registered
- How location changes are updated
- Who owns the process
- What happens when a device moves
Do not assume a desk phone knows where it is.
8. Configure Caller ID
Decide what should display on outbound calls.
Different users or departments may need:
- Main business number
- Direct number
- Department number
Confirm the provider's caller-ID process and test before launch.
9. Configure Devices and Apps
Prepare:
- Desk phones
- Cordless phones
- Desktop apps
- Mobile apps
- Headsets
- Conference phones
Give employees enough time to learn basic tasks before the old system disappears.
10. Train Users on the Important Functions
Most employees do not need a two-hour class.
Teach them how to:
- Answer
- Transfer
- Park or hold
- Check voicemail
- Use the mobile app
- Set availability
- Send SMS if authorized
- Get help
Create a short cheat sheet for common tasks.
11. Test Before the Port
Test:
- Inbound calls
- Outbound calls
- Transfers
- Auto attendant
- Queues
- Voicemail
- Business hours
- After-hours routing
- Mobile apps
- SMS where applicable
Use test numbers before the published main number moves.
12. Plan the Porting Day
Assign one person to coordinate with the provider.
On cutover day:
- Confirm old service is still active
- Confirm new system is ready
- Monitor port status
- Test inbound calls after completion
- Test outbound caller ID
- Test voicemail
- Test major call flows
- Notify staff when complete
Avoid making unrelated network changes on the same day if possible.
13. Keep the Old Equipment Until the Migration Is Stable
Do not remove everything immediately.
Confirm:
- All numbers ported
- No missed specialty lines
- Users can work
- Call flows are correct
- SMS is functioning where expected
- Fax replacement is working if applicable
Then schedule removal.
14. Review the System After One Week
Real customer calls reveal issues testing may not.
Ask staff:
- Are calls reaching the right people?
- Are queues too long?
- Is the menu clear?
- Are mobile apps working?
- Are there missed calls?
- Are after-hours calls handled correctly?
Make adjustments while feedback is fresh.
Chantell Borges of Bonita Concierge Medicine says on the FLTECHS home page, “FLTECHS offers affordable VOIP service and great customer service as well.”
For more planning context, see Business VoIP for Miami and Naples: What to Know and VoIP vs. Landline for Florida Businesses.
Frequently Asked Questions
How long does a VoIP migration take?
It depends on the number of users, numbers, locations, hardware and porting requirements. Build and testing can happen before the final number port.
Will we lose our business number?
Eligible numbers can often be ported, but every number should be verified before the migration is scheduled.
Should we cancel the old provider first?
No. Keep the old service active until porting is complete and the new system is verified.
Can we migrate multiple offices at once?
Yes, but phased migrations can reduce risk for complex environments. The right approach depends on the business.
FLTECHS provides business VoIP with FlowPBX for Florida companies that need planned migrations, call routing and ongoing support.