Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migration Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Hybrid Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Provisioning Groups

After all source Office 365 groups without Teams functionality are discovered you can start to provision groups on the target tenant.

Make sure that all associated accounts are matched or migrated in account migration project and create the Provision task:

  1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
  2. Click M365Groups widget.
  1. Select the Office 365 groups to be provisioned on the he target. Provisioned groups will be owned by target Azure AD administrative account and with account matched with source group owner in case this account exists. The target Azure AD administrative account also will be added to the provisioned group as a member along with the members matched with source group members. In case any matched account cannot be found on the target, this account cannot be processed and related event will be reported.

TIP: Use search and filtering to quickly navigate through the list of groups.

  1. Click Provision.
  1. Select whether automatic Group Welcome Message will be suppressed to avoid disturbing users by automatic Microsoft messages about adding to the provisioned groups. However, suppressing these messages results in performance degradation due to issues with Microsoft’s synchronization behavior. We recommend do not suppress these messages to avoid issues related to synchronization.
  2. Schedule when the task will be started. See Task Scheduling for details.
  1. Click Next to view the task summary. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

The provision task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

Migrating Groups and Associated Content

  1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
  2. Click Teams widget.
  1. Open M365Groups and select the groups with provisioned state you want to migrate. Migration will be skipped for all groups that are not yet provisioned

TIP: Use search and filtering to quickly navigate through the list of groups.

  1. Click Migrate. Group Mailbox and Calendar will always be migrated. This option cannot be cleared.
  2. Select whether to migrate associated SharePoint sites including all related content..
  3. Select whether to migrate Planner including all related content. This option is selected by default.
  4. Schedule when the task will be started. See Task Scheduling for details.
  5. Click Next to view the task summary. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

The migration task is created. Consider, additional content migration task will be also created automatically to transfer all associated content. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

Troubleshooting

Before you contact Quest support is recommended to prepare organization ID, project ID and task ID

To find Task ID and Project ID

In Events grid right click task link in Task Name column and select Copy link address. Copied link contains the Task ID and the Project ID.

To find organization ID

If you are trying to find an existing On Demand organization ID that another users have created, make sure that they have added your email address under Access Control > Administrators.

  1. In case you are Administrator of the organization, click your account in top right corner to open the account related menu.
  2. Click the organization name. You can see Organization ID in Manage Organization dialog.

Special Cases

Table 1: Special Cases

Feature Event Root cause Workaround
Microsoft Teams Migration Cannot find the group '{Group ID}' on the source. Try to check whether the group exists using PowerShell cmdlet 'Get-UnifiedGroup' as described in the documentation Group associated with the team not found

Use the following PowerShell script and the group ID provided by the error message to get the group name:

   Install-Module PowerShellGet -Force Install-Module -Name ExchangeOnlineManagement
 $UserCredential = Get-Credential
 Connect-ExchangeOnline -Credential $UserCredential
 Get-UnifiedGroup -Identity "b1552bc6-f932-4ac9-a4f2-24a5d2da2eed" | Format-List DisplayName,Id

If this is a source group, fix your source data before proceed for migration.

If this is a target group, check if this group exists in target. If this group exists, please contact our support. If this group doesn't exist, remove this group associated team from target, and re-run provision and migration.

Finalizing the Migration

Congratulations! The migration is complete.

If you have created a temporary account for the migration (as recommended in Before you Start section), it is time to remove it. This account has elevated permissions, so it might pose security risks.

Microsoft Teams Migration

Azure Ad Administrative Accounts added to all source and target teams respectively as members and/or owners ,can now be removed. For instruction on how to remove this temporary account refer to the following Microsoft documentation. Suggested Remove-TeamUser command removes an owner or member from a team, and from the unified group which backs the team.

IMPORTANT:The Remove-TeamUser command will return immediately, but the Teams application will not reflect the update immediately. The Teams application may need to be open for up to an hour before changes are reflected.

Related Documents