Before you start, verify that you have provisioned all the Microsoft 365 groups without teams. See Provisioning Groups for more information. Migration will be skipped for all groups that are not yet provisioned.
Considerations
- When groups are migrated, the account that is assigned the Migration Manager role is added to the group. If dynamic membership is enabled, the rules are modified to include this account. This temporary role is required for migrating groups by the On Demand Migration service.
- The migration service performs a full comparison during a remigration between the source and target, ensuring that messages are not moved or deleted, and folders are not moved, renamed, or deleted in the target.
Starting a Microsoft 365 Groups Migration Task
- Log in to Quest On Demand and choose an organization if you have multiple organizations.
- From the navigation pane, click Migration to open the My Projects list.
- Create a new project or open an existing project.
- Click Teams from the project tiles. Click Open from the Teams tile to open the Teams dashboard.
- Click theM365 Groups tab.
- Select one or more groups from the Groups List View that are provisioned (State = Provisioned)
- Click Migrate. The New Groups Migration Task wizard opens.
- Step 1: Migration Options
- Group mailbox - Select this option to migrate Group Mailbox.
- SharePoint Content - Select this option to migrate associated SharePoint sites including files, One Note, OneDrive Shared Library and other supported tools.
- Planner - Select this option to migrate the group Planner.
- Group Membership - Select this option to migrate group members. If this option is not selected, group members will not be migrated.
- Step 2: File Version Options
- Choose the migration option for file versions associated with groups selected for migration.
- 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.
- 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.
- 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.
- Click Next.
- Choose the migration option for file versions associated with groups selected for migration.
- Step 3. SharePoint Permission Options
- 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.
- Click Next.
- Select how Sharing Links permissions are migrated. Direct permissions are always migrated.
- Step 4. SharePoint File Options
- Choose from the following options to determine how changes to 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.
- Migrate all list items - all list items are remigrated.
- Choose a conflict resolution option.
NOTE:
- Conflict resolution rules are applied only to list items that have been previously migrated.
- Conflict resolution rules will not be applied if the Migrate all list items 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 migrate 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.
- 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.
- Auto re-run list item migrations to retry missing items - select this option to automatically re-run the list item migration during list migrations to retry and repair missing items.
- Click Next.
- Choose from the following options to determine how changes to list items that were previously migrated should be remigrated:
- Step 5: Notification
- Send notification email once the task is completed - select this option to send a notification email when a migration task completes.
- Only in a case of failure - select this option to send the email if the migration task fails to complete successfully.
- Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
- Click Next.
- Send notification email once the task is completed - select this option to send a notification email when a migration task completes.
- Step 6: Reporting
Select the check box Generate detailed report of migration errors to generate a migration error report when you run the migration task.
You can download the report from the Reports tab of the Teams migration 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.
- Step 7: Schedule
- 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.
- Click Next.
- Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
- Step 8: Summary
- Verify the task specifications as described below:
- Name - Name of the task. The default name is Migrate Groups. You can specify a custom name.
- Source tenant - Name of the source tenant in this project.
- Target tenant - Name of the target tenant in this project.
- Scheduled start - Date and time when the task will start. Now indicates that the task will start immediately.
- Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
- Verify the task specifications as described below:
The migration task is created. You can track its progress from the Tasks tab, view the summary on the Dashboard or monitor alerts and notifications from the Events tab.
|
NOTE: If a group from the source tenant is merged with a group in the target tenant during the provision process, any new mail items, SharePoint files and Planner items that are generated in the source tenant will appear in the target group. |