Better connections. Business first.
BUYER GUIDE · MIGRATION

A phone migration
your team can prepare for.

Plan discovery, routing, device setup, porting, training and acceptance as one coordinated change. Give each phase an owner and a clear completion condition.

Get a Quote
THE SHORT ANSWER

A Cloud Phone migration plan should cover number and dependency discovery, approved routing, connectivity and device readiness, configuration, user training, porting and acceptance. Assign business and technical owners, rehearse important calls and agree the cutover and fallback. The launch date depends on carrier processing and readiness, not simply the day a phone system is configured.

Discovery: understand what is being replaced.

Inventory numbers, providers, equipment, locations and specialist connections. Ask reception and department leads to explain current routes and the situations that do not work well.

Record who owns each number and account, which services must stay active and who can authorize changes. Include mobile staff and users who move between locations. This prevents the project from treating the main office as the whole company.

The output is a shared requirements brief and dependency list. It should be understandable to the business owner as well as the technical team.

Design: approve the routing and responsibilities.

Document the main number, department and extension plan, office schedules and fallback for each important caller type. Decide whether AI answers first during business hours, supports overflow or handles closed-office requests.

For queues, agree membership, availability, announcements, maximum-wait handling and any automated callback option. Keep callback requests captured by AI separate from automatic queue calls. Name who receives and reviews every resulting request.

For recording, approve its purpose, included and excluded calls, automatic or on-demand operation and the business’s notice and consent process. Document listening, download and deletion rights, retention, storage and archiving responsibilities. Confirm the selected edition and version support the intended controls. Review how existing recordings will be accessed or retained; moving phone numbers does not move those files.

Prepare: devices, connectivity and people.

Check the network, internet, power, supported devices and app access. Review service addresses and emergency-calling limitations with the provider. Prepare a continuity contact method.

Set up the proposed configuration and rehearse with test numbers where available. Reception should practise transfers and unavailable destinations. Mobile users should test calls in the places and network conditions where they normally work.

Training should focus on everyday tasks and exceptions. A short reference for answering, transferring, changing availability and finding support is more useful than expecting every user to learn the whole administration console.

Reference: CRTC: VoIP emergency-calling information

Cut over only when the dependencies are ready.

Confirm the carrier process and the people available to test. Keep old service active until the number transfer is complete. Agree temporary routes and who can authorize a change if an issue occurs.

Migration gates
PhaseReady when
DiscoveryNumbers and dependencies have owners
DesignThe business approves routing and fallbacks
PreparationDevices, apps and test users are ready
PortingCarrier details and cutover contacts are confirmed
AcceptanceAgreed calls pass and issues have owners
HandoverSupport and change instructions are retained

Accept the external and internal experience.

Test all published numbers from an outside phone, then test extensions between locations. Check two-way audio, caller ID, transfers, queue behaviour and the approved no-answer route.

Include a closed office, holiday, unavailable agent and AI-to-human handoff where those are in scope. Confirm that requests actually arrive in the correct inbox or supported workflow. Record the result before closing the project.

Where recording is in scope, make a fictional sample call and listen to the saved result. Test the chosen recording mode, approved notice, reviewer access, restricted-user access and deletion permissions. Confirm the retention and archive settings and the person responsible for capacity alerts. Keep exported files within the business’s agreed handling process.

After the move, review remaining old services, the first bills and any unresolved items. Keep the accepted routing plan current as people and locations change.

DIRECT ANSWERS

Questions buyers ask.

How long should a migration take?

Timing depends on numbers, carrier processing, equipment, connectivity, configuration and staff readiness. Set phases and completion conditions before committing to a cutover date.

Who should lead the project internally?

Name a business decision-maker for routing and scope, a technical contact and a representative at each location. Reception and key receiving teams should participate in acceptance.

What should we keep after handover?

Retain the number inventory, routing plan, configuration responsibilities, user instructions, support contacts and change process. If recording is enabled, retain its approved scope, permissions, notice process, storage and retention responsibilities, including arrangements for any recordings kept from the previous system.

LET’S CONNECT

A phone system that works
the way your business does.

Tell us what happens when the phone rings. We’ll start there.

Get a Quote

Optional website measurement

With your permission, we use optional event measurement and, when configured, Google Analytics cookies to understand page visits, demos and inquiries. We exclude inquiry contents and URL query strings. Off by default. See our Privacy notice.