Migrate from 3CX OnPremise to Cloud

[David_K]

Hello

Is there a clear process to follow to migrate from an on premise server to an hosted 3CX instance ?

I had the idea to install the cloud instance then restore the backup, but my concern is what about the phones? They are all configured to point to the local LAN IP of the on premise server.
In my idea, the actual 3CX server will become the SBC.

Also most of the phones (around 60 of them) are Yealink with v66.83 firmware, that one that is not able to provision automatically to 3CX v16, so I'll have to upgrade them manually to v66.84 one
by one?
Today it's working with v66.83 because they were provisionned before that bug occured so no need to re-provision them

Thanks for your ideas.

 

[AWS2P]

I had the idea to install the cloud instance then restore the backup

If you do cloud install with pbxepress then it ask you for restoration during install and not after.

How many phones do you have to connect behind SBC ?
Do you want to do an SBC on windows or linux plateform ?

 

[cobaltit]

Migrating to 3CX hosted is no different then migrating to a new local host on a different IP, or to a cloud instance. Backup, uninstall or otherwise shutdown the old instance, spin up new instance (or 3CX hosted) and restore. So in that sense it's clear as it's the same as it's always been since 3CX is just another hosting option.

As far as the firmware goes if you have to upgrade them manually because you haven't kept up to date, you would have to do so regardless of where your new instance sits.

 

[David_K]

How many phones do you have to connect behind SBC ?
Do you want to do an SBC on windows or linux plateform ?

Today the 3CX is on Windows so I'll probably make it an SBC on Windows

 

[cobaltit]

In theory, if you moved your instance to the cloud and then uninstalled 3CX from the box you have it on now and then installed the SBC, everything should just work, although it won't be supported. This would give you the time to manually upgrade phones at your leisure and then factory reset them to get them provisioned properly. This is of course assuming the current box meets the requirements to run the SBC. If the current box is running an older OS and that's why you are looking to upgrade, then the current SBC won't install on it.

 

[David_K]

As far as the firmware goes if you have to upgrade them manually because you haven't kept up to date, you would have to do so regardless of where your new instance sits.

I don't have to upgrade them manuall because we haven't kept up
But the phones were to the latest firmware (66.83 at that time) then we've upgraded 3CX from v15 to v16
And then when new Yealink firlmware was released, v16 was not able to push the update anymore. It's a known bug. We have to upgrade the phones manually to 66.84, then wait, and upgrade to 66.85 (we can't upgrade to 66.85 directly we have to go through 66.84)
So phones stuck to 66.83 since months and we did not have time to upgrade manually the 60 phones (will take a full day or more)

 

[cobaltit]

Well regardless of the reason, you have to upgrade them manually so 3CX hosting is not a factor in that. It seems like you would be best suited by manually upgrading the phones prior to moving 3CX. You don't have to do them all at once.

 

[StefanW]

if you press in the customer portal to "switch to hosted", a popup will guide you and links to a more comprehensive to-do guide what needs to be done prior migration from on-premise to the cloud.
No worry, clicking on this button does not alter anything to your installation!