Migrate 3CX to Yeastar PBX

I have a brand-new Yeastar cloud instance already spun up and a Twilio account fully authorised for Australian numbers. My existing 3CX PBX is still live, but I now need everything cut across to Yeastar within the next 48 hours.

Scope of work
• Build the Twilio SIP trunk on Yeastar and confirm registration.
• Create six extensions that mirror the current 3CX users (keep the same extension numbers).
• Replicate the existing call routing rules—day/night logic, voicemail destinations, and any hunt or ring groups—so inbound calls land exactly where they do today.
• Point each Twilio DID away from 3CX toward the new Yeastar trunk and verify inbound/outbound calling.
• Run test calls with me on completion to confirm audio quality, caller-ID presentation and fail-over behaviour.
• Provide a quick hand-off document or screen recording showing where everything was set so future tweaks are easy.

Environment & access
I will supply admin credentials for both the current 3CX and the Yeastar portal, plus Twilio console access for number routing. Work can be done fully remote; I’m on AWST and can be available for immediate questions or live testing.

Acceptance criteria
• All six extensions register successfully on softphones or desktop apps.
• All Twilio numbers route through Yeastar with no audio issues.
• Outbound caller-ID matches existing presentation.
• 3CX can be powered down without service interruption.

If you have solid Yeastar and Twilio SIP trunking experience and can slot this in right away, let’s get started—I’m ready to grant access as soon as you’re available.