Converse agora com nosso suporte
Chat com o suporte

On Demand Migration Current - User Guide

About On Demand Migration Before you Start Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Troubleshooting Finalizing the Migration Appendix A: Working with PowerShell

Microsoft Teams Migration

On Demand Migration for Teams securely migrates Microsoft Teams and associated Microsoft 365 Groups across Microsoft 365 tenants. You can also use this dashboard for migration of content for Microsoft 365 Groups without Teams functionality. (Microsoft 365 Groups Migration). Microsoft Teams migration requires additional licensing.

Basic Microsoft Teams migration workflow consists of the following steps:

# Step
1 Create a migration project (created automatically with New Migration UI)
2 Grant necessary permissions in case these permissions are not already granted (Prerequisites)

IMPORTANT: It is not recommended to use existing user accounts as source and target temporary Migration Manager accounts, because it is recommended to remove them for safety reasons after the migration will be completed. These accounts can be removed from teams as described in Finalizing the Migration.

3 Discover teams/groups on the source tenant

On this step you can see names, suggested for target teams. In case you need some changes use manual mapping as described below. There are no provision on the target on this step.

TIP: Organize teams in collections to streamline the provision and migration process

4 Export teams mapping to CSV file
5 Map teams manually using exported CSV file

You can use manual mapping to migrate source team to the target team with another name. If the channel do not exist, it will be provisioned. Also you can use manual mapping to merge several source teams to one target team.

6 Create Microsoft 365 Groups and Provision teams on the target tenant. Target teams will be owned by the target temporary Migration Manager account that is used to perform the provisioning.
  • The temporary Migration Manager account in the source tenant will be added to all source teams as a member, and source private channels as an owner.
  • The temporary Migration Manager account in the target tenant will be added to all target teams and Microsoft 365 Groups as a member and an owner, and target private channels as an owner

These accounts can be removed from teams as described in Finalizing the Migration.

7 Migrate teams

Migrate / merge all conversations (including inline content) from the source to target channels.

  • Target temporary Migration Manager account will own all private channels migrated to the target.
8 remigrate teams to incorporate supported changes made after the migration task (step 7) was started.
9 Monitor the progress and track issues

What We Migrate

Objects and content types

Object Support Notes
Team owners and team members ✔ Only for Microsoft 365 Groups that are migrated / matched. Teams and groups with dynamic membership can be migrated but cannot be merged.

The memberships is not updated in Teams immediately after membership migration. It takes a while before Microsoft synchronizes memberships between groups and Teams. Workaround: Wait for membership synchronization.

Archived team ✖ If you need to migrate these teams, you must unarchive them in the source to migrate and then archive them again in the source and in the target.
Public channels ✔  
Private channels ✔ See Channel settings subsection below.
Conversations ✔ The target tenant's temporary Migration Manager account is displayed as the owner of all migrated messages on the target: The original owner and creation time of a message are displayed in the first line of the message starting with "Originally posted by...".

Individual messages larger than 4 MB will not migrate. Messages containing several inline messages can exceed 4MB. The chat will migrate without the large messages. An error will display in the On Demand Migration for Teams Events tab of the form: Request failed with RequestEntityTooLarge status code (Request Entity Too Large).

SharePoint document libraries (Files) ✔  
Team picture ✔  
Timestamps ✔  
Team settings partial See Team settings subsection below.
Custom tags for teams ✔ GCC tenants do not support tags.
Guest accounts and conversations ✔  
Planner partial Planner Tab, Buckets, Tasks and Comments. If there are more than 400 Planner tasks in a bucket then On Demand migrates the first 400 tasks only. Only one assignee will be migrated if multiple users are assigned to a task.
Custom website tab ✔  
Chats ✔ Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you migrate the chats. File links in team chats will not work after chat migration if the files are moved to another folder in the source tenant.

Files that are linked to the private chats and meetings are migrated but do no display in the Files tab of private chats and meetings.

Private one-to-one chats with a Skype user are not migrated. The Microsoft Graph API List chat messages do not support querying messages of that type.

Private one to one chats are migrated as group chats. All the messages in the migrated chats are posted by the temporary Migration Manager.

On the source tenant a member removed from a chat can still see the history of the chat in the source. On the target, members cannot see the history of chats they have been removed from.

Users deleted on the tenant are not migrated, so do not show as members of a chat on the target. Deleted users do remain visible as members of a chat on the source. 1:1 chats, where one of the users is deleted, are migrated for the user that is still a member of the tenant.

Private one-to-one chats with an ‘External user’ (user from another tenant) are treated as follows. Private one-to-one chats initiated by an ‘External user’ are not migrated. Private one-to-one chats not initiated by an ‘External user’ are migrated, and in the title the external user’s real name is replaced with the text ‘External user’.

Applications partial Only Word, Excel, PowerPoint, OneNote and List tab applications linked to files in the same channel are supported. If you rename a tab in the source team and then re-migrate, the renamed tab will be migrated. The target will then have two tabs, one with the old name and one with the new name.
OneNote partial When the team name in source tenant is different from the one in target tenant, a blank default team’s notebook (with the target team name) will be created in target tenant. The original default team’s notebook (with the source team name) will be migrated correctly by Team’s migration. This results in two default team’s notebook in target.

OneNote tabs migration fails if the team contains a large number of items (folders or files, some of which could be OneNote entities such as notebooks, sections or section groups) and the following error message is reported: Request failed with Forbidden status code (Forbidden). { "error": { "code": "10026", "message": "One or more of the document libraries on the user or group’s OneDrive contains more than 20,000 OneNote items (notebooks, sections, section groups). Please try again later."....Workaround: Before proceeding with migration consider the following Microsoft recommendations to avoid the problem: https://docs.microsoft.com/en-us/archive/blogs/onenotedev/onenote-api-calls-fail-with-a-large-number-of-items-in-a-sharepoint-document-library

Lists partial Lists must be created in the same SharePoint site used by the team or Private Channel. You must select the Standard and Customized (All SharePoint Content) option in the Migration Options step of the New Teams Migration Task to allow the migration of Lists and their content.

Lists with spaces in the list name cannot be migrated.

Wiki sections and pages ✖  
Bots ✖  
Applications including Shifts for schedule management ✖  
Inbox folder and Calendar from the group mailbox associated with a team ✔  
Formatted text ✔  
Authorship partial Authorship in messages is migrated as a string with author name and creation date. File authorship is supported.
File preview partial Preview icons of files attached to a post are not migrated. The file is migrated as a link.
Link preview of public sites partial Preview icons are not migrated. Only the link is migrated.
Mentions:
  • Users
  • Channels
  • Teams
 ✔ Mention in migrated message can be used only if mentioned source object has a pair in the target
Images posted inline from buffer ✔  
Emoji, GIF, Sticker, Praise, memes ✔  
Link preview of public images ✔ Preview icons are not migrated. Only the link is migrated.
Attached images, media files, documents partial Preview icons are not migrated.

Meeting recordings

partial

Recordings of scheduled meetings in a team channel, stored in SharePoint or OneDrive, are migrated.

  • Meeting recordings stored in Microsoft Stream (Classic) are not migrated; the link to the recording on the source team channel is retained.
  • On Demand does not support meeting recordings in a group chat. Recordings in group chats and one-to-one chats cannot be migrated with the On Demand Migration for Teams service. Since the recording file is stored in the chat organizer's OneDrive account, you can use the On Demand Migration for OneDrive service to migrate recordings.
  • On Demand does not support meeting recordings for "Meet now" meetings.
Meeting Notes in private meetings ✖  
Meeting conversations ✔ Conversations are migrated as private chats, but cannot be written to the original Teams meeting. Conversations in a channel stay in the channel rather than a private chat, and are migrated to the target channel with a Teams migration task.
Whiteboards in private meetings ✖  
E-mail attachments ✖  
Code snippets ✖  
Announcements partial Customized background picture for announcements are not migrated
Rich card attachments ✖  
Files uploaded from mobile application 
Media files ✔  
Voice recordings ✖  
Documents ✔  
Team Settings
Team picture ✔  
Team description ✔  
Allow members to create and update channels ✔ Member permissions
Allow members to create private channels ✔ Member permissions
Allow members to delete and restore channels ✔ Member permissions
Allow members to add and remove apps ✔ Member permissions
Allow members to upload custom apps ✖ Member permissions
Allow members to create, update, and remove tabs ✔ Member permissions
Allow members to create, update, and remove connectors ✔ Member permissions
Give members the option to delete their messages ✔ Member permissions
Give members the option to edit their messages ✔ Member permissions
Allow guests to create and update channels ✔ Guest permissions
Allow guests to delete channels ✔ Guest permissions
@mentions ✔ When teams are migrated, each instance of @mentions generates a new activity email and users could receive a large number of unexpected emails. As a result @mentions are migrated as text and new activity emails are suppressed.
Team code ✖  
Enable Giphy for this team ✔ Fun stuff
Filter out inappropriate content using one of the setting below ✔ Fun stuff
Enable stickers and memes ✔ Fun stuff
Allow memes to be uploaded ✔ Fun stuff
Channel Settings
General settings ✔ Channel isFavoriteByDefault property migration is not supported. Workaround: Enable Automatically show this channel in everyone’s channel listoption for the channel manually in your Teams client.
Public channel settings ✔  
Private channel settings ✔ The Teams client will not display the updates immediately. It may take up to 24 hours before the changes are reflected due to Microsoft limitations. Private channel members not visible in the Teams application unless you explicitly search for a member.
Group Settings
Allow external senders to email this group ✔ General
Send copies of group conversations and events to group members ✔ General
Hide from my organization's global address list ✔ General

Migration from a Commercial tenant to a GCC High tenant

The table below lists the content types in Microsoft Teams that are available for migration from a Commercial tenant to a GCC High tenant with the On Demand Migration for Teams service.

Content type Availability in
GCC High tenant		 Migration support
Announcements ✔ ✔
Applications ✔ ✔
Applications including shifts for schedule management ✔ ✖
Associated SharePoint document libraries (files) ✔ ✔
Attached images, media files, documents ✔ ✔
Authorship ✔ ✔
Bots ✖ ✖
Calendars ✔ ✖
Chats ✔ ✔
Code snippets ✔ ✖
Conversations ✔ ✔
Custom tags for teams ✖ ✖
Custom website tab ✔ ✔
Email attachments ✔ ✖
Emoji, Teams GIFs, memes ✔ ✔
Formatted text ✔ ✔
Group mailbox associated with team ✔ ✖
Guest accounts and conversations ✔ ✔
Images posted inline from buffer ✔ ✔
Link preview of public images ✔ Partial. Icon is not migrated.
Link preview of public sites ✔ Partial. Icon is not migrated.
Meeting conversations ✔ ✔
Mentions
  • Users
  • Channels
  • Teams
 ✔ ✔
OneNote ✔ ✖
Planner (Planner Tab, Buckets, Tasks and Comments) ✔ ✔
Private channels ✖ ✖
Public channels ✔ ✔
Team owners and team members (Creation of Microsoft 365 Groups) ✔ ✔
Team picture ✔ ✔
Timestamps ✔ ✔
Wiki sections and pages ✔ ✖

Migration from one Education tenant to another

Teams migration from one education tenant (Microsoft 365 for Education) to another is partially supported. The following team types and supported content can be migrated:

  • Standard Team
  • Class Team
  • PLC Team
  • Staff Team

During provisioning, the teams with the same type will be created in the target tenant. Provisioning of public teams is not supported for migration scenarios from one education tenant to another.

Assignment app, personal OneNote notebook linked to a Teams channel and the OneNote tab linked to another team are currently not supported. Links to files in migrated messages are not supported in case these links point to files located outside the default SharePoint URL. These links are missing in the target.

Prerequisites

Verify the following requirements are met before migrating Microsoft Teams. If these actions are not performed, discovery, provision and migration tasks will fail or some data might be lost!

  • The following consents are granted before Teams migration can be started
    • Migration - Basic,
    • Migration - Mailbox Migration
    • Migration - SharePoint,
    • Migration - Teams.

TIP: If the consents are not granted or expired, Discover Teams action is disabled and the following notification is displayed: Grant admin consent to the following Migration sub modules on the Tenants page for both source and target tenants: Basic, SharePoint, and Teams. Open Tenants page and grant the necessary Consents and Permissions so that the product can access the source and target tenants. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering Teams.

  • User must be matched or migrated before using the On Demand Migration for Teams service.
  • Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you migrate the chats.
  • It is recommended to create or use source and the target temporary Migration Manager accounts.
  • The temporary Migration Manager accounts in the source and target tenant should have Teams license from the Microsoft 365 admin center.
  • Do not change your temporary Migration Manager accounts before completing the migration project.
  • The temporary Migration Manager accounts should be granted the Global Administrator or Teams Administrator role on the tenants for which these account are used.
  • The temporary Migration Manager accounts should be granted Application Impersonation role on the tenants for which these account are used.
  • Accounts joined to existing teams should be matched or migrated in the migration project.

IMPORTANT: It is recommended to remove the source and target temporary Migration Manager accounts for safety reasons after the migration is completed. These accounts can be removed from teams as described in Finalizing the Migration.

Required permissions

Feature Required permissions
Migrate conversations Read all channel messages
  Have full access to the Chat Service Aggregator
  Have full access to the Skype Teams Service
  Create chat and channel messages with anyone's identity and with any time stamp
Migrate private chats Read all chat messages
  Read and write user chat messages
Provision groups and teams Read and write directory data
  Read and write all groups
Migrate files and OneNote items Read and write all OneNote notebooks
  Read and write items in all site collections
  View and modify notes for all users
Migrate groups and teams membership Read all users' full profiles
  Read or write user region
  Add and remove members from all teams
  Add and remove members from all channels

Temporary Migration Manager accounts

It is strongly recommended to create source and target temporary Migration Manager accounts. These accounts should not be an owner or member of any team. For security reasons it is recommended to remove these accounts once the migration is complete.

The target temporary Migration Manager account use is in and not limited to the following scenarios:

  • The target temporary Migration Manager account that is used to perform Teams provisioning creates and owns these provisioned target teams.
  • The target temporary Migration Manager account is added to all target teams and Microsoft 365 Groups as a member and an owner, and to all target private channels as an owner.
  • The target temporary Migration Manager account is used to perform the Teams migration and displayed as the owner of all migrated conversation and chat messages and planner tasks on the target.
  • The target temporary Migration Manager account is added to all the chats (both group chats and private chats) as a participant during chats migration, and then removed from the migrated chats as soon as the chat migration is complete. All migrated chats of the target temporary Migration Manager account are hidden when the chat migration is complete.

Teams Workspace

In this topic:

Dashboard

The components of the dashboard are as described below:

Notification panel - presents relevant information and shortcuts to migration activities.

Dashboard Menu - contains the following links to common activities in the migration process.

  • Discover - Starts the New Teams & Groups Discovery Task wizard to collect information about accounts in the source tenant. For more information see Discovering Teams and Groups

Dashboard Tiles

  • Getting Started - Presents quick start links to the various actions for preparing and migrating teams.
  • Teams - Presents a summary of the teams in various migration states. Click Show All to open the Teams List view to inspect the teams.
  • M365 Groups - Presents a summary of the M365 Groups in various migration states. Click Show All to open the Groups List view to inspect the groups.
  • Tasks - Displays the five most recent tasks that were completed in the Teams workspace. The title displays the total number of tasks. Click Show All to open the Tasks List view.
  • Events - Displays the five most recent events that were completed in the Teams workspace. The title displays the total number of events. Click Show All to open the Events List view.

Teams List View

The Teams List View is comprised of the following components:

Notification panel - presents relevant information and shortcuts to migration activities.

Filter panel - consists of predefined filters for the Teams List view and tabs to switch between the Teams List view and the Assessment view. See Filtering for more information about working with filters. The predefined filters are:

  • Teams - migration state of the team.
  • Teams By Size - size of a team. Valid ranges are More than 1GB, 100MB - 1GB, 10MB - 100MB, Less than 10MB. The dropdown also shows the nunbver of teams in the list for each range.
  • SharePoint - nature of the SharePoint site linked to the team. Valid values are Customized and Standard.

List View Menu - contains links to teams migration activities and the search box. Each activity is explained in greater detail in subsequent topics. See Searching for more information about working with the search box.

List View - displays information about teams in the source and target tenants. Use the Edit Columns list view menu to show or hide columns in the list. The columns are as described below:

  • Team Name - name of the team in the source tenant.
  • Migration State - status of the task in the migration process. Values are as listed below:
    • Discovered
    • Exists in target - team in the source tenant exists in the target tenant
    • Provisioning
    • Provisioned
    • Provisioned with issues
    • Provision failed
    • Migrating
    • Partially migrated
    • Partially migrated with issues
    • Migrated
    • Migrated with issues
    • Migration failed
  • SharePoint - nature of the SharePoint site linked to the team. Values are as described below:
    • <no-value> - SharePoint content has not be discovered yet.

    • Standard - There is at most 1 SharePoint site and 4 Lists in the SharePoint site collection

    • Customized - There are more than 1 site and 4 Lists in the SharePoint site collection

    NOTE: The SharePoint status is available only after the New Teams Provisioning Task is run.

  • Channels - number of channels in the source tenant team.
  • Members - number of members in the source tenant team.
  • Source Files (GB) - total size in GB of files across all channels in the source tenant.
  • Target Files (GB) - total size in GB of files across all channels in the target tenant.
  • Messages - number of messages in the source tenant team.
  • Migrated Messages - number of messages migrated to the target tenant team.
  • Plans - number of plans in the source tenant team.
  • Migrated Plans - number of plans migrated to the target tenant team.
  • Tasks - number of tasks in the source tenant team.
  • Migrated Tasks - number of tasks migrated to the target tenant team.
  • Last Activity - date and time of the last action performed on the team record.
  • Created - date and time the team record was created.
  • Target Team Name - name of the team in the target tenant.
  • Source MailNickname - email alias of the associated Microsoft 365 Group.

Teams Assessment View

See the Premigration Assessment for Teams for the complete list of available reports.

Team Details

When you select a team from the List View, the Team Detail pane opens. The information in the pane is described below:

  • Description - name of the team in the source tenant.
  • Visibility - indicates whether the source tenant team is Public or Private.
  • Is Archived - indicates whether the source tenant team is archived.
  • SharePoint Customized - status of the selected account. Valid values are New, In Progress, Failed and Completed.
  • Owner count - number of owners of the source team. A team can have up to 100 owners.
  • Member count - number of members in the source tenant team.
  • Migrated messages count - number of messages migrated to the target tenant team.
  • Archive messages count - number of archived messages in the source tenant team.
  • Last Operation - the most recent operation performed on the team. Valid values are Discovered, Provisioned, and Migrated.
  • Events - count of the events that occurred during account processing through one or more tasks.
  • Tasks - list of tasks invoked for the selected account.

Team Content

The Team Content tab presents a list of teams and its components along with the count of child items of the object type. When you open the Team Content tab, the list view initially displays all the teams and their migration state along with the total count of the team components of each team: Channel, Planner, Mailbox, team membership and SharePoint Content. For each team component you can additionally view its components and their child item counts as well.

To display the contents of a specific team:

  1. Select the team to open the details pane on the right hand side.
  2. Click Show Content. The components of the selected team are displayed in the list view along with the migration state and child item counts for each component. In the details pane, the Show Parent link is activated and the Show Content link is deactivated.

NOTE: Components of a team can be displayed when teams are migrated through a new project created after the Jan 10, 2023 release.

To display the parent of a specific team component:

  1. Select the team component to open the details pane on the right had side.
  2. Click Show Parent. The parent team is displayed in the list view along with the migration state and the total count of the team components. In the details pane, the Show Content link is activated and the Show Parent link is deactivated.

The components of teams are migrated when you start a migration task with the New Teams Migration Task wizard and select the team component types to migrate.

NOTE: The Events property value in the detail pane for a selected child component will be zero.

Filter panel - consists of predefined filters for the Teams List view and tabs to switch between the Teams List view and the Assessment view. See Filtering for more information about working with filters. The predefined filters are:

  • Status - migration state of the team.
  • Type - object type: Team, Channel, Planner, Mailbox, team membership or SharePoint Content.

List View - displays information about teams in the source and target tenants. Use the Edit Columns list view menu to show or hide columns in the list. The columns are as described below:

  • Type - object type: Team, Channel, Planner, Mailbox, membership or SharePoint Content.
  • Name - name of the object
  • Migration State - status of the task in the migration process. Values are as listed below:
    • Discovered
    • Exists in target - object in the source tenant exists in the target tenant
    • Mapped
    • Provisioning
    • Provisioned
    • Provision failed
    • Migrating
    • Partially migrated
    • Partially migrated with issues
    • Migrated
    • Migrated with issues
    • Migration failed
  • Items to migrate - the count of child items of the object. For each team, the count indicates the total number of child components of the team. For each team components the item counts displayed are as described below:
    • Planner: number of Planner tasks
    • Channel: number of messages
    • Mailbox: the team mailbox. The count is always 1
    • Membership: number of team members
    • SharePoint Content: number of sites
  • Processed - the number of items considered for migration.
  • Progress (%) - migration progress in percentage. If a team component is not selected for migration in the New Teams Migration Task wizard, this value does not exist for the component.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação