Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration Current - Administrator Guide

About On Demand Migration Signing up for Quest On Demand Before You Start Working with On Demand Migration Starting a Migration Project Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Classic web parts

The following classic web parts are verified (in alphabet order):

  • About the community
  • Blog Archives
  • Blog Notifications
  • Blog Tools
  • Community Tools
  • Content Editor
  • Get started with your site
  • Image Viewer
  • Join Community
  • Library
  • List
  • My Membership
  • Page Viewer
  • Picture Library Slideshow
  • Project Summary
  • Site Feed
  • Site Users
  • What's happening

All classic web parts not included in this list are unverified and will be copied as is to the target, links and references to other SharePoint entities may remain linked to the entities on the source.

Site Templates

The following site templates are supported for site collection discovery and migration:

  • Modern Office 365 group site (Group#0). Some limitations are applicable
  • Modern team site – no Office 365 group (STS#3)
  • Modern communication site (SITEPAGEPUBLISHING#0)
  • Classic team site (STS#0, SPSMSITEHOST#0)
  • Classic project site (PROJECTSITE#0)
  • Community site (COMMUNITY#0)
  • Document Center (BDR#0)
  • Enterprise Wiki (ENTERWIKI#0). Some limitations are applicable.

Migration of site collections based on other templates is not supported. Sub-sites based on unsupported templates will be skipped.

IMPORTANT:

  • 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.

Limitations

  • The default site language on the source and the target tenant should match.
  • 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.
  • Maximum number of items that can be migrated in a single list or library is 1 million
  • 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.
  • The migration of some look and feel settings require that running of custom scripts be allowed on the site. See https://docs.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script for more information on allowing custom scripts.
  • 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.

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

 

Considerations

Your target tenant might already host SharePoint top-level 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 Source and target default languages match Clear existing site collection option is selected Migration action
Yes Yes No Merge, all supported properties will be overwritten using source settings
Yes Yes Yes Create and migrate
Yes No Yes/No Skip and report
No - - Create and migrate
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating