Chatta subito con l'assistenza
Chat con il supporto

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 Power BI Migration Troubleshooting Finalizing the Migration Appendix A: Using PowerShell Appendix B: How Queuing Works

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 partial Column formatting is not supported
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 page headers and footers ✖  
Site permissions ✔  
Sub-sites ✔  
Title, description and logo ✔  
Top navigation ✔  
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
Express Hosted Site (EHS#1) ✖  
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 ✔  
Content type hub ✖  
Document set settings ✔ The Document set setting to define default content is not currently supported
Name and description ✔  
Term Store partial

Term Set does not migrate when Available for Tagging is deactivated.

Translation for term sets cannot be migrated.

Reused, Pinned, Deprecated terms are not supported

Column types of site, list, and content type
Choice ✔  
Currency ✔  
Date and time ✔  
Hyperlink or picture ✔  
Image partial Image column, column data and referenced image assets are migrated but links to image assets are broken.
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.
Document library item highlighting/pinning ✖  
Document library sensitivity labels ✖  
Forms for lists ✖  
List alerts ✔  
List columns partial Column formatting is not supported
List content types
  • New content type button order
  • Default content type
 ✔  
List name, description and navigation ✔  
List permissions ✔  
List rating settings ✖  
List views partial View formatting is not supported
Modern list comments ✔  
Pages libraries ✔  
Rules for lists ✖  
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 ✔ Calendar overlays are not supported.
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 date
  • Last modified by
 ✔ Source user email will be used for Created by and Last modified by if the source user account has not been matched to an account on the target.
Column data ✔  
List item permissions ✔  
Document
Alerts on documents ✔  
Authorship properties
  • Created date
  • Created by
  • Last modified data
  • Last modified by
 ✔ Source user email will be used for Created by and Last modified by if the source user account has not been matched to an account on the target.
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
Forms for Lists ✖  
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 SharePoint Migration Considerations for details on remigration behavior or if the target site or sub-site exists before the migration is started.

 

Considerations

Your target tenant might already host SharePoint sites (site collections) or sub-sites created before the migration. See the table below to see the migration action that will be used depending on the existing site properties and the selected migration options.

Target site (sub-site) exists Clear existing site collection option is selected Migration action
Yes No Merge, all supported properties will be overwritten using source settings
Yes Yes Create and migrate
No - Create and migrate

Merging and remigration considerations

  • Sub-sites based on unsupported site templates are skipped unless they are remapped.
  • System settings including site columns, content types etc. from the source will overwrite settings that were changed on the target.
  • New site structure including list item and docs that only exist on the target remains unchanged.
  • If a new list item with the same name is added on both source and target, the source item will be migrated and added as a separate item (i.e. target will have two items with identical names).
  • If a new document with the same name is added on both the source and target, the migration of the source item will be skipped, and the warning that the item already exists on the target is reported. Document libraries only allow one document per name.
  • Conflict resolution setting on the List Options step of the New SharePoint Migration Task wizard controls how list items and docs (same name and ID) that were previously migrated in this project are remigrated to the target.
  • Versions for remigrated List item and files will be removed and updated based on the settings selected in the Version Options step of the New SharePoint Migration Task wizard

Prerequisites

  • It is highly recommended to at least match all accounts in the project to ensure that membership and content ownership are processed correctly.
  • The target tenant should already have the fully configured SharePoint with the active license plan. Note, that licenses are not automatically assigned to the target users during the migration.
  • The following admin consents should be granted for SharePoint migration:
    • Migration - Basic
    • Migration - SharePoint - Minimal (for source)
    • Migration - SharePoint - Full (for source and target)

In case necessary admin consents are not granted or expired, discovery will be deactivated and the following notification will be displayed: Grant admin consent to the Migration module on the Tenants page for both source and target tenants: Basic and SharePoint. To grant admin consents open Tenants page and grant the Required Consents and Permissions to allow the product to access the source tenant and the target tenant. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering site collections.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione