Teams/S4B Online/S4B on-premise : What will be the migration path ?

%3CLINGO-SUB%20id%3D%22lingo-sub-112029%22%20slang%3D%22en-US%22%3ETeams%2FS4B%20Online%2FS4B%20on-premise%20%3A%20What%20will%20be%20the%20migration%20path%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112029%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20started%20our%20migration%20from%20Skype%20on-premise%20to%20Skype%20online%20using%20an%20Hybrid%20Voice%20scenario%20(at%20the%20beginning).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20with%20the%20Teams%20roadmap%2C%20we%20are%20in%20some%20doubt%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20best%20migration%20path%20frome%20Skype%20on-premise%20to%20Teams%20Online%20%3F%3C%2FP%3E%3CP%3EWill%20we%20continu%20our%20migration%20to%20Skype%20Online%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20question%20about%20client%20usage%20enforcement%20%3B%3C%2FP%3E%3CP%3ESide%20by%20side%20%E2%80%93%20use%20both%20Skype%20for%20Business%20and%20Microsoft%20Teams%3CBR%20%2F%3ESide%20by%20side%20with%20notify%20%E2%80%93%20use%20both%3B%20notify%20Skype%20for%20Business%20users%20to%20try%20Microsoft%20Teams%3CBR%20%2F%3ETeams%20only%20%E2%80%93%20enforce%20Microsoft%20Teams%20only%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20a%20Teams%20will%20be%20able%20to%20communicate%20(chat%20etc)%20with%20a%20Skype%20User%20(online%20or%20onpremise)%3F%20It%20will%20be%20possible%20or%20not%20%3F%3C%2FP%3E%3CP%3EBecause%20in%20migration%20point%20of%20view%2C%20we%20don't%20want%20to%20%22break%22%20to%20communication%20between%20peoples%20because%20they%20don't%20use%20the%20same%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-112029%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112559%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%2FS4B%20Online%2FS4B%20on-premise%20%3A%20What%20will%20be%20the%20migration%20path%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112559%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20more%20details%20will%20be%20forthcoming%20on%20these%20different%20scenarios%2C%20migrations%2C%20recommendations%20etc.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight%20now%2C%20Microsoft%20is%26nbsp%3Bencouraging%20all%20Office%20365%20customers%20to%20start%20using%20Teams%2C%20independently%20or%20in%20parallel%20with%20Skype%20for%20Business.%26nbsp%3B%20Microsoft%20also%20says%20for%20those%20customers%26nbsp%3Bin%20the%20process%20or%20are%20planning%20to%20deploy%26nbsp%3BSkype%20for%20Business%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CEM%3ECustomers%20should%20evaluate%20the%20Teams%20roadmap%20to%20determine%20if%20capabilities%20will%20meet%20business%20needs%20and%20timing%20requirements.%20If%20so%2C%20they%20should%20adjust%20strategy%20to%20deploy%20Teams.%20Planning%20and%20infrastructure%20investments%20such%20as%20network%20assessments%20will%20accrue%20to%20Teams%20deployment.%20If%20not%2C%20customers%20should%20move%20forward%20with%20Skype%20for%20Business.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20the%20specific%20guidance%26nbsp%3Bthat's%20available%26nbsp%3Bright%20now%20including%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FMicrosoftTeams%2Ffaq-journey%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EFAQ%3C%2FA%3E%2C%20in%20case%20you%20haven't%20seen%20it%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FMicrosoftTeams%2Fprepare-teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EOptimize%20your%20current%20Skype%20for%20Business%20environment%20for%20Microsoft%20Teams%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FMicrosoftTeams%2Fpilot-essentials%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EPilot%20Microsoft%20Teams%20alongside%20Skype%20for%20Business%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FMicrosoftTeams%2Fguidance-skypeforbusiness%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EEnable%20Microsoft%20Teams%20side-by-side%20with%20Skype%20for%20Business%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FMicrosoftTeams%2Fcontinue-journey%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EDrive%20value%20with%20Microsoft%20Teams%20through%20user%20adoption%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EStuff%20like%20hybrid%20I%20haven't%20seen%20mentioned%20yet.%26nbsp%3B%20Microsoft%20Teams%26nbsp%3Bwon't%20have%20all%20the%20Skype%20for%20Business%26nbsp%3Baudio%20and%20PBX%20features%20until%20the%20second%20half%20of%20next%20year%20anyway%20I%20understand%20and%26nbsp%3Bthese%20timescales%20may%20change.%20Depending%20on%20what%20stage%20you%20are%20with%20the%20migration%20and%26nbsp%3Bstuff%20like%20priorities%2C%20user%20impact%2C%20costs%2C%20it%20might%20be%20worth%20continuing%20the%20migration%20and%20then%20at%20a%20later%20date%2C%20move%20to%20Teams%2C%20when%20everything%20is%20in%20place.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20makes%20sense%20and%20is%20of%20some%20help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112548%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%2FS4B%20Online%2FS4B%20on-premise%20%3A%20What%20will%20be%20the%20migration%20path%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112548%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Stephane.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20too%20early%20to%20answer%20your%20questions%20precisely%2C%20as%20the%20Teams%20UC%20roadmap%20is%20not%20in%20place%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20advise%20is%20to%20evaluate%20if%20the%20Cloud%20Voice%20offers%20meets%20your%20organizations%20needs%20and%20move%20to%20Skype%20for%20Business%20Online%20if%20this%20should%20work%20for%20you.%20Then%20at%20a%20later%20stage%20evaluate%20Teams%20as%20your%20UC%20client%2C%20so%20go%20side-by-side.%20Replacing%20the%20client%20is%20a%20fairly%20large%20change%20for%20most%20of%20the%20users%2C%20so%20you%20need%20to%20do%20a%20good%20adoption%20plan.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2FKenneth%20ML%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

Hi,

 

We started our migration from Skype on-premise to Skype online using an Hybrid Voice scenario (at the beginning).

 

Now, with the Teams roadmap, we are in some doubt :)

 

What is the best migration path frome Skype on-premise to Teams Online ?

Will we continu our migration to Skype Online ?

 

Another question about client usage enforcement ;

Side by side – use both Skype for Business and Microsoft Teams
Side by side with notify – use both; notify Skype for Business users to try Microsoft Teams
Teams only – enforce Microsoft Teams only

 

How a Teams will be able to communicate (chat etc) with a Skype User (online or onpremise)? It will be possible or not ?

Because in migration point of view, we don't want to "break" to communication between peoples because they don't use the same client.

 

Thanks in advance.

2 Replies

Hi Stephane.

 

It's too early to answer your questions precisely, as the Teams UC roadmap is not in place yet.

 

My advise is to evaluate if the Cloud Voice offers meets your organizations needs and move to Skype for Business Online if this should work for you. Then at a later stage evaluate Teams as your UC client, so go side-by-side. Replacing the client is a fairly large change for most of the users, so you need to do a good adoption plan.

 

/Kenneth ML

I think more details will be forthcoming on these different scenarios, migrations, recommendations etc. 

 

Right now, Microsoft is encouraging all Office 365 customers to start using Teams, independently or in parallel with Skype for Business.  Microsoft also says for those customers in the process or are planning to deploy Skype for Business:

 

"Customers should evaluate the Teams roadmap to determine if capabilities will meet business needs and timing requirements. If so, they should adjust strategy to deploy Teams. Planning and infrastructure investments such as network assessments will accrue to Teams deployment. If not, customers should move forward with Skype for Business."

 

Here is the specific guidance that's available right now including a FAQ, in case you haven't seen it:

 

Stuff like hybrid I haven't seen mentioned yet.  Microsoft Teams won't have all the Skype for Business audio and PBX features until the second half of next year anyway I understand and these timescales may change. Depending on what stage you are with the migration and stuff like priorities, user impact, costs, it might be worth continuing the migration and then at a later date, move to Teams, when everything is in place. 

 

Hope that makes sense and is of some help.