A specific Group or Distribution List email address (MailNickName) already exists on the Destination. Because the migration attempts to recreate the Source MailNicknames on the Destination, or associate them with existing Destination MailNickNames, this can result in failure of a Collaboration migration or the unintentional merging of Groups or Distribution Lists on the Destination during a Collaboration migration.
Note: Some common nicknames might include “Marketing”, “IT”, “Support”, etc.
Adding a Support Option in the Advanced Options for the migration allows MigrationWiz to change the MailNickName with an added suffix or prefix. The Group Name (Display name) will not be changed.
Changing the MailNickName will allow the team to be displayed in Teams alongside an already existing Team of the same name and will prevent files from being migrated to unexpected locations on the Destination.
Note: This Advanced Option will change the names of all Teams migrated while the option is in place. To only rename specific Teams, it would be necessary to use a filter to specify which teams to migrate. For more information on using filters, see Collaboration Migration: Adding a Filter.
Depending on the preferred renaming format, choose one of the Support Options listed below.
To add text before the Team name:
Add text after the Team name:
- Replace “text” with the desired text to be added before or after the team name.
For example, if using PrependRootFolderName=“Migrated” and migrating a Team named “Product”, after migration, the team name will be “MigratedProduct”. Using AppendRootFolderName in the same example would rename the team “ProductMigrated”.
- The Group Name will not appear differently on the Destination after the migration. The change is only for the MailNickName. If a team with the same name already exists on the Destination, there will be two instances of that team name on the destination after the migration.
Recommendation: Use a prefix or suffix to identify the original Channel for ease of group management after the migration completes.
See the images below for an example of the results when using this Advanced Option.
As shown, “Team 1” was a team name that existed on both the Source and the Destination at the time of the migration. By using the Advanced Option, both teams remain separate on the Destination after the migration. All files and conversations from the Source are correctly placed under the migrated team, rather than being merged into Team 1, which already existed on the Destination.