Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration Current - Administrator Guide

About On Demand Migration Signing up for Quest On Demand Before You Start Working with On Demand Migration Starting a Migration Project Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Collections

SharePoint sites, webs and lists can be grouped in collections.

To gather a site and all its children into a collection

  1. Add the site to a collection.
  2. Run the Discover SharePoint Contents task for the site.

For known issues, see https://support.quest.com/technical-documents/on-demand-migration/current/release-notes#SharePoint

 

Exporting Site Collection Mapping

To export site collection mapping into comma-separated values (CSV) file for analytics or archival purposes open SharePoint Contents on SharePoint migration Dashboard, select site collections to export and click Export.

Output CSV file will contain mapping data for discovered and matched (migrated) site collection URLs.

Removing Sites from the Migration Project

You can temporarily remove any source site collections from the migration project, if necessary. Consider, site collections cannot be removed permanently from the migration project, all existing source site collections will be added in after next discovery.

To temporarily remove sites from the migration project:

  1. Go to the migration project Dashboard.
  2. Click SharePoint widget.
  3. Open SharePoint Contents and select the items you want to remove from the migration project.
  4. Click More Actions | Delete
  5. Click Delete to confirm the action.

Microsoft Teams Migration

On Demand Migration for Teams securely migrates Microsoft Teams and associated Office 365 groups across Office 365 tenants. You can also use this dashboard for migration of content for Microsoft Office 365 groups without Teams functionality. (Content Migration for Office 365 Groups). Microsoft Teams migration requires additional licensing.

IMPORTANT: In case you use classic product UI, the Account Migration project for your source and target tenant should exist before migrating Teams. Account matching /migration should be completed.

Basic Microsoft Teams migration workflow consists of the following steps:

# Step
1 Create Microsoft Teams migration project (created automatically with New Migration UI)
2

Grant necessary permissions in case these permissions are not already granted (Prerequisites)

IMPORTANT: It is not recommended to use existing user accounts as source and target Azure AD administrator accounts, because it is recommended to remove them for safety reasons after the migration will be completed. These accounts can be removed from teams as described in Finalizing the Migration.

3

Discover teams/groups on the source tenant

On this step you can see names, suggested for target teams. In case you need some changes use manual mapping as described below. There are no provision on the target on this step.

TIP: Organize teams in collections to streamline the provision and migration process

4 Export teams mapping to CSV file
5

Map teams manually using exported CSV file

You can use manual mapping to migrate source team to the target team with another name. If the channel do not exist, it will be provisioned. Also you can use manual mapping to merge several source teams to one target team.

6

Create Office 365 groups and Provision teams on the target tenant. Target teams will be owned by the target Azure AD administrator account that is used to perform the provisioning.

  • Source Azure AD account will be added to all source teams as an owner, to all source Office 365 Groups as a member, and to all source private channels as an owner
  • Target Azure AD account will be added to all target teams and Office 365 Groups as a member and an owner, and to all target private channels as an owner

These accounts can be removed from teams as described in Finalizing the Migration.

7

Migrate teams

Migrate / merge all conversations (including inline content) from the source to target channels.

  • Target Azure AD account will own all private channels migrated to the target.
8 Re-migrate teams to incorporate supported changes made after the migration task (step 7) was started.
9 Monitor the progress and track issues
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating