Microsoft Teams to Microsoft Teams Migration Guide

Teams to Teams Migration (New)

This document is an end-to-end migration guide that demonstrates how to perform an Office 365 Teams to Teams (New) migration using MigrationWiz. MigrationWiz supports the migration of teams, channels, conversations, permissions, and files.  

The original Teams to Teams (Original) migration guide is below. If you have a Teams to Teams migration in progress, use the links to the right of the document to navigate down to the Teams to Teams (Original) guide and follow those steps. If you are just beginning your Teams migration process, we suggest utilizing the Teams to Teams (New) guide and parallel endpoints. 

We are not able to support migrations with two-factor or multifactor authentication. 

What data will be migrated?

MigrationWiz can migrate most of the data within Teams, but there are some limitations. The following list explains which items will be migrated, which won't, and any limitations or special considerations. 

Migrated Not migrated
  • Teams
    • Public
    • Private Teams
    • Organizational
    • Archived teams - moved as public teams and must be re-archived at destination.
  • Channels - all public channels are migrated. 
    • Conversations
    • Structure
    • Format
    • Root messages
    • Replies
    • Fonts
    • Bullets
    • Lists
    • Colors
    • Quotes
    • Emojis
    • Inline images and stickers
    • Code snippets
    • Hyperlinks
    • GIFs
    • Deleted message notifications;
    • Mentions (as plain text to prevent duplicate notification after migration)
    • Timestamps (in UTC)
  • All files are migrated except files in private chats.
  • Memberships: All memberships are migrated, except for private Teams and Private Channels.

 

MigrationWiz only supports document migrations from SharePoint for Collaboration migrations. We do not support migrations from any other storage point.

  • All private data
  • Private conversations and files under the Chat tab
  • Likes/Reactions
  • Links to files and meeting requests in conversation threads
  • File previews
  • Teams meeting recordings
  • Hyperlink previews
  • Calendar previews
  • User-specific settings (Favorites, Profile pictures, Status messages, and saved messages)
  • Dynamic groups (the groups will be migrated, however, they will be migrated as static groups)
  • Tabs (for example: Planner, Yammer, etc. No custom tabs will be migrated, either)
  • Customized Team settings (these include team picture, member permissions, guest permissions, mentions, etc. New Teams will be created with the Default settings)
  • Team list order (after migration, Teams will not appear on the Destination in the same order as on the Source. Users can drag and drop to reorder the list of teams)
  • Wikis
  • Tags (after migration, the name of the tag will be in plain text if it was included in a conversation)
  • Due to Microsoft limitations, private channels are not migrated for GCC High Tenants.

A note about private channels

MigrationWiz does not migrate private channels within Teams by default. If you have private channels you want to migrate, do so by adding the line TeamsMigratePrivateChannel=1 to the support section of the project's Advanced Options. Note, users will not be added to the private channel on the destination. This needs to be done manually after the private channel migrates

Due to Microsoft limitations, private channels are not migrated for GCC High Tenants.

Migrating guests

Guest access on the source will be migrated if the guest exists and guest permissions are enabled at the destination tenant prior to migration. This may be done via the Teams or Office 365 admin portal.

Other Limitations

1. Conversations

A Conversation History tab will be created for each corresponding channel at the destination. Each team will show the most recent 60 messages, while all older messages may be downloaded as an HTML file in the Conversation History tab.

This number may be increased through the use of the advanced option:TeamsMaxConversationMessage=XXXX. Replace XXXX with the number of messages you wish to migrate. E.g. TeamsMaxConversationMessage=1000 would load 1000 messages per team. This may slow your migration, so plan accordingly if you use this option. 

 

2. Teams EDU Migration 

MigrationWiz will only migrate teams, channels, documents, and messages for Teams EDU instances. MigrationWiz will not migrate many of the Teams EDU features. For more information, contact Support. 

3. GoDaddy 

Due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this migration type.

 

Licenses

There are two types of Collaboration license, currently. For the original Teams to Teams migration, use the Collaboration License. For the new Teams (Parallel) endpoint, purchase MigrationWiz-Collaboration (per Team) licenses. 

  • Each license allows up to 100GB of data to be migrated per license per team.
  • If more than 100GB of data per team is being migrated, purchase enough licenses to cover the total amount of data being migrated. For example, if you have six teams and two of them have 200GB of data, you will need to purchase 8 licenses. 
  • Each license is applied to a single team and expires 12 months after its purchase date. 

 

Prerequisites 

Ensure consent has been given for the Teams application permission.

  • Use Teams-FullControlApp for both the source and destination. To learn more about what these permissions mean, view the article Application Permissions for Teams Migrations.
  • For the New Teams migration endpoint (Parallel), the advanced option UseApplicationPermission=1 does not need to be used. For Original migration scenarios, this option must be enabled during the Advanced Option phase. 

If you have not done so already, log in to your account on MigrationWiz or create a new account.

 

Create a New Project

  1. Go to Projects > Create Project 
  2. Select Collaboration Project.
  3. Update the project information: add a Project Name, select a Customer from the drop down, then click Next Step.
  4. Create the source endpoint by selecting Microsoft Teams Parallel (Source) from the drop down. Ensure Parallel is selected, the migration will fail if the Microsoft Teams endpoint is selected. 
           parallel3.png
  5. Provide your Office 365 credentials (these will be the same Office 365 username and password      you use for the MigrationWiz security group), then click Add.
  6. Next, create a destination endpoint by choosing an Endpoint Name and selecting Microsoft Teams Parallel (Destination) from the endpoint-type drop down. Ensure Parallel is selected, the migration will fail if the Microsoft Teams endpoint is selected. 
      parallel4.png
  7. Enter your Office 365 credentials. These will be the same username and password you used for the MigrationWiz security group. Once your credentials are selected, click Add.
  8. One of the two Azure Storage options listed is required to create the endpoint. For migrations of less than 5GB, you may use the Microsoft Provided Azure storage. For anything over 5GB, we recommend using Custom Azure Storage. The following steps will help you set up the custom storage:
    1. Prepare Azure Environment. If using Microsoft-provided Azure storage, you can skip this section.
    2. Estimate Azure storage costs. This step is optional but is useful in order to provide the customer with upfront storage costs ahead of time. For more information, see Estimate Azure Storage costs for migrations. 
    3. Buy an Azure subscription. You can also use the free one-month trial but be aware that this option is only viable if you are performing a very small migration. 
    4. See How do I Create an Azure Storage Account? to create your storage account. You will need to set up a STORAGE (General Purpose v1 or v2) account rather than a storage blob. Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen.) These need to be entered into the MigrationWiz migration project when specifying the destination settings. We recommend that you create your Azure storage account in the same Microsoft data center as the destination Office 365 tenant. There is no need to create any Azure containers for this migration. 
    5. The access key information that is needed are these: 
    6. -accesskey – This is the Storage account name for the Blob – example “accountname 
    7. -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==” 
  9. Once complete, click Save and Go to Summary.
  10. Verify that both the source and destination are Teams (Parallel) to Teams (Parallel). Variable endpoints are not supported.
  11. For the following step, credentials are mandatory. Ensure all the mandatory fields are filled to activate the Update button. Click this once all steps above are completed.

 

Add Teams

There are three ways to add teams to the migration. Either of these may be used, or both. Read through each of the options before beginning your process. Follow the Autodiscover process to find all the teams you are moving, and then select either Quick Add or Bulk Add. Generally, Quick Add will be used for small migrations, proof of concept migrations, and other tests, while Bulk Add will be used for large migrations and full migration passes.

 

Autodiscover 

  1. On the MigrationWiz project page, click the Add dropdown, then click Autodiscover Items.
  2. Click Start Autodiscover.
  3. Click Discover ItemsMigrationWiz will now discover teams at the source. If the authentication/credentials verification is successful, discovery status will show as Completed however, if the authentication/ credentials verification fails, error messages will be shown.
  4. To download a CSV, click the Download CSV icon. This will generate a CSV file that includes all the teams discovered at the Source. This file can be uploaded via Bulk Add during that stage.
  5. Click Import Items. The discovered Teams at the Source will be populated as line items. By default, destination mail nickname will be set to the same as Source mail nickname.

 

Quick Add

This option is generally used for small migrations, proof of concept migrations, and other tests. It allows you to migrate specific teams without the full CSV management.

  1. Click Add
  2. Select Quick Add Item

You may now add a specific team to be migrated, based on the Team Mail Nickname at the source, e.g. TeamAwesome. You will be able to select the mapping at the destination, including renaming teams if desired. For example, TeamAwesome may be mapped to TeamAwesome at the destination, or to TeamFantastic. 

If TeamFantastic exists at the Destination, the contents from TeamAwesome will be merged to the existing TeamFantastic. If TeamFantastic does not exist at the Destination, it will be created with the data from TeamAwesome.

Bulk Add

You also have the option to use Bulk Add via the CSV template file to manage adding your teams. This is a good option if you are mapping a large number of teams to new destinations, or simply have a large migration. Previously, this had to be done manually, but with the Parallel update, this is now all done within the user interface.

  1. In your project dashboard, click Add.
  2. Select Bulk Add. 
  3. The interface will now walk you through the steps up upload the CSV found through the Autodiscover process. You may edit the columns after upload to change team names or mapping. 

 

Start Migration

Use the checkbox to select the team(s) you will be migrating.

You will need to run a single verify credentials pass before migrating multiple items.

starimig1.png

  1. Click the Start dropdown and select Full Migration. This will bring up a new window to select what data you want to migrate in this pass. 
  2. Select Setting Up Teams, then Teams Creation if it is not selected by default. What_will_be_migrated_Teams.png
  3. Click Start Migration. This pass will create the teams at the destination. Once the teams creation process has been successfully completed, wait a few hours to allow the data to finalize.  
    Note: Due to an API limitation the Channels may not be fully provisioned until they are used.
  4. You will now repeat the full migration process for the data. Repeat step 1, but select Migrate Data this time. The options beneath this should be auto-selected. After confirming that all data options have been selected, click Start Migration. Teams permissions, documents, conversations, and document permissions will all migrate in parallel, 30 teams at a time.
  5. Check the Status column for each team migration progress to ensure your teams are migrating correctly. If teams are not migrating correctly, check the credentials and run another full pass if necessary.startmig3.png
  6. User mapping: By default, we match users from the source to the destination based on the prefix in their User Principle Name (UPN). For example, if the user UPN is “name@domain.com”, we match the “name” portion. If there are multiple people with the same prefix at the destination (e.g. name@domain1.com and name@domain2.com, or the prefix of a particular user is changed in the destination (e.g. name@source.com → name.full@destination.com), it is necessary to use the advanced option UserMapping="name@source.com->full.name@destination.com" to set the new or correct name for each user. 
  •  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 UPN addresses in the example with the actual UPN addresses. 

 

Special Circumstances

Migrating Teams with Special Characters in the Name 

If any team names have special characters, such as emoji icons, Excel may not be able to open the generated CSV file. The steps below may allow the CSV file to be imported with these special characters: 

  1. Open Excel and import the data using Data--> Import External Data--> Import Data. 
  2. Select the file type csv, then browse to your file. 
  3. In the Excel import wizard, change the File_Origin to 65001 UTF (or choose correct language character identifier). 
  4. Change the delimiter to comma.
  5. Select the location to import the CSV to and click Finish. 
    • Note: While these steps should work for most versions of Excel, some versions may still not be able to open the CSV. 
  6. Click Start Full Migration
  7. When the migration is complete, verify that the users are able to see their teams and channels in the Destination tenant. 
  8. Click the bar chart icon in the MigrationWiz dashboard to request an email that contains the project migration statistics. 

 

Migrating using U.S. Government Tenants 

Migrating to or from a U.S. Government tenant requires specialized commands for MigrationWiz to connect. Failing to use these options will result in login errors. 

  1. Click Edit Project. 
  2. Click Advanced Options. 
  3. Under Support Options, add the following options below, depending on the specific migration scenario. 
  • If migrating from a U.S. Government Tenant, add: OneDriveProExportEnvironment=AzureUSGovernment 
  • If migrating to a U.S. Government Tenant, add: OneDriveProImportEnvironment=AzureUSGovernment 
  • As U.S. Government Tenant does not support Application Permission, make sure that the migrating accounts are Global Admin, add: UseDelegatePermission=1

 Government-Specific Limitations

  • Conversation History will not be migrated to a tab in the destination. Instead, a message will be posted in the channel with a link to the conversation history HTML file.
  • Due to limitations in the Microsoft system, images will not be migrated as part of the conversation(s). They will still appear in the conversation history HTML file. 

 

Resolve Errors 

Errors vary widely, so if you encounter migration errors, refer to the Collaboration error list and follow the steps listed under Resolution.

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. 

 

Post Migration

Once the migration has finished, remove the Office 365 user account created for the migration, as well as the MigrationWiz Security Group. 

You will also need to remove the Azure app:

  1. Once the migration has finished, remove the Office 365 user account created for the migration, as well as the MigrationWiz Security Group. You will also need to remove the Azure app using these steps:
    1. Launch PowerShell.
    2. Connect PowerShell to Office 365.
    3. Enter the command: Connect-AzureAD
    4. Enter the admin credential in the prompt.
    5. Enter the command: Get-AzureADServicePrincipal -SearchString Migration
    6. Look for the ObjectId of the app you want to remove and enter the following command: Remove-AzureADServicePrincipal -objectId <the object id>

 

 

*Teams to Teams (Original) Migrations*

A Teams to Teams migration is complex and requires several prerequisites to be met. Read the Collaboration Best Practices article before you begin this migration.

Due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this migration type.

Important: MigrationWiz does not migrate private channels by default. If you have private channels you want to migrate, do so by adding the line TeamsMigratePrivateChannel=1 to the support section of the project's Advanced Options. Please note, users will not be added to the private channel on the destination. This needs to be done manually after the private channel migrates

Due to Microsoft limitations, private channels are not migrated for GCC High Tenants. 

To discover what other items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. These items will vary by source and destination so check the proper environment listings carefully.

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

 

License Type

This endpoint requires MigrationWiz Collaboration licenses. 

Teams EDU Migrations

MigrationWiz will only migrate teams, channels, documents, and messages for Teams EDU instances. MigrationWiz will not migrate many of the Teams EDU features. For more information, contact Support. 

 

Prepare the Source

  1. Create a new, fully licensed, cloud only, Global Administrator account in Office 365 to be used for migration or use the existing Global Administrator account for the tenant. If using the existing Global Administrator account, it must be fully licensed and must not configured with multi-factored authentication (MFA) or AFDS. 
  2. ADFS and Multi-Factor Authentication must be turned off for the administrator accounts on both the source and destination before starting a Collaboration migration.
  3. Add the Administrator account as an owner to the teams on the source. Do this at least 24 hours before migration testing to avoid delays in permission setting. Do not add the admin to any private channels.
  4. Set up the app-based authentication in the Office 365 tenant by following the steps below in the Enable App-Based Authentication section of this document.

 

Prepare the Destination

  1. Create a new, fully licensed, cloud only, Global Administrator account in Office 365 to be used for migration or use the existing Global Administrator account for the tenant. If using the existing Global Administrator account, it must be fully licensed and must not configured with multi-factored authentication (MFA) or AFDS.
  2. ADFS and Multi-Factor Authentication must be turned off for the administrator accounts on both the source and destination before starting a Collaboration migration.
  3. Create user accounts and assign Office 365 licenses. The Office 365 licenses must include Teams access. For more information on which licenses can be used, refer to Office 365 Licensing for Teams. Note, free or Kiosk licenses are not supported.
  4. Set up the app-based authentication in the Office 365 tenant by following the steps below in the Enable App-Based Authentication section of this document.
  5. Prepare Azure Environment. If using Microsoft-provided Azure storage, you can skip this section.
    1. Estimate Azure storage costs. This step is optional but is useful in order to provide the customer with upfront storage costs ahead of time. For more information, see Estimate Azure Storage costs for migrations.
    2. Buy an Azure subscription (or use the free one-month trial and be aware that this option is only viable if you are performing a very small migration). For more information, see How do I buy an Azure subscription?
    3. See How do I create an Azure Storage Account? to create your storage account. You will need to set up a STORAGE (General Purpose v1 or v2) account rather than a storage blob. Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen.) These need to be entered into the MigrationWiz migration project when specifying the destination settings. We recommend that you create your Azure storage account in the same Microsoft data center as the destination Office 365 tenant. There is no need to create any Azure containers for this migration.
      The access key information:
      1. -accesskey – This is the Storage account name for the Blob – example “accountname”
      2. -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”

 

Enable App-Based Authentication

Set up the app-based authentication in the Office 365 tenant. BitTitan uses app-based authentication for SharePoint, OneDrive for Business, Office 365 Groups (Documents) migrations, and Teams migrations. This provides greater security and reduces the potential of Microsoft throttling. It replaces the previous Office 365 authentication, which has been subject to increased throttling by Microsoft. This app-based authentication method is specific for Office 365 tenants.


Important: This app must be added in both .microsoftonline.com tenants (source and destination) to reduce the throttling and failures due to Microsoft throttling policy changes.

If this app is not added on both tenants, MigrationWiz will attempt to create a temporary substitute app in the tenants to be used for authentication. We do not recommend relying on this substitute app creation, as this behavior will only be a temporary transitional behavior within MigrationWiz. To avoid potential interruptions or failures in migrations, it is strongly recommended to set the app up in the tenants.

Add the App to the tenant

1. Visit the following URL and sign in as the administrator user:

For Teams migrations: https://login.microsoftonline.com/common/adminconsent?client_id=e541adb0-93aa-4053-a1e3-04692035881d&state=12345

For SharePoint or OneDrive migrations: https://login.microsoftonline.com/common/adminconsent?client_id=e7c20566-14a7-4722-acd1-396f7268ea1a&state=12345

Do this for both source and destination tenants.

2. Authorize the App for both source and destination tenants.

Click the Accept button.

Steps to remove these permissions are provided below in the Post-Migration section.  

 

Run Migration

Create a Collaboration migration project

  1. Sign in to your MigrationWiz account.
  2. Click Go To My Projects.
  3. Click Create Project.
  4. Select a Collaboration migration type. Collaboration projects are used to migrate a Microsoft Teams instance from one Microsoft tenant to another. Collaboration migrations migrate all Teams, Channels, files, and permissions.
  5. Click Next Step.
  6. Enter a Project name and select a Customer.
  7. Click Next Step.
  8. Select a Source Endpoint from the Endpoint dropdown menu. If an Endpoint has not been created, click New and provide the requested information in the Endpoint creation flyout.
  9. Select a Destination Endpoint from the Endpoint dropdown menu. If an Endpoint has not been created, click New and provide the requested information in the Endpoint creation flyout. The endpoints will automatically default to the type “Teams”. This is normal and cannot be changed.
  10. Click Save and Go to Summary.
  11. Click Start Assessment to add items to the Collaboration project.
    • During Assessment, the Admin/Service account will be automatically added as an owner to all teams in the Source tenant. This is required to be able to discover all teams, channels, users, conversations and files in both tenants before the migration can proceed.
    • When the Assessment completes, MigrationWiz will display information such as the number of teams, total file size, total number of users, the number and type of licenses needed, and the number of licenses currently available to be used.
    • Guest users will not be included as part of the assessed license requirement. Conversations that guest users participate in will be migrated as part of the migration process.
    • If enough licenses were already purchased and seen by the Assessment, skip steps 12 and 13.
  12. Purchase MigrationWiz-Collaboration licenses. The total number of licenses is shown on the completed Assessment page.
  13. Once the licenses have been purchased, refresh the browser page showing the Assessment results.
  14. Username changes: By default, we match users from the source to the destination based on the prefix in their User Principle Name (UPN). For example, if the user UPN is “name@domain.com”, we match the “name” portion. If there are multiple people with the same prefix at the destination (e.g. name@domain1.com and name@domain2.com, or the prefix of a particular user is changed in the destination (e.g. name@source.com → name.full@destination.com), it will be necessary to use the advanced option UserMapping="name@source.com->full.name@destination.com" to set the new or correct name for each user. 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 UPN addresses in the example with the actual UPN addresses.
  15. Once the assessment shows the message “You have sufficient licenses. You can start your migration”, you will be able to click the Start Full Migration. To migrate only some Teams from the Source, it is possible to use a CSV to select the specific teams to migrate. Follow the steps below to migrate from a CSV.

 

Migration Customization Options

The following options are not required, and will only apply to some migrations. Follow the steps outlined for scenarios that apply to your migration. Once these steps have been followed, continue to the Post Migration section below.

Migrate Teams via CSV

After running an Assessment, it is possible to use a MigrationWiz-generated CSV to select which teams are included in the migration. To use this functionality, follow the steps below.

  1. Open the Collaboration project that needs specific teams selected.
  2. If an Assessment has not already been completed, run an Assessment.
  3. After the Assessment completes, click the Actions button and click Select Teams.
  4. From the flyout, click Assessment Summary CSV File.
  5. When the file finishes downloading, open the file and edit only the first column, titled Selection (true/false).
    1. All teams with “TRUE” in the Selection column will be included in the migration. To exclude a team from the migration, change “TRUE” to “FALSE”. A blank cell will be treated as a “FALSE”.
    2. Do not change any other information in the CSV file. Changing other fields will cause the team selection to fail.
  6. Save the modified CSV. Note, the file must remain in .csv format and cannot exceed 5MB.
  7. The new CSV will be uploaded to the project in the same flyout menu that it was downloaded from. The upload entry field is shown at the bottom of the flyout menu.
  8. Click Select File.
  9. Find the modified CSV on your computer and select it.
  10. Click Import. The Assessment results for the project will be updated to reflect only the teams now selected for migration.
  11. When ready, click Start Migration.
  12. After the migration completes, verify on the Destination tenant that only the specified teams have been migrated.
  • After uploading the CSV file, a new option will show under the Actions menu.
  • Clear All Selections: This option will clear the updated CSV list, resetting the migration back to the default. This means all teams will be selected for migration.
  • Selecting Run Full Assessment after uploading a modified CSV will also clear the updated CSV list and reset the migration back to the default of all teams being selected for migration.

Migrating Teams with Special Characters in the Name

If any team names have special characters, such as emoji icons, Excel may not be able to open the generated CSV file. The steps below may allow the CSV file to be imported:

  1. Open Excel.
  2. Import the data using Data--> Import External Data--> Import Data.
  3. Select the file type "csv" and browse to your file.
  4. In the Excel import wizard, change the File_Origin to "65001 UTF" (or choose correct language character identifier).
  5. Change the Delimiter to comma.
  6. Select where to import to and Finish. While these steps should work for most versions of Excel, some versions may still not be able to open the CSV.
  7. Click the Start Full Migration
  8. When the migration is complete, verify that the users are able to see their teams and channels in the Destination tenant.
  9. Click the bar chart icon in the MigrationWiz dashboard to request an email containing the project migration statistics.

Migrating Teams while adjusting Team names during migration

If Teams already exist on the destination tenant with the same MailNickName as Teams on the source tenant, the Teams can be migrated using the steps below to avoid merging the Teams or causing the migration to run into errors.
This Advanced Option will change the MailNickNames 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 MailNickName: PrependRootFolderName="text"

Add text after the Team MailNickName: AppendRootFolderName="text"

  • 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.

It is recommended you use a prefix or suffix to identify the original Channel for ease of group management after the migration completes.

Migrating using US Government Tenants

Migrating to or from a US Government tenant requires specialized commands to all MigrationWiz to connect. Failing to use these options will result in login errors.

  1. Click Edit Project.
  2. Click Advanced Options.
  3. Under Support Options, add one or both of the commands below, depending on the specific migration scenario:
    1. If migrating from a US Government Tenant, add:
      OneDriveProExportEnvironment=AzureUSGovernment
    2. If migrating to a US Government Tenant, add:
      OneDriveProImportEnvironment=AzureUSGovernment
  • Conversation History will not be migrated to a tab in the destination. Instead, a message will be posted in the channel with a link to the conversation history HTML file.
  • Due to limitations in the Microsoft system, images will not be migrated as part of the conversation(s). They will still appear in the conversation history HTML file. 
Was this article helpful?
4 out of 11 found this helpful