The document provides an overview of migrating from Skype for Business to Microsoft Teams. It discusses the evolution of collaboration tools from Skype for Business to Teams. Key points covered include different migration paths depending on the organization's current setup, features that make Teams preferable to Skype, and tips for managing coexistence and the transition. The document aims to help organizations understand the options and best practices for migrating communication and collaboration to Microsoft Teams.

1. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
1
SM
Your Migration Path
to Teams: A
Comprehensive Guide
Daniel Cohen-Dumani – Withum Digital
Jill Hannemann – Avanade

2. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
2
SM
What to Expect From Today’s Session
• Evolution of Skype for Business
and Microsoft Teams
• The history behind why Teams is
replacing Skype
• The benefits of moving to
Teams and features it offers that
Skype doesn’t
• Tips and insights on how to best
approach your migration from
Skype to Teams
▪ Understand the migration path to
achieve a smooth transitions to MS
Teams
▪ Understand the migration options and
end user experiences
▪ Understand how to manage co-
existence
▪ How is Teams different than Skype for
Business
▪ How to manage change
▪ Where to get started
Agenda Objectives

3. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
3
SM
Skype online to be retired by 7/1/2021

4. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
4
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Skype for Business Teams
Roadmap/History
2006
Office
Communicator
2010
Lync
2015
Skype for
Business
Nov 2016
MS Teams
Launch
Preview
March
2017
MS Teams
is widely
available
September
2017
Microsoft
announced
Teams will
replace
Skype for
Business
July 2018
Free
version of
Microsoft
Teams
August
2018
Microsoft
announces
Teams voice
features are
now
available
Q1 2019
Additional
Voice
features
coming
Better
Interop
2021
Skype
Online
Retire
ment

5. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
7
SM
Why Should You Migrate to Teams?
Why you should actively consider it now…
Features and
capabilities
 Teams can already do more
than Skype for Business Online
 Rich Intelligent
Communications roadmap and
rapid innovation
User
experiences
 Modern, rich experiences
 State-of-the-art cross-platform
and mobile experiences
 Collaboration, Teams and
Channels
Operational
performance
 Modern client built on modern
infrastructure
 Teams can provide
improvements in quality and
operational metrics

6. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
8
SM
Migration Paths
New Customer < 500 users now or all customers after Sep 1 2019
Migration from Skype for Business Online (and may be a Teams
users already)
Migration from Skype for Business on-premises or Hybrid (and may
be a Teams users already)

7. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
9
SM
Skype for Business not deployed yet

8. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
10
SM
New tenant < 500 users or tenant created after Sep 1, 2019
Good news Microsoft Teams is your only option

9. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
11
SM
New tenant or Teams not in use > 500 users
You should consider Teams rather than Skype for Business

10. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
12
SM
Upgrading from Pure Skype for Business Online

11. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
13
SM
Pure SfB Online Organization: User Perspective
Full Side by Side Approach
• Enable Teams with full functionality
• Allow users to experience full benefits of Teams digital transformation soonest
• All users must run both SfB and Teams clients at all times until they become Teams Only

12. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
14
SM
Pure SfB Online Organization: Org perspective
• Full side-by-side approach
• Drive rapid adoption across your organization to saturation, while leaving SfB enabled.
• Deploy Teams side-by-side with SfB Online with full functionality in Teams
• Once you have reached a saturated level of adoption and all room devices are deemed Teams compatible, upgrade all
users to Teams-only as rapidly as possible.

13. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
15
SM
What is a Teams-Only User?
Long Story:
Experience of a Teams-Only user
Short Story:
“Upgraded User” “Teams-Only User”= Chat & Calling
Receives and initiates all chats and calls in Teams
Can interop (IM/call) with any SfB user
Is redirected to Teams if they try to sign in to SfB
Meetings
Schedules all new meetings in Teams
Can join existing SfB Meetings
Data that gets migrated
Existing contacts from SfB
Existing on-premises SfB meetings to Teams (TAP only)

14. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
16
SM
Upgrade for Skype for Business (on-premises/
hybrid) and More Complex Organizations

15. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
17
SM
SfB + Teams Collaboration: Upgrade From a User’s Point of View
For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality
• Starting point: User is in SfB with UC functionality
• Introduce Teams to the user, without UC functionality*
• All calls & chat continue to land in and originate from SfB
• User can explore net new functionality of Teams (Channels/apps/etc)
• Switch UC functionality over to Teams
• Non-upgraded users and upgraded users rely on interop to communicate
* Recently made available

16. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
18
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Org perspective: Upgrade without overlapping functionality
• For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality
• Variation A: No prior Teams usage
 During migration, users in SfB can communicate with users in Teams via interop
 Presence is aligned with routing
 SfB users can use non-UC functionality in Teams prior to upgrade

17. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
19
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Org perspective: Upgrade without overlapping functionality
For on on-prem & hybrid orgs, or if end users are confused having two apps with same functionality
Variation B: For orgs with prior Teams usage

18. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
20
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
SfB + Teams Collaboration and Meetings: Upgrade from a user’s point of
view: Meetings First
For on on-prem & hybrid orgs, that will move to Meetings First before going Teams Only
• Begin State: User is in SfB with UC functionality.
• Introduce Teams to the user, without UC functionality, previously described
• Switch Meetings scheduling functionality from SfB to Teams
• Up to this point, all calls and chats initiate from and land in SfB
• Upgrade fully to Teams-Only Teams
• Chat & Calling between Upgraded (Teams-Only) users and all other users relies on interop

19. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
21
SM
How About Co-existence and Interoperability?

20. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
22
SM
User
Experience
During Co-
Existence
Customers manage interop & coexistence via
“mode”
• Exposed in Teams Admin Center UX and PowerShell
Mode governs:
• Routing of incoming messages and calls
• In what client do you initiate chat and calls (requires
upcoming TeamsAppPermissionsPolicy)
• In what service do you schedule meetings?
Mode is a per user assignment, achieved using
O365 admin tools
• Can also be assigned to on-prem users (except TeamsOnly)
If necessary, can mix and match modes across an
org

21. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
23
SM
Co-existence Modes
Mode Calls and Chats
Meeting
Scheduling
Teams Channels
available?
Recommended Use Case
Teams Only
(Requires home in SfB Online)
Teams Teams Yes
The final state of being upgraded.
Will also be default state for *new* tenants as of 9/1/2019
SfB With Teams Collab And
Meetings*
SfB Teams Yes
“Meetings First” scenario: Enables on-prem customers to
benefit from Teams meeting functionality, if not yet ready to
move calling to the cloud.
SfB With Teams Collab* SfB SfB Yes
Recommended starting point for on-prem/hybrid orgs. Also
for online orgs that want tighter admin control
Calls and chats always routed to only 1 client throughout the
migration.
SfB Only* SfB SfB No Specialized scenario for orgs with strict requirements
Islands Either Either Yes
Recommended for online orgs that can migrate fast (default
setting)
Allows a single user to evaluate both clients side by side.
Chats and calls can land in either client; Users must continue
to run both clients.

22. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
24
SM
Co-existence mode example

23. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
25
SM
Interoperability
• What is interop?
• Native Interop
- 1:1 chat
- Calling
• Interop
Escalation

24. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
26
SM
Interoperability
• Coming soon
• Screen sharing between Skype for Business and Teams

25. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
27
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Devices
• Don’t forget your devices

26. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
28
SM
Getting Started:
Designing Your Path to
Teams

27. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
29
SM
“13 million daily active
users,” says Microsoft
Teams chat app is now
growing faster than Slack
- July 11, 2019
Competition is getting Nasty
https://www.businessinsider.com/microsoft-teams-daily-active-users-slack-
2019-7
"Slack Takes Aim at Teams'
Weaknesses"
Slack introduces a
'snappier, more efficient
Slack desktop experience.
- July 22, 2019
https://www.petri.com/slack-aims-teams-weaknesses

28. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
30
SM
Teams and Channels are the Hub for Collaboration
• Teams can have many channels
• Channels are where tabs exist:
• Conversations
• Documents
• Wiki
• Notes
• Other apps/bots
• Channels can be private
• Teams correlate with SharePoint site
collections
• Channels correlate with folders
• Information architecture is flat –
everyone in the tenant shares the space
• Users can control what teams they see
and the order in which they appear
• Create templates for common scenarios

29. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
31
SM
When you
Create a
Team…
Here’s what gets created:
• A new Office 365 Group
• A SharePoint Online site and document library to
store team files
• An Exchange Online shared mailbox and calendar
• A OneNote Notebook
• Ties into other Office 365 apps such as Planner
and Power BI
When you create a team from an existing group, that
group’s membership, site, mailbox and notebook are
surfaced in Teams.
31

30. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
32
SM
Interesting
things…
CHANNEL
MODERATION
SCOPED DIRECTORY
SEARCH
PRIVATE CHANNELS STAFF HUB/SHIFTS
32
Many more coming in the next six months

31. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
33
SM
Managing changes
• Everyone has their threshold for change capacity. Is your organization:
❑ Upgrading from Skype for Business
❑ Upgrading Windows, Office or other Office apps?
❑ Replacing desk phones with headsets?
❑ Moving or redesigning physical office space?
❑ Merging with or acquiring a new company?
❑ Internal reorganization?
❑ Other _________?

32. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
34
SM
What We Know for Sure
• is more
prominent than
ever
• 80% admit to
using their
communication
tool of choice1
Organizations are made
up of innovators,
laggards and everyone
in between
Resistance is a normal,
human behavior that
takes time
‘Deploy it and they will
come’ doesn’t work
1“What is Shadow IT?”, https://www.skyhighnetworks.com/cloud-security-university/what-is-shadow-it/ (accessed March 2017)

33. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
35
SM
Upgrade: The Worst Kept Secret
• People talk, rumors start. Bring users into the conversation early and
often, helping them feel part of the change.

34. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
36
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Building your
user acceptance
plan
How to generate
excitement for
the upgrade to
Teams

35. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
37
SM
Creating Governance at the Company Level
Teams Creation and
Management
• Process for new team
creation – why and when
for new teams vs. channels
• Naming convention
• App store access
• Use and accessibility of
other Office 365 workloads
• Recommended IA
• SharePoint vs. Teams
IT Operations and
Security
• Meeting policies – i.e.
screen sharing, white board
• Network assessment
• Heavy client presence
• Teams content retention
• Teams archival and
abandonment
• eDiscovery, labels and
classification
External Access
• Determine level of
interaction with people
outside your organization
• Chat and call federation
• Guess Access for
collaboration

36. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
38
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Take Your Plan Out for a Test Drive
• Conduct a pilot with end-users to validate user and organizational
readiness.

37. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
39
SM
010101010101010101010101010100101010101010101010101100111101010110001111100000000000000000000000
000000011111011011011010101010101010101010101010100101010101010101010101100111101010110001111100
000000000000000000000000000011111011011011101010101010101010101010101001010101010101010101011001
111010101100011111000000000000000000000000000000111110110110110101010101010101010101010101001010
101010101010101011001111010101100011111000000000000000000000000000000111110110110110101010101010
101010101010101001010101010101010101011001111010101100011111000000000000000000000000000000111110
110110110101010101010101010101010101001010101010101010101011001111010101100011111000000000000000
00000000000000011111011011011
Challenges: It’s a new way to work
Reality – Teams is intentionally transparent.
Reality – Your company culture may not be.
Conversations and document sharing may be a culture shift.
• No more attachments
• No more emailing colleagues
• Teams becomes a core part of every day

38. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
40
SM
Key takeaways
Users may have
limited discretion
in upgrading to
Teams, but they
do control how
much they will
use it (and
Adoption is key
to business value
realization/ROI)
01
Managing user
change is critical
for overall
upgrade success
02
Technical and
user readiness
planning and
implementation
should happen
simultaneously
03
Microsoft is
providing tools
for you to
manage your end
to end migration
04
Whether coming
from on-premise
or online, there
is a simple path
to get from skype
for business to
Teams
05
You can
customize the
deployment path
to fit your needs
06
This is more than a technical migration

39. WithumSmith+Brown, PC | BE IN A POSITION OF STRENGTH
47
SM
Thank You!
@dcohendumani
@ImJillHannemann