Phase 1: Assessment and Planning (Weeks 1 to 2)
Before selecting a provider or committing to a timeline, take stock of what you have and what you need. This phase is about gathering information, not making decisions.
- Document all current phone numbers and which departments or users they belong to
- List all features your team currently uses: voicemail, call recording, call groups, auto-attendant, conferencing
- Assess internet connection quality at each office location (minimum 100 kbps per concurrent call, plus headroom)
- Identify any regulatory requirements such as HIPAA, call recording mandates, or retention requirements
- Get quotes from 2 to 3 cloud providers with your full feature list
Phase 2: Provider Selection (Weeks 2 to 3)
With a clear picture of your requirements, evaluate providers on fit rather than price alone. Key selection criteria:
- Features vs. your list. Confirm the provider includes every feature you documented in Phase 1 in the plan tier you are considering.
- Number porting process. Porting your existing phone numbers to the new provider takes time (typically 2 to 4 weeks). Understand the process and timeline before you commit.
- Hardware compatibility. If you want to reuse existing IP phones, confirm they are compatible with your chosen provider.
- Migration support. Ask specifically what migration support is included. Some providers offer dedicated onboarding assistance; others hand you documentation and wish you well.
Phase 3: Number Porting (Weeks 3 to 6)
Number porting is the most time-sensitive part of a cloud migration. Submit your port requests as early as possible because the process involves your current carrier releasing the numbers, which can take 2 to 4 weeks and may require paperwork. During porting, your numbers will still ring on your old system, so there is no interruption, but you need to plan for the parallel operation period.
Phase 4: Configuration and Testing (Weeks 5 to 7)
While number porting is underway, configure your new cloud system. Set up users, extensions, auto-attendant menus, call groups, and voicemail. Test all call routing thoroughly before any numbers are ported over. Have a small group of early testers use the new system for internal calls for at least a week before any cutover.
Phase 5: Cutover and Training (Weeks 7 to 8)
Plan your cutover for a low-traffic period, typically early in the week rather than Friday afternoon. Train all staff on the new system before the cutover date. Document key workflows: how to make a call, how to check voicemail, how to transfer a call, how to access the mobile app. Keep the old system accessible for 1 to 2 weeks after cutover as a fallback.
Common Migration Mistakes
- Starting number porting too late and running out of time before a planned go-live date
- Not testing internet quality before assuming VoIP will work at each location
- Skipping staff training and assuming the new system is intuitive enough to use without guidance
- Canceling the old system before the new one is confirmed stable
- Not documenting all phone numbers before the migration starts, leading to missed ports
Recommended Cloud Providers for Migration
Based on migration experience, number porting support, and onboarding quality, the top providers for organizations migrating from legacy systems are PanTerra Networks, RingCentral, and Nextiva. All three offer dedicated migration support teams and have experience with PBX replacement projects across a range of business sizes.
