Chat now with support
Chat with Support

On Demand Migration Current - User Guide

About On Demand Migration 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: Using PowerShell

Renaming and Mapping Teams and Groups

You can rename and map teams and M365 groups, or rename, map and merge one or more source teams (or M365 group) to a specific team (or M365 group) in the target tenant in two ways:

Renaming and Mapping Teams and Groups automatically

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
  5. Click the Teams tab or the M365 Groups tab and select one or more teams or groups that you want to rename and map.
  6. Click More Actions and then click Rename and Map. The New Teams & Groups Rename and Map Task wizard opens.
  7. Step 1: Mapping options
    1. Enter the information as described below:
      • Add prefix - specify a prefix for the team or group name.
      • Add suffix - specify a suffix for the team or group name.
    2. Rename mail nick name - select this option to add a prefix or suffix to the target team or group.
    3. Click Next.
  8. Step 2: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a mapping task completes.
      • Only in a case of failure - select this option to send the email if the mapping task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  9. Step 3: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Step 4: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name. The default name is Rename and Map Task.
      2. Source tenant - name of the tenant in this project.
      3. Target tenant - name of the target tenant in this project.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The task is created. You can track its progress from the Tasks tab, view the summary on the Dashboard or monitor alerts and notifications from the Events tab.

Mapping, Renaming and Merging Manually from a File

To rename Microsoft 365 groups or merge one or more source groups to a specific group in the target tenant, a CSV file is used to indicate the mapping between source and target groups as described below.

To creating a mapping file:

  1.  Prepare a comma-separated values (CSV) file with the source and target group names.

    TIP: Export selected groups to a comma-separated values (CSV) and then edit this file. See Exporting Groups for more details.

  2. The header row defines the names of the source and target attribute used for mapping. Subsequent rows list the mapping values of the attributes.

    The columns are as follows:

    • Source Mailnickname - unique name of the source group. The following column header variations are supported: SourceMailNickname, Source MailNickname, Source MailNickName. The column header is case sensitive.
    • Target Mailnickname - unique name of the target group. The following column header variations are supported: TargetMailNickname, Target MailNickname, Target MailNickName. The column header is case sensitive. You can merge multiple source groups to a single target group when you specify the same Target Mailnickname in a mapping file.
    • Target Group Name - display name of the target group. The column header is case sensitive.

    Example 1: Row 2: Simple change of name.

    The source group display name and mailnickname are changed.

    Example 2: Rows 3 and 4: Different target groups with the same display name.

    The Target Mailnicknames are different but the Target Group Names are the same. The Target Mailnickname takes precedence and the groups will be mapped to distinct target groups but the display name of each target group will be the same. It is recommended that you use unique display names to avoid confusion.

    Example 3: Rows 5, 6 and 7: Merge multiple source groups with the same target group.

    The Target Mailnickname is the same. The source groups will be merged with the same target group with the specified display name.

  3. Save the CSV file.

NOTE: File names with non-ASCII characters are not supported.

To upload a mapping file:

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
  5. Click the M365 Groups tab.
  6. Click More Actions and then click Map from File. The New Mapping from File Task wizard opens.
  7. Step 1: Mapping file
    1. Click Browse and select the CSV mapping file. The selected file name appears next to the Browse button.
    2. Click Next.
  8. Step 2: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a mapping task completes.
      • Only in a case of failure - select this option to send the email if the mapping task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  9. Step 3: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Step 4: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant in this project.
      3. Target tenant - name of the target tenant in this project.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The task is created. You can track its progress from the Tasks tab, view the summary on the Dashboard or monitor alerts and notifications from the Events tab.

 

SharePoint Migration

On Demand Migration offers a fast and convenient way to transfer SharePoint content between Microsoft 365 tenants. SharePoint migration functionality requires additional licensing.

IMPORTANT: Before migrating any SharePoint sites, you must ensure all impacted accounts exist in the target tenant. Account matching or migration should be completed.

The Getting Started tile on the SharePoint migration Dashboard with Quick help helps you to prepare, start and perform all the steps to migrate your SharePoint sites. The basic SharePoint migration workflow consists of the following steps:

Step Description
1 Configure the SharePoint migration project defaults (optional)
2 Verify prerequisites are met
3 Discover sites (top-level sites) in the source tenant
4 Discover site contents like members, webs and lists (optional)
5 Map geo-locations (optional)
6 Map source sites to custom target sites (optional)
7 Match source sites to with existing target sites (optional)
8 Map Lists (optional)
9 Override migration defaults for specific migration tasks (if necessary)
10 Migrate site collections and their content
11 Monitor the progress and track issues

IMPORTANT: Quest recommends performing test and pilot migrations before starting the full-scale migration of the production environment. This helps you better plan the migration project and align the migration tasks with the organization requirements.

Caution: Finish all account migration tasks that are pending before starting the SharePoint migration.

What We Migrate

Migration limitations indicated below may not be an exhaustive list of limitations as some may appear in unique customer migration scenarios, or arise due to platform or legacy support restrictions. In some cases, a solution to a limitation may already be on the product roadmap.

Quest On Demand migrates the following SharePoint components:

NOTE: You can migrate files with a maximum size of 250 GB. Quest On Demand supports Shared with me panel functionality on the user's Office portal OneDrive pages for the documents and folders shared using SharePoint.

Microsoft public preview features are not supported.

Objects and content types

Object Support Notes
Site collections and sites

Modern experience: top-level sites and sub-sites

Document ID service feature  
Global and site term groups  
Hub settings and associations  
Language settings
 
List templates  
Lists and Libraries  
Navigation elements  
People and groups  
Quick launch  
Regional settings  
SharePoint Designer settings  
Site collection admins  
Site collection feature activation
 
Site collection owner  
Site columns  
Site content types  
Site feature activation Active site feature will be activated on the target during migration but the impact of activating the feature may not be supported on the target.
Site permissions  
Sub-sites  
Themes gallery  
Title, description and logo  
Top navigation  
Web parts gallery  
Site templates

Sites and webs based on unsupported templates are not supported for migration and will be skipped unless they are remapped. Unsupported site templates listed below is selective of common and popular templates.

Community site (COMMUNITY#0)  
Classic project site (PROJECTSITE#0)  
Classic team site (STS#0, SPSMSITEHOST#0)  
Document Center (BDR#0)  
Enterprise Wiki (ENTERWIKI#0) Some limitations are applicable
Modern communication site (SITEPAGEPUBLISHING#0)  
Modern Microsoft 365 group site (Group#0). The Group or Team site based on the Group#0 must already exist on the target before the migration is allowed to be performed. The Group or Team sites cannot be set to be cleared before migration.
Modern team site without Microsoft 365 group (STS#3)  
Publishing Portal (BLANKINTERNET#0, BLANKINTERNET#2, CMSPUBLISHING#0) Some limitations are applicable
Point publishing sites (POINTPUBLISHINGHUB#0, POINTPUBLISHINGPERSONAL#0, POINTPUBLISHINGTOPIC#0) Can be remapped.
Project Web App site (PWA#0) Can be remapped.
Record Center (OFFILE#1)  
Search Center (SRCHCEN#0, SRCHCENTERLITE#0, SRCHCENTERLITE#1) Can be remapped.
Content types
Advanced settings  
Column  
Column Order  
Document set settings The Document set setting to define default content is not currently supported
Name and description  
Column types of site, list, and content type
Choice  
Currency  
Date and time  
Hyperlink or picture  
Image  
Managed metadata  
Multiple lines of text  
Number  
Person or group  
Single line of text  
Yes/No  
List and libraries
Advanced settings
  • Folders
  • Search
  • Offline client availability
  • List experience
  • List attachments
  • List item-level permissions
  • List index non-default views
  • Library Document Templates
 
Audience targeting settings
Only Classic audience targeting is supported for document libraries.
List alerts  
List columns  
List content types
  • New content type button order
  • Default content type
 
List name, description and navigation  
List permissions  
List views  
Modern list comments  
Pages libraries  
Validation settings  
Version history of documents (optional) Version history transfer means a significant increase in migration time.
Version history of list items (optional)  
Version settings  
List templates
Announcements  
Contacts  
Custom list  
Custom list in data sheet view  
Discussion board  
Document Library  
Events and Calendar  
Issue tracking  
Links  
Picture library  
Promoted links  
Tasks  
Tasks with timeline and hierarchy  
Wiki page library  
Folder
Properties  
Folder permissions  
List item
Alerts on list items  
Attachments  
Authorship properties
  • Created date
  • Created by
  • Last modified data
  • Last modified by
 
Column data  
List item permissions  
Document
Alerts on documents  
Authorship properties
  • Created date
  • Created by
  • Last modified data
  • Last modified by
 
Document ID service feature  
Document permissions  
Document properties  
Site pages
Modern site pages  
Classic pages  
Web Parts

Supported web parts have been verified to ensure all links and references to SharePoint entities are updated during migration as required. Unverified web parts are migrated as is to the target tenant, links and references to other SharePoint entities may remain linked to the entities on the source.

Modern web parts partial
Supported web parts
Bing Maps Hero Quick Chart
Button Highlighted content Quick links
Call to action Image Recent documents
Code Snippet Image gallery Site activity
Countdown Timer Kindle instant Preview Sites
Divider Link Spacer
Document Library List Text
Embed List properties Twitter
Events Markdown Weather
File viewer News World Clock
Group Calendar Page Properties YouTube
  People  
     
Unsupported web parts    
Conversations Microsoft Power Apps Organization Chart
Highlights My Feed Planner
Microsoft Forms Office 365 Connectors Power BI
    Saved for Later
     
Classic web parts partial
Supported web parts
About the community Get started with your site Page Viewer
Blog Archives Image Viewer Picture Library Slideshow
Blog Notifications Join Community Project Summary
Blog Tools Library Site Feed
Community Tools List Site Users
Content Editor My Membership What's happening
     
Unsupported web parts    
Business Data category Media and Content category Social Collaboration category
Content Rollup category Search category  
Filters category Server-driven content category  
     
Custom web parts  
Workflow and Forms
Microsoft InfoPath Forms Migrating InfoPath Forms requires a SharePoint token to be associated with the migration project to allow access to the Microsoft retention policy and InfoPath form APIs. For more information see Migrating Record Center Retention Policies and InfoPath Forms.
Microsoft Forms  
Nintex Classic Forms, Responsive Forms, and workflows  
SharePoint 2010 Workflows SharePoint 2010 workflows are no longer supported in SharePoint Online.
SharePoint 2013 Workflow definitions and subscriptions Migration is attempted on a best effort basis and it is recommended that you must review the workflow definitions after the migration.
Workflow instances Any references to in-progress or completed workflows are not migrated
M365 security and compliance features
Legal Hold  
M365 Compliance Customer Lockbox  
Microsoft Information Protection policies and labels  
Retention Labels  
Power Platform features
Power Apps  
Power Automate (Flow)  
Power Pages  
Power Virtual Agents  

Limitations

  • Checked out status for files in document libraries is not migrated.
  • Currently checked out documents are not migrated. The last checked in version of the document is migrated. If the file has never been checked, no version of the file is migrated.
  • Reputation Settings for Community site migration are not supported
  • Reporting of offensive content setting for Community sites is not supported
  • Private views and personal sites are not migrated.
  • Classic web parts in classic wiki pages are not migrated. This may affect the home pages of older classic team sites (STS#0) where the home.aspx page is built on a Wiki page.
  • Assigned translators in Language settings for Communication site are not migrated
  • Comments on modern site pages are not migrated
  • Migration from an education tenant to another education tenant is not supported for education templates.
  • Migration of verified web parts is a best effort. A warning event will be posted for any site pages where an issue occurred while migrating web parts. The warning event will identify the web part and possible cause of the problem. Please review the identified web parts on the site pages and correct as needed.
  • OnDemand Migration for SharePoint migrates the content starting with the root site and then proceeds to any sub-sites. As a result:
    • Links to SharePoint lists, libraries and sub-sites that have not been migrated to the target will not be added to the Quick Launch menu.
    • Navigation links and links in web parts to SharePoint content in sub-sites cannot be updated if the linked sub-site has not been migrated.
  • Migration of the Master Page Gallery is not supported because active master pages cannot be updated or overwritten during the migration. Custom master pages should be manually added to the Master Page Gallery in the target tenant and set as the new master page.
  • Some Pages library files like Home.aspx, About.aspx and PageNotFoundError.aspx, and the Welcome Page setting cannot be migrated if the sites are built with the following features or templates. You must manually move these files and reconfigure the Welcome page setting if necessary.
    • The SharePoint Server Publishing Infrastructure site collection feature is activated in the source.
    • The site is based on the Wiki site template.
    • The site is based on Publishing Portal templates.
  • Managed navigation is based on term sets. The term set setting for Managed Navigation for the Publishing Portal is not migrated. The term set is set to the default on the target. You must manually update the term set setting in the target tenant if the selected term set setting in the source is no longer the default.
  • There could be duplication in navigation links because links are managed from the site UI and from a Publishing Portal specific Navigation site setting.
  • Hub settings for sites located in non-central regions of a multi-geo tenant cannot be migrated. The hub and spoke relationship for sites in non-central regions must be built manually after the site migrations are complete.

See the Considerations for details on remigration behavior or if the target site or sub-site exists before the migration is started.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating