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 credentials, and begin to import Teams
Add Teams to A Collaboration Project
Once the project has been created, it’s time to add Teams to your project. MigrationWiz offers three methods to accomplish this:
- Autodiscover: automatically scan the Source tenant to identify all teams in the instance. Once autodiscover has completed, users will have the option to directly import all the Teams as line items into the project or download a CSV file of all the Teams to further manage the Teams. The same CSV file can also be uploaded via Bulk Add.
- Bulk Add: A good option for larger projects with more sophisticated mapping, MigrationWiz offers a CSV template file to manage adding Teams, or the option to use the one created during Autodiscover.
- Quick Add: For smaller projects or proof of concepts, Quick Add allows you to migrate specific Teams without the full CSV management.
Start Your Migration
Once Teams have been imported, it’s time to start your migration. Like other workloads such as mailboxes, MigrationWiz treats each Team as an individual line item, allowing you to select individual Teams to migrate or move them all.
Once you have verified credentials for the selected Teams, you are now able to kick off the migration itself. Similarly to a pre-stage approach for mailboxes, the first pass in a Teams project will establish the “scaffolding” for the Teams instance on the Destination – recreating Teams and Channels but not yet migrating data.
Once that creation process is complete, the second pass will move Teams Permissions, Documents, Conversation History, and Document Permissions to the Destination tenant. We migrate up to 30 Teams in parallel and are able to migrate over 500 Teams/day depending on the amount of data contained within each Team. For more granular information on this scenario, see our step-by-step guide here.
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.