Cloud PBX Cutover Day Jamaica: Step-by-Step Checklist for Going Live Without Downtime

Why Cutover Day Is the Riskiest Hour of Any Migration

You have spent weeks planning. Your extensions are mapped, your auto-attendant is recorded, your team has been briefed, and your SIP credentials have been tested on a staging number. Yet when live traffic hits the new cloud PBX for the first time, something unexpected nearly always surfaces — and the window for a clean recovery is measured in minutes, not hours.

For Jamaican businesses, the stakes are real. A medical clinic in New Kingston that loses its main line for two hours during cutover does not just miss calls — it loses patients who will dial a competitor. A logistics firm in Portmore whose dispatch line goes dark at 7 a.m. faces a standstill. Weeks of careful preparation mean nothing if the live switch is executed in the wrong order.

This checklist gives you a practical, hour-by-hour guide for the day itself: what to confirm the night before, the exact sequence for throwing the switch, how to verify the system is healthy in the first 60 minutes, and the hard triggers that should send you back to the legacy system before the situation gets worse.

T-24 Hours: What to Lock Down Before You Leave the Office

The evening before cutover is an active preparation period, not a rest day. Every item below must be signed off before staff go home.

• Configuration freeze: No changes to the new cloud PBX after 5 p.m. Last-minute dial-plan edits or re-recorded auto-attendant files introduce untested risk. Document anything outstanding and address it the morning after cutover.
• Legacy PBX confirmed operational: The old system must be fully functional and ready to accept inbound calls. If the cutover fails, you need to be able to restore service within minutes, not hours.
• Porting window confirmed with the carrier: Number ports in Jamaica activate during scheduled windows. Confirm the exact activation time so someone is watching when the flip occurs — not discovering it afterwards.
• Key staff notified with a specific time: Your receptionist, department heads, and IT contact need to know the exact cutover time — not a vague "tomorrow morning." Give them a time like 8:30 a.m.
• Outbound routes tested: Dial a local number, an international number, and the WOCOM support line from the new system. Confirm the correct caller ID is displaying on each.
• Full auto-attendant walkthrough completed: Call in from a mobile and navigate every IVR option. Reach every extension. Listen to every voicemail greeting. Do this the evening before — not on cutover morning.
• Mobile backup number ready: Have a personal mobile number available as a public failsafe during the cutover window. Post it to your WhatsApp Business status and Google Business Profile before the switch starts.

The Live Sequence: Order Determines Outcome

Doing these steps out of sequence is the single most common cause of avoidable downtime during cloud PBX migrations.

1. Route new DID numbers first. Before porting your main business number, confirm that newly assigned DIDs on the cloud PBX are receiving and routing calls correctly. This is your live proof-of-concept before anything irreversible happens.
2. Activate and confirm the SIP trunk. Register your SIP credentials and confirm the trunk shows as registered in the cloud PBX admin panel. Do not proceed to any porting until this is confirmed.
3. Initiate or confirm the port of your main business number. Once the trunk is confirmed live, trigger or observe the scheduled port activation for your primary inbound number.
4. Test the ported number immediately from an external line. The moment porting activates, call your main business number from a mobile outside your system. Confirm it rings the correct destination before doing anything else.
5. Decommission inbound routing on the legacy PBX. Only after confirming calls are landing correctly on the new system should you redirect or disable inbound routing on the old system. Leave the legacy PBX powered on and reachable.
6. Notify staff the switch is live. Send a group message or walk the floor immediately. Staff must know which system is active so they do not route callers to the wrong platform.

Never schedule a cutover for a Friday afternoon. If something goes wrong, you are looking at a weekend of disruption with limited vendor support available. Tuesday or Wednesday morning, between 7 a.m. and 9 a.m., is the safest window for most Jamaican businesses.

The First 60 Minutes: Active Monitoring, Not Relief

The hour immediately after going live is not the time to relax. Assign one person — your IT contact, your office manager, or a WOCOM support engineer — to actively monitor during this window.

• Watch the live call log. Your cloud PBX admin panel shows inbound and outbound activity in real time. A flat dashboard during a normally busy period is a red flag — investigate immediately.
• Confirm ring times. Calls should ring at extensions for the correct duration before forwarding to voicemail or overflow. A ring time that is too short may indicate a dial plan error.
• Ask a staff member to make an outbound call. Confirm it completes and that the caller ID displayed to the recipient is correct.
• Check voicemail notification delivery. Allow a call to hit voicemail and confirm the email notification arrives at the correct address within five minutes.
• Listen for one-way audio reports. If staff can hear callers but callers cannot hear them — or vice versa — this indicates a NAT or firewall configuration issue. Flag it immediately and do not let calls continue in this state.

Rollback Triggers: When to Call It Off

A rollback decision made at 9:15 a.m. costs 45 minutes. The same decision made at 2 p.m. costs a day. Agree on your rollback triggers before cutover morning so the call is made on logic, not panic.

Trigger a rollback if any of the following occur in the first two hours:

• Inbound calls are not reaching any extensions and the cause cannot be identified within 15 minutes
• One-way audio is affecting more than one concurrent call
• The SIP trunk deregisters and does not recover within 10 minutes
• A critical department — billing, dispatch, or patient services — has a complete inability to receive calls
• Outbound calls display an incorrect or missing caller ID and the issue cannot be resolved remotely

To roll back: restore inbound routing on the legacy PBX, redirect your main number back to the old system with your carrier, and notify all staff. Keep the new system online but remove it from the live call path. Document exactly what happened and schedule a debrief with your provider before the next attempt.

Day-After Validation: Confirming Everything Settled

Not all issues surface on day one. Number porting propagates across carriers at different speeds, and call recording storage can take 24 hours to confirm. The morning after cutover, run these checks:

• Review total inbound call volume against the same weekday from the previous two weeks. A significant drop suggests some routing did not fully propagate.
• Test inbound calls from both Digicel and Flow mobile numbers. Porting confirmation on one carrier's routing table does not guarantee it on another's.
• Confirm call recordings are accessible for calls taken on cutover day, and that files are downloading correctly.
• Remove the temporary mobile backup number from your Google Business Profile and WhatsApp status once you are confident everything is stable.
• Send a brief feedback form to staff asking about call quality, any missed calls they are aware of, and voicemail delivery. Technical logs miss what your front-line team notices.

Move to Cloud PBX With WOCOM Alongside You

WOCOM does not hand you credentials and step away. Our team works with you through the configuration audit, the pre-cutover testing, and the live cutover window — so that if something needs adjusting on the day, we are already on the line.

Businesses across Kingston, Portmore, Montego Bay, and beyond have moved from legacy PABX systems to WOCOM's cloud platform, keeping their existing numbers and maintaining call quality without a gap in service.

If you are planning a migration and want to get the cutover right the first time, speak with our team today. Visit wocomja.com or reach us through the contact page — we will assess your current setup and build a migration plan that puts your business continuity first.