Solved Migrating from GCP to private cloud

[YWiegman]

Hi guys,

For one of our customers I'm planning a migration to a private cloud via our VoIP partner. I'm making this thread to make sure I dont overlook certain area's that could impact the customer in the long run. Below is the current setup:

Current situation:
Licensekey: standard with custom FQDN
Provisioning: SBC installed on a Windows device with static IP
Server: on a static IP in GCP running 3CX V18

New situation:
3CX hosted in private cloud with 3CX certified Partner/SIP trunk
Would love to use same licensekey + same FQDN

If we are to migrate this server to another instance in private cloud, would it be any more than just running the backup and loading it back up?

Hope to hear some tips and tricks if possible.

 

[ChrisC_3CX]

To clarify a few things:

For one of our customers I'm planning a migration to a private cloud via our VoIP partner.

Will you have the ability to deploy the instance using the 3CX ISO? This is absolutely essential if deploying a Linux machine so make sure you use the latest ISO file which you can download from the 3CX Portal.

Licensekey: standard with custom FQDN

Custom FQDNs can only be used with a PRO or ENT License Key, are you sure this is the case?

If we are to migrate this server to another instance in private cloud, would it be any more than just running the backup and loading it back up?

Might very well be the case since you're already in the cloud meaning you have no local devices using the local IP of the PBX. If you are using any SIP Providers that need to know your PBXs Public IP to allow and route traffic accordingly then you might also need to inform them of the change.

 

[YWiegman]

Hi ChrisC,

Thanks for your reply.

Will you have the ability to deploy the instance using the 3CX ISO? This is absolutely essential if deploying a Linux machine so make sure you use the latest ISO file which you can download from the 3CX Portal.

In this instance our partner would deploy the 3CX environment in the private cloud, after which I would receive the credentials and then I would be able to log in and set it up. I will check with them if they are using the ISO you are recommending (but I would think so).

Custom FQDNs can only be used with a PRO or ENT License Key, are you sure this is the case?

You are right, I was confussed with another customer. This is a XXXX.my3cx.nl-FQDN, so that is not fully custom.
Would that change anything for us?

Might very well be the case since you're already in the cloud meaning you have no local devices using the local IP of the PBX. If you are using any SIP Providers that need to know your PBXs Public IP to allow and route traffic accordingly then you might also need to inform them of the change.

I'm planning to work on this migration outside of office hours, so I will inform the client, but it propably wouldn't affect them. I'm also swiching providers to the same partner, which are using 3CX supported SIP Trunks.

Thanks again for your reply!

 

[ChrisC_3CX]

You are right, I was confussed with another customer. This is a XXXX.my3cx.nl-FQDN, so that is not fully custom.
Would that change anything for us?

Yes but in a good way. It simplifies things a bit because if you're using a 3CX FQDN, which you are, it means that we manage the SSL certificates and the DNS records. Both will be automatically taken care of during the new PBX's installation.

I'm also swiching providers to the same partner, which are using 3CX supported SIP Trunks.

Excellent, though do bear in mind that some 3CX Supported SIP Providers still need to know your PBX's public IP so I do recommend checking just in case.

Another thing you should consider is the current PBXs backup size and if it's very large due to recording files, etc. If this is the case, you might actually want to consider taking a backup without the recordings files and then just move the recording files manually to the new server. The new PBX should be able to detect them since it already has them indexed in its database.

 

[YWiegman]

Alright, thank you for clarifying.
I will go ahead with the migration!

 

[ChrisC_3CX]

Brilliant! Do let us know if you need anything else on this!