Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migrations Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Online Migration Microsoft Teams Migration Finalizing the Migration

Exporting Site Collection Mapping

To export site collection mapping into comma-separated values (CSV) file for analytics or archival purposes open Site Collections and click Export.

Output CSV file will contain mapping data for discovered and matched (migrated) site collection URLs.

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. 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. Click Migrate.
  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 filed 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 stricture is migrated.
  2. Specify whether the existing target sites are cleaned up (all exciting 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.

  1. Schedule when the task will be started. See Task Scheduling for details.
  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.

Microsoft Teams Migration

On Demand Migration for Teams securely migrates Microsoft Teams across Office 365 tenants. Microsoft Teams migration requires additional licensing.

IMPORTANT: Before migrating any Teams sites, you must ensure all accounts exist in the target tenant. Account Migration project for your source and target tenant should exists, and account matching /migration should be completed.

Basic Microsoft Teams migration workflow consists of the following steps:

# Step
Create Microsoft Teams migration project
Grant necessary permissions in case these permissions are not already granted

Discover teams 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.

Export teams mapping to CSV file

Manual mapping using prepared 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.

Create Office 365 groups and Provision teams on the target tenant

Migrate teams

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

Automatically migrate associated files

All files, associated with selected teams are transferred to the channels. If the channel do not exist, it will be provisioned.

Monitor the progress and track issues

What We Migrate: Microsoft Teams Migration

Objects and content types migrated and not supported:

A
Object Supported? Comments
Team owners and team members (creation Office 365 groups) Only for accounts that are migrated / matched
Channels  
Conversations  
Associated SharePoint document libraries (Files)  
Team picture  
Team settings Including team permissions
Guest accounts and conversations  
Chats  
Applications  
Wiki sections and pages  
Bots  
Applications including Shifts for schedule management  
Calendars  
Mail  
Formatted text  
Authorship partially Authorship in messages is migrated as a string with author name and creation date
Link preview of public sites  
User mentions  
Mentions of Teams and channels  
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  

NOTE:If you re-run the migration, only new messages are processed. The modified messages are unchanged; deleted messages remain visible.

Related Documents