Migrate from 3CX platform to OVH or Google

[jreddy]

Hope some one has done this and can help. I looked at all of the docs and the steps, but what they did not answer is what happens to the domain, SSL etc. We setup a system in google using custom FQDN and it was a painful process. Will likely use OVH as we already use them. We have a 8 SC Pro license that we will downgrade to the free 4SC license. So here are my questions:

1. What happens to the FQDN that 3CX gave us during the setup (using Pbexpress) last year - XXXXX.3cx.us. Can we still use it or do we now need to use our own.
2. Can we downgrade the license from 8SC pro to the free one 4SC.
3. The docs suggest using pbexpress to setup a new system in OVH and then restore the backup. This is a linux machine and I am not an expert in Linux but can do it if the steps are identified.

Any help is greatly appreciated. Hopefully we can use the same FQDN and not have to reprogram the phones, but since there are only a few, it should be okay if that changes.

John

 

[AWS2P]

the easiest way it"s to install a new free pbx instance on ovh, on old one do a backup without key an fqdn, during install restore your backup.

FQDN will got a new public IP from OVH so it will takes some hours to dns propagation

No need to be a linux expert, during this process linux is invisible for you.

If you have several phones install a SBC, or use STUN mode if no more than 2 or 3 phones.

 

[cobaltit]

So if 3CX originally gave you 3CX FQDN but then you later released it and setup your own custom FQDN then the original 3CX FQDN is no longer tied to you. It may or may not be available depending on if someone else claimed it.

If you want to move your instance and keep your FQDN then do as @aws2p recommended, except to your backup first and then install on OVH as you'll be given the option to restore during the inital installation. You can do a regular backup with key and FQDN, no need to do one without. You will want to shutdown the Google instance before restoring so the systems don't 'fight' over the FQDN.

 

[jreddy]

Actully, the system is still active with the 3cx FQDN. However my question was, will I be able to continue to use that fqdn or will I need to release it. This was set up using pbxpress on 3cx server.- .the default trial setup. the year is almost up and we need to move it to our own server.

 

[jreddy]

the easiest way it"s to install a new free pbx instance on ovh, on old one do a backup without key an fqdn, during install restore your backup.

FQDN will got a new public IP from OVH so it will takes some hours to dns propagation

No need to be a linux expert, during this process linux is invisible for you.

If you have several phones install a SBC, or use STUN mode if no more than 2 or 3 phones.

After a bit more research, I am more confused than ever with all of 3CX documentation about migrate, restore etc. The current system is still active. It was installed using pbxpress last year with default setup at 3cx. Since the year is ending, the server will be deleted by 3cx in a few days. So I need to move it to my own google or ovh server. looking at docs, looks like google will be easier. Would prefer to keep the same fqdn 3cx gave me - xxxx.3cx.us. So do i do a full backup with license, fqdn. Then setup new server with same fqdn and then do restore? How do I shut down current server since it is with 3CX.

 

[cobaltit]

Releasing the FQDN has to do with unbinding the FQDN from your key. It has nothing to do with your server or where it's hosted. If you did the 3CX free trial version where you created a Google account and then gave PBXExpress API access, you just need to enter a credit card with Google and it will keep going as-is. But if you no access to the account the current instance is under you'll need to pm @JohnS_3CX or @YiannisH_3CX to see about coordinating the shutdown of your instance so you can spin your own up. Or just make sure you have a current backup and you can spin up your own instance after the current one shuts down.

 

[jreddy]

Releasing the FQDN has to do with unbinding the FQDN from your key. It has nothing to do with your server or where it's hosted. If you did the 3CX free trial version where you created a Google account and then gave PBXExpress API access, you just need to enter a credit card with Google and it will keep going as-is. But if you no access to the account the current instance is under you'll need to pm @JohnS_3CX or @YiannisH_3CX to see about coordinating the shutdown of your instance so you can spin your own up. Or just make sure you have a current backup and you can spin up your own instance after the current one shuts down.

Yes the current one was last year using the 3cx servers - free 1 year trial. So I got email saying server will get shut down in a few days. But now here is what I did...Did a complete full backup. Then ran PBX express with restore backup. The backup was in my google account. So gave the url, put in the license key (same one) and then allowed 3cx access to the same google account and it ran thru fine. Got email about installation saying xxxx.3cx.us (current fqdn) is pointing to new google IP. But the installation email only mentioned the new IP and asked to login using that. I was able to login into the new installation. shows everything correct. but the wierd part is, when i log using fqdn, it shows old server. doing a dns check show a record to new ip. So my only guess is that dns has not propogated yet. so will wait till morning. the current server will get shut down by 3cx in a few days. so not sure if i need to do anything if fqds works and phones work. Thanks for your help.

 

[AWS2P]

While you have old pbx running fqdn is always known with old pbx IP, you need 3CX stops or delete old pbx, then new IP from Google instance propagate in few hours

 

[cobaltit]

What you can do is login to the MC of the old instance and stop the services. Then restart the new instance. That should refresh the DNS to point the FQDN to the new IP. There is a 6hr TTL but you should be good after that.

 

[JohnS_3CX]

Like @cobaltit said above, you can stop services and restart the services on the new instance to cause a DNS update. Should take a few minutes to change and then a while to propagate on the internet.

If you leave the old instance with the services stopped, eventually we will delete it as per the automatic schedule. Otherwise you can PM me to delete it for you.