Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

Microsoft Teams Migration

On Demand Migration for Teams securely migrates Microsoft Teams and associated Microsoft 365 Groups across Office 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 Azure AD administrator 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 Azure AD administrator account that is used to perform the provisioning.

  • Source Azure AD account will be added to all source teams as a member, and source private channels as an owner.
  • Target Azure AD account 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 Azure AD account will own all private channels migrated to the target.
8 Re-migrate teams to incorporate supported changes made after the migration task (step 7) was started.
9 Monitor the progress and track issues

What We Migrate

IMPORTANT: Teams migration from one education tenant (Office 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.

Objects and content types
Object Support Comments
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.
Public channels  
Private channels See Channel settings subsection below.
Conversations  
Associated SharePoint document libraries (Files)  
Team picture  
Timestamps  
Team settings partial See Team settings subsection below
Custom tags for teams  
Guest accounts and conversations  
Planner (including Planner tab app)  
Custom website tab  
OneNote Before to start OneNote migration you should re-grant Migration.Teams admin consent on Tenants.
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.

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.

Applications partial Planner, Word, Excel, and PowerPoint tab apps
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.
Link preview of public sites  
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  
Attached images, media files, documents

 

Meeting recordings

partial

Recordings of scheduled meetings in a team channel, stored in SharePoint/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 small groups 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  
Whiteboards in private meetings  
E-mail attachments  
Code snippets  
Meeting conversations  
Announcements  
Files uploaded from mobile application:    
Media files  
Voice recordings  
Documents  
Rich card attachments:    
vnd.microsoft.card.hero  
vnd.microsoft.card.thumbnail  
application/vnd.microsoft.card.adaptive  
vnd.microsoft.card.animation  
vnd.microsoft.card.audio  
vnd.microsoft.card.video  
vnd.microsoft.com.card.receipt  
vnd.microsoft.com.card.signin  
Team Settings
Category Setting Supported?
Team picture Team picture
Team description Team description
Member permissions 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
Guest permissions Allow guests to create and update channels
Guest permissions Allow guests to delete channels
@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 Team code
Fun stuff 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
Channel Settings
Category Setting Supported?
General All
Public channels All
Private channels All. The Teams application will not reflect the updates immediately. The Teams application may need to be open for up to a 20 hours before changes are reflected due to Microsoft limitations.
Group Settings
Category Setting Supported?
General 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

Teams 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 Available in
GCC High
Supported by
On Demand Migration
Team owners and team members (Creation of Microsoft 365 Groups)
Public channels
Private channels
Conversations
Associated SharePoint document libraries (files)
Team picture
Timestamps
Custom tags for teams
Guest accounts and conversations
Planner (including Planner tab app)
Custom website tab
OneNote
Chats
Applications
Wiki sections and pages
Bots  
Applications including shifts for schedule management
Calendars
Group mailbox associated with team
Formatted text
Authorship
Link preview of public sites
Mentions
  • Users
  • Channels
  • Teams
Images posted inline from buffer
Emoji, Teams GIFs, memes
Link preview of public images
Attached images, media files, documents
Email attachments
Code snippets
Meeting conversations
Announcements

 

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!

  • Consents are already granted for source and target tenants.
    The following consents should be granted before Teams migration feature can be used
    • Migration - Basic,
    • Migration - Mailbox Migration
    • Migration - SharePoint,
    • Migration - Teams.

TIP: If the admin 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 Required 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. On Demand for Migration uses the global administrator account to grant consent because the ‘admin consent flow’ which it uses requires it; read more about the admin consent flow experience.

  • 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 dedicated (not added as owner or member to any team) source and the target Azure AD administrator accounts.

IMPORTANT: It is not recommended to use existing user accounts as source and target Azure AD administrator 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.

  • Azure AD administrator accounts should have Teams license.
  • It is not recommended that you change your Azure AD administrator accounts before completing the migration project.
  • Azure AD administrator accounts should be granted the Global Administrator or Teams Administrator role on the tenants for which these account are used.
  • Azure AD administrator 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.

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

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation