Retiring a Hosted PBX for Cloud Calling

The challenge

Calling ran on a hosted open-source PBX — capable, but a separate system to understand and maintain for an organisation with no technical staff, and one more thing that only works while somebody remembers how it was set up.

Where we came in

For an organisation this size the right answer is usually the one with the fewest moving parts, not the most capable one. Since the collaboration platform was already licensed and already carried calling, the migration removed a system rather than replacing it with an equivalent.

What we did

• Confirmed which numbers were migrating and mapped the intended call flow during discovery
• Purchased and assigned the required calling licences
• Initiated the number port and managed the porting window
• Configured call routing and an auto-attendant on the new platform
• Retained a troubleshooting phase after cutover rather than closing at go-live

Where it landed

• Calling moved onto the platform the organisation already licensed, retiring the separate PBX
• Existing numbers were ported rather than replaced
• Post-cutover troubleshooting was scoped into the engagement, not treated as an extra