Microsoft Teams to Microsoft Teams Migration Guide

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

First time?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide 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.

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

The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.

For more information on special case migrations, frequently asked questions, and other information, see Microsoft Teams Migration FAQs and Teams Troubleshooting & Error Lookup

Migrating Teams for Education templates

MigrationWiz can assist with the migration of Microsoft Teams for Education (Classroom template only, including Classroom Notebook). We currently do not support the migration of Notebooks for Teams based on PLC or Staff templates.
Note: Teams based on these templates will need to be provisioned in the destination prior to migration. Please contact Sales for more information. 


Planner content may now be migrated. See our Planner guide for more information. Steps to migrated Planner are included below.

Versions & Metadata

MigrationWiz now supports migrating document metadata and versions for Teams to Teams projects. Reach out to BitTitan Technical Sales to activate this feature for your project. 

What items are and are not migrated?


Teams: Migrated teams may not appear in the same order. User may drag and drop to reorder the lists.

  • Public
  • Private 
  • Organization-wide - these teams appear as public teams at the destination. Admin can change the privacy to organization-wide via the UI. 
  • Team picture
  • Team description


  • Public
  • Private: via the Advanced Option listed above. This only migrates the conversations and documents. Adding users must be done via a PowerShell script.


  • 60 messages per team will be displayed in the destination team. Channel conversation history is downloadable as an HTML file in the Conversation History tab. 
  • Conversation structure
  • Root messages
  • Replies
  • Formatting - fonts, bullets, lists, colors
  • Quotes
  • Emojis
  • Inline images & stickers
  • Code snippets
  • Hyperlinks
  • GIFs
  • Mentions (as plain text)
  • Timestamps (in UTC)
  • Deleted message notifications - Messages will remain as deleted on the destination and show "Original message has been deleted."
  • Private conversations and files under the Chat tab
  • Private chats (Migrated via Mailbox migration flow and will only be visible in Outlook, not in Teams)

    • One-on-one chats

    • Group chats

    • Meeting chats


  • Files in public teams and channels
  • Files in private channels


  • Static memberships are migrated.

The following tabs are migrated:

  • Word
  • Excel
  • PowerPoint
  • PDF
  • Website
  • Planner
  • OneNote

Team Settings

  • Team description
  • Team picture
  • Guest permissions - guest access on the source will be migrated if the guest exists at the destination and guest permissions are enabled prior to migration. This may be done via the Teams of Office 365 admin portal. 
  • Member permissions
    • Create and update channels
    • Create private channels
    • Delete and restore channels
    • Add and remove apps
    • Create, update, remove tabs
    • Create, update, remove connectors
    • Delete messages
    • Edit messages
    • Tag @team or @[team name] (this will send a notification to everyone on the team)
    • Tag @channel or @[channel name]. This will notify everyone who's shown the mentioned channel in their channel lists.
  • Guest permissions
    • Create and update channels
    • Delete channels
  • Other permissions
    • Enable Giphy
    • Enable stickers and memes
    • Allow memes to be uploaded
    • Filter inappropriate content

Channel settings (Public channels)

    • Channel moderation
    • New post permissions
    • Allow members to reply to channel messages
    • Allow bots to submit channel messages
    • Allow connectors to submit channel messages


  • OneNote tabs


  • Tabs
  • Plans
    • Title
    • Owner
    • Settings (labels, descriptions, shared with)
  • Buckets
    • Title
    • Order: 1-1 mapping of order will not be present between delta-passes. See ‘Limitations’ section for more info.
    • Plan (which plan the bucket belongs to)
  • Tasks
    • Title
    • Assignees
    • Labels/Categories
    • Parent Bucket
    • Progress
    • Start Date
    • Due Date
  • Task Details
    • Notes
    • Show on Card
    • Checklist
    • Attachments*
    • Attachment preview
    • Description
    • Comments
    • Priority
  • Charts

*Only attachment links on the team's SharePoint site will be automatically remapped. 

  • Files that are uploaded directly at the task (files are eventually stored in the team's SharePoint site) will be automatically remapped.
  • SharePoint file links (links to files already in the team's SharePoint site) will be remapped.
  • No other links, including external links, will be remapped.

Not Migrated


  • Team order - Teams may be manually reordered at destination via drag and drop. 
  • Tabs (Website tabs, Word, Excel, PowerPoint and PDF tabs, Document Library tabs, Wiki tabs, Microsoft Stream tabs, PowerBi, SharePoint page and list tabs, Custom tabs)


  • Tags
  • Likes & reactions
  • Links to files and meeting requests
  • Files previews
  • Hyperlink previews
  • Teams meeting invites in conversations
  • Calendar previews - Calendar is an attachment and the Graph API does not support sending messages with attachments. 
  • Teams recordings


  • Dynamic memberships - all memberships are migrated as static, user must recreate dynamic memberships.


  • User-specific settings - favorites, profile pictures, status messages, saved messages
  • Allow members to upload custom apps
  • Team code
  • Channel settings: general/private. This is an API limitation. Default settings will be retained after migration. 
  • Global/organization-wide and custom Teams messaging policy is currently not supported. These policies are used to control which chat and channel messaging features are available to users in Microsoft Teams.


  • Wikis
  • Yammer
  • PowerBi reports
  • Other apps/tabs


  • Task Details (Microsoft Graph API limitation)
    • Created by
    • Created date
    • Last modified by
    • Last modified date
    • Completed by^
    • Completed timestamp
    • Assignee priority

The following tabs are not migrated:

  • Document Library
  • Wiki
  • Stream
  • PowerBI
  • SharePoint page and List
  • Yammer
  • Flow
  • Custom tabs
  • Public or Private channel tabs linking to any location outside the team's document library.
  • No EDU or Government tenant tabs are migrated. This includes tabs in public channels, private channels, 1:1 chats, group chats, and meeting chats.

Teams Private Chats

Migrated Not Migrated

Chat titles
(If there’s no title, participant names will be shown by default)


Chat participants

GIFs Polly

Embedded images

Saved messages

File Attachments
(A completed OneDrive migration with necessary permissions is required for this to be successful)

Chats from deactivated users

Chats marked ‘Important’
(Email item will appear flagged as ‘Important’)

Chats on external tenants 
(i.e. You are the guest of that tenant)

Edited messages in a Chat

Links directly pasted into chats, including documents and images.

Praise (Icon/image not migrated)



This migration type requires the MigrationWiz-Collaboration (per Team) license type.

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


Ensure consent has been given for the Teams application permission.

Use either Teams-ReadOnlyApp or MigrationWiz-Teams-FullControl for Source and MigrationWiz-Teams-FullControl for destination. 

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

  2. To enable permission at the Source, go to either Teams-ReadOnlyApp or MigrationWiz-Teams-FullControl and consent to the app access when prompted.

  3. To enable permission at the Destination, go to MigrationWiz-Teams-FullControl and consent to the app access when prompted.
  4. Note that if you are migrating 'Document Permissions', you will need to use MigrationWiz-Teams-FullControl for both Source and Destination tenant. 
    Perform below steps 5 to 7 for both Source and Destination: 
  5. 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.

  6. Create new user. This user must have an active Teams license applied nd must be on a cloud-only account. On-premises and hybrid user account types are not supported. 

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

  8. Create MigrationWiz project.

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

Create a New Project

Important: IP lock down will not work for your custom Azure Storage unless Microsoft server IPs are included as well. For more details on Microsoft endpoints, refer to URL & IP address ranges.

  1. Go to Projects.
  2. Click Create Project.
  3. Select Collaboration Project.
  4. Update the project information: add a Project Name, select a Customer from the drop down, then click Next Step.
  5. Create the source endpoint by selecting Microsoft Teams (Source) from the drop down.  
  6. Provide your Microsoft 365 credentials (these will be the same Microsoft 365 username and password you use for the MigrationWiz security group), then click Add.
  7. Next, create a destination endpoint by choosing an Endpoint Name and selecting Microsoft Teams (Destination) from the endpoint-type drop down. image-20210129-065430.png
  8. Enter your Microsoft 365 credentials. These will be the same username and password you used for the MigrationWiz security group. Once your credentials are selected, click Add.
  9. 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 to create Azure StorageV2 storage for destination endpoints to create your storage account. You will need to set up a STORAGE (General Purpose 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==” 
  10. Once complete, click Save and Go to Summary.
  11. Verify that both the source and destination are Microsoft Teams. Variable endpoints are not supported.
  12. 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.

If the UPN prefix changes

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 “”, we match the “name” portion.

If there are multiple people with the same prefix at the destination (e.g. and, or the prefix of a particular user is changed in the destination (e.g., it is necessary to use the advanced option UserMapping=">" to set the new or correct name for each user.

  1. The User Mapping 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. 

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. The Team names added to the project use the mailnickname only.


  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. 

Advanced Options

ForceSharePointOnlineEnvironment=1 : By default, the Teams endpoint for SharePoint documents will migrate to However, if you have a custom SharePoint domain, the files will not migrate properly. By setting this advanced option, it will tell MigrationWiz that you're using SharePoint Online, even though the actual domain doesn't include in the name.

Start Migration

For each batch of 200 teams

  1. Start with scaffolding the teams: Start a Full Migration with only Teams Creation checked.

  2. After the scaffolding for all the teams has been completed, wait at least 1 hour before starting the next phase.

  3. Start a migration with the rest of the content checked:

    • Conversation

    • Documents

      • Planner attachments will also be migrated as part of a Documents migration.

    • Document Metadata

    • Document Versions

    • Document permissions, if needed

  4. Start the migration of Channel Tabs after at least one round of document migration has been completed.

  5. After one batch is completed, start the next batch.

  6. When you are ready to cut over to the destination tenant, review the Migrating Private Channels section below, then start migration for Teams and Channel Memberships and Planner if you wish to migrate those. This is done last to prevent users at the destination from receiving email notifications about Teams migration events. 


Resetting a migration will be considered a new migration run and will re-migrate all plans, buckets and tasks into new ones at the destination.

Resetting errors will re-migrate only those plans, bucket and tasks that have failed. The respective failed buckets and tasks will be migrated to the existing plans.

If a channel has both OneNote and Planner tabs, and the user selected to migrate OneNote Tabs and Planner at the same time, the tabs at the destination channel will appear in this order:

  1. OneNote
  2. Planner

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 Microsoft 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 Microsoft 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 Microsoft 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 Microsoft 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>

Special Circumstances

Migrating Channel Conversations

MigrationWiz will migrate 60 messages (60 root message + all replies) per team by default.

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 message threads per channel.

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

The total number of messages to be migrated can be increased via this Advanced Option:

  •  TeamsMaxConversationPostPerTeam=XX
    • Replace XX 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 this option is used

Migrating Private Channels

For Teams to Teams migration projects created after August 25, 2021, private channels are now migrated by default when the Teams Permissions item type is selected for migration.


  • This migration no longer requires PowerShell Script MWTeamsPrivateChannelMembers.ps1 or Advanced Options to migrate private channels.

  • Private channel migration can be skipped by adding the new Advanced Option TeamsSkipPrivateChannel=1

Expected migration behavior:
  • The migration user, regardless of source or destination role, will remain the channel owner in the destination tenant.
  • MigrationWiz does not remove extra users in the destination (similar to previous Teams permission migration behavior). 

Role in Source Private Channel

Role in Destination Private Channel

Role After Migration




























For existing Teams to Teams project created before Aug 25, 2021:

Private channels are not migrated by default. The following Advanced Options must be added to migrate private channels:


  • UserMapping must be set properly prior to migration.
  • Migrate Teams and Channel Memberships must be part of the last migration phase, along with Planner. 
  • Please ensure that destination destination tenant does not restrict creation of private channels.

Can I migrate private channels belonging to an archived team?
No. This is still a Microsoft API limitation.

Can I skip private channel migration?
Yes, add the Advanced Option TeamsSkipPrivateChannel=1 into the project before starting the migration

Are there any prerequisites that I must take care of on my destination Tenant before migration?
Please ensure that destination tenant does not restrict creation of private channels.

Channel Tabs migration 

MigrationWiz supports the migration of some channel tabs as part of a Teams to Teams migration. 

This item can be selected in the Start Migration flyout window:

  1. Go to Start Migration.
  2. Select Migrate Data.
  3. Select Channel tabs item type.

The following tabs will by migrated by default if the Channel tabs option is selected:

  • OneNote
  • Microsoft Word
  • Excel
  • PowerPoint
  • PDF
  • Websites

Tabs will be migrated after documents are migrated, following the same behavior as the previous OneNote tab migration option.

Once the migration is successful, all tabs should be fully rehydrated at the Teams destination tenant and all links should be correctly remapped (only for Channels).


Migrated tabs will also be reflected in the Folder Summary section under the relevant team/channel: 


Migrated Items will also show the total number of tabs migrated:  


All emailed project statistics will now also include the tabs data. 

Important: Channel tabs cannot be migrated independently without migrating Documents.  

Migrated Items 

The following items will only be migrated if the Channel Tabs item type is selected. 

OneNote Documents/Notebooks 

  • The existing/default OneNote notebook for each migrated team (both public and private teams). 
  • New OneNote notebook. This notebook will automatically be stored in a particular folder associated with each channel (inside the SharePoint site). 
  • Password-protected notebooks will be migrated as well. 
  • Only OneNote documents relevant to the team/line items in the project will be migrated. 

OneNote Tabs  

Only migrated if the Channel Tabs item type is selected.

  • OneNote tabs will be migrated and created at the destination tenant. This is for both public and private channels. 
  • For private channels, if the OneNote document is originally created/added in the destination private channel itself, the contents are 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, the OneNote contents gets migrated into the OneNote tab created. 

OneNote Contents 

  • OneNote permissions will be migrated if the document permissions type is checked to enable document permissions. 
  • All the OneNote content structure/formatting will also be migrated - including section, pages, title, tables. 

Scenarios/Use Cases: Where was the OneNote tab added from?  

OneNote Notebook migrated? 

OneNote Tabs created?  

Default/existing OneNote notebook per source team 



New OneNote notebook created in the source team 



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



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



OneNote notebook present in another team’s SharePoint site 

Yes; only if this other team is already migrated in MigrationWiz 


Personal OneNote (stored in personal OneDrive at source) 



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

Additional Tabs

  • Microsoft Word

  • Microsoft Excel

  • Microsoft PowerPoint

  • PDF

  • Websites

Items Not Migrated 

  • A OneNote document present in an individual user’s OneDrive account. 
  • This type of item will be migrated via standard MigrationWiz document project. A warning message will be shown.



  • 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.  
  • After migration, the OneNote tab will show the first page of the section by default. 
  • Tabs for Private Chats (1:1 chats, group chats, meeting chats) are not supported

  • Tabs for EDU and Govt tenants are not yet supported. This includes public channels, private channels, 1:1 chats, group chats and meeting chats. 

  • Public channel tabs linking to any location outside the team's main document library will not be migrated.

  • Private channel tabs linking to any location outside the private channel or the team's main document library will not be migrated. 

  • Website tabs are not supported for Teams on the web/browser. Only supported on Teams desktop application. (This is a Microsoft limitation)


There are three scenarios which may apply during the migration of a team’s default OneNote notebook (present in the SiteAssets document library of the team’s SP site) while migrating teams:

Scenario 1: Migrating to a new team that does not exist in the destination:

The source team’s default notebook is migrated as is and appears as the default notebook in the destination after the migration is complete.

Scenario 2 - Migrating to an existing team with the same display name as the source (note that mailNickname is not in question here since the default notebook’s display name does not follow the mailNickname):

The source team’s default notebook is migrated into the already existing default notebook in the destination.

However, if for some reason the destination team’s default notebook was not provisioned (or does not exist at all) due to some Microsoft limitation, the source team’s default notebook will still be migrated and the migrated notebook will appear as a default notebook in the destination.

Scenario 3 - Migrating to an existing team with a different display name as the source (note that mailNickname is not in question here since the default notebook’s display name does not follow the mailNickname):

The source team’s default notebook and destination team’s default notebook will be auto-mapped. This means that contents in the source team’s default notebook will be automatically migrated to the destination team’s default notebook even though their names are different without the need for any manual mapping from the user. (The reason for the difference in the names of the default notebooks is because the naming convention for the team’s default notebook follows the display name of the team).

However, if for some reason the destination team’s default notebook was not provisioned (or does not exist at all) due to some Microsoft limitations, the source notebook will be migrated as-is without any mapping and the migrated notebook will not appear as a default notebook in the destination.

Migrating Tabs 

This should be done as part of the migration process. It is included separately as it is not a required part of a Teams migration. 

Advanced Options

This Advanced Option is only required for projects that are created before October 6, 2021 to enable migration of Microsoft Word, Excel, PowerPoint, PDF and Website tabs 


  1. Ensure the MigrationWiz User has already consented to either Teams-ReadOnlyApp or MigrationWiz-Teams-FullControl.
  2. Log in to MigrationWiz.
  3. Create a Teams Collaboration project. 
    • Required endpoints: Microsoft Teams (Source) and Microsoft Teams (Destination). 
  4. Start adding Teams via Autodiscover, Quick Add, or Bulk Add. 
  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 Channel Tabs.
    1. Select teams to migrate.
    2. Click Start Migration with ‘Documents and OneNote’ with any other item types but do not select Channel Tabs.
    3. Wait approximately 4 hours for the OneNote documents to be discovered by the OneNote service.  
  9. Migrate data with Channel Tabs. 
    1. Select Channel Tabs and any other item types which still need to be migrated. 
    2. Documents and Channel Tabs can be selected again to bring over any newly created documents since the last migration.  


Will these new Microsoft Office, PDF and Website tabs be migrated by default?
Yes, but only for new projects created after October 6, 2021. User can check the ‘Channel Tabs’ item type and the following tabs will be migrated by default:

  1. Microsoft Word

  2. Excel

  3. PowerPoint

  4. PDF

  5. Website

However, for existing projects created before October 6, 2021, the Advanced Option TeamsMigrateChannelTabs=1 needs to be added in order to migrate these new tabs. OneNote tabs will still migrate by default.

What does the warning message ‘Skipping Tab: [TabName] for the Channel... ‘ mean?
Since the files do not belong to the environment's root or its own private channel document library, MigrationWiz is not able to remap it. This is a known limitation. We recommend manually recreating these tabs at the destination.

Migrating Teams with Special Characters in the Name 

This section is specific to migrations utilizing Autodiscover. 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.

Once Autodiscover has been completed: 

  1. Download the CSV generated by the Autodiscover process.
  2. Open Excel and import the data using Data--> Import External Data--> Import Data. 
  3. Select the file type csv, then 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 the location to import to CSV and click Finish. 
    • While these steps should work for most versions of Excel, some versions may still not be able to open the CSV. 
  7. Navigate back to MigrationWiz.
  8. Upload the edited CSV via the Bulk Add function.
  9. Click Start Full Migration
  10. When the migration is complete, verify that the users are able to see their teams and channels in the Destination tenant. 
  11. 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 natively support Application Permissions, to make sure that the migrating accounts are Global Admin, add: UseDelegatePermission=1This is also required to use the following advanced options.

If application permissions can only be used at the source or the destination, use the following advanced options as applicable:

Source: UseApplicationPermissionAtSource=1

Destination: UseApplicationPermissionAtDestination=1

For example, to use the Application Permission on the source, and the Delegate Permission at the destination, you would enter UseApplicationPermissionAtSource=1 and UseDelegatePermission=1.

For a successful migration, authorize the use of our delegate permission app on Microsoft. The steps for doing this are outlined in Using App-based Authentication. However, it is important to note that you must use the "For Teams Government" link for your migration, otherwise the migration will fail.

 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. 

Teams Support Options

Support Options Description
TeamsMaxConversationMessage=XXX Limit the number of conversations to load in the source tenant. E.g. TeamsMaxConversationMessage=1000 would only load 1000 messages

Increase the number of conversation threads that will be posted to the channel. Minimum of 0 and maximum 1000 . Default will be 60 if this option is not added.

*Setting a higher limit will have adverse effect on migration time, as each message post takes 0.5 seconds to post

TeamsMigratePrivateChannel=1 Private channels will be migrated as private channels with conversations and documents. Users will not be migrated; users at the destination must be added manually or via PS script. Refer to section on Migrating Private Channels 


Was this article helpful?
4 out of 12 found this helpful