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

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: Working with PowerShell

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 open an existing project.
  4. Click theSharePointtile, or click Open from the SharePoint tile to open the SharePoint dashboard.
  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: Options
    1. Collect forms and workflow statistics - select this option to count the number of Infopath forms and workflows associated with the selected sites.
    2. Click Next.
  9. Step 2: 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.
  10. Step 3: 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for the task.
    2. Click Next.
  11. Step 4: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name. The default name is Discover SharePoint Contents Task.
      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 open an existing project.
  4. Click theSharePointtile, or click Open from the SharePoint tile to open the SharePoint dashboard.
  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 dropdown list. 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.

      The SharePoint Contents list view columns are as described below. One or more columns may be hidden by default. Use Edit Columns to hide or show columns.

      • 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
      • 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 -
      • 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 an 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, 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.
  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 dropdown list. The list of content types are displayed.

Mapping Geo Locations

NOTE: This feature is available if the target tenant is geo-enabled.

In this topic:

NOTE: We recommend that you run the Map Geo Location task before you run the Mapping from File task. The Mapping from File task sets the geo locations using the default settings, and once the target location is set it can't be reset by the Map Geo Location task.

Workaround: Delete site from the SharePoint Contents list and rerun the Discover Site Collections task.

If you want to migrate SharePoint sites to a geo located target tenant, you must map the discovered source tenant sites to active geo locations in the target tenenat using a CSV file.

To prepare a CSV file with geo mapped SharePoint sites, use the CSV format described below:

  • Source Url - column header for the urls of the site in the source tenant
  • Source Location - column header for the geo location of the source site. The geo location could be blank if your source tenant is not geo enabled.
  • Target location - column header for the geo location of the site in the target tenant. The geo location could be blank if you choose to use the Default target geo location in the SharePoint project settings.

New Map Geo Location Task wizard

The New Map Geo Location Task wizard maps the geo locations of migrated SharePoint sites based on the mappings in the CSV file described in the previous section.

  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. From the ribbon, click More Actions and then select Map Geo Location from File. The New Map Geo Location Task wizard opens.
  7. Step 1: Mapping File
    1. Click Browse and select the CSV file with the geo location mappings that you prepared.
  8. 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.
        • Start - enter the start time for the task.
    2. Click Next.
  9. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Map Geo Location. You can specify a custom name.
      2. Source tenant - name of the tenant where the statistics will be collected.
      3. Target tenant - name of the target tenant in this project.
      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.

 

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 open an existing project.
  4. Click theSharePointtile, or click Open from the SharePoint tile to open the SharePoint dashboard.
  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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for 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. The default name is Matching 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 Provision 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 open an existing project.
  4. Click theSharePointtile, or click Open from the SharePoint tile to open the SharePoint dashboard.
  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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for the task.
    2. Click Next.
  9. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Mapping from File 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 Provision state of each matched site is set to Matched.

 

Migrating SharePoint Objects

Use the SharePoint contents tab to migrate SharePoint objects like sites, lists, web, members, retention policies and InfoPath forms. 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:

Migrating Record Center Retention Policies and InfoPath Forms

Migrating Record Center Retention Policies and InfoPath Forms requires a SharePoint token to be associated with the migration project to allow access to the Microsoft retention policy and InfoPath form APIs.

To associate a SharePoint token with the migration project using PowerShell:

  1. Download the PowerShell module and connect to ODM PowerShell to get the project id. See Appendix A: Working with PowerShell for more details.
  2. Get the project workloads (Accounts, Teams, SharePoint, Public Folders)

    Get-OdmProjectWorkload -Project 'Elf813YBfQYAK6Q42Kun'

  3. Select the Id for the SharePoint project workload as the context

    Select-OdmProjectWorkload -ProjectWorkloadId 'tH8u5nsB-aY5ES3q6NyZ'

  4. Get the SharePoint connection token

    Set-OdmSpConnectionToken -ConnectionType target

  5. In the credentials window that opens, enter the On Demand credentials (typically the On Demand administrator)

    NOTE:

    • Token is stored in the SharePoint project
    • Token expires in 2-3 days. We recommend that you refresh the token after 2 days if you expect your migration to run for longer periods.
  6. Start the migration task. See Starting a SharePoint migration task for details.

To migrate tenant level settings:

  1. Log in to the SharePoint admin center of your target tenant.
  2. Go to More Features > InfoPath.

  3. Copy the information over from your source tenant.

Mapping a list to a different web on the target tenant

Lists or libraries that have not been migrated can be mapped to a different web on the target tenant. When these objects are migrated, they will be relocated to the new SharePoint web. This web can be in the same site or a different site.

  • The web in the target tenant must exist before the mapping otherwise mapping will fail.
  • Previously migrated lists cannot be mapped to a different web.
  • The list mapping will be used by a migration task that includes the list.

To map a list to a different site

  1. Open the SharePoint contents tab and locate the list
  2. Select a list that has not been migrated. You can select only one list at a time.
  3. Click Map List from the list detail pane to start the New SharePoint Map Task wizard.
  4. Select the option Update target web Url to move this list to a different parent web in this or another site.
  5. Enter the new name in the New target Url field .

  6. Click Finish.

Starting a SharePoint migration task

Any discovered SharePoint object where Provision 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 the object will not be migrated.
  • 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 or web results in a full migration of all child lists 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 SharePoint Migration Task wizard opens.
  8. Step 1: Migration Scope

    1. Choose a migration scope as described below:
      • Migrate all - select this option to migrate the selected objects including any descendants or content associated with these objects.
      • Migrate structure without list or library content - select this option to limit the scope of the migration to the full site structure like Site, Members (users and groups), Webs and Lists. List items will not be migrated.
      • Migrate selected objects without descendants or content - select this option to migrate only the selected objects. Any descendants or content associated with these objects will be ignored.
    2. Select Include site level term group as part of site migration to add site level metadata to the Global Term Store. The Global Term Store must be migrated before you can use this option, otherwise an error will be logged as an event. For more information, see Migrating the Global Term Store.
    3. Click Next.
  9. Step 2: Migration Options

    1. Configure the migration options as described below:
      • Default user account - Specify a default user account if the source user account cannot be matched with a target user account.
      • Clear selected objects from the target - 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.
      • Upgrade classic team sites to modern team sites - Select this option to upgrade classic team sites to modern team sites. If the classic team site does not exist on the target, create the site using the modern team site.
    2. Click Next.
  10. Step 3: Permission Options

    1. Select how Sharing Links permissions are migrated. Direct permissions are always migrated.
      • Migrate permissions - select this option so that unique permissions associated with web, list and list items are migrated. If you clear this option all other options in this step are deactivated and permission migration is prevented. When permissions are not migrated, the permissions for new migrations of web, list and list items, that are not already on the target tenant, will be inherited from its parent. The permissions will not be changed for migrations of content that was already migrated to the target tenant.
      • Migrate permissions only for previously migrated webs and lists - select this option to migrate permissions for webs and lists only. Permissions will be merged with any existing permissions on the target tenant. List item permissions are not migrated with this option because list item permissions cannot be migrated separately from the list item. To re-migrate list items and its permissions, re-migrate the whole list without selecting this option. Selected objects must be in a migrated or migrated with issues state for this option work.
      • Do not migrate Sharing Links permissions - select this option to ignore Sharing Links permissions.
      • Migrate Sharing Links permissions as direct permissions. Migration is slower - select this option to migrate Sharing Links permissions. These permissions will be migrated as direct permissions. The conversion and migration of Sharing Links permissions takes more time to migrate.
    2. Click Next.
  11. Step 4: List Options

    This step applies to specific lists selected for migration from the SharePoint Contents list view.

    1. Choose from the following options to determine how changes to selected list items that were previously migrated should be remigrated:
      • Refresh list items - an incremental migration is performed to repair and update the target list with missing or new items.

        NOTE:Repairing Lists with Migration Issues

        The On Demand Migration for SharePoint service can repair lists with the Migration state = Migrated with Issues. When such a list is remigrated, the contents of the list in the source and target tenants are compared. Missing items in the target are restored and items that are updated in the source since the previous migration will be incrementally migrated.

        • Lists in the Migrated with Issues state will be repaired if the user selects the Refresh list items option in the migration task.
        • All child lists will be repaired and refreshed for migrations of sites and webs.
        • If a list is in the Migrated state, no repair is required and only incremental migration will be done.
      • Migrate all list items - all list items are remigrated.
    2. Choose a conflict resolution option.

      NOTE:

      • Conflict resolution rules are applied only to lists that have been previously migrated.
      • Conflict resolution rules will not be applied if the Migrate all list items list option is selected in the previous step. All files in the target tenant will be overwritten if all files are migrated.
      • Conflict resolution rules will not be applied to Site Pages and Site Assets system libraries.
      • Overwrite target files - all migrated files in the target tenant will be overwritten. Migration is fastest with this option selected.
      • Skip if target list item is the same version or newer - ignore list items in the target tenant with the same or newer version. If the item does not exist in the target tenant, a copy of the source item will be migrated.
      • Create a copy if target list item is the same version or newer - preserve the list item in the target tenant with the same or newer version and create a copy of the source item. When you choose this option, you must choose from one of the following file suffix options: _Copy, _Source, _Older, _Backup, and _1.
    3. Migrate list and library comments - select this option to include list and library comments in the migration task. A large number of list and library comments increase task processing time.
    4. Click Next.
  12. Step 5: Version Options

    1. Specify the versions of the SharePoint files to migrate. These options are relevant only if the Migrate all option is selected in the Migration Scope step.

      NOTE:When you select a conflict resolution option and a version option, you should expect the following behavior:

      Overwrite target files - the file is replaced with the file and version history from the source based on the version settings.

      Skip if target list item is the same version or newer - the target file is not changed, but new items migrated will follow versions settings.

      Create a copy if target list item is the same version or newer - the copy is migrated using the version settings.

      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 dropdown list. 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 dropdown list. 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.
  13. Step 6: 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.
  14. Step 7: 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.
        • Start - enter the start time for the task.
      • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued (Migration state = Queued). When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
    2. Click Next.
  15. Step 8: Reporting

    Select the checkbox Generate detailed report of migration errors to generate a migration error report when you run the New SharePoint Migration Task wizard.

    You can download the report from the Reports tab of the SharePoint workspace by clicking the Download link in the Error Log column. If there are no migration errors, a download link is not available. Error reports are retained for 30 days. After 30 days the download link is replaced with the label Expired and you can no longer download the report. For more information about error reports, see Reports.

  16. Step 9: Summary
    1. This step lists the following configured options for this task.
      • Name - Specify a name for the task. The default name is Migrate SharePoint Contents Task.
      • SharePoint objects selected - number of SharePoint objects selected for migration.
      • Migration Scope - selected migration scope.
      • Include site level term groups from Term store - whether or not the site level term group from the Term store should be included in the migration.
      • Default target user - UPN of the default target user if the source user cannot be matched to a target user.
      • Clear selected objects from target - whether or not the target site collection are deleted if it exists is the target tenant.
      • Upgrade classic team sites - whether or not classic team sites are migrated to modern team sites.
      • Migrate permissions - whether permissions are migrated or migrated objects will inherit permissions from their parent.
      • Migrate permissions only - whether or not permissions are migrated for previously migrated webs and lists.
      • Migrate Sharing Links permissions - how Sharing Links permissions are migrated.
      • List migration - choice between migration of all list items or migration of incremental changes with a refresh.
      • Conflict Resolution migration action - how version conflicts are resolved. Indicates the suffix if a copy of migrated list items are created.
      • Migrate list and library comments - whether or not list and library comments should be migrated.
      • Migrate list item and document versions - version option selected.
      • Scheduled start - expected start time of the task.
      • Reporting - option to collect and retain data for report generation.
      • Priority - the priority of this task.
    2. Click Back to change configurations if necessary or click Finish to save and start the task as scheduled.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级