- Joined
- Sep 10, 2020
- Messages
- 3
- Reaction score
- 0
Hi there,
I am migrating a customers 3CX instance. They currently have a completely unrelated custom FQDN (oldsupport.hostingprovider.tld). I am migrating them to a new server running in Azure. I will be changing them to a 3CX domain using PBXExpress (company.3cx.co.uk).
The only thing that I really need to bring over from the old server is the key (no recordings, call logs aren't required etc). I was going to build the new server using a trial key with the desired FQDN. The SIP Trunk is also being migrated to a new provider so I can set everything up, fully test it.
Once I am happy all is working and the number has been ported from the old Provider, can I just unlink the license key from the old unrelated FQDN and then do a replace license on the new server? Or do I need to build everything with a development FQDN and trial license, take a backup (minus License/FQDN), destroy development server and provision the new server doing a restore?
Thanks
Mark
I am migrating a customers 3CX instance. They currently have a completely unrelated custom FQDN (oldsupport.hostingprovider.tld). I am migrating them to a new server running in Azure. I will be changing them to a 3CX domain using PBXExpress (company.3cx.co.uk).
The only thing that I really need to bring over from the old server is the key (no recordings, call logs aren't required etc). I was going to build the new server using a trial key with the desired FQDN. The SIP Trunk is also being migrated to a new provider so I can set everything up, fully test it.
Once I am happy all is working and the number has been ported from the old Provider, can I just unlink the license key from the old unrelated FQDN and then do a replace license on the new server? Or do I need to build everything with a development FQDN and trial license, take a backup (minus License/FQDN), destroy development server and provision the new server doing a restore?
Thanks
Mark