Switching from 3CX, Without the Drama

Deciding to switch is the hard part; the switch itself is mostly choreography. This guide covers the parts specific to leaving 3CX, then the universal order that keeps any provider change boring. For the side-by-side numbers first, see Cannon VoIP vs. 3CX.

What leaving 3CX involves

Leaving 3CX is different because you own the system: your numbers live with your SIP trunk carrier, not with 3CX, so the port request goes to that carrier. Find the trunk contract (it has its own term and notice window) and your license renewal date, and simply let the license lapse once you've moved.

The good news: 3CX shops run standard SIP phones, so phones on our supported list carry over, and there's no more server, hosting bill, or upgrade project. Export recordings and voicemails from your own server before you decommission it, since after that it's your backup or nothing.

The safe switching order (same for everyone)

• Inventory every number you own, including fax, toll-free, and forgotten tracking numbers. Unported numbers die with the old account.
• Pull a current bill or customer service record; porting paperwork must match it exactly.
• Export everything you want to keep: recordings, voicemails, contacts, reports.
• Get the new system fully built and tested before any port date. Ours ships preconfigured and we run the cutover with you.
• Cancel the old service only after every number has ported. Never first.

What the move to Cannon VoIP looks like

Numbers port for $15 per line; most move the next business day with about two minutes of downtime, and scheduled multi-line ports get a firm date. Desk phones you already own carry over if they're on our supported list, which includes popular Fanvil, Yealink, Grandstream, Cisco and Poly models (such as the Poly VVX 150, 250, 350 and 450), and other models can be added with a configuration template; anything new ships preconfigured overnight from our office next to DFW Airport. Service is $34 per extension, month to month, with texting, transcription, queues, and CRM integrations included, so the feature mapping usually ends with a shorter bill and a longer feature list. The whole vendor-neutral version of this process lives in our switching checklist.

The technical side of the cutover

Your phones already speak plain SIP to a system you control, which makes this the smoothest hardware migration on this list: repoint or factory-reset, and keep whatever VLAN and QoS work you've already done, it transfers as-is. Decommission the PBX only after recordings and voicemails are exported, and remember your SBC and any firewall rules for the old server can be retired too.

Phones and provisioning. The short version: we handle it. New Cannon Certified phones ship preconfigured and set themselves up the moment they're plugged in, which is the path we recommend, because it's the one with zero surprises on cutover day. If you'd rather keep supported phones you already own, we support that too: factory-fresh Fanvil, Yealink and Grandstream phones find us on first boot, Cisco and Poly phones set up with a one-time link, and our team handles the rest during onboarding, so nobody at your office is digging through phone menus or provisioning servers.

Network. Two settings decide most call-quality outcomes on day one: disable SIP ALG on the router (the classic cause of one-way audio), and confirm QoS prioritizes voice. If desk phones are PoE-powered, sanity-check the switch's power budget before adding units. Our plug-and-play appliance ($148) handles the network side automatically and gives our support team a secure path in for troubleshooting.

Numbers, texting, and caller ID. Porting moves the numbers; three registrations move with them. A 911 address is registered on each phone number during setup, checked with 911 systems first (the law requires it); an extension at another site can get its own 911 number, each building can be a 911 site with its own address, and 911 calls from the mobile app send the phone's location. Business texting re-registers under 10DLC when numbers change carriers, which we handle, but plan for a short texting settling period on port day. And CNAM plus attestation re-establish on our side, where calls get the highest trust rating (full attestation) when the number truly belongs to the caller; if callers ever saw "Spam Likely" on your old service, this is typically where that ends.

Call flows and integrations. Your setup comes across by import, not rebuilt by hand: 3CX version 18 update 7 or version 20 imports live, older 3CX systems import from a backup file, and 3CX menu wording needs no re-recording. You review a plan with counts before anything is applied, and an import report lists anything that couldn't come across. Old recorded prompts and greetings can come across as sound files, or be re-spoken in a new professional voice, and optional discovery calls can ring your old system and record its menu wording word for word. Your old system keeps taking calls until your numbers port. The built-in CRM is included, so contacts and deals can move in by spreadsheet import. CRM integrations reconnect with a fresh OAuth sign-in per platform, and fax moves to T.38 or cloud eFax rather than hoping analog tones survive.