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

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

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

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.

SharePoint Migration Workspace

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.

Configuring the Migration Project

  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. From the project Dashboard click Open in the SharePoint tile.
  1. Click Configure Project on the SharePoint project dashboard menu. The Edit Project wizard starts
  2. Step 1: Project Settings
    1. Set Migration Defaults

      Default Target User - Specify the default target user to use as the site collection owner when the existing owner has no match in the target tenant. During the migration, On Demand Migration checks whether accounts associated with the source site are matched with accounts in the target tenant. Depending on the results, one of the following actions is performed:

      SharePoint Entity Matched owner found Matched owner missing Matched owner and default user missing
      Top-level sites (site collection) Target account matched with source owner Default target user Migration Task fails
      Sub sites System account

      System account

      Lists

      System account

      System account

      Folders Target account matched with source owner Default target user

      NOTE: Migrated list items and files will retain the source user metadata if the user has not been matched with Accounts in the target tenant. This includes Created by, Modified by and Person column metadata on list items and documents. The default target user is not used for matching list items or files.

    2. Set SharePoint Admin Center Urls

      The SharePoint migration service builds the expected SharePoint Admin Center URL based on SharePoint's default naming convention. If a customer has custom SharePoint Admin Center URLs, these URLs should be set manually.

      • Source SharePoint Admin Center Url - Enter the SharePoint Admin Center Url of the source tenant.
      • Target SharePoint Admin Center Url - Enter the SharePoint Admin Center Url of the target tenant.

      NOTE: On Demand Migration does not validate SharePoint Admin Center URLs. These URLs are a subject of special request to Microsoft. Do not change the default URL if the custom one is not yet approved by Microsoft.

    3. Click Next.
  3. Step 2: Multi-Geo settings

    Migrated SharePoint sites can be mapped to geo locations in the target tenant with the Map Geo Location Task. The task requires a CSV file that contains the mappings for the migrated sites. For more information about the CSV file format see Mapping geo locations. You can control how the mapping in the target tenant is determined by configuring the following settings:

    1. When the SharePoint project is created a task (Name = Refresh Project) runs. The task determines whether the target is enabled for geo location, and retrieves the set of active geo locations from the target teanant.
      • Default target geo location - choose a default geo location from the set of active geo locations discovered in the target tenant.

      NOTE: If a new geo location is added to the target tenant after the SharePoint project is created, the task (Name = Refresh Project) must be rerun.

    2. Choose an option for migrating sites to a multi-geo tenant.
      • Use target geo location. If undefined use geo location of source site. Otherwise use default target geo location - The Target Location column in the CSV file that is used for geo mapping sites, will be used by the Map Geo Location Task to determine the geo location of the migrated site in the target tenant. If the column value is blank or invalid, the geo location of the site in the Source Location column will determine the geo location in the target tenant. If the column value is blank or invalid, the Default target geo location will be used.
      • Use target geo location. If undefined use default target geo location - The Target Location column in the CSV file that is used for geo mapping sites will be used by the Map Geo Location Task to determine the geo location of the migrated site in the target tenant. If the column value is blank or invalid, the Default target geo location will be used to determine the geo location in the target tenant whether or not a geo location is specified for the site in the Source Location column of the CSV file.
  4. Click Finish.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択