Move off 3CX without rebuilding the call flows from scratch.
Users, contacts, business hours, IVRs, ring groups, queues, SIP trunks and IP phones each have a documented mapping from 3CX to Yeastar P-Series. TeraFi supports Australian partners through the design, the cutover and the weeks that follow it.
Most of the configuration has a direct mapping.
Yeastar publishes a step-by-step guide for moving from 3CX to P-Series. It is written around interface-to-interface replication rather than a rebuild, which is what keeps the effort predictable enough to quote.
- Account information: extension numbers, user names, email addresses, mobile numbers
- Account settings: voicemail state and PIN, IP phone registration credentials
- Contacts imported into the Yeastar phonebook
- Business hours, holidays and uploaded voice prompt files
- IVR, ring group, queue and voicemail configuration
- Allowed country codes, blacklisted numbers, IP blacklist and whitelist
Where the guide stops.
The guide covers user and configuration data, SIP trunks, call control and IP phones. Anything outside that list — bespoke integrations, reporting history, recordings already captured in 3CX — is a separate decision that belongs in the migration scope before a date is set.
The trunks move last, and that is deliberate.
The documented order keeps the 3CX system functioning while the Yeastar system is built and populated. The service moves at the point the trunks are cut across, which makes the window short and scheduled rather than open-ended.
Users and configuration first
Import users and contacts, then replicate business hours, call features and system security while 3CX continues to carry live calls.
Linkus before cutover
Set up Linkus clients for users so the new experience is in place and tested ahead of the change.
Then the SIP trunks
Migrate the trunks and replicate inbound routes, outbound routes and emergency numbers. This is the point the service changes hands.
Phones last, by network scenario
Same subnet, different subnets and remote networks each have their own reprovisioning procedure. Establish which applies per site during discovery.
Tell the customer what changes before the cutover, not after.
Feature parity on core telephony is close. The differences that generate support calls are the ones nobody mentioned during the sale.
- Remote extensions connect over an encrypted tunnel using a Yeastar-supplied domain name, with either a Yeastar-managed or an onsite SBC — without a customer-owned SBC or inbound firewall ports opened
- The Linkus desktop client covers Windows and macOS
- Call Flow Designer is built into the PBX interface rather than a separate application
- Operator and queue panels are independent, with drag-and-drop call dispatch
- Outbound call centre, agent pause reasons and satisfaction surveys are available
Be straight about the other direction.
Wake-up IVR is a 3CX feature without a direct Yeastar equivalent, VoIP quality monitoring sits on the Yeastar roadmap rather than shipping, and 3CX positions a heavier video conferencing capability than Yeastar’s SME-oriented meetings. Raise these during design if the customer relies on them.
What TeraFi does on a 3CX migration.
You keep the customer relationship. TeraFi works behind it on the design decisions, the licensing position and the parts of the transition that carry the most risk.
Where partners use us most
- Validating the target edition against who operates the environment
- Mapping the current feature use to a Yeastar licence position
- Reviewing numbers, trunks and porting before a date is committed
- Acceptance criteria, fallback and hypercare structure
- Escalation during and after the cutover
Bring the next 3CX renewal to us before it lands.
The earlier a migration is scoped, the more of it can be scheduled rather than improvised. Send the current-state evidence and the customer outcome.
Fact-checked on 22 September 2026 against the Yeastar PBX Migration Guide: From 3CX to Yeastar (v1.0) and the Yeastar vs. 3CX feature comparison (March 2026). The migration guide is written against 3CX V18; feature availability and migration requirements must be confirmed for each environment and software version.