Microsoft Teams to Microsoft Teams Migration Guide for Version and Metadata Migration

This document is an end-to-end migration guide that demonstrates how to perform a 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 before beginning your migration process.

MigrationWiz now supports migration for GCCH projects. For more information, please check the Microsoft Teams to Microsoft Teams Migration Guide for GCC High Migration guide.


MigrationWiz is a migration tool, rather than 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 scenarios such as conflict resolution without user interaction are not supported. However, if versions and metadata are being migrated (see below for more details) then the new versions of documents will be migrated with subsequent migration passes after the first.

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.


MigrationWiz no longer supports Teams private chat history as part of Mailbox migrations due to Microsoft's restriction on Teams data access through EWS. For more information please review this article.

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.


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 migrate Planner are included below.

Versions & Metadata

MigrationWiz now supports migrating document metadata and versions for Teams to Teams projects.

Which items are migrated?


Migrated teams may not appear in the same order. Users 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 and Private channels only. Shared channels are not migrated


  • 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)
  • Deleted message notifications - Messages will remain as deleted on the destination and show "Original message has been deleted."
  • Private conversations and files are under the Chat tab


  • 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, and remove tabs
    • Create, update, and 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 the 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 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

    SharePoint Provisioning

    SharePoint site creation occurs automatically within 24 hours of team creation.
  • No other links, including external links, will be remapped
Which items are not migrated?


  • Team order - Teams may be manually reordered at the destination via drag and drop


  • 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, the 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
  • Microsoft Teams Connect (aka shared channels). If the migrated teams contain shared channels, the shared channels will be skipped and conversations in them will not be migrated


  • 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 (GCC High) tenant tabs are migrated. This includes tabs in public channels, private channels, 1:1 chats, group chats, and meeting chats


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

  • Each license allows up to 100 GB 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 Teams application permission.

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


The Teams-ReadOnlyApp does not support migrating document permissions.
  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 tenants.
    Perform below steps 5 to 7 for both Source and Destination:
  5. Create a 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 a new user. This user must have an active Teams license applied and must be on a cloud-only account.


    On-premises and hybrid user account types are not supported.

  7. Add the new (or existing) user to the previously created security group as a Member (Adding as an Owner will not work here).


    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

IP lockdown 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.
  8. After selecting the Endpoint Type, choose Microsoft Teams with Document Versions and Metadata migration type.
  9. Enter your Microsoft 365 credentials. Use the same username and password you used for the MigrationWiz security group.
  10. Choose one of the two Azure Storage options:
    • Use Microsoft Provided Azure Storage, by default, this option is selected for this type of migration.
    • Use Custom Azure Storage.
      The Microsoft Provided Azure Storage option will be enough for most migrations and is the recommended option unless you need or want to use your own. If you do, go to Using a Custom Azure Storage section.
  11. Once complete, click Add and go to Project Summary.
  12. Verify that both the source and destination are Microsoft Teams. Variable endpoints are not supported.
  13. For the following step, credentials are mandatory. Ensure all the mandatory fields are filled to activate the Update button. Click this once all the steps above are completed.

Using a Custom Azure Storage

If you want to use your own Azure storage, please follow the steps below:

  1. Prepare Azure Environment.
  2. Estimate Azure storage costs. This step is optional but is useful 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 is the following:
    • accesskey – This is the Storage account name for the Blob – example “accountname”
    • -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”


When entering the Azure Storage Account Name for the destination endpoint, consider using only numbers and lowercase letters. If you enter an upper case letter, your migration will fail.

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 into 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 mail nickname only.

Quick Add
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:
  • An email address
  • Login name
  • Password
  • Mailbox status

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 into the existing TeamFantastic. If TeamFantastic does not exist at the Destination, it will be created with the data from TeamAwesome.

Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add.
  5. Follow the instructions on the page.

The interface will now walk you through the steps up to upload the CSV found through the Autodiscover process. You may edit the columns after upload to change team names or mapping.


​Autodiscover process within MigrationWiz can be used to discover items from the Source environment so that they can be imported into your projects. This can then be edited in the project to remove users not being migrated. All users are added with the source and destination email addresses set to match the source email.

This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

Steps to Run Autodiscover

  1. On the MigrationWiz project page, click the Add dropdown, then click Autodiscover Items.
  2. Click Start Autodiscover.
  3. Click Discover Items. MigrationWiz 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, the destination mail nickname will be set to the same as the source mail nickname.

Advanced Options

Support Tab

  • 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.
  • TeamsMaxConversationMessage=XXX Limits the number of conversations to load in the source tenant. E.g. TeamsMaxConversationMessage=1000 would only load 1000 messages
  • TeamsMaxConversationPostPerTeam=XXX Increase the number of conversation threads that will be posted to the channel. Minimum of 0 and maximum 1000. By default, the number of conversations will be 60.


    Setting a higher limit will harm the migration time, as each message post takes 0.5 seconds to post.

Start Migration

For each batch of up to 200 teams

The migration process is made up of four passes. These consist of:

  • Initial 'Scaffolding' Pass to create the Teams and public channels themselves in the target tenant.
  • Migration Pass to copy the SharePoint data from the source Teams to the destination Teams. Private channels will be created in this pass
  • Channel Pass to copy tabs data into the various Teams Channels
  • Membership Pass to copy the Teams and Channel memberships. Planner and Teams Channel conversations are recommended to be migrated in this pass as well

Perform the three tasks in that order allowing about an hour between each one to ensure that the migration has 'settled' and it is ready for future data ingestion.

Pass One: Initial 'Scaffolding' Pass

When starting the migration select the 'Teams Creation' as shown here.

Pass Two: Data Migration Pass

Start the migration using the options shown here.

Note: Only select Document Permissions if needed as this can slow a migration down considerably.

Pass Three: Channel Tabs Migration Pass

After at least one round of data migration has been performed, this pass will migrate the data inside the various Channel Tabs that are in the Teams. Select these options.

Pass Four: Teams and Channel Membership, Planner, and Conversations

The final pass is to add the users into the Teams and Channels with the membership pass along with migrating the Converasations and Planner data. Select the options as shown below to complete this final step. Teams and Channel memberships are performed last to stop users from receiving excessive email notifications about Teams migration events with a multi-pass migration. Included here is also the Conversations, as this pass is a 'run once' for the migration because subsequent migration passes will not sync updates to previously migrated Conversations. It is recommended that the Conversations be run at the end, as a single pass, to make sure that they appear correctly in the target Teams.

Teams Convo_Perms_Planner pass.png


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. Conversations will also be duplicated.

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

Replies to source conversations previously migrated will not sync to the destination with subsequent passes. Subsequent migration passes will only migrate new conversations started at the source after the previous pass has been completed successfully.

If a channel has both OneNote and Planner tabs, and the user selects 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 member's 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 messages + 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.

Channel Tabs migration

MigrationWiz supports the migration of some channel tabs as part of a Teams to Teams migration. No Government (GCC High) tenant tabs are migrated. This includes tabs in public channels, private channels, 1:1 chats, group chats, and meeting chats.

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 be migrated by default if the Channel tabs option is selected:

  • OneNote
  • Microsoft Word
  • Excel
  • PowerPoint
  • PDF
  • Websites (Links for the site will only work in the Teams app and not Teams on the web. This is a Microsoft limitation)

Migrate tabs as an additional pass after a successful migration pass for Documents has been completed first, following the same behavior as the previous OneNote tab migration option.

Once the migration is successful, all tabs should be fully rehydrated at 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 tab data.


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 after that added as a link into the private channel of that team the OneNote contents get 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 sections, pages, titles, and tables.

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

OneNote Notebook migrated?

OneNote Tabs created?

Default/existing OneNote notebookper source team



New OneNote notebook was created in the sourceteam



OneNote notebook that was originally created/added in a parentsource team and after that added as a link into the private channel of that team



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



OneNote notebook present in another team’s SharePoint site

Yes; only if this other team is already migrated toMigrationWiz


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 is present in an individual user’s OneDrive account.
  • This type of item will be migrated via a 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 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 that 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 the 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 that 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.

*Word, Excel, and PowerPoint tabs are currently unable to be migrated due to Microsoft Graph API calls update*

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).
  • Start adding Teams via Autodiscover, Quick Add, or Bulk Add.
  • Select which teams to migrate.
  • Click Start Migration for a ‘Teams Creation’ pass first.
  • Wait 24 hours for the Teams to provision.
  • 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.
  • Migrate data with Channel Tabs.
  1. Select Channel Tabs and any other item types that 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. Users 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 them. 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 the correct language character identifier).
  5. Change the delimiter to a 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.


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