This feature spotlight provides an in-depth look at the process of migrating a Microsoft Teams instance to a new Office 365 tenant with MigrationWiz. Learn more about the growing demand (and opportunity) to support Teams migration projects here, or watch a short demo video of a Teams migration with MigrationWiz.
As adoption of Microsoft’s new collaboration platform has grown, so too has the need to migrate the files and conversations as part of a broader tenant-to-tenant project. That’s why we’re pleased to announce MigrationWiz now supports the migration of a Microsoft Teams instance to a new Office 365 tenant! We’ve been hard at work on this solution for several months and worked closely with beta partners, analysts, and internal teams to understand new migration demands of this workload and how to deliver the best experience for our partners and end-users.
This article will detail what components of a Teams instance we are able to migrate; how this new workload can be configured in the same familiar MigrationWiz flow as other workloads like mail or documents; and information about our new pre-migration assessment and license type. For step-by-step migration guides and other technical information, visit the BitTitan Help Center.
What Components of a Teams Instance Can BitTitan Migrate?
MigrationWiz now supports the migration of the following components:
- Teams: the top-level Groups comprised of a user base, file site, and Channels. There may be several Teams in the organization’s broader instance and users may belong to multiple Teams.
- Channels: within each Team, Channels are individual sections that contain a threaded Conversation tab and file folders.
- Conversation History: the central discussion threads specific to each channel. This does not include private or group chats between users in the same tenant or a federated tenant.
- User Permissions: the governance behind the Teams instance, specifically access control for users to each Team.
- Files: documents stored on a SharePoint site specific to each Team with subfolders for each Channel.
The migration of Conversation History is worth calling out here – as of this writing, Microsoft APIs are limited in their ability to export/import conversation history. Fortunately for partners, we’ve developed a process to migrate the most recent 2,500 conversation threads from the Teams instance on the Source tenant and rehydrate those conversations in their proper Channels on the Destination. Unlike other vendors that migrate Conversation History all into HTML, our solution enables users to reply to conversations from the Source tenant on the Destination. It also migrates timestamps (in UTC) to preserve an audit trail for legal departments and the fun stuff like emojis, GIFs, and more for end-users (note this does not include reactions within those conversations such as a “thumbs up”). MigrationWiz will also indicate which discussions migrated from the previous tenant (see screenshot below).
Conversation History older than the most recent 2,500 messages will be migrated in HTML format for data retention. This is in response to significant throttling from Microsoft experienced during some of our early testing. These threads will be made available in the corresponding Channels on the Destination with a tab at the top labeled “Files.”
What’s the Flow for Teams Migration in MigrationWiz?
Configuring the Project
Teams migration projects will follow the same simple setup process as other workloads in MigrationWiz. For Teams projects, we’ve created a new project option: “Create a Collaboration Project.” This will now be presented alongside mailbox, document, archive, and public folder options in the “Create a Project” window.
Here the traditional MigrationWiz flow takes over: select Microsoft Teams as your Source and Destination endpoints, provide Global Admin Credentials, and move to the pre-migration assessment.
Built into the pre-migration flow for a Teams-to-Teams scenario is an assessment of the Source instance. This assessment will collect information such as the number of users, number of Teams, total file size, and the MigrationWiz licensing necessary to complete this project. The assessment will help gauge aspects of a Teams migration project, including timelines and number of licenses required, to better estimate overall project costs. This assessment is free and can be run multiple times on the Source environment prior to migrating.
Once that is complete for all Teams on the Source, MigrationWiz will display information about your entire instance, including the number of licenses needed to migrate (more on that below).
Select Individual Teams to Migrate
Following the Source assessment, MigrationWiz users can now specify which individuals Teams they would like to migrate. This is important for scenarios such as a divestiture or in an effort to reduce sprawl from the initial deployment.
After the assessment completes, users can edit the Assessment Summary CSV to specify which Teams they would like to migrate. Once this modified CSV is imported, the assessment results for the project will reflect on the Teams selected for migration, providing you with the amount of data, number of users, and required licenses for the new project constraints.
Additional guidance for selecting individual Teams can be found here.
Introducing the Collaboration License
For Teams migration projects, we’re introducing a new license type: MigrationWiz Collaboration. This license will allow the lift-and-shift migration of a Teams instance from one Office 365 tenant to another. The Collaboration License will be priced at $15 per user within the Teams instance and with a data allowance of 10 gigabytes per license. Should the total amount of data in the Source exceed the shared data allowance of 10GB per user, additional licenses will be required.
Start Your Migration
Once the assessment has been performed and licensing requirements met, MigrationWiz is ready to go. You can launch your project immediately or schedule for a later date. Once a project is launched, MigrationWiz will:
- Recreate Teams and Channels on the Destination tenant
- Create a SharePoint Site for each Team and Subfolder for each Channel in that Team
- Populate those Teams, Channels, and underlying SharePoint site with data from the Source tenant’s Conversations and Files
- Assign Permissions to Users on the Destination
Note that the Teams and Channels will show the administrator account as having added the users and then leaving the group. This is normal behavior from Office 365.
MigrationWiz in Action: Teams Demo
Learn more about Teams migrations with MigrationWiz in the short demo video below. Our technical experts walk through project setup, the new Teams assessment tool, and other best practices to ensure your first Teams migration is a success.