Cloud telephony migration: what to plan for

Moving a switchboard to cloud telephony on the Côte d'Azur without cutting numbers is a controlled sequence — inventory, portability, QoS, training — not an improvised weekend. SMEs from Nice to Monaco, and organizations in Tourrettes-sur-Loup, are switching under pressure from the end of the PSTN and the need for mobility. Host Technology acts as the integrator: network, SIP trunk or cloud IPBX, 4G backup, and business settling-in in the same package.

Cloud, on-premise, or hybrid: decide before the quote

Cloud: mobility, light multi-site setups, dependence on the WAN. On-premise: local control, low internal latency, a rack to maintain. Hybrid: local switchboard plus remote softphones. The choice depends on the number of handsets, PACA sites, continuity requirements, and LAN maturity. Host makes the assessment before pushing a license.

The cloud does not excuse a messy LAN: softphones and IP handsets remain sensitive to saturated Wi-Fi and missing QoS. Host Technology often refuses to port numbers until the network foundation has been validated.

Line and usage inventory

DID numbers, queues, IVR, faxes still in use, alarms, “legacy” lines nobody dares to cut. Each use has an IP target or a temporary adapter. Without an inventory, portability leaves gaps and reception discovers silence on Monday morning.

Include voicemail, ring groups, and call-recording rights in the inventory: those are what waste time on the Monday after cutover if they are discovered too late.

Network foundation: QoS and voice VLAN

Voice over IP requires a clean LAN: voice VLAN, QoS, PoE switches, a firewall opened correctly for SIP/RTP. Moving to the cloud on saturated Wi-Fi or FTTH without prioritization means trading a stable analog line for mediocre VoIP. Host Technology validates the network before portability day.

Also measure jitter and packet loss toward the chosen cloud provider, not only local throughput. An FTTH link that is fine on download can be poor on upload during backup hours.

Portability: the window that matters

Complete DID list, RIO, losing and gaining operators, cutover slot. Avoid Friday evening without on-call cover. Prepare a rollback plan and overflow mobiles. Host runs the operator contact so you are not juggling three hotlines.

Multi-site portability (Nice plus Monaco, for example) needs phasing: a pilot site, then expansion. Host avoids simultaneous cutovers on every address with no settling-in period.

The 7 steps of a cloud telephony migration

1. Inventory of lines, DIDs, queues, IVR, fax, and special uses.
2. Choice of cloud / on-premise / hybrid IPBX according to sites and continuity.
3. Target numbering plan and rights by department.
4. Validation of fiber, voice VLAN, QoS, and 4G/5G backup.
5. Portability: complete file, window, cross-checks.
6. Training for reception and managers (transfer, queues, mobile overflow).
7. Settling-in week: tickets, schedules, welcome messages, adjustments.

Each step produces a deliverable: inventory file, VLAN diagram, test report, training attendance sheet. That is what turns a cloud migration into a project management can audit.

What breaks most often

Numbers not ported, a firewall cutting SIP, teams not trained, no backup if the fiber drops, IPBX config backups forgotten. These five points are handled before cutover day. Post-cutover managed IT absorbs the fine tuning (schedules, queues, messages).

Add backup of call recordings and configs before any major post-migration update. Host managed IT schedules these points in the maintenance calendar.

Backup and continuity

A 4G/5G link in failover, tested failover rules, a mobile overflow number: cloud telephony does not excuse the lack of a plan B. On the Côte d'Azur, a local fiber cut happens; the switchboard must not follow it. Host includes telecom backup and monitoring in the same project.

4G backup must be tested with a real inbound call during a simulated failover, not only with a ping. Cloud voice crosses the firewall differently from web browsing.

Training and change management

Reception must know how to transfer, queue, and overflow to a mobile. Managers must know supervision rights. One hour of on-site training avoids weeks of “it doesn’t work anymore” tickets. Host Technology trains on the real system, not on a marketing demo.

Planning reinforced support in the first week (on-call or extended hours) reduces stress at reception. Host Technology includes it in the migration package.

After migration: monitoring and backup

Trunk registered, links up, IPBX configs backed up, call recordings inside the retention policy. Telephony, network, and backup remain three building blocks of the same managed-IT contract. A cloud migration succeeds only when day-to-day operations are stable.

Finally, align monitoring: trunk registered, WAN latency, config backup jobs. The migration is closed only when these indicators stay green for several business days.

• SIP trunk availability, call quality, latency, and packet loss on each Internet access.
• Status of handsets, gateways, queues, and overflow scenarios to mobiles.
• Backup of configurations, welcome messages, and the numbering plan after every significant change.
• Tracking of licenses, unused numbers, and supervision rights so recurring costs stay under control.

The thirty-day review compares the target with reality: lost calls, wait time, perceived quality, tickets, and feature use. Some queues need simplifying, schedules correcting, or licenses reassigning. This settling-in period is normal provided it is managed. Host Technology organizes the adjustments with reception and department heads, then updates the operations file so every rule stays understandable.

• Test an inbound and an outbound call on each main number and each ported direct number.
• Validate open hours, closed hours, public holidays, announcements, voicemail, and overflow destinations.
• Simulate loss of the primary link and confirm that backup keeps priority calls.
• Train one contact per department on transfers, conferences, queues, and simple diagnostic procedures.

For multi-site SMEs in PACA, shared governance stops each branch from recreating its own rules. The numbering plan, user profiles, and backup policy are aligned, while keeping the specifics of Nice, Cannes, Monaco, or Tourrettes-sur-Loup. The integrator can then add a site or a remote worker without starting from zero, with consistent security and a clearer bill.

FAQ

Does a move to cloud telephony necessarily cut service?

No. A short operator window can exist during portability, but it is prepared with temporary forwards, backup mobiles, and tests. Risk rises above all when the number list is incomplete or the network has not been validated. Host Technology schedules the slot, coordinates the old and new operators, and keeps a way to be contacted during the transition, which makes the cutover manageable for reception and for clients.

What Internet connection is needed for voice over IP?

The throughput needed per call is modest, but stability, latency, jitter, and packet loss are decisive. A fast fiber link saturated by backups can still produce poor quality. Flows must be measured, QoS applied, and a backup link planned. Sizing takes into account the maximum number of simultaneous calls, the site’s other uses, and the SME’s continuity objectives.

Can existing numbers be kept?

Most numbers can be ported if the holder, the address, and the operator information are consistent. Main numbers, direct numbers, fax, and technical lines must be inventoried before anything is cancelled. Cancelling early can lose a number. Host Technology checks the portability file, follows any rejections, and asks for the old services to be closed only after calls have been fully validated.

Can current phones be reused?

It depends on their SIP compatibility, their condition, whether the platform supports them, and their ability to receive security updates. Reusing a recent estate can reduce the budget, but keeping unsupported handsets creates technical debt. The audit separates equipment to keep, to reconfigure, or to replace. Headsets, accessories, and reception modules are checked as well, so there is no bad surprise after cutover.

How do you protect cloud telephony against fraud?

Administrator accounts must be secured with MFA, expensive destinations limited, caps applied, authentications monitored, and unused interfaces closed. Default passwords and overly broad SIP rules must be ruled out. Alerts must trigger a clear action if consumption is abnormal. Host Technology ties these controls to the firewall and to managed IT, because telephone fraud often crosses several technical layers.

Ready to move your switchboard to cloud telephony without cutting clients off? Contact Host Technology (Tourrettes-sur-Loup, interventions on the Côte d'Azur and in Monaco) for an audit covering inventory, portability, and QoS.