立即与支持人员聊天
与支持团队交流

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

Discovering Site Contents

Discovering the site structure and content provides a better understand of the scope of the migration. The SharePoint contents list displays the following SharePoint object types: Site (site collection), Web (root site), Lists, Webs (sub sites, child sites). The display will include the number of lists and the number of items in each list.

To discover SharePoint site contents

  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 select an existing project.
  4. Click SharePoint. The Dashboard opens.
  5. Click SharePoint Contents from the Dashboard ribbon to open the SharePoint Contents list page.
  6. Choose one or more sites by selecting the respective check box for the site. You can select the check box in the column header to select all sites.

  7. Click Discover SharePoint Contents from the Actions ribbon. The New DiscoveryTask wizard opens.
  8. Step 1: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Click Next.
  9. Step 2: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant where the statistics will be collected.
      3. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

To view SharePoint contents:

  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 select an existing project.
  4. Click SharePoint. The Dashboard opens.
  5. Click SharePoint Contents from the Dashboard ribbon to open the SharePoint Contents list page.
  6. To view the contents for a specific site:
    1. Clear any filters in the Filter panel
    2. Set the Type filter to Site from the drop down. The list of sites and site collections are displayed.
    3. Select a site by clicking the corresponding check box. The site details panel opens.
    4. Click Show Content. The site contents are displayed in the list.

  7. To view the contents for a specific content type:
    1. Clear any filters in the Filter panel
    2. Set the Type filter to a content type from the drop down. The list of content types are displayed.

Matching and Mapping Sites

When site collection discovery is completed and before you migrate the site collections and descendant objects to the target tenant, the OnDemand Migration for SharePoint service must know where to migrate the site collections. There are two ways you can provide the reference:

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

Matching Site Collections

To ensure that no data is lost or duplicated, match the source site collections with the corresponding target site collections using the Matching Task.

To match site collections automatically:

  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 select an existing project.
  4. Click SharePoint. The Dashboard opens.
  5. Click SharePoint Contents from the Dashboard ribbon to open the SharePoint Contents list page.
  6. Choose one or more site collections by selecting the respective check box for the site collection. You can select the check box in the column header to select all site collections.

  7. Click Match from the Actions ribbon. The New Matching Task wizard opens.
  8. Step 1: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Select the Include site structure check box to allow sub-sites and other descendant structures to be matched.
    3. Click Next.
  9. Step 2: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant where the source URLs exist.
      3. Target tenant - name of the tenant where the source URLs may or may not exist.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
      5. Include site structure - option to match sub-sites and other descendant structures.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  10. You can track the progress in the Tasks tab, monitor alerts and notifications in the Events tab and view the summary on the Dashboard.
  11. When the task completes, the SharePoint Contents list is updated. Compare the Source Urlcolumn with the Target Url column for the selected sites. The object state of each matched site is set to Matched.

Mapping Site Collections

To change the name of a migrated site collection or relocate the root site, use a CSV file to set up a custom map. URLs in a mapping file are case sensitive and must be relative URLs. There are three ways to prepare a CSV site mapping file.

NOTE: Site collections cannot be merged or reorganized with a mapping file.

  1. Download the CSV file from the SharePoint Admin Center
    1. Log in to the SharePoint Admin Center of the source tenant.
    2. From the navigation pane, click Active sites.
    3. From the Active sites page menu, click Export to download the CSV file.
    4. In the CSV file, delete all columns before the URL column. Rename the URL column header to either SourceURL or Source URL. This must be the first column.
    5. In the Source URL column keep only the sites that you want to map. Ensure that only relative URLs are used.
    6. Insert a blank column as the second column and specify the header as either TargetURL or Target URL. This must be the second column.
    7. Specify the corresponding target URLs. Ensure that only relative URLs are used.
  2. Download the CSV file from the SharePoint Contents page
    1. Choose one or more sites by selecting the respective check box for the site. You can select the check box in the column header to select all sites.
    2. Click Export from the Actions ribbon.
    3. Extract the CSV file from the downloaded ZIP file.
    4. In the CSV file, delete all columns before the Source URL column. This must be the first column.
    5. Insert a blank column as the second column and specify the header as either TargetURL or Target URL. This must be the second column.
    6. Specify the corresponding target URLs. Ensure that only relative URLs are used.
  3. Create a new CSV file and specify the column header in the first row and then enter the URLs in the subsequent rows manually. Since URLs in a mapping file are case sensitive, this method must be used with caution.
    1. In the first column, specify the header as either SourceURL or Source URL.
    2. In the second column, specify the header as either TargetURL or Target URL.
    3. Enter the source and target URLs manually in the subsequent rows . Ensure that only relative URLs are used.

NOTE: You need to map only the URLs that will change in the target Tenant.

Example 1 - The Target URL is used to rename a site collection from the source tenant.

  • The URL /sites/StarzBrand has been renamed to /sites/StarzCorporate.
  • The URL /sites/StarzAccounting has been renamed to /sites/StarzFinance.
  • The URL /sites/Starzmarketing has been renamed to /sites/StarzMarketing.
  • The URL /sites/Starzteam has been renamed to /sites/StarzTeam.

Example 2 - The target URL is used to relocate the root site.

The root URL is relocated to a managed site in the target tenant called /sites/oldroot.

To map site collections with a CSV file:

  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 select an existing project.
  4. Click SharePoint. The Dashboard opens.
  5. Click SharePoint Contents from the Dashboard ribbon to open the SharePoint Contents list page.
  6. Click More Actions from the Actions ribbon and then click Map from File. The New Mapping from File Task wizard opens.
  7. Step 1: Mapping File
    1. Click Browse and locate the CSV mapping file.
    2. Click Open in the File Explorer window to load the file into the wizard
    3. Click Next.
  8. Step 2: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Click Next.
  9. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant where the source URLs exist.
      3. Target tenant - name of the tenant where the target URLs may or may not exist.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  10. You can track the progress in the Tasks tab, monitor alerts and notifications in the Events tab and view the summary on the Dashboard.
  11. When the task completes, the SharePoint Contents list is updated. Compare the Source Urlcolumn with the Target Url column for the selected sites. The object state of each matched site is set to Matched.

 

Migrating Sites

Use the SharePoint contents tab to migrate SharePoint objects (sites, lists, web, members). You can migrate an entire site or initiate granular or incremental migration. You can navigate through SharePoint site objects and identify any site objects that failed to migrate.

In this topic:

Starting a SharePoint migration task

Any discovered SharePoint object (object state = discovered) can be migrated including sites, lists (including individual lists) and webs (root and child webs). All children of the object selected for migration will be migrated.

Caution: Don’t start the migration before the discovery task is finished because migrated objects could be incorrectly processed.

NOTES:

  • When migrating multiple SharePoint sites, it is a best practice to add no more than 10 sites to a migration task to avoid creating a large load that may trigger throttling in the Microsoft export interfaces.
  • Creating and running multiple migration tasks at the same time may create a large load that may trigger throttling in the Microsoft export interfaces.
  • If the parent of the object selected for migration does not already exist on the target then migration will be skipped.
  • Migration of a Group site collection will be skipped if the corresponding Group site collection does not already exist at the target Url.
  • Migration of a site collection will be skipped if a site collection already exists at the target Url and the default language does not match with the source.
  • Migration of a site or web will do a full migration of all child lists (not incremental) and discovery of any new child web or list.

To start a SharePoint migration task:

  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.
  5. Click the SharePoint Contents tab.
  6. Select the sites to migrate. You can check multiple sites.
  7. Click Migrate. The New Migration Task wizard opens.
  8. Step 1: Options
    1. Configure the options as described below:
      • Map unmatched users to - Specify a default owner for the selected SharePoint sites. The default owner that you specify will override the default owner specified in the project settings for the selected SharePoint sites that are being migrated. For more information about project settings see Configuring the Migration Project.
      • Include child structure and content - Select this option to migrate the contents of the selected SharePoint sites.
      • Clear selected SharePoint objects from the target before starting the migration - Select this option to delete the selected SharePoint objects that already exist on the target before being migrated. Clearing of Group site collections is not supported and will be skipped to keep the association with Microsoft 365 Groups and Teams.
    2. Click Next.
  9. Step 2: Version Options
    1. Specify the scope of the SharePoint files to migrate. These options are relevant only if the Include child structure and content option is selected from the previous step.

      Each site has its own version history of its files and each change to a file is saved with a new version. Select from the following migration options to determine how SharePoint file versions should be migrated:

      • Latest version only - This is the default selection. The most recent version of the file will be migrated. All other versions will be ignored.
      • More versions - Additional versions of a file will be migrated based on the options described below. Large version sets take a significantly long time to migrate.
        • Number of versions - The maximum number of version to migrate. The available choices are: 2, 5, 10, 30, 60, 90 and 365. When you specify the number of versions, additional options can be selected.
        • Latest version and preceding versions - The version count includes the latest version and the preceding versions in chronological order restricted to the Size Limit of the latest version. For example, if you choose to migrate 5 versions, then the most recent version and 4 preceding versions will be migrated as long as the most recent version does not exceed the selected size limit specified.
        • Latest version and daily latest from preceding days - The version count includes the latest version and the latest version from each preceding day restricted to the Size Limit of the latest version. For example, if there are many versions of a site and you choose to migrate 5 versions, then the most recent version and the latest version from each of the 4 preceding days will be migrated as long as the most recent version does not exceed the selected size limit specified.
        • Size limit - This setting is available if the Latest version and preceding versions or the Latest version and daily latest from preceding days option is selected. By default, the size limit is 80 MB. You can configure the size limitation by selecting from one of the possible values in the drop down. If the size of the latest file version exceeds the selected size limit, the latest version will be migrated and previous versions will be ignored. If the size of the latest file version does not exceed the selected size limit, then the file and its versions will be migrated based on your selection between Latest version and preceding versions or Latest version and daily latest from preceding days.
      • All Versions - The latest version of the file will be migrated, and all previous versions of the file will be migrated if the latest version does not exceed a specified size limit. This option requires significantly more time to migrate all the versions.
        • Size limit - This setting is available if the All Versions option is selected. By default, the size limit is 80 MB. You can configure the size limitation by selecting from one of the possible values in the drop down. If the size of the latest file version exceeds the selected size limit, the latest version will be migrated and previous versions will be ignored. If the size of the latest site version does not exceed the selected size limit, then the file and its versions will be migrated.
    2. Click Next.
  10. Step 3: 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 - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Click Next.
  11. Step 4: Summary
    1. This step lists the following configured options for this task.
      • Name - Specify a name for the task.
      • Default target user - The default user specified for the selected sites. If this is blank, the default user in the project settings will be used.
      • Include site structure and content - Indicates whether or not the site structure and content will be migrated.
      • Delete target Site Collection - Indicates whether or not the target site collection will be deleted if it exists is the target tenant.
      • Migrate list item and document versions - Indicates the version option selected.
      • Scheduled start - Indicates when the task will start.
    2. Click Back to change configurations if necessary or click Finish to save and start the task as scheduled.

Review migration results

The migration task is complete and an object state is provisioned with issues or a content state is migrated with issues. Locate these objects in the SharePoint hierarchy.

In this topic:

Review using the SharePoint content view

Once the migration task is complete, locate objects where the object state is provisioned with issues or the content state is migrated with issues using the SharePoint content view.

From the SharePoint contents tab

  • Select the object so the row is highlighted and the details pane opens to the right of the screen.
  • From the details pane click Show Contents
  • Continue following the webs into the site structure until you see
    • an object where the Object State is Provisioned with Issues
    • a list where the Content State is Migrated with Issues
  • From the details pane click SHOW PARENT to return upward through the hierarchy.

Review using the table with filters

Once the migration task is complete, locate objects where the object state is provisioned with issues or the content state is migrated with issues using a flat view of the objects and filtering.

To see all SharePoint objects in the table in a flat view

  • Remove the Site filter.

To filter the table to see all Share Point objects with issues with provisioning

  • Set the Object State filter to Provisioned with Issues. You can filter further by setting a filter on the object Type.

To filter the table to see objects with issues with the migration

  • Set the Object State filter to Migrated with Issues. You can filter further by setting a filter on the object Type. The smallest object type where migration issues will be found is List.

About object and content states

Use the Object state and Content state properties in the SharePoint Contents list page to determine the state of any SharePoint object in the migration process.

Object state

Use the object state property to track the object itself. When the object is added to On Demand its status is discovered. When discovered you can trigger a migration:

State Description
Discovered On Demand has discovered the object at the source.
Matched On Demand has matched a site on the source URL with a corresponding site on the target URL.
Provisioned On Demand has created (updated) the SharePoint object (site, web, list, users and groups) on the target without warnings or errors. You are now ready to track the content state.
Provisioned with issues On Demand has created (updated) the object with warnings or errors. See Warnings and errors.
Content state

Use the On Demand content state property to track the progress of migrating the SharePoint object's content. Note that the content state value is transient (may change) while the task status is in progress.

State Description
Not Migrated On Demand has not migrated the content. This is the default content state when the object state is Discovered.
Migrating On Demand is migrating the object content.
Migrated On Demand has successfully migrated the content to the target without warning or errors. If the object is a list then all the list items have migrated successfully. If the object is a SharePoint site or web (root site) then all the child lists and webs have migrated successfully.
Partially Migrated While a migration task is in progress, partially migrated can be a transitory state showing at least one child is migrating or not migrated. Once the migration task is complete, partially migrated indicates that not all children of the object migrated: at least one child migrated and at least one child did not migrate.
Migrated with Issues On Demand has migrated the content to the target with warnings or errors. See Warnings and errors.
The transient nature of the object and content states during migration

When migrating a site the web and list task status will be set to complete when the web or list object state is set to provisioned. This is expected behavior in the current implementation. It indicates that the sub task to provision the object is complete. The Content State will not go to migrated until the child content is migrated

When migrating a site or web, the content state may be set to migrated and then reset to partially migrated. This will typically happen for a site that had not had the SharePoint content discovery run before migration is started. In this case the migration is discovering content to migrate as it goes along. The content state is set to migrating when the migration completes what it has discovered so far, then it looks for more and resets to partially migrating, repeating until all content is discovered and migrated. It discovers lists in a web in groups (not all at once) and then it discovers any sub sites after the lists are done.

 

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级