Moving to a cloud phone system: a migration checklist.

A checklist, not a product comparison

Our guide to the 3CX cloud phone system explains how the platform works and the deployment choices. This article is the other half: a working checklist for the move itself, whatever system you choose. If you are planning a 3CX project, the business phone system page describes what Missan Global, a 3CX Partner, delivers.

1. Map your call flows first

Before touching technology, write down how calls move today. Who answers the main number? What happens after hours, on public holidays and when the receptionist is busy? Which calls go to a team, which to a person, which to voicemail? Draw it on one page, then ask each department whether it is right. Most migration surprises come from flows nobody documented, such as a fax line, a lift phone or a door entry unit.

2. Inventory numbers and lines

List every number, its purpose, its provider and what is connected to it. Decide which numbers move to the new system and which are retired. Moving existing numbers between providers is called porting. Rules, timelines and paperwork vary, so check with your carrier and the regulator on current rules before you promise a date to anyone. Keep the old lines live until the new ones are proved.

3. Choose handsets and softphones

Decide who needs a desk phone and who is better served by an app on a laptop or mobile.

• Reception and shared areas usually keep desk handsets.
• Mobile and hybrid staff often prefer a softphone on the same extension.
• Headsets matter more than most people expect, so test them.
• Check whether existing handsets are compatible before buying new ones.

4. Check network readiness

Voice is sensitive to a poor network, so test before you move. Look at internet bandwidth at each site, the quality and stability of the line, and whether you have a backup link. Voice traffic usually needs to be prioritised over bulk traffic, which is called quality of service, and the Wi-Fi must be good enough for softphone calls. Switch ports, power for handsets and cabling should also be checked. Our Wi-Fi and network design service and the multi-site Wi-Fi guide cover the foundations.

5. Plan emergency calling

Make sure emergency numbers can be dialled from every handset and app, and that the location information associated with each user or site is correct. If staff work remotely, explain how emergency calls behave from a home or mobile connection. Check the details with your carrier and confirm the current requirements before go-live, and test emergency routing as part of acceptance.

6. Decide your call recording approach

If you record calls, decide why, who can listen, where recordings are stored and how long they are kept. Tell callers and staff clearly. Consent and notification requirements can be complex, so confirm your wording and practice with a legal adviser. Our PDPL basics article gives general background on handling personal data.

7. Plan cutover and fallback

A calm cutover is usually staged. Move a pilot group first, run both systems side by side where possible, and choose a quiet period for the main switch. Before the day, agree:

• The order in which numbers, sites and teams move.
• Who is on hand, and how staff report problems.
• A fallback: how to send calls back to the old lines or to mobiles if something fails.
• A point at which you decide to proceed or roll back.

Keep the old system available until you are comfortable that every number and flow works.

Common pitfalls

• Forgetting auxiliary lines such as alarms, lifts, card machines or fax.
• Testing only internal calls and not calls from mobile networks and international numbers.
• Leaving out the after-hours and public-holiday routing.
• Going live on a busy day, or on a day when nobody senior is available to decide.
• Updating the main number but not the numbers printed on websites, signage and email signatures.

8. Train people and check afterwards

Give staff a short guide covering transfers, voicemail, call pickup, the mobile app and how to report faults. Walk reception through the new call flows in person, and name a few confident colleagues in each team who can help others in the first days. After go-live, review missed calls, queue behaviour and user feedback, then adjust. The free IT health check can include a look at the network your phones depend on. Missan Global has supported UAE organisations since 2004 from its head office in Al Majaz, Sharjah.