FWIW I'm going to answer my own earlier question, if (as I did) you have V16 running on a rather old system that probably isn't up to the job and want to update the hardware as well as 3CX then it really is as easy as running a full backup of the old system, transferring the ZIP file to the new host (Windows this time) and installing 3CX "restoring" the backup. I would recommend you have the backup copied to the host or on a removable drive as the browser-based install prefers to restore from a local drive.
You might have to shut down the old box before the new one "restores" the backup, not sure but they might conflict for the license and FQDN. I shut down my old V16 box at that point.
Then you can give the new box its IP, a bit of fiddling in admin (update IP, test firewall and a new backup schedule) and it is done.
Incidentally IMO MS Remote Desktop is easier to use if you reduce the "virtual" screen resolution, which you need to do BEFORE signing in (show options and stuff).
Oh and incidentally the server doesn't appear to restart after a reboot, the NGINX and management console processes didn't come up last time. This is a 3CX on Linux thread though so my new problems belong elsewhere.
