The following steps are recommended before setting up or running a Collaboration project to help reduce the number of errors or delays that might be encountered.
Before a Migration
- Ensure that the users are all set up and licensed on the Destination (MigrationWiz does not create or license the users). We recommend setting up the users several hours prior to the migration, as Microsoft can take up to 24 hours to complete user setup in a tenant.
- The administrator account on the destination must be set up without a federated account.
- ADFS and Multi-Factor Authentication turned off for the administrator accounts on both the Source and Destination before starting a Collaboration migration.
- Add the Administrator account as an owner to the teams on the Source and the Destination. Do this at least 24 hours ahead of the migration testing, to avoid possible delays in permission setting.
- Assessments are required for Collaboration migrations. They cannot be skipped. Assessment completion typically takes about thirty seconds per Team; however, speeds are affected by several external factors and the assessment may take longer to complete. These external factors include, but are not limited to, current server demand, the size of the Teams on the Source server, and available bandwidth. You can read more about potential factors in our article How long does a migration take?
- To prevent users from updating or using specific Teams while the migration is ongoing, it is possible to archive the team on the Source for the duration of the migration. This will prevent changes to the Team and its channels.
- By default, we match users from the Source to the Destination based on the email prefix in their SMTP address. For example, if the user email is “firstname.lastname@example.org”, we match the “name” portion. If there are multiple people with the same email prefix at the Destination (e.g. email@example.com and firstname.lastname@example.org, or the email prefix of a particular user is changed in the destination (e.g. email@example.com → firstname.lastname@example.org), it will be necessary to use the advanced option UserMapping="email@example.com->firstname.lastname@example.org" to set the new or correct name for each user. For instructions on adding this option, see How do I add support options to a project or to a single item?
Note: The Usermapping command goes in the Support Options section and will require one line per user that needs mapping. Click the + to add additional lines. Replace the email addresses in the example with the actual user email addresses.
- Important: During a Teams migration, permissions for the files are inherited from the parent team by default. Some source files may have custom permissions due to cross-team or external-partner sharing. Migrating these custom permissions happens at the file level, requiring more API calls to the source and destination, which increases the likelihood of the migration being throttled. To avoid this, we recommend not selecting this option and informing users that custom permissions will need to be re-added.
During a Migration
- MigrationWiz is not an updating tool. Once a Collaboration project has been started, we recommend that you do not rename any Channels at the Source. If Channels need to be renamed, they should be renamed before an initial Assessment is run, or after all teams have been successfully migrated to the Destination tenant. If a Channel is renamed between when the initial Assessment is run and the final migration has completed, some files may end up in incorrect Destination locations.
- Conversations that are migrated, then updated on the Source, will not be updated on the Destination when the migration is run again. Because of this, it is best to plan to do this migration in a single migration pass, generally over a weekend or a planned down time.
- If conversations are updated during the course of the migration, the migrated files will need to be deleted from the Destination tenant. The project will need to be reset from the Action menu, the assessment will be run again, and then you can migrate the files again.
- Alternatively, it is possible to delete only the updated conversation from the Destination, adding a filter to the project to migrate only that specific conversation. After the project has been reset, run the migration again. To add a filter, use the instructions in the article How do I filter a Folder? The team name will be used for the filter. For example, if the specific team is called Team_Alpha and the specific channel is called Project_ChitChat, then the filter used to migrate only this channel would be ^(?!Team_Alpha/Project_ChitChat)
Note: To add filters or mapping to a project, click Edit Project and select Advanced Options.
After a Migration
- If a migration completes successfully, but not all members show on the Teams destination, the users may be taking extra time to sync. This can happen when a Team has a large number of users. It is possible to verify that all the users were migrated by logging into the Office 365 Admin portal, going to the migrated group (Team), and viewing the members list to verify that the expected number of members were migrated. This should be synced to the Teams interface within the next few hours.
- After the migration is completed, remove the MigrationWiz App Authentication with the instructions here.