The migration to cloud phone is straightforward when planned well and chaotic when not. Here is the eight-week schedule that works reliably for nonprofits up to 50 staff.
Week 1: Audit and inventory
- List every phone number your organization owns. Carrier bill helps; older lines often hide.
- List every extension. Note who uses it, how often, and what features they rely on.
- Catalog every integration: CRM, scheduling tools, fax, paging, door entry.
- Document call patterns: typical volume, peak times, after-hours behavior.
Output: a spreadsheet that becomes the source of truth for the rest of the project.
Week 2: Vendor selection
- Run two or three demos against the audit doc.
- Ask the ten questions from our buying checklist.
- Get reference calls from peer nonprofits.
- Get a written quote tied to the configuration in your audit.
- Review contract terms with someone other than the executive director.
Output: a signed contract or, equally valuably, a deliberate decision to stay with what you have.
Week 3: Account setup and number porting initiation
- Account provisioned by the new vendor.
- Number porting orders submitted (these take 5 to 15 business days; start now).
- Admin training scheduled with the vendor's onboarding team.
- Internal project channel set up: who is doing what, by when.
Common gotcha: porting requires the EXACT account name and address from your current carrier. Pull the latest bill. Mismatches reject the port.
Week 4: Configuration design
- Build the auto-attendant menu.
- Define call queues and routing rules.
- Configure each user with the right tier and features.
- Set up integrations (CRM, calendar, etc.).
- Customize voicemail greetings (organization-wide and per-user).
Output: a working test environment using temporary numbers. Place test calls. Find what does not work. Fix it.
Week 5: User onboarding
- Distribute account credentials to staff.
- Run a 60-minute live training session for staff (with recording).
- Run a 30-minute live training for active volunteers.
- Each user installs the desktop and mobile apps and signs in.
- Each user records their personal voicemail greeting.
Common gotcha: training a week before cutover is the right amount. Too far in advance and people forget; too close and there is no time to fix issues.
Week 6: Parallel operation
- New cloud system live, but old system still active.
- Internal calls and outbound calls flow through the new system.
- Inbound calls still go to the old system; staff use the new system to dial out.
- Daily standup: any issues? What broke? What needs fixing before cutover?
Output: confidence. By Friday of week 6, the team should be using the new system fluently for everything except inbound.
Week 7: Cutover
- Numbers port over the weekend (vendor coordinates).
- Inbound calls now arrive on the new system Monday morning.
- Old system kept active in parallel for one week as a safety net.
- Daily check-in: any inbound calls landing on the old system? Any callers reporting issues?
Common gotcha: a number occasionally fails to port and falls back to the old carrier. Have the old system live for the safety week to catch this.
Week 8: Decommissioning
- Old carrier service formally canceled in writing.
- Maintenance contracts canceled.
- Hardware leases returned (return shipping handled).
- Final audit: confirm new system is handling 100% of traffic correctly.
- Document new admin procedures for the team.
Output: a fully migrated, fully optimized phone system. And, equally importantly, no more legacy bills hitting your accounting team next month.
The unspoken phase: month 3
Three months after cutover, do a usage review. Are there volunteer seats that have not signed in? Drop them. Are there features no one is using? Remove the add-ons. Are there features the team did not know about? Schedule a refresher training. The migration is not complete until the system is right-sized to actual usage.
