You inherited a 3CX server from someone who inherited it from someone else. It works, mostly, until it doesn't — and now you're the person staring at a SIP trunk config wondering what a BLF key is. If your business just needs to make calls, log them, and move on, you've outgrown 3CX in the opposite direction: it's too much system for too little team.
Here's how to move off it without losing your numbers, your voicemail, or a week of your life.
Why 3CX stops making sense for owner-operators
3CX is a real PBX. That's not a knock — it's powerful, flexible, and cheap per-seat if you have someone to run it. The catch is the "someone to run it" part. You're responsible for:
- The server (on-prem or your own cloud VM)
- OS patches, SIP security, fail2ban rules
- SIP trunk provider relationships and DID management
- Firmware on desk phones
- Backups, certificates, and the occasional 2 a.m. registration failure
None of that produces revenue. A hosted Phone System collapses all of it into someone else's problem. You get a dashboard, a mobile app, and a bill.
What to actually look for
Ignore feature matrices that compare 80 checkboxes. For a small team, four things matter.
1. Admin you can do in 30 seconds
Adding a user, changing a greeting, forwarding a number after hours — these should take a few clicks. If the demo involves the phrase "and then you'll want to open a ticket," keep looking.
2. Call logging that's automatic and exportable
Every cloud provider logs calls now. Don't pay extra for it. What you do want:
- CSV export of call history
- Recordings (with retention you control)
- Transcripts and summaries if your team is bad at writing notes
- A native integration or webhook to whatever CRM or spreadsheet you live in
3. A mobile app that actually works
Test this before you sign. Place a call on cellular, then switch to Wi-Fi mid-call. Receive a call with the app closed. Check that caller ID shows your business number, not your cell. A lot of "mobile apps" are abandoned wrappers — you'll find out fast. If your team is fully distributed and you'd rather assemble softphones against a raw API instead of buying seats, this guide to building a CPaaS-based softphone stack walks through the tradeoffs.
4. They handle porting and E911
If the provider treats number porting as a self-serve form you fill out alone, that's a yellow flag. You want a porting specialist who reads your current bill, catches the mismatched service address, and tells you when the FOC date lands.
What to skip
Things that sound important but aren't, at your scale:
- Advanced call queues and skills-based routing. You have five people. A ring group is fine.
- On-prem hybrid setups. The whole point is to stop running servers.
- Per-feature add-on pricing. If voicemail transcription costs extra, the base plan is a bait price.
- Hardware lock-in. Most cloud providers let you BYOD with any SIP-capable desk phone. Don't let a salesperson sell you a closet full of new phones unless yours are genuinely dead.
- Hunt for the cheapest per-seat number. Saving $4/user/month and then losing two hours a week to a clunky admin is a bad trade. Look at actual pricing including the things you'll really use, not the lowest sticker.
The migration checklist
Give yourself two to four weeks. Porting is the long pole; everything else is faster than you think.
Two to four weeks out
- Pull a recent invoice from your current SIP trunk provider or 3CX hosting. You'll need the account number, PIN, and exact service address for porting.
- List every DID (direct number) in your 3CX. Don't forget the fax line nobody uses and the warehouse number.
- Export call history from 3CX while you still have it. Keep a CSV for your records.
- Document the current call flow: who rings first, what happens after hours, what the voicemail says.
- Pick your new provider. Run a one-week trial with the mobile app on your actual phone.
One to two weeks out
- Submit the port request with the new provider. Include a copy of the current bill (CSR — Customer Service Record). Mismatches between the bill's service address and what you submit are the #1 reason ports reject.
- Set the FOC (Firm Order Commitment) date for a low-traffic morning. Tuesday or Wednesday around 10 a.m. is usually safe.
- Configure users, extensions, and ring groups in the new system.
- Record greetings. Or pay $30 to have someone with a real voice do it.
- Set up E911 for every user and every physical location. More on this below.
- If you're keeping desk phones, factory reset them and provision against the new system.
Port day
- Numbers typically cut over in a 1–4 hour window on the FOC date.
- Keep 3CX running until the port completes — calls in flight may route either way.
- Test inbound on every ported number from an outside cell.
- Test outbound caller ID shows the right number.
- Test 911 (call, tell the dispatcher it's a test, confirm address — or use your provider's test service if they offer one).
After the cutover
- Cancel the old SIP trunk and 3CX license. Don't forget the VM if it's running in AWS or Azure burning $40/month.
- Wipe and recycle or sell old hardware you're not reusing.
- Update your website, Google Business Profile, and email signatures if anything changed.
Don't skip E911
The FCC's Kari's Law and RAY BAUM's Act require that 911 calls from a multi-line phone system route to emergency services with a dispatchable location — meaning a street address and, where applicable, a suite or floor. For a cloud system, this is a per-user setting because users move.
For each user:
- Set a registered address that matches where they actually work.
- If you have remote staff, get their home address into the system.
- Make sure 911 calls notify someone internally (front desk, owner cell) when they happen. Most providers support this — turn it on.
This is not optional and fines exist. It's also a 10-minute task per user, so just do it.
10DLC and texting your business number
If you want to text customers from your main business number — which you almost certainly do, since customers text now — your new provider needs to support 10DLC registration. That means registering your business (brand) and use case (campaign) with The Campaign Registry so carriers will deliver your A2P messages. Hosted providers handle the paperwork; 3CX setups often don't text at all without bolting on a third-party service.
If your provider tells you texting "just works" without registration, they're either wrong or about to get your messages filtered. The SMS-deliverability post covers what actually happens when carriers see unregistered traffic.
What to do next
Pick two providers. Run a real one-week trial on both — make calls, send a text, add a fake user, export a call log, install the mobile app on your actual phone. The one that feels boring and obvious is the one to pick. Then start your port request and put the FOC date on the calendar.
If you'd rather not stitch porting, E911, call logging, and 10DLC together yourself, that's the whole reason our Phone System exists — calls, texts, and the compliance pieces in one place, set up in an afternoon. Either way, the goal is the same: stop being your own phone company.