On-Prem to 3CX Hosted Migration Question

[Frank86]

I plan to migrate 3CX Enterprise from on-prem to 3CX hosted.

I'm reviewing the steps in the migration guide, which mentions this, "The IP phones need to be re-configured to use the 3CX SBC."

Does that mean that, for each user, I will need to go into the Phone Provisioning tab and change the Provisioning Method from Local LAN to SBC? Is that all that is required on the phone side of things? No factory reset and reconfiguration needed?

Also, any gotchas I need to watch out for during the migration from on-prem to cloud?

Is the migration from on-prem to 3CX hosted painless and recommended for a company with about 60 to 70 users?

Thank you.

 

[SweetAction]

I plan to migrate 3CX Enterprise from on-prem to 3CX hosted.

I'm reviewing the steps in the migration guide, which mentions this, "The IP phones need to be re-configured to use the 3CX SBC."

Does that mean that, for each user, I will need to go into the Phone Provisioning tab and change the Provisioning Method from Local LAN to SBC? Is that all that is required on the phone side of things? No factory reset and reconfiguration needed?

I would setup the SBC first and get it talking to the on prem PBX. Then, make the changes to phone to use the SBC. Then, phones tab, select all, reprovision button. Wait a few minutes, reload the page, make sure all phones came back up and all of them say via SBC. Any that won't come up correctly - factory and reprovision. And then migrate the PBX to hosted.

Also, any gotchas I need to watch out for during the migration from on-prem to cloud?

Is the migration from on-prem to 3CX hosted painless and recommended for a company with about 60 to 70 users?

That's a very loaded question. But as long as the limits of Hosted are OK with you AND all your items are supported in Hosted, none that I know of.

 

[AWS2P]

May I ask what is the main point for you changing from on premise to 3CX hosted ?

 

[Frank86]

I would setup the SBC first and get it talking to the on prem PBX. Then, make the changes to phone to use the SBC. Then, phones tab, select all, reprovision button. Wait a few minutes, reload the page, make sure all phones came back up and all of them say via SBC. Any that won't come up correctly - factory and reprovision. And then migrate the PBX to hosted.


That's a very loaded question. But as long as the limits of Hosted are OK with you AND all your items are supported in Hosted, none that I know of.

Thank you. That is very helpful. If a user has a lone STUN Yealink T57W phone set up at home, can the T57W be configured as a router SBC phone, thus bypassing a Linux/Windows SBC?

 

[Frank86]

May I ask what is the main point for you changing from on premise to 3CX hosted ?

The client wants to be server-less. Should they keep 3CX on-prem, is there an appliance that is generally recommended for the job?

 

[SweetAction]

Thank you. That is very helpful. If a user has a lone STUN Yealink T57W phone set up at home, can the T57W be configured as a router SBC phone, thus bypassing a Linux/Windows SBC?

Yes

The client wants to be server-less. Should they keep 3CX on-prem, is there an appliance that is generally recommended for the job?

I'm a fan of Lenovo uSFF machines with Intel vPro, but there are many x86 boxes like Protecti and others that do the job as well.

 

[AWS2P]

Do you mean you are actually running a real dedicated Windows server machine to run the pbx software ?

 

[SweetAction]

Do you mean you are actually running a real dedicated Windows server machine to run the pbx software ?

No, this is a desktop machine. I use linux on the machine.

 

[AWS2P]

No, this is a desktop machine. I use linux on the machine.

Sorry question was for @Frank86

 

[Frank86]

Sorry question was for @Frank86

Right now, 3CX runs on a VM on a server that is a year or so from retirement. The client does not plan to replace it since they have moved almost all their systems to the cloud.

 

[Frank86]

I would setup the SBC first and get it talking to the on prem PBX. Then, make the changes to phone to use the SBC. Then, phones tab, select all, reprovision button.

Does the SBC setup and connection to 3CX on the the same LAN need to be done off-hours? Is it going to cause any conflict for end users if done during business hours?

 

[SweetAction]

Does the SBC setup and connection to 3CX on the the same LAN need to be done off-hours? Is it going to cause any conflict for end users if done during business hours?

Always better to do it after hours, but it should only cause a few minutes outage for a phone to reboot once you hit the reprovision button.

 

[Frank86]

Gotcha. Thank you.

 

[JohnS_3CX]

@Frank86 During your migration, make sure the SBC is up and running.

- Then, delete the phone from the user and press OK to save.

- Factory reset the phone and wait for it to come back up.

- You can then assign it via the management console.

- Repeat for each phone.

Do not make the mistake of skipping the factory reset - often there will be leftover settings that will cause issues down the line, so best to it right from the first time around.

 

[Frank86]

During your migration, make sure the SBC is up and running.

Thank you for the advice. What are the proper steps?
1. Install the SBC and connect it to the 3CX server while the latter is still on-prem?
2. Or migrate the 3CX server to the 3CX hosted cloud, then configure the on-prem SBC to connect to the hosted 3CX instance?

 

[SweetAction]

Thank you for the advice. What are the proper steps?
1. Install the SBC and connect it to the 3CX server while the latter is still on-prem?
2. Or migrate the 3CX server to the 3CX hosted cloud, then configure the on-prem SBC to connect to the hosted 3CX instance?

It's all about how much downtime you can allow.
Connecting it after migration is the way I would go if downtime didn't matter.

 

[JohnS_3CX]

I imagine you will be doing this during quiet hours, so turn off your existing server, finish the installation and backup restore on new one, then bring up the SBC.

Once everything is up and running, you can start migrating phones one by one.

And in case anything goes wrong and you have to abort, just shut down the new server and start up the old one until you get the next opportunity to migrate again.