Introduction

Customers running 3CX on-premise or in the cloud (e.g Google or Amazon etc) can switch to 3CX Hosted and have us host your installation. Why should you do this:

• We deploy your instance and automatically configure the firewall rules.
• We manage the 3CX operating system, including security patches and version upgrades (i.e. from Debian 10 to Debian 11)
• We take nightly backups.
• We keep your 3CX on the latest non-beta update.
• We monitor your 3CX system 24/7.

Requirements for 3CX-hosted instances:

• You must use a supported SIP trunk.
• You must use a 3CX FQDN.
• You can not use CFD (Call Flow Designer) apps.
• IP phones must be run behind the 3CX SBC.
• FXO and ISDN gateways are not supported.
• No remote system-level (e.g. SSH) or web terminal access to the machine.
• Network settings, Parameters, License Key, Failover, custom IP-phone templates, scriptable IVRs, and Path and Quota for Recordings or Voice mail can not be changed.

Preparing for the Switch

From On-premise to 3CX Hosted

To transfer an on-premise installation into the cloud, complete the below checklist to ensure a smooth transition and minimize downtime and device re-provisioning.

1. Move to a SIP trunk (if you have a PSTN gateway) - If you are running PSTN lines  in combination with PSTN gateways, first you need to move to a 3CX supported SIP trunk provider. Configure and test run the SIP Trunk on your current (on-premise) installation.
2. Install an SBC (if you are using IP phones) - If you are using IP phones, you must deploy a 3CX SBC using your 3CX FQDN.  The IP phones need to be re-configured to use the 3CX SBC. Installing the 3CX SBC is easy and free. You can use an existing Windows or Linux PC/VM, mini PC or a Raspberry Pi 4 and run the SBC as a standalone or failover cluster service. During the setup of the SBC, the PBX’s FQDN should be used to connect. 
   Note: Now is the time to think whether you still need IP phones as in many cases our Web Client and smartphone apps are much more flexible and easier to maintain.
3. Test run your system to ensure your SBC and SIP Trunk are working correctly with your on-premise installation. When you switch to “Hosted”, both your SIP trunks and your IP Phones will connect automatically.

From Self-Hosted to 3CX Hosted

You must make sure that your current SIP Trunk Provider is supported for “Hosted” (it needs to be a register-based SIP Trunk)

Completing the Switch

1. Download a configuration backup of your existing system and save it locally. Note: The 3CX backup must include the “License Key Information, FQDN & Conference” option.
2. From your 3CX Customer Portal account, go to “Systems” and find the instance you want to migrate.
3. Select “Switch to Hosted”, choose “Hosted by 3CX” and press “Next”.
4. Choose “Over 10 Users - 3CX Dedicated”, then click “Next”.
5. Click “Yes” to upload your configuration backup
6. Your 3CX-hosted instance will be up within 15 minutes (restore time depends on size and content).

Note: DNS Change Delay - After migration is completed, it can take up to one (1) hour for your DNS information to be updated.

Migration Support

Please note that this service does not include technical support and does not replace the need for a partner if you require support to configure 3CX.