Migrating from 3CX to Hosted Cloud PBX in Jamaica: Audit, Port, Configure
Why Jamaica Businesses Are Moving Off 3CX
3CX became popular because it offered a modern, software-based PBX without the cost of a proprietary Avaya or Panasonic system. You licensed the software, installed it on a local server or a cheap VPS, and owned the whole stack. For many Kingston and Montego Bay businesses that made sense in 2015 — but the model carries a hidden cost most owners do not budget for: someone has to manage the server, apply security patches, replace hardware when it fails, and renew the annual licence.
Hosted Cloud PBX removes all of that. There is no server to own, no patch cycle, and no renewal to miss. The provider manages the infrastructure; you manage your users and your call flows. For businesses with ten to two hundred staff, total cost of ownership almost always falls after migration — and resilience improves significantly because a hosted platform runs on redundant infrastructure rather than a single box in your server room or a VPS you do not monitor at 2 a.m.
Audit Everything Before You Touch a Setting
A 3CX migration that runs into trouble almost always skipped the audit phase. Before you request a number port or provision a single Cloud PBX extension, document every configuration your 3CX system handles today. A spreadsheet covering the following six areas takes two to three hours to complete and prevents a week of firefighting after go-live.
- Extensions and users — Export your full extension list from the 3CX management console. Record the extension number, assigned user, device type (IP desk phone, Windows softphone, mobile app), and any special settings such as call recording or monitoring.
- Inbound routes — List every DID number, the trunk it arrives on, and which extension, ring group, or queue it is routed to. This mapping is what you will rebuild in your Cloud PBX dial plan.
- Digital receptionist menus — Document each IVR level, the audio prompts used, and every keypress destination. Download the audio files from your 3CX server now — you will need them when you configure the Cloud PBX auto-attendant.
- Ring groups and queues — Record the agent list, ring strategy, maximum wait time, and failover destination for each group.
- Call recording settings — Note what is recorded, where recordings are stored, and whether a legal or compliance retention period applies. Confirm where recordings will live after the migration before you cut over.
- Third-party integrations — Check whether 3CX is connected to a CRM (Zoho, HubSpot) or any other system via API, webhook, or CTI. These connections will need to be re-established on the Cloud PBX side.
Number Porting: The Item That Sets Your Timeline
Your phone numbers are the most time-sensitive element of the migration. In Jamaica, porting a business number typically takes five to ten business days once the receiving carrier submits a completed port request. That window is your single biggest scheduling constraint — everything else can be built in parallel while you wait.
Submit the port request as early as possible in the project. While porting is in progress, build and test the entire Cloud PBX configuration. On the day port completion is confirmed, your new system takes live traffic and your 3CX server can be stood down or run briefly in parallel as a fallback.
Three porting details matter for 3CX deployments specifically:
- 3CX does not own your numbers. The numbers are registered to the carrier your SIP trunk connects to. The port goes from that carrier to WOCOM — not from 3CX itself. If you are unsure which carrier holds your numbers, check your monthly SIP trunk invoice.
- Group all numbers in one request. If you have a mix of geographic Kingston numbers and non-geographic lines, include them in a single port request so they cut over together and you avoid a split period where some numbers are on the old system and some on the new.
- Match the account name exactly. The name on the port request must match the name on your current phone bill character for character. A mismatch is the most common reason port requests are rejected and add days to your timeline.
Translating 3CX Configuration to Cloud PBX
3CX and hosted Cloud PBX use different terminology for largely the same underlying features. Working through your audit spreadsheet column by column, here is how the concepts map:
- 3CX Digital Receptionist → Cloud PBX Auto-Attendant. Upload your existing audio prompts and recreate the keypress routing. The logic is identical; the interface is different.
- 3CX Ring Group → Cloud PBX Ring Group or Hunt Group. Configure the same members, ring strategy (sequential, simultaneous, or round-robin), and timeout. Failover destinations map directly.
- 3CX Queue → Cloud PBX Call Queue. Set the same maximum wait time, hold music, and agent list. If you use a callback option in 3CX, verify the Cloud PBX equivalent is configured before go-live.
- 3CX SBC (Session Border Controller) → not required. A hosted Cloud PBX handles NAT traversal on the provider's infrastructure. After migration you can remove the SBC from your network, which simplifies your firewall rules and eliminates one more piece of hardware to maintain.
- 3CX call recording → Cloud PBX call recording. Recordings are accessible from the hosted portal. If your business records calls for compliance reasons — financial services, credit unions — confirm the retention period and export capabilities with WOCOM before migration day.
Cutover Day: Parallel Run, Then Switch
The safest approach is a parallel run of one to two days where both systems are provisioned but inbound traffic still arrives on 3CX. Your team makes outbound test calls from Cloud PBX extensions to confirm audio quality, dial plan behaviour, and device provisioning before any external call reaches the new system.
When you are satisfied with testing, cutover follows a short sequence:
- Confirm port completion with WOCOM — you will receive written confirmation.
- Verify that inbound calls to your main number reach the Cloud PBX auto-attendant correctly.
- Make a brief outbound call from two or three extensions to confirm caller ID is presenting correctly.
- Check voicemail-to-email delivery on at least one mailbox.
- Brief staff on any interface changes — new softphone app, different transfer key sequence, or updated hold procedure.
Schedule cutover for mid-morning on a Tuesday, Wednesday, or Thursday. Avoid Friday afternoons and Monday mornings — both are high-volume periods for most Jamaica businesses and leave little room to handle anything unexpected that surfaces on go-live day.
After Migration: Decommission Clean
Once your Cloud PBX has run cleanly for five business days, the 3CX server can be shut down. Before powering it off, take a final backup of call recordings, voicemail audio files, and any configuration documentation you want for reference. Then cancel the 3CX licence subscription, reclaim the server resources for another purpose, and close the SIP trunk credentials with your previous carrier.
Post-migration is also the right moment to clean up your extension list. Migrations consistently reveal ghost extensions — users who left two years ago, phones that have never been plugged in, and queues that have not rung in months. Starting Cloud PBX with a clean, accurate extension list makes ongoing administration simpler and reduces your licence costs.
Migrate with WOCOM's Support
WOCOM has helped Jamaica businesses migrate from 3CX, Asterisk, Avaya, and legacy PABX systems to hosted Cloud PBX. The team handles number porting, assists with configuration mapping, and provides a parallel-run window so your business never faces a hard cut with no fallback.
If you are running 3CX today and want to understand what a hosted Cloud PBX would look like by comparison, bring your extension count and your current monthly phone bill to a WOCOM assessment. We will give you a clear cost breakdown and a proposed migration timeline.
Ready to move off your server? Contact WOCOM at wocomja.com/contact or call 876-926-6268 to book a no-obligation migration assessment.
Continue exploring
Ready to upgrade your communications?
Talk to our team about the right solution for your business.
Book a Demo Contact SalesEverett Kildare is WOCOM's voice and infrastructure specialist, with more than 25 years of experience designing and running carrier-grade voice, SIP and virtualization infrastructure. Holding a BSc in Information Technology, he has built, secured and migrated phone systems for businesses of every size. Everett writes WOCOM's technical coverage of SIP trunking, cloud PBX, contact centres, business continuity and migration.