Converse agora com nosso suporte
Chat com o suporte

On Demand Migration Current - User Guide

About On Demand Migration Before you Start 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: Working with PowerShell

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 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
  • 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.
  • For previously migrated list items and docs (same name and ID):
    • Updates on source will be migrated to the target
    • Updates to target will be overwritten by remigrated source item or document
  • System libraries like Site Pages are always cleared before a remigration. Any new files added only to the target will be deleted from the target as part of the remigration.

Currently, only the latest versions of documents and list items are migrated. In case of remigration, please consider the following:

  • The previously migrated document is replaced but the document version remains unchanged in the target tenant.
  • The previously migrated list item is replaced with a new version if the SharePoint List Settings control Create a version each time you edit an item in the list is activated in the target tenant.
  • The previously migrated list item is replaced but the document version remains unchanged if the SharePoint List Settings control Create a version each time you edit an item in the list is deactivated in the target tenant.

For more information about version control in lists or libraries, see Enable and configure versioning for a list or library.

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

 

Prerequisites

  • It is highly recommended to match / migrate all accounts in the corresponding Migration 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.
  • Consents already get granted for source and target tenants.
    The following admin consents should be granted for SharePoint migration feature:
    • Migration - Basic,
    • Migration - SharePoint

In case necessary admin consents are not granted or expired, discovery will be disabled 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 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.

Dashboard

The SharePoint migration dashboard presents quick links to help you prepare and migrate SharePoint content with intuitive data points and key performance metrics.

The dashboard sections are described below:

Notification panell - displays helpful information that may include links to manage the content migration

Dashboard Menu - contains links to the following actions:

  • Discover site collections - starts the New Discovery Task wizard to collect information about SharePoint sites in the source tenant. For more information see Discovering SharePoint Site Collections.
  • Configure project - starts the Edit Project wizard for configuring migration defaults, SharePoint Admin Center URLs and multi-geo settings. For more information see Configuring the migration Project.
  • Refresh project - refreshes the SharePoint migration project settings.

Getting Started - presents quick start links to the various actions for preparing and migrating SharePoint content.

SharePoint site migration status - indicates the number of SharePoint sites being migrated with a color coded status bar that indicates the migration count of the SharePoint sites.

Item Migration Progress - status count of SharePoint content that is discovered in the source tenant and migrated to the target tenant. The following metrics are displayed:

  • Discovered items on source
  • Items selected for migration on source
  • Migrated items on target

File Count (per hour) - performance chart that indicates the files migrated per hour.

Content migration (per hour) - performance chart that indicates the SharePoint items migrated per hour.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação