Most migration guides assume you are moving from a legacy PBX to VoIP for the first time. But what about the second migration — when your current VoIP provider is not cutting it and you need to switch to a different one?
This is actually harder than the first migration. Here is why, and how to do it without disrupting your business.
Why VoIP-to-VoIP Is Harder
| Challenge | First Migration (PBX to VoIP) | Second Migration (VoIP to VoIP) |
|---|---|---|
| Number porting | From telco (straightforward) | From VoIP provider (may resist) |
| User expectations | Low (any improvement is welcome) | High (they expect at least the same features) |
| Integration rewiring | Fresh setup | Must replicate existing CRM/helpdesk connections |
| Training | Everyone learns together | People resent relearning |
| Political risk | Approved project | "Why are we changing again?" |
The Porting Trap
Some VoIP providers make it intentionally difficult to port numbers away. Tactics I have seen:
- 30-day cancellation notice required before they will release numbers
- Porting department only available by email with 5-day response times
- "Your account has a balance" — even $0.47 blocks the port
- LOA rejection on technicalities (wrong address format, missing middle initial)
Before you sign with any provider, test the exit process. Call their porting department. Ask: "If I wanted to port my numbers out, what is the process and timeline?" Time the response. If it takes more than 24 hours to get an answer, imagine how long the actual port will take.
The Parallel Run Strategy
The safest approach:
| Week | Action |
|---|---|
| Week 1 | Set up new provider with temporary numbers |
| Week 2 | Configure all features (IVR, ring groups, recording, CRM) |
| Week 3 | Pilot with 5-10 users on temporary numbers |
| Week 4 | Fix issues found during pilot |
| Week 5 | Submit port request to move numbers from old to new |
| Week 6-7 | Port executes (keep old system active as backup) |
| Week 8 | Decommission old provider |
The key insight: set up everything on temporary numbers FIRST. Test thoroughly. Only submit the port request after you are confident the new system works. This way, if something goes wrong, your old system is still running on your real numbers.
Feature Parity Checklist
Before migrating, document every feature your team actually uses on the current system:
- [ ] Auto-attendant (record the exact menu structure)
- [ ] Ring groups (list every group and its members)
- [ ] Call recording settings (who is recorded, retention period)
- [ ] Voicemail greetings (save the audio files)
- [ ] Speed dials and BLF keys
- [ ] CRM integration mappings
- [ ] Call flow rules (business hours, holidays, after-hours)
- [ ] Fax configurations
- [ ] Conference bridge settings
Missing even one of these during migration will generate complaints.
What I Recommend
Providers like VestaCall handle VoIP-to-VoIP migrations specifically. They assign a migration specialist who documents your current setup, replicates it on their platform, and manages the porting process end-to-end. The parallel run period is included at no extra cost.
The second migration does not have to be painful. It just requires more planning than the first one.
