School districts and universities planning to replace a legacy phone system like an Avaya CM or Mitel MiVoice Business during summer 2027 should begin the discovery and budgeting process in fall 2026. A successful migration requires much more than choosing a cloud calling provider: institutions must inventory every phone and analog line, validate their networks, design accurate 911 location information, coordinate number porting, integrate paging and emergency notification systems, and complete training before students and faculty return.
The summer break creates an excellent implementation window, but it also creates a fixed deadline. Construction projects, vacations, limited building access, enrollment activities, summer classes and the start of fall athletics can quickly consume the available time. The safest approach is to complete design, procurement and most configuration before the final day of the 2026–2027 academic year.
This guide gives K–12 districts, colleges and universities a practical path from a legacy PBX—such as an older Avaya, Mitel, Cisco, NEC or other on-premises platform—to a modern cloud communications solution.
Why education organizations are moving beyond the legacy PBX
Many education phone systems still work, but “still working” is not the same as being sustainable. Common warning signs include:
- Manufacturer end-of-support dates or shrinking access to replacement parts
- Dependence on a small number of technicians with platform-specific knowledge
- Separate systems at different schools or campuses
- Expensive PRI circuits, aging gateways and proprietary handsets
- Limited support for mobile and hybrid employees
- Inconsistent 911 location information
- Difficult changes when staff move between rooms or buildings
- Weak reporting, call analytics and centralized administration
- Poor integration with Microsoft Teams, Google Workspace, Microsoft 365 or modern contact-center tools
- Limited options for continuity when a campus loses power or internet access
A cloud phone platform can centralize administration, make users and locations easier to manage, support calling from desk phones, computers and mobile devices, and reduce dependence on aging PBX hardware. The goal, however, should not be to reproduce the old system in the cloud. The project is an opportunity to improve how faculty, staff, parents, students and public-safety personnel communicate.
The summer 2027 planning timeline
September–November 2026: Discovery, inventory and stakeholder alignment
Start by creating a project team that includes information technology, facilities, campus safety, administration, procurement and representatives from high-call-volume departments. In a university environment, include housing, admissions, registrar, athletics, health services and departmental IT. A K–12 district should involve principals, transportation, special education, food service and district security.
Build an inventory by physical location—not just from the PBX database. Record:
- Every main number, direct number, extension and toll-free number
- Desk, classroom, office, common-area and emergency phones
- Main office and departmental call flows
- Auto attendants, hunt groups, queues and recorded announcements
- Fax machines and fax numbers
- Analog classroom, elevator, pool, boiler-room, door-entry and courtesy phones
- Fire, security, intrusion and environmental systems that may use phone lines
- Paging, bell, intercom and mass-notification connections
- Blue-light and emergency call stations
- Contact-center functions, call recording and reporting requirements
- Athletic facilities, remote buildings and temporary locations
- Current carrier services, account numbers, service addresses, contracts, authorized contacts and account PINs
Do not assume the existing extension list is accurate. Walk the buildings, interview local staff and compare physical findings with carrier invoices and PBX programming.
At this stage, define success. Examples might include one administrative platform for all sites, accurate dispatchable 911 locations, improved parent call handling, mobile service for administrators, integration with Microsoft Teams, redundant connectivity and reduced support risk.
November 2026–January 2027: Requirements, budget and procurement strategy
Turn the inventory into functional requirements and a realistic budget. Decide which users need a full cloud communications profile, which need a basic or common-area profile, and which locations require only an analog adapter, paging interface or emergency device connection.
Your budget should consider more than monthly user licenses. Include:
- Professional services and project management
- New desk phones, analog gateways and paging adapters
- Network switching, Power over Ethernet and cabling remediation
- Primary and backup internet connectivity
- Session border controllers or survivability appliances, if required
- Taxes, regulatory fees and carrier charges
- Call recording, contact center, SMS, fax and analytics options
- Training, on-site cutover support and post-launch support
- Early-termination charges or overlapping service during migration
- Removal or responsible disposal of legacy equipment
For public institutions, align the project with board approvals, competitive procurement rules, cooperative purchasing agreements, legal review and funding deadlines. If an RFP is required, issue it early enough to allow demonstrations, reference checks, contract negotiation and implementation—not merely vendor selection—before summer.
January–March 2027: Select the solution and complete detailed design
Evaluate the provider and the implementation partner separately. A strong cloud platform can still produce a poor result if no one takes responsibility for discovery, dial-plan design, number porting, field deployment, integrations, testing and training.
Require finalists to demonstrate the actual workflows your institution uses. Ask them to show:
- A parent or student calling a main number after hours
- A caller reaching attendance, transportation, admissions or campus safety
- A 911 call from a classroom, office, residence hall or remote building
- Operation during an internet or power disruption
- A principal, superintendent, dean or on-call employee using mobile and desktop apps
- Central administration across multiple schools or campuses
- Paging, door-phone, analog-device and contact-center integrations
- Single sign-on, multifactor authentication and automated user provisioning
- Role-based administration, audit logs and retention controls
Complete the dial plan, site structure, user classes, emergency locations, call flows, security policies and device standards before configuration begins. Confirm who owns every decision and establish a formal change-control process.
March–May 2027: Build, integrate, test and prepare users
Most of the cloud environment should be configured while the legacy PBX is still operating. This creates time to test without placing the opening of school at risk.
Recommended activities include:
- Configure users, sites, numbers, auto attendants, queues and schedules
- Connect identity management and single sign-on
- Install or stage phones, analog adapters and gateways
- Test paging, bells, intercoms, door phones and emergency devices
- Validate network quality, VLANs, Quality of Service and firewall settings
- Confirm backup internet, power and call-forwarding procedures
- Record professional greetings and emergency announcements
- Train IT administrators, front-office personnel and departmental champions
- Submit number-porting documentation and resolve carrier discrepancies
- Test every 911 location using an approved, non-emergency validation process coordinated with the provider and local public-safety procedures
Do not wait until June to discover that a carrier account name does not match the port request, a fire alarm uses an undocumented copper line or a remote athletic building has inadequate connectivity.
June–August 2027: Pilot, migrate and stabilize
Begin with a controlled pilot involving IT, administration and a small group of representative users. The pilot should include different device types, buildings and use cases—not only technically experienced employees.
After the pilot is accepted, migrate in manageable phases. A typical sequence might be:
- IT and project-team users
- District or university administration
- Low-complexity schools or departments
- High-volume offices and contact-center groups
- Complex sites with paging, analog or life-safety integrations
Schedule number ports and physical phone deployment carefully. Maintain a written rollback or contingency plan, even when the cloud configuration has already been tested. After each phase, verify inbound and outbound calling, caller ID, transfers, voicemail, queues, paging, emergency calling and after-hours routing.
Leave enough time before opening day for stabilization. A cutover completed the weekend before students return provides almost no margin for correcting hidden analog lines, incomplete call flows or training gaps.
Ten requirements that belong in every education cloud-phone evaluation
1. Emergency calling and precise location information
Emergency calling is a design requirement, not a final checklist item. Kari’s Law requires direct 911 dialing and notification capabilities for covered multi-line telephone systems, while the FCC’s rules implementing Section 506 of RAY BAUM’S Act address transmission of a dispatchable location with 911 calls. For a school or campus, that location may need to identify the building, floor, room, wing or other information that helps responders find the caller quickly. See the FCC’s multi-line telephone system requirements and dispatchable-location guidance.
The design must account for fixed phones, softphones, mobile users, remote staff, residence halls and devices that move between network ports or wireless networks. Institutions should also determine who receives on-site 911 notifications and how campus safety personnel coordinate with local first responders.
2. Network and power resiliency
A cloud phone system depends on the local network and wide-area connectivity. Review internet capacity, latency, packet loss, firewall configuration, Power over Ethernet, switch capacity and UPS runtime at every site.
Resiliency may include diverse internet providers, automatic failover, cellular backup, redundant switching, local survivability, preset call forwarding and mobile-app continuity. Document what happens when a classroom loses power, one building loses connectivity or the entire district’s primary carrier fails.
3. Cybersecurity and identity management
Require single sign-on, multifactor authentication, least-privilege administration, encryption, logging, secure retention policies and a defined incident-response process. CISA recommends that K–12 organizations prioritize the most impactful security measures and address systemic cybersecurity risk; its K–12 cybersecurity resources provide a useful planning reference.
Avoid unmanaged shared administrator accounts. Define who can change emergency locations, listen to recordings, view messages, export call data or modify main-number routing.
4. Privacy, records and contractual protections
Determine what information the platform will store, where it will be stored, who can access it, how long it will be retained and how it will be deleted when the agreement ends. Review voicemail transcription, call recording, SMS, contact-center interactions and directory synchronization with legal and records-management staff.
The U.S. Department of Education provides a cloud-computing FAQ and data-security resources for K–12 and higher education. Institutions should evaluate FERPA, state student-privacy laws, public-records obligations, accessibility requirements and any institution-specific policies with qualified counsel.
5. Paging, bells and mass notification
Cloud calling does not automatically replace a paging or bell system. Determine whether existing speakers and amplifiers will remain, whether paging is zone-based or all-call, and how routine paging differs from emergency mass notification.
Test page initiation, audio quality, priorities, scheduled bells and failover behavior. If emergency notification spans phones, speakers, SMS, email and desktop alerts, define which platform initiates the event and which system is authoritative.
6. Analog and specialty devices
Fax machines, elevator phones, alarm panels, modems, postage machines, pool phones and door-entry systems can delay an otherwise well-planned migration. For each device, decide whether to replace it, convert it to IP, connect it through an analog adapter, retain a purpose-built line or retire it.
Life-safety and code-regulated devices require coordination with the relevant vendor, authority and applicable codes. Never disconnect a legacy line merely because it has little or no visible call traffic.
7. Parent, student and public call flows
Map the caller experience for school closures, holidays, registration, attendance, transportation, admissions, financial aid and emergency events. Preserve access to a live person where appropriate and avoid deeply nested menus.
Use schedules and centralized templates, but allow authorized local control for weather closures, building-specific notices and special events.
8. Accessibility and inclusive communications
Include accessibility requirements in procurement and user testing. Review compatibility with relay services, hearing devices, accessible desktop and mobile applications, real-time text where applicable, voicemail transcription and alternative notification methods. Involve the institution’s accessibility team before selecting the platform.
9. Administration, reporting and support
Clarify what the internal IT team will manage and what the implementation partner or provider will handle. Evaluate moves, adds and changes; bulk user updates; delegated administration; audit history; call-quality diagnostics; inventory; emergency-location management; and reporting.
Require an escalation plan for opening week, severe-weather events and critical calling failures. Obtain references from organizations with comparable numbers of users, sites and complex integrations.
10. Contract flexibility and total cost
Compare solutions over the full contract term, not only by the advertised per-user rate. Confirm annual increases, minimum quantities, optional-feature pricing, support scope, service-level commitments, renewal language, data-export rights and exit assistance.
Match licenses to actual use. A classroom phone, an admissions counselor, a campus operator and an occasional mobile user may not require the same profile.
Common migration mistakes to avoid
- Starting after the RFP is awarded. Discovery and network assessment should shape the procurement document, not follow it.
- Treating the project as a phone swap. Call flows, identity, security, emergency response and business continuity are equally important.
- Porting every number at once. A phased approach limits disruption and makes lessons from early sites useful to later sites.
- Ignoring analog lines. Undocumented elevator, alarm, fax and emergency devices are frequent sources of delay.
- Assuming Microsoft Teams replaces every telephony requirement. Teams may be part of the user experience, but institutions still need to evaluate carrier services, 911, analog support, paging, contact center, resiliency and administrative support.
- Waiting until summer to train. Administrators and front-office teams should practice with the new call flows before the cutover.
- Scheduling too close to opening day. Reserve several weeks for stabilization and corrections.
What should be completed before students leave in spring 2027?
By the last day of the 2026–2027 academic year, the institution should have:
- A validated inventory of users, numbers, devices, lines and integrations
- An executed agreement and assigned implementation team
- Approved system design, call flows and emergency-location plan
- Completed network remediation or a firm installation schedule
- Clean carrier records and accepted port requests
- Configured core services and staged equipment
- Tested integrations and representative 911 locations
- A published cutover, communication, training and contingency plan
If these items are not substantially complete, the institution should reassess whether a full summer 2027 migration remains prudent or whether a narrower first phase would reduce risk.
Frequently asked questions
When should a school district or university start planning for a summer 2027 cloud phone migration?
Planning should begin by fall 2026, with inventory and requirements completed before procurement and detailed design beginning no later than early 2027.
How long does a school cloud-phone migration take?
A multi-site education migration commonly requires several months of discovery, design, contracting, configuration, testing and training; complex paging, analog, emergency-calling or contact-center requirements can extend the schedule.
Can a school keep its existing phone numbers?
In most cases, existing numbers can be ported, but the institution must verify ownership, authorized contacts, service addresses, account numbers, PINs and contractual obligations well before cutover.
Can existing desk phones be reused?
Sometimes, but compatibility depends on the phone model, hardware revision, firmware, licensing and the selected cloud platform. Reuse should be confirmed through an actual pilot rather than assumed from a model-number match.
Does moving to the cloud eliminate the need for backup service?
No. Schools and universities still need plans for internet outages, power failures, carrier disruptions and local network failures, including how emergency and main-number calls will continue.
Should a district or university use Microsoft Teams as its phone system?
Microsoft Teams Phone may be appropriate for some or all users, but the decision should account for 911 location management, analog devices, paging, common-area phones, contact-center needs, uptime strategy, carrier design and support responsibilities.
What is the most important first step?
The most important first step is a physical and carrier-level inventory of every number, phone, analog line, call flow and integration across all buildings.
Prepare now for a controlled summer 2027 cutover
The best summer migrations are largely designed and built before summer begins. Starting in fall 2026 gives education leaders time to develop a defensible budget, run a fair procurement, correct network issues, resolve carrier records and test the details that affect safety and daily operations.
High Country Workplace Technologies helps school districts, colleges and universities evaluate, design and deploy cloud and on-premises communications solutions. Because HCWT works with both legacy PBX environments and modern cloud platforms—including RingCentral, Zoom Phone, Vonage, Microsoft Teams integrations, Mitel and supporting network technologies—our team can identify what must be migrated, what can be reused and what should be redesigned.
This article was authored by Jim Whitfield
Planning a summer 2027 migration? Contact HCWT now to schedule a communications and infrastructure assessment before the procurement calendar becomes the project’s biggest risk.