Moving License from old production to new production

[Phil Sbrana-Browning]

I am just trying to get clear, the steps to move my old 3CX license (renewed 2 months ago) from old in house 3cx server onto new hosted private cloud server.
Old server now switched off and all users now running on private cloud. This has a POC license that will run out next month, so would like to move it over my paid for license.
now if I go into portal.3cx.com login and go to the license with 10 months left (old production) and disconnect from FQDN.
Can I then go into the new server and under license replace the key, removing the old POC license, will this then pick up the FQDN on the new server?
Or do I need to go through a more complex procedure previously mentioned in these forums.

1. take full backup without license or FQDN (make sure to download locally)
2. Clean (debian) sudo /usr/sbin/3CXWizard --clean
3. restore the backup via the web interface
4. enter new license key
5. choose new FQDN

I am guessing I would need then to disconnect the FQDN from the POC license if I went down this route otherwise I would probably get an error saying this FQDN is already in use?

Obviously would prefer to just replace the key after disconnect from old server. But any feedback on how best to do this would be appreciated.

 

[Evolute IT]

You can indeed release FQDN of the old license, then go to Settings > License on your new one, and click "Replace License Key". It will bind the FQDN and instance to that old license and release the PoC one.

 

[Phil Sbrana-Browning]

Thanks for your prompt reply. That will be much easier. That's a relief.

 

[GeorgeK_3CX]

Hello @Phil Sbrana-Browning.

Are you not able to replace the current POC key with the paid key?

In the case that you must re-install, the supported procedure is to use the 3CX ISO to do the install (clean install). I will include the steps to follow below:

1. Take a full backup without the option "License Key Information, FQDN & Conference" selected
2. Log into portal.3cx.com with owner account of POC License and Disconnect the FQDN from that license
3. Install 3CX System using the latest 3CX ISO, new License and FQDN previously released, restoring backup during installation process

 

[Phil Sbrana-Browning]

Hi George, I have NOT yet tried to replace the key.

Although we are now running on the new server, I have until 11/11/22 to do this so until the system is fully bedded and tested have left the option to fall back to local server again. In case a real problem arises. .

However before end of month, I will try the easy method Disconnect the license from old system FQDN, and replace license.

if that fails, it will be a much bigger issue. I posted here just to make sure that I was thinking correctly, regarding the process. Aways better to check before over-complicating.