You have a Microsoft Lync Server 2013 deployment. Some users use Enterprise Voice. You plan to migrate to Microsoft Teams. You need to design a migration solution. The solution must minimize the…

Question

Options

• AMigrate all users directly from Lync Server 2013 to Teams.
• BMigrate the Enterprise Voice users from Lync Server 2013 to Microsoft Skype for Business Server
• CMigrate all other users directly from Lync Server 2013 to Teams.
• DPerform an in-place upgrade from Lync Server 2013 to Microsoft Skype for Business Server

• A
  8% (5)
• B
  3% (2)
• C
  5% (3)
• D
  84% (53)

Explanation

Performing an in-place upgrade from Lync Server 2013 to Skype for Business Server (D) is the correct first step because Microsoft's supported migration path to Teams requires going through Skype for Business Server first - you cannot directly migrate Enterprise Voice configurations from Lync 2013 to Teams while preserving telephony settings, and the in-place upgrade minimizes disruption by keeping users on a familiar interface with their existing voice configurations intact. Option A (direct Lync 2013 → Teams) is wrong because there is no supported direct migration path that preserves Enterprise Voice from Lync 2013 to Teams - you must stage through Skype for Business. Option B is a partial step (only moving Enterprise Voice users) and Option C (only moving non-voice users directly) both describe incomplete or unsupported piecemeal approaches that would create a fragmented, harder-to-manage environment. The question asks what to include in a complete solution, and the foundational step is the in-place upgrade to Skype for Business Server, which then enables a clean Teams migration path.

Memory tip: Think of it as a staircase - Lync 2013 → Skype for Business → Teams. You can't skip a step, especially when Enterprise Voice is involved. "In-place upgrade first" = least disruption.

No community discussion yet for this question.