サポートと今すぐチャット
サポートとのチャット

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

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.

 

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

SharePoint Migration Workspace

In this topic:

Dashboard

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

TIP: Click Refresh Project to get the latest updates for the SharePoint dashboard.

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.

Global Term Store - indicates the status of the Term Store migration. You must migrate the Global Term Store before you migrate SharePoint sites.

To migrate the Global Term Store:

  1. Click Migrate Term Store from the Actions menu. The Migrate Term Store wizard opens.
  2. Step 1: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - Select this option to send the email if the discovery 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.
  3. Step 2: 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.
  4. Step 3: Summary
    1. This step lists the following configured options for this task.
      • Name - Specify a name for the task. The default name is Migrate Term Store.
      • Source tenant - name of the source tenant.
      • Scheduled start - expected start time of the task.
    2. Click Back to change configurations if necessary or click Finish to save and start the task as scheduled.

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.

SharePoint Contents

The SharePoint Contents List View is comprised of the following components:

Notification panel - presents relevant information and shortcuts to migration activities.

Filter panel - consists of predefined filters for the SharePoint List. See Filtering for more information about working with filters. The predefined filters are:

  • Task Status - returns a list of SharePoint objects based on the status of a task that includes this object.
  • Provision State - returns a list of SharePoint objects based on the current state of the object. Values are Discovered, Matched, Provisioned and Provisioned With Issues.
  • Migration State - returns a list of SharePoint objects based on the migration state of the object and its children. The various values are described below.
  • Priority - returns a list of SharePoint objects based on the precedence level of this object if it is included in a migration task. Values are Highest, High, Medium, Low, and Lowest.
  • Migration - returns a list of SharePoint objects based on whether migration is supported for the site or web template type. Options are Supported and Unsupported.
  • Type - returns a list of objects based on the SharePoint object type. Values are Site, Web, List, and Members.

List View Actions Menu - contains links to SharePoint object migration activities and the search box. Each action is explained in greater detail in subsequent topics. See Searching for more information about working with the search box.

List View - displays information about SharePoint objects in the source and target tenants. Use the Edit Columns to show or hide columns in the list. The columns are as described below:

  • Type - SharePoint object type. Values are Site, Web, List, and Members.
  • Name - name of the object type.
  • Provision State - current state of the object. Values are Discovered, Matched, Provisioned and Provisioned With Issues.
  • Migration State - migration state of the object and its children. Values are:
    • Not Migrated - migration has not started
    • Discovered - SharePoint objects have been found in the source tenant.
    • Matched - a SharePoint object in the source tenant has been matched with a corresponding SharePoint object in the target tenant.
    • Mapped - a site in the source tenant has been mapped to another site in the target tenant. Source and target URLs are different.
    • Provisioned - On Demand has created (updated) the SharePoint object (site, web, list, users and groups) on the target without warnings or errors.
    • Queued - waiting for service resources to be available. For more information, see How Queuing Works.
    • Migrating - migration is in progress
    • Migration Failed - migration has failed.
    • Migrated - migration is successful
    • Migrated With Issues - this object or at least one child object had issues with migration
    • Partially Migrated - at least one child object has not been migrated
    • Partially Migrated With Issues - at least one child object has not been migrated and this object or at least one child object had issues with migration
  • Priority - indicates the precedence level of this object if it is included in a migration task where the priority is set in the Schedule step of the migration wizard. Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued. When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
  • Source Location - geo-location of the source object.
  • Source Url - object url in the source tenant.
  • Target Location - geo-location of the target object.
  • Target Url - object url in the target tenant.
  • Mapped to Different Url - Boolean to indicate if user has mapped the object to different url on the target
  • Template - SharePoint template used for the source object.
  • Migration - indicates whether migration is supported for the site or web template type. Values are either Supported or Unsupported.
  • Site Type - possible values are M365 Groups, Teams, and SharePoint. The Team Site template is associated with M365 Groups. If Teams has been activated on a Team Site template then it is associated with Teams. All other site templates are associated with SharePoint.
  • Site Language - default language of the source site.
  • Hub - name of the hub group that the site belongs to if the source site is organized in a hub-spoke relationship.
  • Task Status - status of the task that is working on this object. Values are New, Stopped, In Progress, Completed with Issues, Failed, and Completed.
  • Last Updated - most recent date and time when the object information was updated.
  • Owner - owner account name
  • Source Child Items - total of all the child lists and libraries in the site or web in the source tenant.
  • Target Child Items - total of all the child lists and libraries in the site or web in the target tenant.
  • Source InfoPath Forms - number of Infopath forms in the source tenant.
  • Source SharePoint Workflows - number of workflows in the source tenant.

Term Store

A term store in SharePoint Online is a global site directory of common terms that are used in your organization. The point of the term store is build consistency in the way that users enter and manage data in your SharePoint environment.

The Term Store List View is comprised of the following components:

Notification panel - presents relevant information and shortcuts to migration activities.

Filter panel - consists of predefined filters for the Term Store List. See Filtering for more information about working with filters. The predefined filters are:

  • Task Status - returns a list of Term Store items based on the status of a task that operated on this object.
  • Migration State - returns a list of Term Store items based on the migration state of the object and its children. The various values are described below.

List View Actions Menu - contains links to SharePoint object migration activities and the search box. Each action is explained in greater detail in subsequent topics. See Searching for more information about working with the search box.

List View - displays information about Term Stores in the source and target tenants. Use the Edit Columns to show or hide columns in the list. The columns are as described below:

  • Name - name of the Term Store.
  • Migration State - migration state of the object and its children. Values are:
    • Not Migrated - migration has not started.
    • Discovered - Term Store item has been found in the source tenant.
    • Matched - a Term Store item in the source tenant has been matched with a corresponding SharePoint object in the target tenant.
    • Mapped - a Term Store item in the source tenant has been mapped to another Term Store item in the target tenant. Source and target URLs are different.
    • Provisioned - On Demand has created (updated) the Term Store item on the target without warnings or errors.
    • Queued - waiting for service resources to be available. For more information, see How Queuing Works.
    • Migrating - migration is in progress.
    • Migration Failed - migration has failed.
    • Migrated - migration is successful.
    • Migrated With Issues - this item had issues with migration.
    • Partially Migrated - at least one Term Store item t has not been migrated.
    • Partially Migrated With Issues - at least one Term Store item has not been migrated and this item had issues with migration.
  • Source Location - geo-location of the source Term Store item.
  • Target Location - geo-location of the target Term Store item.
  • Task Status - status of the task that operated on this Term Store item. Values are New, Stopped, In Progress, Failed, and Completed.
  • Last Updated - most recent date and time when the Term Store item information was updated.

Reports

Migration Reports display error reports about migration tasks. For more information see Migration Reports.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択