v18 with 2 digit users. Upgrade to v20 with 3 digit. Self hosted to hosted

[tripleu]

Hi, hope someone can confirm.
I had a v18 Pro whic was setup with 2 digit extns.
The licence came for renewal so we purchased and applied - all ok.

However we wished to move to 3 digit extns and there is no way to migrate so I did te following...

Created hosted instance ov v20 with 3 digit on the 60 days trial.
recreated all the extns/users and moved trunks over.
Move all the phones and 3cx users over.

All working fine.

I now need to close the old v18 instance and have the licence on the v20.

Is it just a case of shutting down the old v18 and replacing the licence on the v20 with our recently renewed one?
Of course the new v20 is a different FQDN.

Or have I messed up the process?

Thanks.

 

[tripleu]

I just tried the following:
Download a blank setupcnfig_v20.xml file
edited the line for the licence and put our key in. No other changes!
Tried the VPS instance with this file. Responce was the FQDN is already in use.
Current state of our old V18 is: VPS is running again. Portal shows no FQDN attached to the licence key.

@tripleu, 3CX works best with supported providers. Aligned with our support procedures, using an unsupported SIP trunk provider limits the assistance from the 3CX support team.

understood. It’s a shame that for supported trunks my costs for this client are 4 times the cost per trunk and also do not include international.
In v18 it’s been working fine for 8!years. Now we are on v20 there are some minor differences in how it’s working but to resolve is either me tryin to understand sip trunks in more detail or explaining to the customer that the cost is now increasing 4x on the trunks.
I have spoken with my current provider and suggested that they may like to become 3cx qualified and this a chance of increasing their revinue stream.
For now I’ll have a blend of the 2 whist we port over to a supported provider.

 

[IrinaP_3CX]

Portal shows no FQDN attached to the licence key.

When you have deleted your license from the portal, you have to delete all associated details, including FQDN.

If you are trying to rebound the previous 3-digit FQDN, it is not possible.
Try to re-install the system with 4-digit FQDN.