This article documents the behavior of Microsoft Teams tab migration in On Demand Migration (ODM).
Tabs migration in ODM is subject to Microsoft API limitations. Many tab types cannot be re-created via the API in the target tenant, even when the associated content migrates successfully through another workload (SharePoint, OneDrive, Planner, etc.).
The table below summarizes the migration behavior for each tab type tested:
|
Tab Created |
Content Migrated |
App / Tab Name |
Migration Behavior |
|
No |
Yes |
Channel Calendar |
The tab is not re-created in the target channel, but calendar events migrate as part of the Teams Mailbox Calendar migration. |
|
No |
No |
Channel Pages |
Loop component - not supported by ODM. |
|
No |
No |
Cisco Webex Meetings |
Third-party integration - not supported. |
|
No |
Yes |
Clipchamp |
Tab creation skipped (target tenant configuration not supported by Microsoft API). Files migrate as part of the Teams Files (SharePoint) migration, or via OneDrive migration if the file was added from OneDrive. |
|
No |
Yes |
Document Library |
Tab creation skipped (target tenant configuration not supported by Microsoft API). Content migrates as part of the Team SharePoint migration, or as part of the relevant SharePoint site migration if the library is on a separate site. |
|
Yes |
Yes |
Excel |
Tab re-created. File migrates as part of the Teams Files (SharePoint) migration, or via OneDrive migration if added from OneDrive. |
|
Yes |
Yes |
Files (Shared) |
Default tab - re-created in target. Now labeled 'Shared' in the Teams UI. |
|
No |
No |
Forms |
Not supported by ODM. |
|
Yes |
Yes |
Lists |
Tab re-created. Content migrates as part of the Team SharePoint migration, or as part of the relevant SharePoint site migration. |
|
No |
Yes |
OneNote |
Tab creation skipped (target tenant configuration not supported by Microsoft API) for both Team Notebooks and other notebooks. Notebook content migrates as part of the Teams Files (SharePoint) migration or via OneDrive migration. |
|
No |
Yes |
|
Tab creation skipped (personal OneDrive configuration not supported). File migrates as part of the Teams Files (SharePoint) migration or via OneDrive migration. |
|
No |
Yes |
Planner |
Tab creation skipped (target tenant configuration not supported by Microsoft API). Plan content migrates as part of the Planner migration. |
|
No |
Yes |
Power Apps |
Tab not re-created. App migrates as part of the Power Apps migration. |
|
Yes |
Yes |
PowerPoint |
Tab re-created. File migrates as part of the Teams Files (SharePoint) migration or via OneDrive migration. |
|
N/A |
N/A |
ProjectPlace |
Paid third-party service requiring a separate subscription. Could not be tested. |
|
No |
Yes |
SharePoint |
Tab not re-created. Site content migrates as part of the Team SharePoint migration or the relevant SharePoint site migration. |
|
No |
Yes |
SharePoint Pages |
Tab not re-created. Pages migrate as part of the Team SharePoint migration or the relevant SharePoint site migration. |
|
No |
Yes |
Visio |
Tab not re-created. File migrates as part of the Teams Files (SharePoint) migration or via OneDrive migration. |
|
Yes |
No |
Website |
Tab shell is re-created in target, but the URL configuration is not carried over. Manual reconfiguration required post-migration. |
|
No |
No |
Whiteboard |
Tab migration skipped (0 objects migrated). Whiteboard tabs can be migrated only if the underlying Whiteboard file in the creator's OneDrive is pre-migrated to the target tenant and at least one Team Owner has permission to the file in the source. When conditions are met, the tab migrates as a Weblink tab in the target - not as a native Whiteboard tab. |
|
No |
No |
Wiki |
Not migrated. As of January 2024, new Wiki tabs can no longer be created. Existing tabs remain accessible temporarily. Microsoft recommends exporting Wiki content to OneNote before migration to avoid data loss. |
|
Yes |
Yes |
Word |
Tab re-created. File migrates as part of the Teams Files (SharePoint) migration or via OneDrive migration. |
|
No |
No |
Workflows |
Not supported by ODM. |
NOTE: "Tab Created: No" does not necessarily mean content is lost. In most cases the underlying file or data migrates through a separate workload (Teams Files/SharePoint, OneDrive, or Planner). The tab itself must be manually reconfigured in the target channel after migration where applicable.
Related KB article:
https://support.quest.com/on-demand-migration/kb/4375730/team-tabs-for-sharepoint-onenote-and-planner-are-unable-to-be-created-and-configured
