We want to upgrade a 3cx V18 on a windows server to V20 on a linux server. Now we use an own fqdn but want to change this to a 3cx fqdn. What's the procedure to perform this upgrade?
We also want to change the clients from version V16/V18 to the microsoft app.
I have done this a few times. Here is a summary of the process I used when upgrading from v18 to v20U5; I don't know if any subsequent 3CX changes would impact the process now:
Prerequisites:
Make sure you have designated a System Owner account in V18. Log in using that account to verify it has the correct access.
You will need access to the 3CX portal using the License Owner's account.
V18 shutdown
Initiate a backup with all data options checked EXCEPT License/FQDN. Make sure the backup is configured in 3CX to store in a remote location (not local).
Uninstall 3CX from Windows (or shut down the host if it is being decommissioned and will not be used again).
V20 prep
Log in to the 3CX portal under the License Owner's account. Locate the system and release the FQDN.
Select the Install option for the system, then select the appropriate options, including the new 3CX FQDN.
Download the config file, make any changes (if you need to change from the default port assignments).
V20 Install
Complete the 3CX Linux installer. When prompted for setup, use the config file downloaded from the portal. DO NOT load from backup.
Complete the remaining setup options for a new system, which will assign a new system owner extension.
Once setup is complete, log in with the new system owner extension.
Go to Admin, System, Storage and configure Remote Data Storage for the remote location where the backup is located. On the bottom of the screen, assign the correct parameters under Backup Archive for the folder path (use / if backing up to the root folder)
Go to the Backup tab, which should list the backup files. Select the V18 backup made without the license/FQDN and select Restore.
After the restoration and restart, log in using the System Owner account previously configured in V18. The system should now be running with all the V18 data and the new FQDN.
You will need to reprovision any clients/devices using the old FQDN, although if the DNS for the old FQDN points to the same IP address as the new system, some devices may be able to connect and reprovision themselves.
