From cloud PBX to on premise PBX

[Helpdesk Avelco]

Hello,

I'm going to migrate a Cloud PBX to an on premise PBX and have a question about the license key. Is it possible to replicate the PBX with the same license key? I want to have the PBX live and tested before their license expires at 9th of September.

Kind regards,

 

[Jeff Prodzinski]

I am not experienced with 3CX but I will chime in here about the issue I am currently experiencing so you dont fall into the same.
If the cloud hosting is through 3CX and not in your own tenant ensure you work with either 3CX or a partner that has direct access to shutdown/disable/remove the cloud PBX post migration.

I have a local install thats currently having issues because I have no way of accessing the 3CX hosted cloud tenant to shutdown the old PBX. The 2 installs (cloud and on-prem) constantly compete for the DNS record which causes problems. The fix is to disable/remove the cloud pbx but I dont have direct access to do that so I am trying to work with 3CX.

Hope this helps.

 

[Dominik Oelmaier]

Hello,

I'm going to migrate a Cloud PBX to an on premise PBX and have a question about the license key. Is it possible to replicate the PBX with the same license key? I want to have the PBX live and tested before their license expires at 9th of September.

Kind regards,

Hello,

I have done this a week before.

First you have to create a full-backup of your system.
Then you log in into your customer portal.

There you can seperate your License key from your FQDN.


After that, install your on premise system and bind your License Key to your new PBX.

That´s all, and you´re ready to configure your new system!


It would be great, if you give me an update either it worked or not.


best regards,

Dominik Oelmaier

 

[YiannisH_3CX]

Hello @Helpdesk Avelco

Please note that you should not have 2 live machines running the same licence key. The first issue is with the licence activation. As the licence will be active on 2 machines the activation server might block your key and then neither PBX will work.
The other issue is with the DNS entry for the FQDN. As both servers will run the same key the DNS will keep changing between the 2 so that will give you issues. I would recommend not having both servers active at the same time.

If you want to move the server then create a backup without licence and FQDN from the original server. Shut down the cloud instance and install the on premise PBX using the created backup and the same licence key. No need to release the key from the costumer portal as suggested above if you are going to use the same FQDN.