Understand coexistence and upgrade journey for Skype for Business and Teams
As an existing Skype for Business customer, your complete transition to Teams might take some time. However, you can begin realizing the value of Teams today, by enabling your users to use Teams alongside Skype for Business. Given that there is some overlapping functionality between the two apps, we recommend that you review the available upgrade modes to help determine which path is right for your organization. For example, you might opt to enable all workloads on both solutions without interoperability. Or, you might decide to manage the user experience, either by gradually introducing Teams capabilities or by targeting groups of users for select capabilities, until your organization is ready to upgrade everyone to Teams.
This article outlines the various modes that enable you to manage which modalities in Skype for Business and Teams are available to your users. As with any deployment, we strongly encourage you to pilot your intended plan with a selected group of users before upgrading your organization to Teams. Remember, introducing new technology can be disruptive for users. Take time to assess user readiness and implement a communication and training plan prior to implementing any of the modes outlined herein.
Upgrade and coexistence modes defined
To help guide your decision-making process, familiarize yourself with the various modes, concepts, and terminology relevant to upgrading from Skype for Business to Teams.
Skype for Business with Teams collaboration–only mode
In this mode, Teams is configured to support teams and channels-based conversations only, with private chats, calling, and meetings disabled.
This mode is a great way to introduce Teams in your environment while you continue leverage your existing investment in Skype for Business.
Skype for Business with Teams collaboration and meetings mode
Along with using Teams for teams and channels-based conversations in this mode, users start using Teams to schedule and conduct their meetings. Private chats, and voice and video calling, remain on Skype for Business.
If your organization needs the capabilities that Teams provides for meetings, but business needs require you to keep enterprise voice capabilities in Skype for Business, you can configure Teams to deliver Skype for Business with Teams collaboration and meetings capabilities to your entire organization (or some parts of it).
This is the default mode. You use it to deploy Teams independently of Skype for Business.
In this mode, Teams users can immediately use Teams with all its capabilities with other Teams users, while other users can continue using Skype for Business and remain productive with no impact on how they’re using Skype for Business today.
Islands mode comes with one-way temporary interoperability that allows chat interoperability from Teams to Skype for Business when the following conditions are met:
- The Teams user is homed at, and enabled for, Skype for Business Online.
- The Skype for Business user has never used Teams (or isn’t licensed for Teams).
This mode is helpful when you want users who are primarily using Teams to connect with other users in the organization who are still using Skype for Business only.
After the users who previously used only Skype for Business start to use Teams, all their chats from other Teams users will arrive in Teams. This switches these users to islands mode. From that point, they must keep running Teams to ensure they stay connected with the other Teams users in the organization.
In this upgraded mode, the Skype for Business client no longer provides basic IM, presence indicators, chat, calling, or meeting capabilities. Users working in upgraded mode must use Teams as their primary communications and collaboration tool.
Users who are ready to use Teams as their primary communications and collaboration tool can be upgraded as Teams-only users.
An upgraded user can only use the Skype for Business client to join existing Skype for Business meetings or meetings on Skype for Business organized by non-upgraded users or external parties. An upgraded user can continue to communicate with other users in the organization who are still using Skype for Business by using the interoperability capabilities between Teams and Skype for Business.
Skype for Business–only mode
Users who need to stay in Skype for Business can be configured as Skype for Business–only users. Users configured in this mode will be prevented from using Teams and will be able to communicate with Teams-only users by using the interoperability capabilities between Teams and Skype for Business.
Upgrade and coexistence building blocks
To formally prepare your organization for its journey to Teams, you need to start planning for the upgrade scenarios that will eventually let your organization fully embrace Teams as your sole communications and collaboration solution.
When some of your users are ready to use only Teams for their day-to-day communications and collaboration needs, you can start upgrading these users to Teams by enabling Teams-only mode for them.
If it’s not feasible for your whole organization to move to Teams, you can start by fully adopting Teams as a group collaboration solution first while keeping Skype for Business as your organization’s unified communications solution. Another option is to start moving meetings to Teams in addition to introducing Teams group collaboration capabilities, while keeping the rest of the unified communications capabilities in Skype for Business.
The following table compares upgrade and coexistence modes.
|Skype for Business with Teams collaboration only||Skype for Business deployment with requirements that aren’t yet met by Teams (for example, advanced compliance)
Long-term need for and/or commitment to Skype for Business
|Start Teams adoption quickly, focusing on group collaboration first
Want to keep all unified communications workloads on Skype for Business for now
|No overlapping capabilities between Teams and Skype for Business
Instant messaging and chat will reside in Skype for Business (tied to calling)
|Skype for Business with Teams collaboration and meetings||Skype for Business deployment with significant use of enterprise voice and requirements that aren’t yet met by Teams calling
Long-term need for and/or commitment to Skype for Business
Might be using a third-party meeting service
|Start Teams adoption quickly, going beyond group collaboration
Improve your users’ meetings experience
|No overlapping capabilities
High-value meetings on Teams (WebRTC, cloud meeting recordings, and so on)
|Instant messaging and chat will reside in Skype for Business (tied to calling)|
|Islands||Smaller or simpler Skype for Business deployment
Ability and willingness to manage some short-term complexity to move to Teams more quickly
|Go to the full Teams experience as quickly as possible
Conduct a proof of concept (PoC) of Teams
|Simple to operate, no interoperability
Best Teams experience up-front for all capabilities
|Requires good user communication to avoid confusion and to drive usage toward Teams
Exit strategy requires users to have fully adopted Teams by the time Skype for Business is decommissioned
|Teams only||Some users need to stay on Skype for Business
You’re upgrading your Skype for Business Online users to Teams while keeping Skype for Business on-premises users on Skype for Business Server
You might have already deployed users in islands mode and are ready to retire Skype for Business for groups of users
|Reduce variable costs on Skype for Business (on-premises server operations, outsourcing contract, and so on)
Go to the full Teams experience as quickly as possible, for at least some users
|Limits user confusion by providing only one client to work with||Interoperability only supports basic chat and calling between Skype for Business and Teams|
|Skype for Business only||Some users need to stay on Skype for Business
||Limits user confusion by providing only one client to work with||Continue to meet business requirements that currently can only be met by Skype for Business||Interoperability only supports basic chat and calling between Skype for Business and Teams|
To help you enable each of the modes described above, we'll publish a Quick Start Guide about how to execute your journey from Skype for Business to Teams when the policies are available at a later time. Stay tuned!
You can take multiple approaches to upgrading from Skype for Business, either online or on-premises, to Teams:
- In a simple upgrade journey, you first deploy Teams in Skype for Business with Teams collaboration–only mode as part of evaluation and early adoption, and then implement Teams-only mode with the goal of eventually retiring Skype for Business from the environment for all users in the organization.
- A gradual upgrade journey delivers a specific upgrade mode to a specific group of users (also called a cohort), depending on their communications and collaboration requirements. Over time, the entire organization can converge into using Teams only and eventually replace Skype for Business. However, if your organization has compelling business reasons to keep Skype for Business—such as a dependency on a Unified Communications Managed API (UCMA)–based solution that integrates with line-of-business applications, or an ethical wall solution currently available for Skype for Business only—you can upgrade a majority of users to Teams-only mode while retaining Skype for Business users in one of the Skype for Business modes for a portion of your user population.
For both types of upgrade journey, if your organization is currently a Skype for Business on-premises deployment only, you need to start planning to implement Skype for Business hybrid before upgrading your users to Teams-only mode. This will also help facilitate interoperability with Teams. Use MyAdvisor to guide your Skype for Business hybrid implementation.
Teams-only mode requires that the users who are part of cohorts be homed in Skype for Business Online, and a hybrid relationship between your Skype for Business on-premises deployment and your Skype for Business Online tenant is required to facilitate the upgrade and interoperability between Skype for Business and Teams. The move to Skype for Business Online must be completed for users who are part of the cohorts before they’re upgraded to Teams-only mode. Skype for Business Server 2019, and also a future cumulative update for Skype for Business Server 2015, plan to simplify the mechanics of upgrading on-premises users to Teams by managing the migration to Skype for Business Online and upgrading the users to Teams-only mode in one step.
Whichever journey you choose, Microsoft is here to support you through the upgrade process. From technical requirements to user readiness resources, we’ll share guidance and best practices to help ensure a successful transition from Skype for Business to Teams. Detailed upgrade guidance will be ready soon, so be sure to check back for more information.
Simple upgrade journey
The simple upgrade journey is illustrated in the following diagram.
Teams is deployed to all users in the organization and configured in Skype for Business with Teams collaboration–only mode. When your organization determines that Teams is ready to fulfill all of your communications and collaboration needs, all users are upgraded to Teams-only mode. At that point, Skype for Business can be retired from the environment.
Gradual upgrade journey
An example of a gradual upgrade journey is illustrated in the following diagram.
Teams is deployed in the organization by using different upgrade modes for different groups of users, or cohorts. For example, a group of users can be enabled for islands mode, another enabled for Skype for Business with Teams collaboration and meetings mode, while a third group of users might initially be enabled for Skype for Business with Teams collaboration–only mode.
Over time, groups of users can be upgraded to Teams-only mode, followed by the rest of the organization. Eventually, the entire organization will be ready to retire Skype for Business and use only Teams for communications and collaboration, or—if business requirements dictate that Skype for Business be retained for a specific group—the majority of users in the organization can use Teams only.
Based on the upgrade journeys described earlier in this article, the following prescriptive guidance is provided for specific Skype for Business deployment models that might map to your current deployment model.
|Deployment model||Starting point||Considerations||Journey|
|Skype for Business Online–only with Calling Plans||Office 365 tenant with Azure AD Connect, SharePoint Online, Exchange Online, and Skype for Business Online
Phone System with Calling Plans implemented using Skype for Business Online for all users
|All users leverage certified headsets
Meetings require internal and anonymous external VoIP participants
Messaging includes internal and external contacts
|Messaging roadmap: Federation feature targeted for release Q2 of 2018
Meetings roadmap: Features you want are already available
Calling roadmap: Features you want are already available
|Skype for Business Online with Cloud Connector Edition (CCE)||Office 365 tenant with Azure AD Connect, SharePoint Online, Exchange Online, and Skype for Business Online
Phone System with hybrid voice via CCE implemented by using Skype for Business Online at multiple office locations
1,000 users are using messaging and voice workloads only
|80% of the user population leverages Phone System with hybrid voice via CCE
All messaging is contained within the company
Meetings aren’t currently being used, but there’s interest in enabling Audio Conferencing in the future
|Messaging roadmap: Features you want are available
Meetings roadmap: Future requirements can be met
Calling roadmap: Direct routing to Teams feature targeted for release Q2 of 2018
|Skype for Business Hybrid||Office 365 tenant with Azure AD Connect, SharePoint Online, Exchange Online, and Skype for Business Online
Skype for Business Server 2015 deployed and hybrid is configured with Skype for Business Online
|A number of users require the ability to record meetings
There are 10 conference rooms, currently leveraging Skype Room Systems v2
The organization wants to take advantage of Teams as a collaboration tool as quickly as possible
|Messaging roadmap: Features you want are available
Meetings roadmap: Cloud meeting recording, meeting room devices feature targeted for release Q2 of 2018
Calling roadmap: Features you want are available
|Skype for Business Server (on-premises)||Office 365 tenant with Azure AD Connect and Exchange Online
SharePoint and Skype for Business are deployed on-premises
|Full enterprise voice feature set (Skype for Business Server 2015) currently in use
Contact center deployed
Meetings are conducted with internal and external federated users, using both VoIP and dial-in conferencing
Messaging with internal and external users
|Deploy SharePoint Online
Configure Skype for Business hybrid (split domain)
Messaging roadmap: Federation feature targeted for release Q2 of 2018
Meetings roadmap: Federated meeting-join, PSTN lobby feature targeted for release Q2 of 2018
Calling roadmap: Feature targeted for release Q4 of 2018 and onward
Investigate upgrade to Skype for Business Server 2019
Decide the required additional work to complete your upgrade journey.