On premises to hosted, confirming process.

[Earthbound]

From what I have read in the forums and learned via research, as follows, please add any corrections needed.
1. Create a new cloud instance in our account.
2. In that cloud instance: create the storage location.
3. Create a backup, not to exceed 3GB of our on premise 3CX system.
4. Load that backup into the storage location created in the cloud instance.
5. Log into the cloud system and restore the backup from the storage location.

Question: What settings in the on premise should I change/remove pre-backup?

Thank you in advance for your time and energy!

 

[Colorado VoIP]

I think you can tidy up a step if you're keeping the same FQDN. just backup from your onsite system and restore the backup during install of the new cloud machine. it's an option upon creation to just restore a file.

 

[Earthbound]

My bad, I forgot to mention that the on premise has a custom FQDN and I will need to change that to the one provided by 3CX.Should I backup my on premise with the 3CX provided FQDN?

 

[SteveITS]

See if this thread helps

Thread 'V20 changing from Custom Domain to 3CX domain'

Jan 2, 2026

Way back in V15 when we moved to 3CX, I set up as a custom domain and all works well as no external access was required.

Due to some hybrid working now taking place, I need to provision either softphones or laptop to work with 3CX remotely and therefore need Certificates

Am i correct in thinking using a 3cx domain will allow for the use for Lets Encrypt to automatically keep certs up to date?

If so, can someone let me know what the recommended procedure is from changing from an custom domain to a 3cx domain on a self hosted (Debian) installation.

Cheers

• Mark Drabble
• Replies: 9
• Forum: Phone System / PBX

All devices will need to be reprovisioned.