Microsoft Teams Migration FAQs

This guide will cover frequently asked questions and troubleshooting processes related to Microsoft Teams to Microsoft Teams (Parallel) migrations. It is not intended to replace any part of the migration guide, which lays out the steps necessary to perform a Teams to Teams migration. 

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:TeamsMaxConversationPostPerTeam=XXXX. Replace XXXX with the number of messages you wish to migrate. E.g.

TeamsMaxConversationPostPerTeam=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.

Permissions

Is Global Admin required for Teams (Parallel)?

No. For Teams Parallel, the AO ‘UseApplicationPermission=1’ has been defaulted. Use Teams-FullControlApp for both Source and Destination.

Application Permissions

MigrationWiz now supports read-only Application Permissions for Teams migrations, in addition to full-control permissions. This new app, with ReadOnly permissions, can only be used at the source to enhance security, and will not export document permissions. The destination permissions will always require FullControl permissions.

This allows for a secure migration without the use of Global Admin or Site Collection Admin permissions on the source and destination.

This app is similar to the Office 365 Authentication App previously deployed, which utilized delegate permissions. This app uses application permissions. If you are not using application permissions, go to the Authentication App article and follow those steps.

61d5b82a-cc9f-42d9-8565-7813f8c94121.png

Enable Application Permissions

These are the steps to enable permission level at the source only. This authentication process gives you control over who is entitled to use the source.

  1. Ensure you are signed in as a Global Admin in the Office 365 Admin Portal.

  2. Go to either Teams-ReadOnlyApp or to Teams-FullControlApp and consent to the app access when prompted. If choosing the Teams-ReadOnlyApp option, you will need to disable AMR via "DisableAsynchronousMetadataRead=1", due to Microsoft API limitation.

  3. Create new Security Group named “MigrationWiz” on the Office 365 Admin Portal. If you have not created a security group before, follow Microsoft's instructions.

  4. Create new user. This user must have an active Teams license applied.

  5. Add new user to previously created security group as a member. Important: ADFS and MFA must be turned off for this user.

  6. Create MigrationWiz project.

  7. When creating the endpoints, enter the new user credentials.

Steps to enable permission level at the destination:

  1. Ensure you are signed in as a Global Admin.

  2. Go to Teams-FullControlApp and consent to the app access when prompted.

  3. Create new Security Group named “MigrationWiz” on the Office 365 Admin Portal.

  4. Create new user. Important: ADFS and MFA must be turned off for this user.

  5. Add new user to previously created security group as a member.

  6. Create MigrationWiz project.

  7. When creating the endpoints, enter the new user credentials.

Teams-FullControlApp may be used on both source and destination tenant and will export document permissions. Teams-ReadOnly can only be used on the source tenant, and will not export document permissions.

Post-Migration Steps

  1. Remove the newly created user.

  2. Remove the MigrationWiz Security Group created in Step 3.

  3. To remove the app from the source or destination, perform the following steps:

    1. Launch PowerShell.

    2. Connect PowerShell to Office 365.

    3. Enter the command: Connect-AzureAD

    4. Enter the admin credentials 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>

Permissions Granted

  Teams ReadOnly Teams FullControl
Conversations Y Y
Teams Permissions Y Y
Documents Y Y
Document Permissions N Y

Read Only permissions granted:

    • SharePoint API

      • Sites.Read.All,

      • User.Read.All

    • Graph API

      • Files.Read.All,

      • Group.ReadWrite.All
        (This is to add the user to the team as a owner first before being able to read conversations)

      • User.Read.All

      • Group.Read.All (delegate permission)
        (This is to be able to read all the conversations as a user after being added)

      • User.Read (delegate permission)

Full Control permissions granted:

  • SharePoint API:

    • Sites.FullControl.All

    • User.ReadWrite.All

  • Graph API:

    • Files.Read.All,

    • Group.ReadWrite.All

    • User.Read.All

    • Group.ReadWrite.All (delegate permission)

    • User.Read (delegate permission)

How long does the Azure SAS token last for the Microsoft-provided Azure Storage?

The Azure storage SAS token Microsoft provides to us last only 5 days instead of 30 days.

Adding Teams & Autodiscovery

What is the difference between the previous Assessment and Autodiscovery?

Assessment previously would calculate the number of teams, number of users file size and licenses needed.

Autodiscover will only discover the total number of teams at the Source

As such, from a speed perspective, autodiscover should be relatively faster than the Assessment. Once auto-discover has completed, users can import the teams and all the teams will be populated as line items.

What should I do when auto-discovery fails?

Check your Source credentials. Auto-discover will fail if the credentials verification fails.

What will Folder Summary show?

Folder summary will be shown per team level, so all the channels, documents and document permissions specific only to that team.

Migrating Teams

Can I select which Teams to migrate?

Yes, by checking only those teams to be migrated after the adding of teams is done either via auto-disover, quick add or bulk add.

Can I migrate only specific users?

No. All users in a selected team will be migrated.

How do I apply user mapping for large number of users?

  1. Download the script and example file attached at the end of this article (Add-MWTeamsUserMapping.ps1 and example.com).

  2. Fill in the example.csv with the desired user mapping

  3. Retrieve your Teams project ID. This can be obtained by copying the text after the projects/ and before the ?, as shown below.Teams_User_ID.png

  4. Run Powershell as an Adminstrator.

  5. Run this command:

    Set-ExecutionPolicy Unrestricted -Scope CurrentUser
    cd <Download folder>
    .\Add-MWTeamsUserMapping.ps1 -projectId <Teams project id> -csv <your csv path>
  6. E.g: .\Add-MWTeamsUserMapping.ps1 -projectId b2b00b67-c6fc-11ea-a81a-000d3af5b517 -csv .\example.csv

  7. Enter your MigrationWiz Account username and password

  8. Input the path to the CSV file with the user mapping.

Can I rename a team before migration?

Yes. However, only the MailNickname gets renamed. There will not be any changes to the Display Name. Prepend/AppendFolder AdvancedOptions is no longer supported for the new Teams Parallel connector.

 

If a team at the destination exists with the same name as a team at the Source tenant, can I rename the specific Team before the migration?

Yes. Click on the Edit icon of the team/line item and change the Destination MailNickname.

Can I migrate Teams with special characters in the name?

Yes. The steps for this are included in the Teams to Teams Migration Guide.

Can I migrate archived Teams?

Currently, archived are migrated over but as a non-archived team. Private channels of archived teams will not be migrated. This is a known Microsoft API limitation.

SharePoint sites are live in the destination. Will the Teams automatically connect to the SharePoint sites after Teams have been migrated? 

No, because this is dependent on teams, we don’t have control. Once a team is created, a new SharePoint site will be created for that team.

Migrating Private Channels

Can I migrate private channels?

Private channel creation was disabled on 7/17 due to recent changes in Microsoft Graph API. However, MigrationWiz can migrate private channels through the use of the Advanced Option TeamsMigratePrivateChannel=1. Steps for this are included in the migration guide. The scripts required are attached at the end of this article.

Private channels will be migrated as private channels with conversations and documents. Users will not be migrated to the channel; users at the destination must be added manually or via PS script. The admin user will not be removed from the private channel or from the team if the team has a private channel. This is applicable for all teams at the destination, both migrated and existing private channels.

Can I migrate private channels belonging to an archived team?

No, private channels of archived teams will not be migrated. This is a known Microsoft API limitation.

Migrating Private Channels

  1. Identify the private channels in the source tenant (use the MWTeamsPrivateChannelMembers.ps1 script).
  2. We suggest starting with smaller batches when working with private channels due to higher rate of admin sync issues faced. Start with a maximum of no more than 10 teams with no more than 20 private channels in a batch.
  3. Add Advanced Option TeamsMigratePrivateChannel=1 into the project.
  4. Do a scaffolding run
    1. Select “Teams Creation” in the Start Full Migration flyout
    2. If there are any errors encountered during the scaffolding run, wait a few hours, then re-run

Important: Private Channels will not be created during the scaffolding run in order to improve the success rate for their SharePoint site provision. Tests have shown that if private channels are created before the parent team SharePoint sites are ready, the private channel SharePoint site will not be created automatically.

  1. Wait 24 hours for the Team sites to provision. Private channels will not be created during the scaffolding run. It will only be created during normal content migration
  2. Continue the rest of the migration normally.
  3. Migrate the private channel users using the PS script “MWTeamsPrivateChannelMembers.ps1”.
  4. After the migration is completed, delete the migration admin user from both source and destination to remove the user from all teams and private channel.

Can I select which channels to migrate?

Yes via the folder filter Advanced Options. Refer to the Folder Filtering directions.

Migrating Conversations

Are all conversations migrated?

60 messages per team will be displayed in the destination team.

MigrationWiz will gather the total number of channels in each team  and then grab the most recent 60 threads in each team. The conversations will be distributed across those channels. For example, if you have six channels in a team, you will have ten messages per channel. This number can be controlled with the TeamsMaxConversationPostPerTeam Advanced Option. Details on this process are found in the migration guide. 

The entire channel conversation history can also be downloaded as HTML in the ‘Conversation History’ tab.

How does MigrationWiz choose 'most recent'?

It is based on the age of the root message. If you reply to an old message, it will not be counted as the most recent.

 

Migrating OneNote Documents & Tabs *New*

Does MigrationWiz migrate OneNote documents and tabs?

Yes, MigrationWiz now supports OneNote documents & tabs migration. There will be a new optional item type, OneNote tab, in the Start Migration flyout.

However, OneNote tabs can only be migrated after the initial migration of documents and the OneNote instance. We also recommend waiting at least four hours after the initial document & OneNote migration has completed before starting the OneNote tabs migration.

mceclip0.png

Can I see which OneNote tabs have been migrated? 

Yes. Migrated OneNote tabs will be reflected in the ‘Folder Summary’ section of the respective team/channel. The Migrated Items section will also show the total number of OneNote tabs migrated

How do I migrate OneNote tabs? 

  1. Ensure the MigrationWiz User has already consented to either Teams-ReadOnlyApp or Teams-FullControlApp.
  2. Log in to MigrationWiz.
  3. Create a Teams Collaboration project. 
    • Required endpoints: Teams Parallel (Source) and Teams Parallel (Destination). 
  4. Start adding Teams via Autodiscover, Quick Add, or Bulk Add. Steps for these processes are included in the Teams Parallel migration guide below. 
  5. Select which teams to migrate.
  6. Click Start Migration for a ‘Teams Creation’ pass first.
  7. Wait 24 hours for the Teams to provision. 
  8. Migrate Data without OneNote tabs.
    1. Select teams to migrate.
    2. Click Start Migration with ‘Documents and OneNote’ with any other item types but do not select OneNote Tabs.
    3. Wait approximately 4 hours for the OneNote documents to be discovered by the OneNote service.  
  9. Migrate data with OneNote tabs. 
    1. Select ‘OneNote tabs’ and any other item types which still need to be migrated. 
    2. Documents and OneNote can be selected again to bring over any newly created documents since the last migration.  

What items are migrated? 

Migrated

OneNote Notebook migrated from destination?

OneNote Tabs created at the source?

Default/existing OneNote notebook of the Team

:check_mark:

:check_mark:

New OneNote notebook created in the team

:check_mark:

:check_mark:

OneNote notebook that was originally created/added in a parent Team and thereafter added as a link into the private channel of that team

:check_mark:

:check_mark:

OneNote notebook that was originally created/added in the private channel itself

:check_mark:

 

OneNote notebook present in another team’s SharePoint site

:check_mark: Only if this other team has already been migrated in MigrationWiz

 

Personal OneNote (stored in personal OneDrive)

 

 

OneNote Documents
Only OneNote documents relevant to the team/line items in the project will be migrated.

OneNote Tabs
For private channels, if the OneNote document is originally created/added in the private channel itself, contents get migrated but tabs cannot be created.
However, if the OneNote tab was originally created/added in a parent Team and thereafter added as a link into the private channel of that team, OneNote contents gets migrated with the OneNote tab created.

What items are not migrated? 

  • A OneNote document present in an individual user’s OneDrive account
    (This will be migrated via the standard MigrationWiz document project. A warning message will be shown)
  • Personal OneNote instances and non-Teams OneNote instances will not be migrated.

What are the OneNote migration limitations?

OneNote Notebooks

  1. If the source team name and destination team name are different, and the destination team notebook is already provisioned, default mapping will apply. This means that contents in the source notebook will be automatically migrated to the destination notebook even though the team names are different.

  2. If the source team display name and the destination team display name are different, and the destination team notebook was not provisioned due to Microsoft limitations, the source notebook will be migrated as-is.

  3. Source default notebook content will be migrated but will not show as the default if the destination notebook has not been provisioned.

OneNote Tabs

  1. If the OneNote associated with the tab is not stored in the specified team, the OneNote tab will not be created at the destination. A warning message will be shown. This may be due to a changed personal OneDrive URL or from a lack of visibility into other teams and their migration status.

What happens if the OneNote tab migration fails?

If there are migration failures of OneNote tab migrations, perform "Reset Items" to reset errors before resubmitting the migration. Otherwise, all OneNote notebooks and tabs will be recreated.

Can the OneNote documents & tabs migration be skipped?

Yes, add Advanced Option TeamsSkipSiteAssets=1 in order to skip OneNote migration.

Migrating Guests

Are guests/external users migrated?

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.

Post-Migration

Team members are missing at my destination. How do I resolve this?

Teams with a large number of members may take longer time to sync. To verify that all members have migrated:

  • Log into portal.azure.com

  • Go to the migrated group (Team)

  • View the members list to verify that the correct number of members were migrated

  • This should be synced to the Teams interface in the next few hours

Government Migrations 

Can I migrate to or from a US Government tenant?

Yes, via Advanced Options. Refer to the migration guide.

Does GCC support the Teams application permission Advanced Option?

No, currently GCC does not support the use of application permission (UseApplicationPermission=1). Add the option UseDelegatePermission=1 instead

Black Forest Tenant Migrations

Teams migration is currently not supported for Black Forest Tenants in the Microsoft Germany Datacenter, as it was not rolled out there to the best of our knowledge, nor could we obtain a test environment. For German customers in a .com Office 365 instance, Teams and migrations to and from should work normally. For US Government tenants, we currently support it as a destination. Source is as yet untested.

 

Advanced Options

User Mapping Troubleshooting

If the user is not found at the destination (w/ or w/o mapping), MW will throw a warning message indicating that the particular user is not found and will not be added to the migrated teams. To fix this, make the correction to user mapping and re-migrate with 'Team Permission' selected.

Does UserMapping refer to the UPN or to the SMTP?

UPN.

What Advanced Options are now built into Teams Parallel? 

  • Prepend/AppendFolder
  • SkipAdminCache
  • TeamsSelectiveLoading
  • UseApplicationPermission
  • UseAsynchronousMetadataRead
Was this article helpful?
0 out of 2 found this helpful