Windows 3CX Pro (8SC) V18 update to Windows V20

[GeekSqueak]

I'm updating our Windows 3CX Pro installation to Windows 3cx V20. I have a V18 backup with the (8SC Pro)License Key, FQDN, Custom templates, and voicemails. Will the license automatically get upgraded to Ent when I install V20 using the V18 backup? Our current license expires in 3/2026. Can we move our license and FQDN over to Linux V20 Pro version on or before our license expiration?

 

[GeekSqueak]

I'm updating our Windows 3CX Pro installation to Windows 3cx V20. I have a V18 backup with the (8SC Pro)License Key, FQDN, Custom templates, and voicemails. Will the license automatically get upgraded to Ent when I install V20 using the V18 backup? Our current license expires in 3/2026. Can we move our license and FQDN over to Linux V20 Pro version on or before our license expiration?

I forgot to mention that all installations are self hosted.

 

[TheodorosG_3CX]

Since there i valid maintenance for the license key as you mentioned there should be no issue.
Once the license is activated on a V20 installation it will automatically be reverted to V20 license key.

 

[GeekSqueak]

Thank you for the quick response. Will the V20 license key automatically update to Enterprise? We may want to move to Linux on or before the end of our current license expiration. Is it possible to move to a Linux version and downgrade to the Pro version of 3CX, we would like to keep our same FQDN?

 

[bitn2]

Why not switch now to linux, you need to reinstall und backup/restore anyway...

 

[CentrexJ]

Thank you for the quick response. Will the V20 license key automatically update to Enterprise? We may want to move to Linux on or before the end of our current license expiration. Is it possible to move to a Linux version and downgrade to the Pro version of 3CX, we would like to keep our same FQDN?

The upgrade from Pro to Enterprise is something you have to pay for, its not automatic

3CX has said that they will eventually enforce the Enterprise edition on Windows requirement and without further notice as they have announced it several times.

If you are thinking about moving to Linux anyway, like Bitn2 said above, now is the time to do it. That way you don't re-install twice and you don't have the complication of upgrading to enterprise and then trying to downgrage back to pro later on.

 

[GeekSqueak]

@bitn2 We currently run Windows and have processes that will have to be updated to the Linux OS. @CentrexJ Another reason is that 3CX stated that they will not charge for the Enterprise version for the life of our current license because we are already on Windows V18. We have about a year left on our license. We can test out Enterprise and see if the extra features are something we can use. It would be nice to know how much of a hassle/possible it will be if we want to move to Linux at the end of our license.

Is it possible to go from Windows 3CX Enterprise to Linux 3CX Pro while retaining your FQDN?

I'm just going to assume that the Windows 3CX Pro license key will automatically upgrade to Enterprise when upgrading a V18 3CX Windows installation. Please comment if this is not the case. Thank you.

 

[CentrexJ]

@bitn2 We currently run Windows and have processes that will have to be updated to the Linux OS. @CentrexJ Another reason is that 3CX stated that they will not charge for the Enterprise version for the life of our current license because we are already on Windows V18. We have about a year left on our license. We can test out Enterprise and see if the extra features are something we can use. It would be nice to know how much of a hassle/possible it will be if we want to move to Linux at the end of our license.

Is it possible to go from Windows 3CX Enterprise to Linux 3CX Pro while retaining your FQDN?

I'm just going to assume that the Windows 3CX Pro license key will automatically upgrade to Enterprise when upgrading a V18 3CX Windows installation. Please comment if this is not the case. Thank you.

From my experience when you upgrade to v20 it will be Pro and you have to purchase the upgrade to Enterprise.

It is very easy to move from v20 Windows to v20 Linux and keep your FQDN.

My biggest concern for you would be if you want to downgrade from Enterprise to Pro with an 8SC License. 3CX is now actively discouraging license downgrades, especially below the 16SC tier.

Hopefully someone from 3CX can chime in on if downgrading from Enterprise to Pro on 8SC is permitted still. Also clarify that you do in fact have to purchase the upgrade to Enterprise after upgrading on Windows to v20 (its not an automatic free upgrade).

 

[GeekSqueak]

I hope we can get some clarification on these questions. I read, it might have been in this forum or a blog post, that the Enterprise upgrade is free, for the life of the current license, because we already have a license for Windows 3CX pro and they no longer allow the Pro version for Windows installations (V20). If we have to pay for it right away we will have to rethink what OS we move forward with.

 

[GeekSqueak]

@CentrexJ I believe I read it here, in regards to Pro to Ent Windows.

Post in thread 'V20: 3CX Re-engineered'

Mar 5, 2024

I had been looking forward to V20 but as its developed and now its here I am disappointing by the business decisions made.

Firstly, I have a perpetual licence that I am informed will no longer be honored or work in V20, even though I pay for updates and support. This is a kick in the teeth to a long standing customer.

Secondly, I run a pro licence which now wont work on my windows window server O/S anymore.

If i have to re-licence and/or run on a different O/S I will be considering an alternative to 3CX.

Hi OAH,

All users with perpetual license that is current are just switched...

• CentrexJ

• 

LOL

 

[CentrexJ]

@CentrexJ I believe I read it here, in regards to Pro to Ent Windows.

Post in thread 'V20: 3CX Re-engineered'

Mar 5, 2024

I had been looking forward to V20 but as its developed and now its here I am disappointing by the business decisions made.

Firstly, I have a perpetual licence that I am informed will no longer be honored or work in V20, even though I pay for updates and support. This is a kick in the teeth to a long standing customer.

Secondly, I run a pro licence which now wont work on my windows window server O/S anymore.

If i have to re-licence and/or run on a different O/S I will be considering an alternative to 3CX.

Hi OAH,

All users with perpetual license that is current are just switched...

• CentrexJ

• 

LOL

That is what 3CX wrote and I was parroting it. but I believe in practice it wasn't implemented and you have to purcahse it.

 

[GeekSqueak]

Please clarify @TheodorosG_3CX
Do existing licensed Windows 3CX PRO V18 customers have to pay the difference for staying on Windows and upgrading to V20 Ent, for the remaining life of the license?
Is it possible to go from Windows 3CX Enterprise to Linux 3CX Pro while retaining your FQDN?

 

[GeekSqueak]

I found a post that referenced what I believe I saw originally. I believe this now has been removed from the 3CX website.

Post in thread 'V20 Upgrade question'

Jul 17, 2024

3CX will upgrade your license to ENT for the remainder of your term and you will then need to renew at ENT cost.

If you renew now, your renewal date will be today.

https://www.3cx.com/blog/releases/v20-final/

Currently V20 is available on Linux only: A Windows installer will come at a later stage and will require an enterprise edition. We’ll upgrade any PRO editions running Windows to Enterprise for the duration of the subscription. More information to follow.

This came from the main man.

• Alphabetic

 

[TheodorosG_3CX]

Please clarify @TheodorosG_3CX
Do existing licensed Windows 3CX PRO V18 customers have to pay the difference for staying on Windows and upgrading to V20 Ent, for the remaining life of the license?
Is it possible to go from Windows 3CX Enterprise to Linux 3CX Pro while retaining your FQDN?

At the moment there is no restriction between OS and licensing.
To be clear, there is no different 3CX license for Windows and for Linux. For the 3CX Licensing clarification you can check also here. If there will be any change in the future it will also be announced in our blog post here.

 

[GeekSqueak]

At the moment there is no restriction between OS and licensing.
To be clear, there is no different 3CX license for Windows and for Linux. For the 3CX Licensing clarification you can check also here. If there will be any change in the future it will also be announced in our blog post here.

Thank you for the clarification. @TheodorosG_3CX. This is what I understand to be true from your clarification.. There will be no extra charge when I upgrade our Windows V18 3CX Pro instance to Windows v20 3CX Enterprise for the life of our current license. At the end of the license we will then be charged the Enterprise price if we stay on windows and we renew our license. If we want Professional, at the end of our current license, we will need to move to Linux and then downgrade our license. Please correct me if I'm wrong.

 

[TheodorosG_3CX]

Just to clarify here, at the moment you have a commercial PRO license. Moving to another OS will not upgrade your license edition to ENT. The installation will remain as it is in V20.
That being said reinstalling the 3CX PBX to another OS does not affect the license edition.
I would also suggest to contact out Customer Care Team to get further clarification on licensing using the contact form here.

 

[GeekSqueak]

Thank you @TheodorosG_3CX and all that have contributed. When I upgrade this weekend, I will be upgrading to Windows 3CX V20 and it will continue to be on the Pro license. I believe I was taking the below statement as if it were written in stone.


"Currently V20 is available on Linux only: A Windows installer will come at a later stage and will require an enterprise edition. We’ll upgrade any PRO editions running Windows to Enterprise for the duration of the subscription. More information to follow."

POST SUMMATION:

The Enterprise version will be required, at some point in the not to distant future, for Windows installations, Linux installations do not have this requirement.