Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migration Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Hybrid Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Removing Sites from the Migration Project

You can temporarily remove any source site collections from the migration project, if necessary. Consider, site collections cannot be removed permanently from the migration project, all existing source site collections will be added in after next discovery.

To temporarily remove sites from the migration project:

  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the SharePoint migration Dashboard, go to step 3.
  2. Click SharePoint widget.
  3. Open Site Collections and select the items you want to remove from the migration project.
  4. Click More Actions | Delete
  5. Click Delete to confirm the action.

Migrating Sites

Double-check that the account migration is finished (or at least that all SharePoint users are migrated) and create the Migration task:

  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the SharePoint migration Dashboard, go to step 3.
  2. Click SharePoint widget.
  1. Open Site Collections and select the items you want to migrate.

TIP: Use search and filtering to quickly navigate through the list of site collections.

  1. Select whether the version history will be migrated for list items and documents. Consider, version history transfer means a significant increase in migration time.
  2. Click Migrate. Refer to the SharePoint Migration Considerations for details on re-migration behavior or if the target site/subsite exists before the migration is started.
  1. Provide the target account (FQDN) that will be used as the default owner (if the actual owner is not found.) The value set in the task is preferred over the project setting.
    By default, this field is already populated with the default target user configured on the project level.
  1. Specify whether child entities are migrated. By default, the entire collection structure is migrated.
  2. Specify whether the existing target sites are cleaned up (all existing content removed) before migration.

Caution: If this option is selected, all content of the target site is removed and replaced by source site's content! Use with extreme caution.

NOTE: Clearing of Group site collections is not supported as it will break the association with Office 365 Groups and Teams. Clearing of Group site collections will be skipped if this setting is enabled.

  1. Schedule when the task will be started. See Task Scheduling for details.

TIP: It is recommended by Microsoft to schedule tasks to run overnight and on weekends to reduce the workload during business hours.

  1. Click Next to view the task summary. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

The migration task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events. Events help you get relevant information in case the tasks are performed over a considerable period of time. ODM SharePoint migration processes are running if you see “Batch <x> in progress” event messages being logged approximately every 5 minutes.

Microsoft Teams Migration

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

IMPORTANT: In case you use classic product UI, Account Migration project for your source and target tenant should exists before migrating ant Teams. Account matching /migration should be completed.

Basic Microsoft Teams migration workflow consists of the following steps:

# Step
1 Create Microsoft Teams migration project (created automatically with New Migration UI)
2

Grant necessary permissions in case these permissions are not already granted

IMPORTANT: It is not recommended to use existing user accounts as source and target Azure AD administrative 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 Office 365 groups and Provision teams on the target tenant. Target teams will be owned by the target Azure AD administrative account that is used to perform the provisioning.

  • Source Azure AD account will be added to all source teams as an owner, to all source Office 365 Groups as a member, and to all source private channels as an owner
  • Target Azure AD account will be added to all target teams and Office 365 Groups as a member and an owner, and to all 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: Microsoft Teams Migration

IMPORTANT: Teams migration from one education tenant to another is partially supported. The following private team types are currently supported for education templates (all supported content can be migrated):

  • Standard
  • Class Team
  • PLC Team
  • Staff Team

During provision 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.

OneNote Staff Notebook, OneNote Class Notebook, OneNote PLC Notebook, and Assignment app migration is not currently supported.

Personal OneNote notebook linked to a Teams channel and the OneNote tab linked to another team are not currently 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 Supported? Comments
Team owners and team members (creation Office 365 groups) Only for accounts that are migrated / matched
Public channels  
Private channels See Channel settings subsection below
Conversations  
Associated SharePoint document libraries (Files)  
Team picture  
Timestamps  
Team settings partially 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 regrant Migration.Teams admin consent on Tenants.
Chats  
Applications partially Planner, Word, Excel, and PowerPoint tab apps
Wiki sections and pages  
Bots  
Applications including Shifts for schedule management  
Calendars  
Group mailbox associated with team  
Formatted text  
Authorship partially 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  
Emojy, Teams GIFs, memes  
Link preview of public images  
Attached images, media files, documents

 

E-mail attachments  
Code snippets  
Meeting conversations  
Meeting recordings  
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 Show members the option to @team or @[team name] (this will send a notification to everyone on the team)
@mentions Give members the option to @channel or @[channel name]. This will notify everyone who's shown the mentioned channel in their channel lists.
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.
Related Documents