For all the hype around the fast-growing collaboration app, Teams instances are susceptible to the same sprawling, poorly governed architecture as its close cousin, SharePoint. That sprawl becomes an issue when users, data, and permissions need to migrate. As adoption grows, so too does the need to migrate Teams as another workload when moving Office 365 tenants.
Through the same easy-to-use interface as all other migration workloads, IT professionals can use MigrationWiz to conduct an assessment of the existing Teams environment to understand critical factors like number of users, amount of data, and the proper licensing needed to complete the project.
Let’s look at how to run this assessment in MigrationWiz.
Running the Teams Assessment
Teams migration projects follow the same simple setup 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. The assessment gathers the following information about your Source instance:
- Number of individual Teams
- Number of users
- Amount of data
- Number of licenses needed, based on the number of Teams and users in the project
After verifying tenant credentials, MigrationWiz will discover all users and the associated Teams, channels, and files within those channels to begin outlining the scope of this project.
