Quest® On Demand Migration

User Guide
© 2023 Quest Software Inc. ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written
permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by
estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest
Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE
AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY
EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO
EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR
INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS
INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN
IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no
representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the
right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any
commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

See our Web site (https://www.quest.com) for regional and international office information.
Patents
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current
information about applicable patents for this product, please visit our website at https://www.quest.com/legal.
Trademarks
Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete
list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx. All other trademarks and registered
trademarks are property of their respective owners.
Legend
CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions
are not followed.

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

On Demand Migration User Guide

Updated - September 2023
Contents

About On Demand Migration 7

Accounts and User Data Migration> 7
Content Migration 7
Signing up for Quest On Demand 8
Product Licensing 8
Organizations and Regions 12
Roles 14

Working with On Demand Migration 18

Migration steps 18
Tenants 18
Consents and Permissions 20
Upgrading Throttling Policies 24
Desktop Update Agent 25
Test and Pilot Migrations 25
Project Management 25
Project Dashboard 37
Reports 39
Task Management 40
Event Management 44
Searching 44
Filtering 45

Account Migration 48
What We Migrate 48
Accounts and User Data Workspace 50
Configuring Connections 54
Discovering Accounts 55
Exporting Accounts 64
Removing Accounts 64
Managing Accounts with Collections 65
Assessment 69
Matching Accounts 70
Migrating Accounts 76
Domain Coexistence 80
Address Rewrite Service 81
Address Rewrite Service Considerations 85

On Demand Migration User Guide 3

 Address Rewriting Scenarios 85
Rewriting senders’ address to the target address 86
Rewriting senders’ address to the source address 86
Provisioning the Address Rewrite Service 86
Selecting Mailboxes for Address Rewriting 87
Configuring SPF Record 87
Activating Address Rewriting 87
Deactivating Address Rewriting for Individual Mailboxes 87
Deactivating Address Rewriting 88
Calendar Sharing 88
Resource Processing 88

Mailbox Migration 94
What We Migrate 94
Collecting Statistics 96
Create a Mailbox Collect Statistics Task 96
Review the Mailbox Collect Statistics Task 97
Review the Mailbox Collect Statistics Task Events 98
Review the statistics collected 99
Assessment 99
Migrating Mailboxes 100
Migrating Meeting Links 107
Mail Forwarding 108
Switching Applications in a Domain Move Scenario 111

OneDrive Migration 112

What We Migrate 112
Dashboard 114
OneDrive List View 114
Collecting Statistics 116
Starting a OneDrive Collect Statistics Task 117
Reviewing the OneDrive Collect Statistics Task 119
Reviewing the events for the OneDrive Collect Statistics Task 120
Reviewing the statistics collected 121
Migrating OneDrive 122
Assessment 136

Microsoft Teams Migration 140

What We Migrate 141
Prerequisites 149
Teams Workspace 151
Discovering Teams 158
Discovering Teams and Groups 163
Managing Teams with Collections 169

On Demand Migration User Guide 4

 Exporting Teams 173
Mapping Teams 173
Provisioning Teams 177
Removing Teams 180
Collecting Statistics 181
Premigration Assessment for Teams 184
Migrating Teams 185
Remigration 192
Discovering Chats 193
Managing Chats with Collections 197
Migrating Chats 199

Microsoft 365 Groups Migration 208

What We Migrate 208
Prerequisites 209
Discovering Groups 211
Discovering Teams and Groups 217
Managing Groups with Collections 223
Exporting Groups 227
Mapping Groups 227
Provisioning Groups 231
Removing Groups 233
Collecting Statistics 233
Migrating Groups 236

SharePoint Migration 241

What We Migrate 242
Limitations 248
Considerations 249
Prerequisites 250
Dashboard 250
Configuring the Migration Project 252
Discovering Site Collections 254
Managing Sites with Collections 257
Discovering Site Contents 260
Mapping Geo Locations 263
Mapping Sites 265
Matching Sites 270
Mapping Webs 272
Mapping Lists 274

On Demand Migration User Guide 5

 Migrating SharePoint Objects 277
Reviewing Migration Results 286
Exporting Site Collection Mapping 288
Removing Sites from the Migration Project 288

Public Folders Migration 289

What We Migrate 289
Dashboard 290
Prerequisites 290
Discovering Public Folders 291
Removing Public Folders from the Migration Project 294
Migrating Public Folders 294

Troubleshooting 295

Finalizing the Migration 296

Removing the temporary account from Teams 296

Appendix A: Working with PowerShell 297

Deploying the ODM PowerShell Module 297
Connecting to the ODM service 297
Selecting the organization and migration project 299

About us 301
Technical support resources 301

On Demand Migration User Guide 6

 1

About On Demand Migration

Quest® On Demand Migration cloud application lets you create migration projects to perform the following:

Accounts and User Data Migration>

l Analyze the structure of your Microsoft Azure Active Directory and get reports on the problems that
might adversely affect the migration.
l Migrate users, groups, and the related information between tenants.
l Migrate hybrid accounts synchronized with on-premises AD
l Map the existing accounts in the source and target tenants for further resource processing.
l Grant migrated accounts access to source tenant’s resources and applications.
l Provide robust project management interface and in-depth progress reporting.
l Provide coexistence services for transition period before migration process will be completed:
l Address Rewrite Service to change the message header as if the target mailbox is already
used by sender.

Mail migration

l Migrate Microsoft 365 mailboxes and share free/busy information between tenants.

Content Migration
OneDrive for Business

l Analyze OneDrive for Business on your source tenant

l Transfer OneDrive for Business data and settings.

Public Folders

l Analyze Public Folders on your source tenant and get hierarchy information, content information and
email addresses for mail-enabled public folders
l Migrate Public Folders and the related information between tenants
l Provide robust Public Folders migration management interface and in-depth progress reporting.

Microsoft SharePoint

On Demand Migration User Guide

About On Demand Migration 7
 l Analyze SharePoint on your source tenant
l Map existing SharePoint sites (previously site collections) in the source and target tenants for
further processing
l Migrate SharePoint sites (previously site collections) to the target tenant
l Provide robust SharePoint migration management interface and in-depth progress reporting.

Microsoft Teams

l Analyze Microsoft Teams on your source tenant

l Create Microsoft 365 Groups with Teams functionality on the target tenant
l Provision Microsoft Teams on the target tenant
l Migrate Microsoft teams including content to the target tenant
l Provide robust Microsoft Teams migration management interface and in-depth progress reporting.

On Demand Migration is a part of Quest On Demand – a single SaaS console for managing your cloud environment
in Microsoft Azure. For more information, see Quest On Demand documentation.

Signing up for Quest On Demand

To get access to On Demand Migration, you need to sign up for the Quest On Demand service. Go to Quest On
Demand and use one of the following options:

l Sign up using the existing Quest account (http://support.quest.com/technical-documents/on-demand-

global-settings/current/user-guide/signing-up-for-quest-on-demand)
l Create a new Quest account and sign up for Quest On Demand (http://support.quest.com/technical-
documents/on-demand-global-settings/current/user-guide/signing-up-for-quest-on-demand/signing-up-
and-adding-users-to-your-organization)
l Join an existing On Demand organization (https://support.quest.com/technical-documents/on-demand-
global-settings/current/user-guide)

You must accept the Software Transaction Agreement before using this product.

Product Licensing
IMPORTANT: Your Azure subscription must have an E3 or E5 enterprise plan. For more information see
Microsoft 365 Enterprise plans.
Use of this software is governed by the Software Transaction Agreement found at www.quest.com/legal/sta.aspx
and the SaaS Addendum at www.quest.com/legal/saas-addendum.aspx. This software does not require an
activation or license key to operate.
You can sign in to On Demand as a Guest user and review the solutions that the product offers. As a Guest user,
you can add your Azure AD tenant and look for problems that can be solved by On Demand. To sign in as a Guest
user, go to quest-on-demand.com and click Continue as Guest.
Trial subscriptions are available. Visit Quest® On Demand Migration page for more information and
pricing: https://www.quest.com/products/on-demand-migration/
In this topic:

On Demand Migration User Guide

About On Demand Migration 8
 l Starting a trial subscription
l Purchasing a commercial subscription
l Viewing the license report
l Exporting licenses consumption data
l Searching for licenses consumed
l Viewing the license summary

To start a trial subscription

NOTE: You can use the product free during the 30-day trial period with a limited number of users that can be
migrated.

1. Open https://www.quest.com/products/on-demand-migration/.
2. Scroll down to the module you want to try and click Try Online.
3. To proceed you should read and accept license agreement.
4. Select Sign In for your Free Trial option to use your existing Quest account, or Create a Trial account
option to create a new account.
5. You will receive an email containing step by step instructions on starting your trial period for the product.

The following table shows the trial license limits:

Feature License Limitation

Accounts 5 Accounts none

Email 5 Mailboxes 5 GB content per mailbox

OneDrive 5 Accounts 256 files or 256 MB per OneDrive account

SharePoint 5 SP sites 5 GB content per SharePoint site. ODMSP will not discover sites with
more than 5 GB.

Teams / M365 5 Teams or 5 GB content per Teams or M365 Groups

Groups Groups

1x1 Chats 5 Accounts The most recent 2 conversations and messages up to 30 days per
conversation

To purchase a commercial subscription

1. Open https://www.quest.com/products/on-demand-migration/.
2. Click Request Pricing and fill in the necessary details.
3. Click Contact Sales to request pricing and get help with your business needs.

The product licensing is based on the number of unique source accounts processed by the migration tasks. The
licenses are only consumed once the migration task is started.
The following object types do not consume any license,

On Demand Migration User Guide

About On Demand Migration 9
 l Group mailboxes
l AD Groups
l Contacts
l Exchange resource mailboxes
l public folder mailboxes
l room mailboxes or equipment mailboxes
l shared mailboxes
l Guest accounts
l Computer accounts

NOTE: The license is permanently assigned to the source account may only be used for one migration
project, and you can use this account in any number of tasks (migration, re-matching, etc.) from one
environment to another environment.
The matching task will result in the error message shown in the image below, in case the number of users in
the task exceeds the number of available licenses.

For commercial licenses, there are no content migration data limits for OneDrive, SharePoint, mailbox and
public folders.

To view the license report

License consumption data is available as you work through your migration project.
NOTE: License data before October 18th 2022 displays only the Licensed user email and the
corresponding Consumed On column value indicates the date when the data was uploaded.

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 migration dashboard. You must create at least one
project to view the dashboard.
3. Click View License Report to open the License Report workspace.
4. Click List View to open the list of consumed licenses. The columns in the table are as described below:
l Consumed On - date and time the license was consumed.
l Signed-in user - user name of the person who consumed the license.
l Licensed user email - User Principal Name (UPN) of the signed-in user
l Task name - name of the task that consumed the license.

On Demand Migration User Guide

About On Demand Migration 10
 l Task type - type of task that consumed the license
l Project - name of the project where the license was consumed.
5. Click Edit Columns to show or hide columns in the list.

To export licenses consumption data

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 migration dashboard. You must create at least one
project to view the dashboard.
3. Click View License Report to open the License Report workspace.
4. Click List View to open the list of consumed licenses.
5. Select the rows that you want to export. Then click Export. A CSV file will be downloaded to your default
download folder.
6. Open the downloaded CSV file to view the exported information.

To search for licenses consumed

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 migration dashboard. You must create at least one
project to view the dashboard.
3. Click View License Report to open the License Report workspace.
4. You can search for consumed licenses in two ways:
5. Use the following predefined filters:
a. License Consumption - filters the list based on the following consumption periods: Last 7 days,
Last 30 days, All
b. Task Type - filters the list based on the selected task type. The following values are available:
Account Migration, Mail Migration, OneDrive Migration, Teams, Chats, All

-or-

c. Enter the full or partial name of the user in the search field. Click Search. The list of licenses
consumed by the user is displayed.

To view the license summary

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 migration dashboard. You must create at least one
project to view the dashboard.
3. Click View License Report to open the License Report workspace.
4. Click Summary to open the summary view of consumed licenses.
5. The two report tiles contain the following information:
a. Licenses Consumed
l Last 7 days - number of licenses consumed in the previous 7 days.
l Last 30 days - number of licenses consumed in the previous 30 days.

On Demand Migration User Guide

About On Demand Migration 11
 l All - total number of licenses consumed.
b. Licenses
l Total ODM licenses - total number of licenses from active migration subscriptions only.
l Used ODM licenses - total licenses used that include active and expired migration
subscriptions.
l Total Teams only licenses - total Teams migration licenses from active migration
subscriptions only.
l Used Teams only licenses - total Teams licenses used that include active and expired
migration subscriptions.
l Reserved by matches - number of licenses reserved but not consumed after accounts in
the source tenant are matched with accounts in the target tenant. You can release the
reserved licenses when you unmatch the accounts using the Clear matching task.

Organizations and Regions

When you sign up for the On Demand service for the first time, you create an organization and you are granted the
On Demand Administrator role. You can add additional organizations and administrators.
For more information about managing your organization see Managing organizations and regions in the On
Demand Global Settings User Guide.
Some common actions with Organizations are reproduced here for your reference:

l Creating an organization
l Switching to another organization
l Renaming an organization
l Deleting an organization

Creating an organization
1. Sign in to Quest On Demand using the credentials you used to sign up for On Demand.
2. If you have not yet created an organization, click Create Organization.

If you have created one or more organizations, the Choose an Organization page opens. Click Create New
Organization.
If you have already selected an organization, click your email address at the top right-hand corner of the
page and the select Create Organization.

On Demand Migration User Guide

About On Demand Migration 12
 3. In the Create Organization page, specify the following information:
l Organization Name - name of your organization. For example, Big Box Inc.
l Deployment Region - A Microsoft Azure region or geographic area where data centers are
deployed. Not all On Demand modules are available in all regions.
4. Click Create Organization.

Switching to another organization

If you have multiple organizations associated with your email address, you can select an organization from the
Choose an Organization page when you sign in. If you have already selected an organization but want to work with
another organization, you can switch to another organization.

1. Click your email address at the top right-hand corner of the page.
2. Select Switch Organization. The Choose an Organization page opens.
3. Highlight and click the organization to which you want to switch.

Renaming an organization
You can rename the organization to which you are currently signed in. You must be an On Demand Administrator to
rename an organization.

1. Sign in and select the organization that you want to change.

2. Click your email address at the top right-hand corner of the page.
3. Click the organization name. The Edit Organization page opens.
4. In the Organization Name field, enter the new name.
5. Click Update Organization Name. The organization name is updated.

Deleting an organization
CAUTION: Deleting an organization cannot be undone.

1. Sign in and select the organization that you want to change.

2. Click your email address at the top right-hand corner of the page
3. Click the organization name. The Edit Organization page opens.
4. Click Delete Organization. A confirmation page opens.
5. Select the following checkboxes to confirm that you understand the impact of deleting an organization.
l All tenants will be removed
l All user information will be lost
6. Click Delete Organization.

On Demand Migration User Guide

About On Demand Migration 13
Roles
Quest On Demand uses the Role-based Access Control (RBAC) security policy that restricts information system
access to authorized users. Subscribers can create specific roles based on job functions, with the permissions to
perform needed operations on the assets of the organization. When users are assigned to On Demand roles, they
inherit the authorizations or permissions defined for those roles. RBAC simplifies permission administration for
subscribers because permissions are not assigned directly to every user (which can be a significant number of
individuals for mid- to large-size organizations) but are instead acquired through role assignments.
The following are some key Quest On Demand and tenant roles that you will need to work with On
Demand Migration.

On Demand Administrator
This role is assigned to users who have full access to the Quest On Demand application. They can manage
organizations and tenants, initiate the migration of tenant assets, manage licenses, audit records and perform many
other functions through the Quest On Demand application. Some of the key permissions associated with this role
are as follows:

Permission Description Service

Scope

Create, Rename and Delete Required permission to create, rename and delete migration On Demand
projects projects from the Projects Dashboard Migration
View projects and manage This permission must be select to activate the individual On Demand
selected services permissions to view and manage services. Services selected for Migration
this permission will be inherited by all child permissions
View projects Required permission to be able to view objects tasks and events On Demand
for the selected services. Only the tiles for the selected services Migration
will be shown in the project dashboards.
Always inherited from parent permission

Edit project properties Permission to edit properties associated with project services. E.g On Demand
Enables access to Accounts Configure Connections and Migration
SharePoint Configure Project.
Run a full discovery Permission to enable the action that allows users to run the task Accounts,
that will discover all available objects. Teams,
SharePoint,
Public
Folders
Run a scoped discovery Permission to enable the actions that allows users to run the task Accounts,
with CSV file that will discover objects based on a list contained in a prepared Teams,
SharePoint
CSV file.

Run a scoped discovery Permission to enable the actions that allows users to run the task Accounts
from security group that will discover objects based on selected security group.
Run content discovery tasks Permission to enable the actions that allows users to discover Mailboxes,
content and statistics about selected objects. OneDrive,
SharePoint
Run match and map tasks Permission to enable the actions that allows users to find Accounts,
matching objects on the target for selected objects and to map Teams,

On Demand Migration User Guide

About On Demand Migration 14
 Permission Description Service
Scope

objects on source and target based on prepared CSV file. SharePoint

Run provision and migration Permission to enable the actions that allow user to provision and Accounts,
tasks migrate selected objects to the target. Mailboxes,
OneDrive,
Teams,
SharePoint,
Public
Folders
Manage collections Permission to enable actions for creating and manage the Accounts,
Collection feature. Mailboxes,
OneDrive,
Teams,
SharePoint,
Public
Folders,
Desktop
Update Agent
Update and delete Permission to enable the action that allows the user to remove Accounts,
migration objects selected objects form the list of services object grid. Mailboxes,
OneDrive,
Teams,
SharePoint,
Public
Folders,
Desktop
Update Agent
Acknowledge and clear task Permission to enable the action that allows the user to Accounts,
events acknowledge and clear events from the Events grid. Mailboxes,
OneDrive,
Teams,
SharePoint,
Public
Folders,
Desktop
Update Agent

Manage Desktop Update Permission to enable all management actions in Desktop Update Desktop
Agent Agent. Update Agent

On Demand predefined roles

Quest On Demand is shipped with many predefined roles. On Demand Administrator, Migration Administrator, Audit
Administrator, License Management Administrator and Recovery Administrator are some examples.

On Demand custom roles

You can create more roles with specific permissions to allow other users to work with On Demand Migration. See
the On Demand Global Settings Current User Guide for more information about setting up roles.

On Demand Migration User Guide

About On Demand Migration 15
Tenant Administrator
In this document the term Tenant Administrator refers to the Azure active directory user account for the source or
target tenant that is assigned the Global administrator security role and has full access to the tenant. Each tenant
that you add to a project requires the credentials of the Tenant Administrator. The Tenant Administrator may require
additional roles to grant the necessary consents to various On Demand service principals that are created in the
tenant to access various assets in the tenant during the migration lifecycle. See Consents and Permissions for more
details. For more information about user and service principals see the Microsoft article Application and service
principal objects in Azure Active Directory.
Tenant Administrator accounts must have a mailbox with a valid Microsoft Exchange Online license.
To use On Demand Migration, the Tenant Administrator for each tenant in a project must grant Azure consents and
permissions to the On Demand Migration service principals.

Migration Manager
You can use a temporary tenant user account to operate on tenant assets. In this document the term Migration
Manager refers to the source or target Azure active directory user account that has temporary access to the tenant
through the Global administrator security role. Depending on the tenant asset that is being migrated, this
temporary user account must grant specific consents. For example, when teams are migrated, the account that is
assigned the Migration Manager role is added to the team. This temporary role is required for migrating teams by
the by the On Demand Migration service.
If you choose to work with this temporary account, you must login to the tenant as the Migration Manager and grant
the consents and permissions to the On Demand service principal.
When you are done with the migration, it is recommended that you delete the temporary account for security
reasons. See Finalizing the Migration for more details.

Multi-factor authentication
Multi-factor authentication (MFA) is supported for tenant administrators. For On Demand users, MFA support
depends on how your organization has set up your access.

If you sign-in with your email and password, MFA has not been activated. If you click Sign in with Microsoft, MFA
has been activated. If your organization requires multi-factor authentication and you receive an authorization error,
your conditional access policy may not be configured correctly. You can do one of two things:

On Demand Migration User Guide

About On Demand Migration 16
l Contact your IT administrator to deactivate MFA for during migrations.
l Contact "Azure Identity" support for help with configuring conditional access policies.

On Demand Migration User Guide

About On Demand Migration 17
 Working with On Demand Migration
On Demand Migration provides intuitive project management for migrating accounts and content from one tenant to
another. You can create a migration project that provides a full range of migration features, and track accounts and
content migration in one comprehensive migration project dashboard. You can create multiple migration projects
and use the My Projects list view for a summarized list of all your migration projects.

Migration steps
Stage # Step

1 Add source and target tenants

2 Grant consents
Preparation 3 [optional] Upgrade throttling policies, install a Desktop Update
Agent, plan a test or pilot migration

4 Create a migration project

5 Discover accounts

6 Match source accounts with the existing target accounts

Account migration
7 Migrate accounts

8 Start Address Rewriting for Domain Coexistence

9 Migrate mailboxes
Mailbox migration
10 Grant access to source user's resources to target users
OneDrive migration 11 Migrate OneDrive
Teams and Groups migration 12 Migrate Microsoft Teams and other Microsoft 365 Groups

SharePoint migration 13 Migrate SharePoint

Private Folders migration 14 Migrate Public Folders

15 Monitor the progress and track issues

Management 16 Finalize the migration

17 Troubleshooting

Tenants
Each On Demand migration project needs a source and target tenant. These are Commercial tenants. For users in
the United States deployment region, On Demand Migration offers two options depending on the type of Microsoft
365 tenant that you want to add:

l Commercial or GCC Tenant - choose this option if you want to add either a Microsoft 365 commercial
tenant hosted on the Azure public cloud or a Microsoft 365 GCC (Government Community Cloud) tenant

On Demand Migration User Guide

Working with On Demand Migration 18
 with moderate cyber-security and compliance standards hosted on the Azure Government cloud.
l GCC High Tenant - choose this option if you want to add a Microsoft 365 GCC High tenant with advanced
cyber-security and compliance standards like NIST 800-171, FedRAMP High and ITAR hosted on the Azure
Government cloud.

NOTE: When you create a migration project, a GCC or GCC High tenant can be used as the target tenant
only. Currently, only the On Demand Migration module supports GCC and GCC High tenants.
For more information about adding, removing and managing tenants, see Managing your Azure tenants and on-
premises domains in the On Demand Global Settings Current User Guide.

Adding a tenant
1. Log in to On Demand using the credentials you used to sign up for On Demand.
2. If you have multiple organizations you must select an organization. If you have a single organization it will be
automatically selected.
3. If there are no tenants in your organization, click Add Tenant.

-or-
In the navigation panel on the left, click Tenants. The Office 365 Tenants page opens. Then click
Add Tenant.

4. The Add Tenant page opens.

l If you are in the US region, you must select the type of tenant that you are adding:
l Click Add Commercial or GCC Tenant
- or -
l Click Add GCC High Tenant
You are redirected to the Azure sign in page.
l If you are in any region other than the US region, such as Europe, United Kingdom, Canada, or
Australia, you are immediately redirected to the Microsoft login page.

On Demand Migration User Guide

Working with On Demand Migration 19
 5. Enter your Azure AD Global Administrator credentials for the source tenant and click Next. A page opens

with the list of permissions that you are granting.

6. Click Accept to grant consent to the initial Core - Basic permission set to the On Demand service principal.
7. The Office 365 Tenants page opens with the tenant added as a new tile.
8. Repeat the steps to add a target tenant.

Consents and Permissions

The ability for On Demand service principals to access and operate with tenant assets requires explicit permissions.
The Tenant Administrator grants these permissions through consents.
Each tenant that is added has granted consent to the initial Core - Basic permission set to the On Demand service
principal. Additional consents are required to work with different features of On Demand Migration.

Granting Consent
1. Click Tenants from the navigation pane.
2. Select a tenant and click Edit Consents from the tenant tile.
3. Click Grant Consent or Regrant Consent for the permissions type.
4. Click Accept in the consents page.

On Demand Migration User Guide

Working with On Demand Migration 20
When you have granted the consents, you can verify that the service principals were successfully created in the
tenant. You must verify both source and target tenants.

1. Log in to the Azure admin portal.

2. Click Enterprise applications from the navigation pane. Then click All applications.
3. Filter the list if necessary and verify the list of service principals.

On Demand Migration User Guide

Working with On Demand Migration 21
This section lists the minimum consents and permissions required by the various On Demand Migration service
principals for managing tenants, Microsoft 365 objects and other migration services.

For initial tenant setup

Task Minimum consents and permissions

Add and configure Core-Basic consent from both Source and Target tenant administrator accounts.
tenants, and grant
Global Administrator role from both source and target tenant administrator accounts.
consent

For Account migration

Task Minimum consents and permissions

All tasks including Migration - Basic consent from both Source and Target tenant administrator
discover and migrate accounts.
accounts
Migrate hybrid accounts Global Administrator role for both Source and Target tenant administrator accounts.

Migrate Guest Users Guest Inviter role for both Source and Target tenant administrator accounts.

Process Resources Guest Inviter role for Source and Target tenant administrator accounts.

On Demand Migration User Guide

Working with On Demand Migration 22
For Mailbox migration

Task Minimum consents and permissions

All tasks Migration - Basic consent from both Source and Target tenant administrator accounts.

Migrate mailboxes Mailbox Migration consent from both Source and Target tenant administrator
accounts.
Migrate Public Folders Migration - Mailbox Migration consent from both Source and Target tenant
administrator accounts.
Exchange Administrator role for both Source and Target tenant administrator
accounts.
Owner permission for the root Public Folder of the target tenant must also be granted to
the target tenant administrator account.
IMPORTANT:You must provide explicit credentials using Configure
Connections.

For OneDrive migration

Task Minimum consents and permissions

All tasks Migration - Basic consent from both Source and Target tenant administrator accounts.

Migrate OneDrive Migration - SharePoint consent from both Source and Target tenant administrator
accounts.
Provision OneDrive SharePoint Administrator role for provisioning OneDrive on the target tenant.
IMPORTANT:You must provide explicit credentials using Configure
Connections.

For SharePoint migration

Task Minimum consents and permissions

All tasks Migration - Basic consent from both Source and Target tenant administrator
accounts.

Migrate SharePoint Migration - SharePoint consent from both Source and Target tenant administrator
accounts. The target tenant should already have the fully configured SharePoint with
the active license plan. See Prerequisites for details.

For Teams migration

Task Minimum consents and permissions

All tasks Migration - Basic consent from both Source and Target tenant administrator
accounts.
Migrate Teams and Mailbox Migration, Migration - SharePoint and Migration - Teams consents.
Microsoft 365 Groups
Global Administrator or Teams Administrator Azure AD role, and the
with Teams
functionality

On Demand Migration User Guide

Working with On Demand Migration 23
 Task Minimum consents and permissions

ApplicationImpersonation Microsoft Exchange Server role for both Source and

Target tenant administrator accounts. In addition to these roles, the tenant
administrator account that grants the consents to the Migration -Teams service also
requires the following:

l an active Microsoft 365 license

l Microsoft Teams app enabled within the Microsoft 365 license
l the account must remain active for the duration of the migration

If the Teams license check fails, verify that the source and target tenants are valid. Then run the PowerShell
commands in Quest KB article 337302 to confirm that the tenant administrator account used to grant consent has
TeamspaceAPI activated.

Upgrading Throttling Policies

Exchange Web Services (EWS) are throttled by Microsoft whenever large quantities of data flows through the EWS
platform. The On Demand Migration service throughput can be improved by upgrading the following throttling policy
parameter setting to Unlimited:

l EwsMaxBurst - Defines the amount of time that an EWS user can consume an elevated amount of
resources before being throttled. This is measured in milliseconds. This value is set separately for
each component.
l EwsRechargeRate - Defines the rate at which an EWS user's budget is recharged (budget grows by) during
the budget time.
l EwsCutoffBalance - Defines the resource consumption limits for EWS user before that user is completely
blocked from performing operations on a specific component.

Tenant administrators can upgrade the throttling policies by making a service request with Microsoft.

On Demand Migration User Guide

Working with On Demand Migration 24
Desktop Update Agent
To complete a migration project, a lightweight user desktop application called Desktop Update Agent (DUA) must be
configured and deployed by administrators and run on users workstations. DUA provides enhanced support, helps
ensure the success of cross-tenant migration projects, makes agent delivery easier, and status reporting more
informative.
DUA features:

l Ability to manage user’s application reconfigurations activities from a single view within On
Demand Migration.
l Support for OneDrive for Business and Microsoft Teams.
l Support for Microsoft 365 application license reset.
l Support for various client authentication mechanisms.

For more information about downloading, administration and use of DUA, see the Quest On Demand Migration
Update Agent Guide.

Test and Pilot Migrations

Any full scale migration should be preceded by test and pilot migrations, to confirm that your migration processes
and procedures will accommodate the organization requirements.

l A test migration uses real users and real data in a segregated test environment, or dummy users and
dummy data in your live production environment.
l A pilot migration uses a small portion of real users and real data in the live production environment.

In either case - a test or pilot migration - the data to be migrated should be a representative sample of the production
data, and the test or pilot migration should be run with the Quest applications set for the same configuration and
process options that you intend to use for the production migration. it is recommended to select test or pilot users
whose usage and data types make them representative of the total user population. Then create and run matching /
migration tasks for those accounts, including all range of tasks you are planning to perform. When the tasks are
completed, review errors and warnings, if any. See Event Management section for more information.
Quest recommends that you use both test and pilot migrations:
Perform one or more test migrations in a separate test environment, migrating test copies of real users and their real
data. The separate test environment ensures that no test process will affect the data or configurations of your
production environment. If a test exposes any problems under migration, you can make amendments and then
repeat the test by simply dumping the test environment and recreating it from scratch.
When you are confident that your test migrations have sufficiently refined your planned migration, perform a pilot
migration for 20 or 30 users to verify if your planned migration is satisfactory for your "real world."

Project Management
A migration project contains the full set of migration features and provides a summary of all the migration activities in
the project dashboard. You can work with a single migration project for small migrations or you can set up multiple
migration projects to split larger migration plans into manageable projects.

On Demand Migration User Guide

Working with On Demand Migration 25
In this topic:
Try the new project management experience

l Creating a new migration project

l Renaming a migration project
l Deleting a migration project

Continue with the current project management user interface

l Creating a new migration project

l Renaming a migration project
l Deleting a migration project

On Demand Migration User Guide

Working with On Demand Migration 26
New project management user interface

To create a migration project:

1. Sign in to Quest On Demand.

2. From the navigation pane, click Migration to open the Migration projects view.

3. To use the new project management user interface, turn on the Try the new project wizard toggle.
4. Click Create Project.
-or-
If you have already created one or more projects, click Create Project as shown below.

5. The New Project wizard starts.

6. Step 1: Project Detail
Enter the information in the fields as described below:

a. Title - Specify a meaningful name for the project. Maximum number of characters is 128.
b. Description - Enter a description about the project. Maximum number of characters is 200.
c. Source Tenant - Select a source tenant from the dropdown list.

On Demand Migration User Guide

Working with On Demand Migration 27
 d. Target Tenant - Select a target tenant from the dropdown list.
e. Click Save and Continue.

7. Step 2: Assets

Select one or more assets from the set of information assets that you want to migrate. The Account asset is
mandatory because all other assets are directly or indirectly linked to active directory accounts in your
source and target tenants.
Each asset is treated as an application for migration purposes and automatically assigned a
service principal.

8. Step 3: Consents
Most Microsoft 365 objects can be migrated when the service principals for each asset have been granted
the consent. See Consents and permissions for more information.
To grant consent the service principals:

On Demand Migration User Guide

Working with On Demand Migration 28
 a. Click Grant Consent to grant the consents to the service principal if the tenant consents were not
granted when you added the tenants.

-or-
Click Regrant Consent to refresh the consents granted to the service principals. It is recommended
that you regrant consent to ensure that the consent to the service principals are refreshed.

b. Migration of some Microsoft 365 objects require a user principal with the Global Administrator or
other specific roles and you must provide additional authorization. Typically, the tenant administrator
credentials are provided. You can provide the credentials for authorization in an Features step.
Select Yes. Proceed to activate the Features step. Select No. Skip to ignore the Features step.

c. Click Save and Continue.

9. Step 4: Features
NOTE: This step is available if you select Yes. Proceed in the previous step.

To grant additional authorization with a source and target user principal:

a. Enter the email address of the target user accounts.

b. Enter the password of the target user accounts.
c. Click Save and Continue, or click Skip this page to avoid entering and verifying user
principal accounts.

On Demand Migration User Guide

Working with On Demand Migration 29
10. Step 5: Overview
a. Verify the information you have provided for each step. Click Edit to return to the step and revise the
information as needed.
b. Select Open Project to open the project dashboard.
c. Click Finish to activate the project.

On Demand Migration User Guide

Working with On Demand Migration 30
To rename a migration project:

1. Sign in to Quest On Demand.

2. From the navigation pane, click Migration to open the Migration projects view.
3. From the top right-hand corner of the project panel, click the More Actions icon (3 dots). Then click
Rename Project.
4. Revise the name or description as needed.

On Demand Migration User Guide

Working with On Demand Migration 31
 5. Click Save Project Name to save the changes and close the dialog.

To delete an existing project:

1. Sign in to Quest On Demand.

2. From the navigation pane, click Migration to open the Migration projects view.
3. From the top right-hand corner of the project panel, click the More Actions icon (3 dots). Then click
Delete Project.

4. Click OK to confirm the deletion.

On Demand Migration User Guide

Working with On Demand Migration 32
Current project management user interface

To create a migration project:

1. Sign in to Quest On Demand.

2. From the navigation pane, click Migration to open the My Projects view.

3. Click Create Project.

-or-
If you have already created one or more projects, click Create Project as shown below.

On Demand Migration User Guide

Working with On Demand Migration 33
4. Step 1: Select Source and Target

a. Project Name - Specify a meaningful name for the project. The default name is New
Migration Project.
b. Project Description - Enter a description about the project.
c. Source Tenant - Select a source tenant from the dropdown list.
d. Target Tenant - Select a target tenant from the dropdown list.
e. Click Save and Continue.
5. Step 2: Provide Admin Consent

On Demand Migration User Guide

Working with On Demand Migration 34
 Most Microsoft 365 objects can be migrated when the service principals (the On Demand Migration service
applications) have been granted the consent. To use the service principal:
a. Click Grant Consent to grant the consents to the service principal if the tenant consents were not
granted when you added the tenants.
b. Click Regrant Consent to refresh the consents granted to the service principals. It is recommended
that you regrant consent to ensure that the consent to the service principals are refreshed.
c. Click Save and Continue.

If you need to provision OneDrive accounts in the target tenant with the credentials of another user principal
with the SharePoint Administrator role you must provide additional authorization.
a. Enter the email address of the target administrator.
b. Enter the password of the target administrator.
c. Click Save and Continue.

6. Step 3: Project Created

a. Verify that permissions were granted
b. Open Project - select this option to open the project dashboard.
c. Click Finish and Close.

To rename a migration project:

On Demand Migration User Guide

Working with On Demand Migration 35
 1. Sign in to Quest On Demand.
2. From the navigation pane, click Migration to open the My Projects view.
3. From the top right-hand corner of the project panel, click the More Actions icon (3 dots). Then click
Rename Project.
4. Revise the name or description as needed.

5. Click Save Project Name to save the changes and close the dialog.

To delete an existing project:

1. Sign in to Quest On Demand.

2. From the navigation pane, click Migration to open the My Projects view.
3. From the top right-hand corner of the project panel, click the More Actions icon (3 dots). Then click
Delete Project.

4. Click OK to confirm the deletion.

On Demand Migration User Guide

Working with On Demand Migration 36
Project Dashboard
Information about the migration project is summarized on the project dashboard. The tiles that you can see and the
features that you can access through the project dashboard depend on your subscription. For information about
subscriptions, see On Demand Global Settings Current User Guide.

Each tile on this dashboard presents a summary of the migration activities and lets you navigate to the respective
migration service dashboards or list views as described below:

Welcome
Quick start your migration activities from this tile. The following activities can be performed here:

Grant Consent - If you see a green icon, you have granted the necessary consents to the source and target tenants
associated with this project. Otherwise the Grant link is displayed and you can click the link to complete the
authorization process for the source or target tenants.
Discover Accounts - If you see a green icon, you have already discovered one or more accounts in the source
tenant. Otherwise, click Discover to open the Accounts List view and start a discovery process.

On Demand Migration User Guide

Working with On Demand Migration 37
Match Accounts - If you see a green icon, you have matched one or more accounts between the source and target
tenants. Otherwise, click Select to open the Accounts List view and start a matching process. You must discover
one or more accounts before you can start the matching process.
Migrate Accounts - If you see a green icon, you have migrated one or more accounts from the source to the target
tenant. Otherwise, click Select to open the Accounts List view and start a migration process. You must match one or
more accounts before you can start the migration process.

Accounts, Mail, OneDrive and Teams

These tiles presents information about the objects that were discovered or migrated in addition to other pertinent
information. These objects are managed through the Account and User Data workspace and share a common
dashboard. Click Open from the Accounts, Mail, OneDrive, and Teams tiles to access the common dashboard.

Public Folders
Displays information about the discovered and migrated public folders. Click Open to access the dashboard in the
Public folder workspace.

SharePoint
This tile presents information about the discovered and migrated SharePoint objects. Click Open to access the
dashboard in the SharePoint workspace.

Active Directory
Click Open to access the Active Directory workspace for Microsoft 365 domain move service, directory
synchronization services for Microsoft Active Directory and Azure Active Directory, and other migration services for
Microsoft Active Directory.

Tasks
Displays the five most recent tasks that were completed in the Accounts and User Data workspace. Click Show All
to open the Tasks List view in the Accounts and User Data workspace.

Events
Displays the five most recent events that were completed in the Accounts and User Data workspace. Click Show
All to open the Events List view in the Accounts and User Data workspace.

On Demand Migration User Guide

Working with On Demand Migration 38
Reports
The Reports tab displays error reports for migration tasks. Each workspace has its own Reports tab.

About Error Reports

l The error report for a migration job is a CSV file with one or more rows. The maximum number of rows in the
CSV file is 50K. You can download a report by clicking the Download link in the Error Log column. If there
are no migration errors, a download link is not available.
l Error reports are retained for 30 days. You cannot modify this global setting. After 30 days the download link
is replaced with the label Expired and you can no longer download the report.
l You can select one or more reports and delete them with the Delete action. If the reports are active
when they are deleted, the row in the table will be removed and the report will be automatically purged
after 30 days.
l Access to reports are secured with Role Based Access Control (RBAC). For example, if you have access to
only Mail migration, the OneDrive reports are not visible.
l If a migration project is deleted, all associated data will be deleted, and any active reports will be purged
after 30 days.

The columns in the reports list are as described bellow:

l Start Time - the date and time the migration task was started.
l Completed Time - the date and time the migration task completed.
l Source Name - name of the source tenant.
l Target Name - name of the target tenant.
l Object Type - name of the asset that is migrated.
l Object State - the state of the migration. Values are: Migrated, Partially Migrated, Migrated
with Issues, Migration Failed and Migration Stopped.
l Processed Items - the number of asset items from the source tenant that were included in the migrattion.

On Demand Migration User Guide

Working with On Demand Migration 39
 l Failed Items - the number of asset items that could not be migrated successfully.
l Error Log - link to the report if available. If there are no migration errors, a download link is not available.
After 30 days the download link is replaced with the label Expired.
l Expiry Date - date and time when the report will expire.

Exporting Reports
l You can download a single report by clicking the Download link in the Error Log column. If there are no
migration errors, a download link is not available.
l You can select multiple rows and download the reports as a ZIP file when you click Error Log Export.
l You can select multiple rows and download the reports list when you click Export. Only rows are exported
but not the report CSVs.

Filtering the Reports List

You can use the following predefined filters to retrieve a subset of the reports:

l Object Type - name of the asset that is migrated.

l Object State - the state of the migration. Values are: Any, Migrated, Partially Migrated, Migrated
with Issues, Migration Failed and Migration Stopped.
l Has Failed Items: whether or not the migration has any failed items. Values are Yes or No. If there are one
or more items that match a Yes or No value, the number of items are indicated as well.

Task Management
In this topic:

l Viewing the task list

l Viewing task details
l Scheduling tasks
l Editing Tasks
l Stopping and restarting tasks

Viewing the task list

Each On Demand Migration dashboard has a Tasks tab.
Click the Tasks tab to see the Tasks list. The Tasks list displays all the tasks that are initiated throughout the
migration process. From the Tasks list you can:

l Track the progress of a task and view the results of finished tasks. When you select a task, the task details
pane appears and displays the details the detailed information and statistics of the task.
l Filter and search to quickly navigate through the list of tasks.
l Start, stop, and delete tasks.
l Edit tasks

On Demand Migration User Guide

Working with On Demand Migration 40
The columns in the Tasks list are as described below:

l Title - name of the task that is initiated. You can specify custom names for task when they are created from
the various task wizards.
l State - state of the task as it transitions from initiation to completion.
l Type - type of the task. For example, the following are some of the task types that are used in On Demand
Migration:

Account Mailbox OneDrive SharePoint

Discovery Mailbox OneDrive ProjectRefresh

Assessment Assessment
Matching Mail Migration OneDrive Migration DiscoverSiteCollections
Migration Mailbox Switch DiscoverSharePointContents

Resource Address Rewriting MatchSharePointContents

Processing
Map From File Meeting Link MappingFromFileSharePointContents
Migration
Assign ODM Calendar Sharing MigrateSharePointContents
License

l Created - date and time the task is started.

l Operation - description of what the task accomplished.

Viewing task details

The task details pane provides the following information:

l Name - name of the task used as the title of the details pane.
l Type - type of the task.
l Created - date and time the task is started.
l Modified - date and time the most recent operation in the task is performed.
l State - state of the task as it transitions from initiation to completion. Valid values are New, In Progress,
Failed, Stopped, Completed and Completed with Issues. The state of an object is set to Stopped when a
task is stopped by the user.
l Last Operation - most recent operation that the task accomplished.
l Schedule - how the task is started. The values are:
l Now - if the task is started immediately after the task wizard is completed.
l On Demand - if the task is started manually.
l <timestamp> - if the task is scheduled to start at a scheduled date and time.
l Events - number of events that occurred during the task.

On Demand Migration User Guide

Working with On Demand Migration 41
Click Copy Diagnostics to copy relevant task properties to the clipboard. You can then paste the properties in a
text file and provide the information to Technical Support for troubleshooting or use the properties in PowerShell
commands. The information that is copied to the clipboard is described below:

l Organization ID - unique identifier of the Quest On Demand organization.

l Deployment Region - Azure region code. Each Azure geography contains one or more regions that are
used for specific data residency and compliance requirements.
l Organization Name - name of the Quest On Demand organization.
l Project ID - unique identifier of the migration project.
l Task ID - unique identifier of the task.

Scheduling tasks
To optimize performance you can select schedule options for all tasks using Schedule page of task wizards. This is
reasonable for the task that may take a considerable amount of time. The following options are available:

l Run now - task runs immediately.

l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task, or use the date and time picker to set a date and time.

Editing tasks
From the Tasks list you can edit previously created tasks to reuse them in one of three ways:

l Editing a completed task

l Editing a running task
l Editing a task that has not started

Editing a completed task

You can edit a completed task. Depending on the schedule option selected you can:

l Automatically restart changed task in case Run now option is selected.

l Manually start changed task in case Run later option is selected. All changes will be applied after the task
is restarted.
l Schedule the start for the changed task in case Schedule option is selected. All changes will be applied
after the task is restarted.

NOTE: You cannot undo this operation after the wizard is finished to reset the edited task to initial settings.

Editing a running task

You can edit a running task to reuse or restart it. Depending on the schedule option selected you can:

On Demand Migration User Guide

Working with On Demand Migration 42
 l Automatically restart changed task in case Run now option is selected.
l Manually start changed task in case Run later option is selected. All changes will be applied after the task
is restarted.
l Schedule start for changed task in case Schedule option is selected. All changes will be applied after the
task is restarted.

NOTE:

l Your changes cannot affect the task that is currently running.

l You cannot undo this operation after the wizard is finished to reset the edited task to initial settings.

Editing a task that has not started

You can edit task in case it is not started to change your settings. Depending on the schedule option
selected you can:

l Automatically start changed task in case Run now option is selected.

l Manually start changed task in case Run later option is selected.
l Schedule start for changed task in case Schedule option is selected.

NOTE: You cannot undo this operation after the wizard is finished to reset the edited task to initial settings.

Stopping and restarting tasks

To stop a running task:

1. Open the On Demand Migration Tasks tab.

2. From the tasks list, click the running task. The Stop button is activated.
3. Click Stop.
4. A confirmation dialog appears. Click Stop

NOTE: The task may take a few minutes to change state.

To restart a stopped task:

1. Open the On Demand Migration Tasks tab

2. Select a task where the State is "Stopped". The Start button is now enabled.

On Demand Migration User Guide

Working with On Demand Migration 43
 3. Click Start.
4. A confirmation dialog appears. Click Start.

NOTE: The task will restart from the beginning using the same settings.

Event Management
Events list contains all notifications and alerts related to the environment configuration and migration process. It
allows you:

l View all events related to the migration process.

l If you are using new migration UI select an event to see details related to the event on the right pane.
l Hide certain alerts from the list by using Acknowledge option. This might be useful if you don’t want to be
distracted by the accidental warning or “expected” error.
l Explore details about selected events. See the details pane on the right pane of the screen for more details
and statistics for the selected event.
l Export selected events into comma-separated values (CSV) file for analytic or archival purposes.

TIP: Use search or filtering to quickly navigate to the points of interest.

Please consider the following:
Depending on selected migration options, the content is transferred in separate batches that can be submitted for
processing at the same time. It can take a while before processing of submitted batches will be completed. To help
tracking the migration, the status for batches that are processed will be reported approximately every 5 minutes.

Searching
The lists of accounts, mailboxes, tasks or events could be large and hard to manage. You cannot scroll past 10,000
items or rows in a view. Use the Search box above this list to look for items that match your custom criteria.

You can use words, phrases, and special queries in your search. The search is performed across all fields. You can
add search criteria to the search using facet filters on the left pane. Any filter can be cleared from the search by
clicking button. Press Enter to get the search results.

TIP: Add * to the end of the search query to match all items starting with the search term. Otherwise, you will
only get the exact matches. For example, john* returns John Doe, Johnson Smith, and john.doe. Search
expressions are case-insensitive.

On Demand Migration User Guide

Working with On Demand Migration 44
Advanced Search
You can refine your results by using the advanced search operators. See Lucene Tutorial for the full information on
search syntax.

To search Operators Examples Result

for

Part of a *serv* Matches items containing "serv".

word *

Exclude -, NOT (case- -mail* ( NOT Excludes items that contain the word starting with “mail”.
specified sensitive) mail*)
content
Include + +mail* Matches items containing “mail” along with the basic search
specified query.
content
Multiple Space, OR mail user, Matches items that contain either “mail” or “user” in case of OR.
keywords (case-sensitive), mail OR Matches items that contain both “mail” and “user”. in case of
AND (case- user, mail
AND. This is the default search behavior for phrases.
sensitive) AND user
Exact Quotation marks "item hard Matches items that contain the exact phrase "item hard
phrase deleted" deleted".

Search by Date Range

You can select period or use Custom range link to specify desired data range for events.

Filtering
You cannot scroll past 10,000 items or rows in a view. To see relevant records, you can quickly filter lists based on
the predefined criteria. The steps to filter a list is the same across all lists.

To apply a filter
Click one or more filters and select a value from the dropdown list.
Filters are applied immediately when selected. Each predefined filter also displays the count of items for each value
available in the dropdown list. These values take into consideration any other filter that is already applied. For
example, in the image above, there are 10 accounts in the Accounts list that have Status = New because the list has
already been filtered for Unmatched accounts of type User.

On Demand Migration User Guide

Working with On Demand Migration 45
To clear a filter
Click the X icon in the filter box to clear a single filter
-or-
Click Clear All to clear all filters.
The filters may be automatically applied, when you navigate across the interface. For example, navigate from
assessment reports, view details on the specific task, or click links in notifications.

On Demand Migration User Guide

Working with On Demand Migration 46
On Demand Migration User Guide
Working with On Demand Migration 47
 2

Account Migration
In this chapter:

l Accounts and User Data Workspace

l What We Migrate
l Preparation
l Configuring Connections
l Calendar Sharing
l Discovering Accounts
l Exporting Accounts
l Managing Accounts with Collections
l Assessment
l Migration
l Matching Accounts
l Migrating Accounts
l Post-migration
l Domain Coexistence
l

What We Migrate
The On Demand Migration service for Accounts migrates discovered user accounts and the following types of
discovered groups:

l Microsoft 365 Groups

l ownership (for accounts that have a pair on the target tenant )
l membership (for accounts that have a pair on the target tenant )
l email address for migrated Microsoft 365 Groups will be created in default target domain.
See Microsoft Teams Migration for details on how to migrate Microsoft 365 Groups
associated with Teams.

On Demand Migration User Guide

Account Migration 48
 l Security groups
l ownership (for accounts that have a pair on the target tenant )
l membership (for accounts that have a pair on the target tenant )
l Mail-enabled security groups
l ownership (for accounts that have a pair on the target tenant )
l membership (for accounts that have a pair on the target tenant )
l membership approval
l delivery management
l message approval
l MailTip
l group delegation
l visibility in GAL
l Distribution lists
l ownership (for accounts that have a pair on the target tenant )
l membership ( for accounts that have a pair on the target tenant )
l membership approval
l delivery management
l message approval
l MailTip
l group delegation
l SendAs and SendOnBehalf group delegates
l visibility in GAL

Migrating distribution lists with group delegations

On Demand migrates distribution lists with group delegations like SendAs and SendOnBehalf, including scenarios
where the distribution list in the target exists or does not exist, or exists and does or does not have group
delegations. When the distribution list with group delegations exists in the target then only newly added group
delegations are migrated, and group delegations are ignored if anything is deleted at the source. Existing SendAs
and SendOnBehalf group delegations on the target, either preexisting before On Demand migration or migrated by
On Demand will be left intact and merged with the one migrated from the source.
Delegated accounts are migrated as follows:

Mail User Mail Box Mail Enabled Security Distribution List

Group

SendAs Y Y Y
SendOnBehalf Y Y Y Y

On Demand Migration User Guide

Account Migration 49
 NOTE: Microsoft does not support the following delegated account types so they do not apply to the
migration.

l For SendAS: AAD User, External/Guest User, Distribution List, Security Group
l For SendOnBehalf: AAD User, External / Guest User, Security Group

NOTE:The temporary Migration Manager account of the target tenant will be added as an owner to all target
mail-enabled security groups, distribution groups and Microsoft 365 Groups.

Accounts and User Data Workspace

In this topic:

l Dashboard
l Accounts List View
l Accounts Assessment
l Account Details

Dashboard

The dashboard in the Accounts and User Data workspace is common for the Accounts, Mailbox and OneDrive
migration services. The components of the dashboard are as described below:
Notification panel - presents relevant information and shortcuts to migration activities.
Dashboard Menu - contains the following links to common activities in the migration process.

l Configure connections - You can configure granular permissions for the source and target tenants in
addition to advanced configurations such as concurrent PowerShell connections and custom EWS URL

On Demand Migration User Guide

Account Migration 50
 specification. For more information see .Configuring Connections
l Discover accounts - Starts the New Account Discovery Task wizard to collect information about accounts
in the source tenant. For more information see Discovering Accounts.
l Enable calendar sharing - Starts the New Calendar Sharing Task wizard to allow users to retrieve
calendar availability information after migration. For more information see Calendar Sharing.
l Browse accounts - Opens the Accounts List view where you can search and filter for accounts, and
manage all the account migration activities. For more information see
l Download agent - Allows you to download a lightweight user desktop application (update agent) for users
workstations that is needed to complete a migration project.

Dashboard Tiles

l Getting Started - Presents quick start links to the various actions for preparing and migrating accounts.
l Accounts - Presents a summary of the accounts in various migration states. Click Show All to open the
Accounts List view to inspect the accounts.
l Mailboxes - Presents a summary of the mailboxes in various migration states. Click Show All to open the
Mailboxes List view to inspect the mailboxes.
l OneDrive - Presents a summary of users with OneDrive in various migration states. Click Show All to open
the OneDrive List view to inspect the OneDrive information.
l Tasks - Displays the five most recent tasks that were completed in the Accounts and User Data workspace.
The title displays the total number of tasks. Click Show All to open the Tasks List view.
l Events - Displays the five most recent events that were completed in the Accounts and User Data
workspace. The title displays the total number of events. Click Show All to open the Events List view .

Accounts List View

The Accounts List View is comprised of the following components:

Notification panel - presents relevant information and shortcuts to migration activities.

On Demand Migration User Guide

Account Migration 51
Filter panel - consists of predefined filters for the Accounts List view and tabs to switch between the Accounts
List view and the Assessment view. SeeFiltering for more information about working with filters. The predefined
filters are:

l Account State - search accounts by specific state values. See Account State column description in the
List View below for a list of values.
l Matching - search for source accounts that are matched with a target account. Valid values are Any,
Matched and Not matched.
l Source Type and Target Type - search by specific account types as defined in Active Directory.
l Any
l User accounts like Guest, Mailbox-enabled, Mail-enabled and Non-mail-enabled.
l Resource mailboxes like Equipment, Room, Scheduled and Shared.
l Groups like Distribution, Mail-enabled-security, Microsoft 365 Group - Dynamic, Microsoft 365 -
Assigned, Security - Dynamic, Security - Assigned, Teams - Dynamic and Teams - Assigned.
l Environment - search by location of the Active Directory with which the account is synchronized. Valid
values are Synced with Active Directory (synchronized with on-premise Active Directory) and In Cloud
(synchronized with Azure Active Directory). This filter corresponds to the Sync Status column in the
Accounts list.
l ODM Licensed - search by license utilization. Valid values are Yes, No, Not required.

List View Menu - contains links to account migration activities and the search box. Each activity is explained in
greater detail in subsequent topics. See Searching for more information about working with the search box.
List View - displays information about accounts in the source tenant and the migration status of each account.
Some columns are hidden by default. Use the Edit Columns list view menu to show or hide columns in the list. The
columns are as described below:
NOTE: If you don't see the Sync Status or object description in the Type column, rerun the account discovery
task as indicated in the Notification panel.

l Sync Status - indicates whether the account is synchronized with the on-premise Active Directory or Azure
Active Directory. The tool tip displays the status value.
l Name - name of the account
l Source Type - account type defined in Microsoft Active Directory for the source tenant. The account type
can be one of the following:
l Any
l User accounts like Guest, Mailbox-enabled, Mail-enabled and Non-mail-enabled.
l Resource mailboxes like Equipment, Room, Scheduled and Shared.
l Groups like Distribution, Mail-enabled-security, Microsoft 365 Group, Security Group, Teams.
l Target Type - account type defined in Microsoft Active Directory for the target tenant. The account type can
be one of the following:
l Any
l User accounts like Guest, Mailbox-enabled, Mail-enabled and Non-mail-enabled.
l Resource mailboxes like Equipment, Room, Scheduled and Shared.
l Groups like Distribution, Mail-enabled-security, Microsoft 365 Group, Security Group, Teams.

On Demand Migration User Guide

Account Migration 52
 l ODM Licensed - indicates whether or not an On Demand Migration license has been consumed when the
migration task is started. Values are Yes, No, Not required.
l Status - status of the account in the migration process. Valid values are New, In Progress, Failed and
Completed. The Status column displays a progress bar that tracks the update for each account when the
Matching and Migration tasks are running.
l Account State - tracks the state of the account migration from source to target tenant. The column values
are as follows:

Column Value Description

Discovered Account has been discovered in the source tenant.

Matching Account is being matched.
Match failed Account matching failed
Matched Account has been successfully matched.

Migrating Migration of this object has started.

Migration failed Migration did not succeed
Migration stopped Migration canceled by the user
Migrated with Issues Migration completed with errors.
Migrated Migration is complete and successful.

l Source UPN - User Principal Name (UPN) of the source account.

l Target UPN - User Principal Name (UPN) of the target account.
l Source Group Type - group membership type in the source tenant. Valid values are Assigned
or Dynamic.
l Assigned - indicates that members are manually added or removed from the group.
l Dynamic - indicates that users are added or removed dynamically once the membership rules
are defined.
l Target Group Type - group membership type in the target tenant. Valid values are Assigned or Dynamic.
l Assigned - indicates that members are manually added or removed from the group.
l Dynamic - indicates that users are added or removed dynamically once the membership rules
are defined.
l Title - Job title of the user account. Does not apply to group accounts.
l Department - department of the user account. Does not apply to group accounts.
l Country - country of the user account. Does not apply to group accounts.
l City - city of the user account. Does not apply to group accounts.

Accounts Assessment
Contains summary reports about the discovered data to analyze your domain structure and track potential
problems, misconfiguration, and risks that might adversely affect the migration. For more information see
Assessment.

On Demand Migration User Guide

Account Migration 53
Account Details
When you select an account from the List View, the Account Detail pane opens. The information in the pane is
described below:

l Source Email - email address of the selected account in the source tenant.
l Target Email - email address of the selected account in the target tenant.
l Collections - list of collections that contain the selected account.
l Status - status of the selected account. Valid values are New, In Progress, Failed and Completed.
l Events - count of the events that occurred during account processing through one or more tasks.
l Tasks - list of tasks invoked for the selected account.

Configuring Connections
You can re-configure connections from the account migration Dashboard as described below.

To configure connections for source and target tenants:

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 Accounts. The Accounts and User Data Dashboard opens.

5. Click Configure Connections from the Accounts and User Data Dashboard ribbon.
6. From the Configure Connection wizard select the source or target tenant that you want to configure and
click Edit.
7. Target tenant only: Grant optional feature permissions
To activate the ability to provision OneDrive accounts in the target tenant using another Azure user account
that has the SharePoint Administrator role, enter the credentials as required.

On Demand Migration User Guide

Account Migration 54
 8. Concurrent PowerShell connections

You can increase Concurrent PowerShell connections settings to speed up the concurrent tasks
completion or set the value in case of editing of the migration projects that have been created in previous
versions of the On Demand Migration. The default Microsoft 365 quota is 3 open connections per user.

CAUTION: Do not exceed the maximum number of concurrent PowerShell connections

allowed for your organization to avoid throttling issues. To increase the maximum number of
allowed concurrent connections open a support ticket with Microsoft.

9. Specify custom EWS URL

Specify custom EWS endpoint for connecting to Exchange Web Services (EWS), if you do not want to use
EWS endpoint located by the Auto-discover service automatically.

10. Click Save to commit your changes.

11. When both source and target connections are configured, click Finish.

Discovering Accounts
Discovering accounts is a critical first step before a migration to enumerate, update and retrieve relevant information
about accounts from the source tenant. The discovery task collects the necessary account data and statistics on
connected mailboxes from your source tenant to avoid misconfiguration and prevent possible issues.
NOTE: Account discovery is deactivated if basic migration consents are missing from either the source or
the target tenant.
If there are user or group accounts from a previous discovery task that you don't want anymore, you can
manually delete the accounts from the Accounts list (Accounts tab > List View). If there are changes to an
account from a previous discovery, the account will be updated if the account is rediscovered by the task.

On Demand Migration User Guide

Account Migration 55
In this topic:
l Discovering all accounts automatically
l Discovering accounts from a file
l Discovering accounts from a file using security groups
l Refreshing Selected Accounts
l Reviewing the Account Discovery Task
l Reviewing the Account Discovery Task Events

Discovering all accounts 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. From the Accounts tile on the project dashboard click Open. The Accounts and User data workspace opens.
5. Open the Accounts tab . From the List View menu, click Discovery and then select Discover All. The New
Account Discovery Task wizard starts.
6. Step 1: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
7. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

8. Step 3: Summary
a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name. Default name is Account
Discovery Task.
l Source tenant - name of the source tenant in this project.
l Discover Type - discovery option that is selected. Value is set to All.

On Demand Migration User Guide

Account Migration 56
 l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard. The task
will start as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab. When the discovery task is complete, a summary about the
accounts discovered in the source tenant is available on the project dashboard.

Discovering accounts from a file

When you have a large set of accounts but you want to discover a subset of those accounts, the CSV file lets you
specify the accounts (users and Microsoft 365 groups) that you want to discover and ignore the rest. You can then
use this file in the New Account Discovery Task wizard.

To prepare the CSV file:

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. Export Users:
a. From the navigation pane, click Active users.
b. If needed, you can filter the set of users that you want to export. Then click Export. A
Users_<timestamp>.csv file will be downloaded to your computer.

3. Export Groups:
a. From the navigation pane, click Active teams and groups.
b. Select the Microsoft 365 tab in the Active teams and groups page.
c. If needed, you can filter the set of groups that you want to export. Click Export and then click Export

On Demand Migration User Guide

Account Migration 57
 groups in this list. A Groups.csv file will be downloaded to your computer.

4. Create a new CSV file and add the user accounts and groups with accounts you want to discover. You can
use any of the two formats shown below:
Format 1

UserPrincipalName - Column header for the login name for a user account based on the Internet
standard RFC 822. Do not use a mail nickname or proxy address.
Format 2

ObjectId - Column header for the globally unique identifier (GUID) of the user or group object.
When you use ObjectId as the column header, you must specify object GUIDs only. You cannot
specify UPNs.
Type - Column header for the type of account: user or Microsoft 365 group.

5. Save the CSV file that you created.

To run the account discovery 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.

On Demand Migration User Guide

Account Migration 58
 4. From the Accounts tile on the project dashboard click Open. The Accounts and User data workspace opens.
5. Open the Accounts tab . From the List View menu, click Discovery and then select Discover From File.
The New Account Discovery Task wizard starts.
6. Step 1: Discovery Options
a. Click Browse to choose the comma-separated values (CSV) file that contains the lists of user
accounts and group identifiers.
b. Click Next.
7. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
8. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

9. Step 4: Summary
a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name. Default name is Account
Discovery Task.
l Source tenant - name of the source tenant in this project.
l Discover Type - discovery option that is selected. Value is set to Using CSV file.
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard. The task
will start as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab. When the discovery task is complete, a summary about the
accounts discovered in the source tenant is available on the project dashboard.

Discovering accounts from a file using security groups

When you need to limit an application's access to a specific set of mailboxes, use this option to include the security
groups in a CSV file. You can then use this file in the New Discovery Task as described in this topic to discover the

On Demand Migration User Guide

Account Migration 59
accounts from the source tenant. Application access policies can be assigned to these discovered groups to restrict
access to the group members only.

To prepare the CSV file:

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. Export Security Groups:
a. From the navigation pane, click Teams and groups.
b. Select the Mail-enabled security tab in the Active teams and groups page.
c. If needed, you can filter the set of groups that you want to export. Click Export and then click Export
groups in this list. A Groups.csv file will be downloaded to your computer.

3. Create a new CSV file and add the email ids of the security groups with the member accounts you want to
discover. The CSV format is shown below:

MailEnabledSecurityGroupEmailID - Column header for email IDs of the security group.

4. Save the CSV file that you created.

To run the account discovery 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 Accounts tile on the project dashboard click Open. The Accounts and User data workspace opens.

On Demand Migration User Guide

Account Migration 60
5. Open the Accounts tab . From the List View menu, click Discovery and then select Discover From
Security Groups. The New Account Discovery Task wizard starts.
6. Step 1: Discovery Options
a. Click Browse to choose the comma-separated values (CSV) file that contains the lists of user
accounts and group identifiers.
b. Create application access policy for provided groups - select this option to create an application
access policy for groups when it is necessary to restrict access to group members only, when
migrating account mailboxes . The new application access policy can take up to 30 minutes to take
effect on Azure groups. For more information see Limiting application permissions to specific
Exchange Online mailboxes.
c. Click Next.
7. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
8. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
l Repeat - select this option to activate a recurring schedule
l Period - select from one of the following options: every 15 minutes, every 30
minutes, hourly, daily, weekly, monthly
l End - specify the end date and time for the task.
b. Click Next.

9. Step 4: Summary
a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name. Default name is Account
Discovery Task.
l Source tenant - name of the source tenant in this project.
l Discover Type - discovery option that is selected. Value is set to Using Mail-enabled
Security Group(s).
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.

On Demand Migration User Guide

Account Migration 61
 b. Click Back to revise or review a previous step or click Finish to complete the task wizard. The task
will start as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab. When the discovery task is complete, a summary about the
accounts discovered in the source tenant is available on the project dashboard.

Refreshing Selected Accounts

For all source and target accounts , the task will refresh the UPN, Primary Email Address and Object Type of
selected accounts. The task will not modify the migration state of the accounts.

To start the refresh 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 Accounts tile on the project dashboard click Open. The Accounts and User data workspace opens.
5. Open the Accounts tab . From the List View menu, click Discovery and then select Refresh Selected
Accounts. The New Refresh Selected Accounts Task wizard starts.
6. Step 1: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
7. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
l Repeat - select this option to activate a recurring schedule
l Period - select from one of the following options: every 15 minutes, every 30
minutes, hourly, daily, weekly, monthly
l End - specify the end date and time for the task.
b. Click Next.

On Demand Migration User Guide

Account Migration 62
 8. Step 3: Summary
a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name. Default name is Refresh
Selected Accounts Task.
l Source tenant - name of the source tenant in this project.
l Discover Type - discovery option that is selected. Value is set to Refresh Selected.
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard. The task
will start as scheduled.

Reviewing the Account Discovery Task

1. Select the Tasks tab.
2. Select the account discovery task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is Discovery Task.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Accounts (number) - The number of accounts that were selected for matching and the number of
accounts passing through the various states of the task from New to Completed..
h. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Account Discovery Task Events

1. Select the Tasks tab.
2. Select the account discovery task for which you want to review the events.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. For account discovery tasks, the category is Discover.
e. Summary - a descriptive statement about the event.

You are now ready for the Assessment.

On Demand Migration User Guide

Account Migration 63
Exporting Accounts
1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Select the Accounts tab and select List View if not already selected.
6. Select the accounts to export.
7. Click More Actions and then click Export.

8. Open the CSV file by extracting it from the ZIP file that is downloaded to your computer.

Removing Accounts
To manage large lists of accounts in a project, you can remove one or more accounts from the accounts list that you
don't need for migration processes. The accounts that are removed will remain in the source tenant and you must
re-discover the accounts in the project when you need them for migration.
If these accounts are listed in other projects, they will be displayed in those projects.

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Select the Accounts tab and select List View if not already selected.

On Demand Migration User Guide

Account Migration 64
 6. Select the accounts you want to clear.
TIP: Use filters, search or collections to quickly navigate through the list of accounts.

7. Click More Actions and then click Delete.

8. The Remove Objects confirmation dialog opens.

9. Click Remove to remove the selected accounts from the list.

Managing Accounts with Collections

Migrating large numbers of accounts requires careful planning. The accounts could belong to different offices and
geographical locations or sensitive departments. Migrating groups of employees in top management, Finance or
Legal departments require special care. Organize the accounts into collections to make large account lists more
manageable.

Working with the Collection Dashboard

The Collection Dashboard shows the collection-specific summary, allows you to see accounts added to it, create
tasks for them, and monitor the progress of tasks.

On Demand Migration User Guide

Account Migration 65
 l To view the collection dashboard for an existing collection
a. Log in to Quest On Demand and choose an organization if you have multiple organizations.
b. From the navigation pane, click Migration to open the My Projects list.
c. Create a new project or open an existing project.
d. From the project dashboard, click Open in the Accounts tile to open the Accounts and User
Data workspace
e. From the top-right corner of the workspace, click Select Collection and then select the collection to
view. The collection Dashboard is displayed.
f. Click Browse Accounts from the collection Dashboard menu or open the Accounts tab. You will
see the list of accounts that belong to the collection.

l To see the tasks for collection-specific accounts, use the corresponding tile on the collection Dashboard or
open the Tasks tab.
l To see the events related to the collection, use the corresponding widget on the collection Dashboard or
open the Events tab.
l To rename or delete the collection, click the corresponding buttons in the menu.
l To return to the project dashboard, click the project name in the navigation bar.

Adding accounts to Collections

You can add accounts to collections in three ways:

l Select the accounts and create a new collection

l Select the accounts and add to an existing collection.
l Use a CSV file to create one or more collections of discovered accounts.

To add selected accounts to a new collection:

1. From the project dashboard, click Open in the Accounts tile to open the Accounts and User Data workspace.
2. Open the Accounts tab and select List View if not already selected.
3. Select the accounts you want to add to a collection.

On Demand Migration User Guide

Account Migration 66
 4. From the actions toolbar, click New Collection. The New Collection dialog opens.

5. Enter a collection name in the Collection name field and click Save to add the selected accounts to the
collection.

To add selected accounts to an existing collection:

1. From the project dashboard, click Open in the Accounts tile to open the Accounts and User Data workspace.
2. If you need to create a new collection:
a. From the top-right corner of the workspace, click Select Collection > + New Collection
b. Enter a collection name and click Save to add this collection to the project.
3. Click the Accounts tab and select the accounts that you want to add to the collection.
4. From the actions toolbar, click Add to Collection. The Add to existing collection dialog opens.

5. Select your collection from the Collection name dropdown and click Save to add the selected accounts to
the collection.

To create one or more collections with a CSV file:

This is a two-step process as described below:
Step 1: Prepare the CSV file
NOTE: Using a CSV file provides the following additional benefits:

l Multiple collections can be created with the same CSV file.

l Existing collections can be specified in the CSV file to add additional accounts
l Accounts can be listed in multiple collections

You can choose one of two formats to prepare the CSV file:
Format 1: Use the ObjectId to identify accounts

On Demand Migration User Guide

Account Migration 67
 l ObjectId - Column header for the globally unique identifier that represents a discovered account.
The following variations of ObjectId are supported: ObjectId, objectid, objectId, OBJECTID
l Collection - Column header for the collection name

Format 2: Use the UserPrincipalName to identify accounts

l UserPrincipalName - Column header for the login name of an account based on the Internet
standard RFC 822. Do not use a mail nickname or proxy address. The following variations of
UserPrincipalName are supported: UserPrincipalName, userprincipalname,
USERPRINCIPALNAME
l Collection - Column header for the collection name

Step 2: Import the CSV file

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data workspace.
5. Select the Accounts tab and select List View if not already selected.
6. From the actions toolbar, click More Actions and then click Import Collections. The Import Collections
from File dialog opens.
7. Click the Provide accounts as a list of drop-down and select either ObjectIds or UserPrincipalNames
depending on the format of the CSV file that you have prepared.
8. Click Browse and select the CSV file. The selected CSV file name appears.
9. Click Import.

NOTE: Identifiers of accounts that are not discovered are ignored without producing an event.

On Demand Migration User Guide

Account Migration 68
Assessment
The On Demand Migration account service analyzes your domain structure and tracks potential problems,
misconfiguration, and risks that might adversely affect the migration. Switch to Assessment view to see the
summary reports about the discovered data.

The following reports are available for Accounts:

l Clean Up
l Disabled accounts
l Users with non expiring passwords
l Adjustments
l Duplicate group names
l Duplicate user names
l Users without first name
l Users without last name
l Inventory
l Number of users
l Number of groups
l User by Type
l External Accounts
l Tenant members
l Licenses
l Available ODM licenses
l Used ODM licenses

On Demand Migration User Guide

Account Migration 69
 l Available Teams only licenses
l Used Teams only licenses

Matching Accounts
Your target tenant might already contain accounts created for the source tenant users before the migration. You can
map them to the corresponding source accounts, so that no data is lost or duplicated. You can also clear all existing
matches and start afresh.
In this topic:

l Matching accounts selected from the accounts list

l Matching accounts with a CSV file
l Reviewing the Account Matching Task
l Reviewing the Account Matching Task Events

Matching accounts selected from the accounts list

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Click the Accounts tab and select List View if not already selected.
6. Select the accounts you want to match and then click Match > Match Selected from the List View menu.
The New Account Matching Task wizard opens.

On Demand Migration User Guide

Account Migration 70
7. Step 1: Account Matching

a. Select and configure the options as described below:

l Clear existing matches - all matches are cleared.
l Match by attribute - use the specified attribute pairs to match accounts in the source and
target tenants. Select the same matching attribute for the Source attribute and Target
attribute. The matching attributes are as described below:
l displayName - the attribute of the account as specified in the same active
directory property.
l mail - email address
l mailNickname - email alias used in Exchange servers.
l ImmutableId - a specific attribute for a Microsoft 365 account object that is
synchronized from on prem Active Directory. When AAD Sync is used with the
default settings on Uniquely Identifying your users, the Active Directory objectGUID
is used as the immutableId.
l employeeId - the identifier of an employee in active directory.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.

On Demand Migration User Guide

Account Migration 71
 9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
l Name - name of the task. The default name is Account Matching Task. You can specify a
custom name.
l Source tenant - name of the tenant where the statistics will be collected.
l Target tenant - name of the target tenant in this project.
l Assign Licenses - value is Yes.
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Matching accounts with a CSV file

This step is required if you plan to map specific accounts from the source to existing accounts in the tenant that do
not have any matching attributes. The CSV file lets you specify the accounts that you want to map and ignore the
rest. You can then use this file in the New Mapping from File Task to map the accounts from the source to the target
tenant. This is a two-step process:
Step 1: Prepare the CSV file

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. Export Users:
a. From the navigation pane, click Active users.
b. If needed, you can filter the set of users that you want to export. Then click Export. A Users_

On Demand Migration User Guide

Account Migration 72
 <timestamp>.csv file will be downloaded to your computer.

3. Export Groups:
a. From the navigation pane, click Active groups.
b. Select the Microsoft 365 tab in the Active Groups page.
c. If needed, you can filter the set of groups that you want to export. Click Export and then click Export
groups in this list. A Groups.csv file will be downloaded to your computer.

4. Repeat steps 1-3 for the target tenant.

5. Create a new CSV file and add the attributes of the users and groups you want to map from the source to the
target tenant, from the CSV files that you exported. You can follow any of the two formats shown below:
NOTE:
l CSV file must have two columns: <source-attribute-name> and <target-attribute-name>
l Account pairs in which one of the accounts is a guest account are not supported.
l CSV file names with non-ASCII characters are not supported.

Format 1 Use the UserPrincipalName

On Demand Migration User Guide

Account Migration 73
 UserPrincipalName - An Internet-style login name for a user account based on the Internet standard RFC
822. Do not use a mail nickname or proxy address.
Format 2 Use the ObjectId

ObjectId - Globally unique identifier (GUID) of the user or group object. When you use ObjectId as the
column header, you must specify object GUIDs only. You cannot specify UPNs.

6. Save the CSV file that you created.

Step 2: Start the Account Mapping from File Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Select the Accounts tab and select List View if not already selected.
6. From the List View menu click Match > Map From File. The New Account Mapping from File Task wizard
opens.

On Demand Migration User Guide

Account Migration 74
 7. Step 1: Mapping File

a. Click Browse and select the CSV file with the account maps that you prepared.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. The default name is Account Mapping from File Task. You can
specify a custom name.
ii. Source tenant - name of the tenant where the statistics will be collected.

On Demand Migration User Guide

Account Migration 75
 iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Account Matching Task

1. Select the Tasks tab.
2. Select the account discovery task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is Matching.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Accounts (number) - The number of accounts that were selected for matching and the number of
accounts passing through the various states of the task from New to Completed.
h. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Account Matching Task Events

1. Select the Tasks tab.
2. Select the account discovery task for which you want to review the events.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. For account mapping tasks, the category is Matching.
e. Summary - a descriptive statement about the event.

Migrating Accounts
CAUTION: Don’t start a migration before the discovery task is finished. Running a matching task is
recommended.

On Demand Migration User Guide

Account Migration 76
In this topic:

l Considerations for Guest User Migration

l Preferred Data Location
l Starting an Account Migration Task
l Reviewing the Account Migration Task
l Reviewing the Account Migration Task Events

Considerations for Guest User Migration

TIP: Guest user accounts have a specific icon to distinguish them from other domain members.

On Demand migration can process all guest user types supported by Microsoft. Before adding a guest user account
to the migration task, consider the following:

l Guest user account cannot be migrated if an original account for this guest user is already in the target
tenant. The guest user account should be matched but not migrated.
l Guest user account cannot be migrated in case a guest user account of the same original account is already
in the target tenant. To update the target guest user account properties create a matching task to pair these
guest user accounts and then migrate the source guest user account again
l Guest user account cannot be migrated in case the invitation procedure in source domain is not finished yet.
In case acceptance procedure was skipped (this case is deprecated now, but such guest users still exist),
and the acceptance status is empty, guest user can be migrated successfully.
l A regular source user mapped to a target guest user during migration, will be converted to a regular user. If
the target guest user was created in an on-premise environment, you must manually convert the target
guest user to a regular user.

Preferred Data Location

For multi-geo enabled tenants, each account could be assigned a Preferred Data Location (PDL) property in
Azure Active Directory. During account migration the property is migrated from source to target tenant. If the
preferred data location is set in the source account then the same setting can be migrated to the target. If the
preferred data location is absent in the source tenant then it will either not be set on the target or it will use the
default location of the target tenant. This applies only for general tenant to multi-geo tenant and multi-geo tenant to
multi-geo tenant migrations.

Starting an Account Migration Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Select the accounts you want to migrate. If you are planning to migrate Microsoft 365 Groups including
content, see Microsoft 365 Groups Migration.

On Demand Migration User Guide

Account Migration 77
6. Click the Accounts tab and select List View if not already selected. The New Account Migration
Task opens
7. Step 1: Custom Target Domain

a. Configure the options as described below:

l Custom target domain name - select the domain you want to use for the UPN and primary
SMTP address of accounts created during the migration process.
NOTE: Accounts that already exist in the target tenant will not have their current UPN
or primary SMTP email address modified.

l Set target PDL - choose how the Preferred Data Location (PDL) will be assigned to target
accounts created in multi-geo tenants. This applies only for general tenant to multi-geo
tenant and multi-geo tenant to multi-geo tenant migrations. The Microsoft 365 multi-geo
feature must be available and enabled in the target tenant, otherwise this option is ignored.
l Migrate PDL value from source account - assign the same PDL value as
the corresponding source account, or use the default location specified in the
target tenant.
l Select PDL value to assign - assign a specific PDL value to target accounts.
Choose a PDL from the Location dropdown. See Microsoft 365 Multi-Geo availability
for location codes.
b. Click Next.
8. Step 2: Custom Source Domain
a. Configure the setting as described below:
l Custom source domain for routing - select the custom source domain name for
forwarding mail from the target account. If the domain is omitted, the primary SMTP address
of the source tenant will be used as the forwarding address for the mail enabled user created
by this task. Optionally, you can select the custom SMTP domain here that will be used as
the forwarding address.

On Demand Migration User Guide

Account Migration 78
 b. Click Next.
9. Step 3: Guest Users
This option is used when guest users are migrated. For all other account types, this option is ignored.
Send invitation email - select this option to send an invitation email to migrated guest users. Guest users
can either accept the invitation or authenticate with Microsoft to access secured applications. If this option is
not selected, guest users must authenticate with Microsoft to access secured applications.

10. Step 4: Notification

a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
11. Step 5: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
12. Step 6: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. Default name is Account
Migration Task.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Custom target domain name - domain name of your target tenant.
v. Custom domain for forwarding - custom source domain or primary SMTP address of the
source tenant used as the forwarding address for the mail enabled user created by this task.
vi. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

You can track its progress in the Taskstab, view the summary on the Dashboard or monitor alerts and notifications
in the Eventstab. When accounts are matched successfully, the Status changes from New to Completed.
IMPORTANT: The account migration service does not synchronize end-user passwords as part of the data
migration process. The migration administrator will need to reset or synchronize end-user passwords from
the source tenant to the target tenant using native Microsoft 365 tools or third-party Single Sign On tools.

On Demand Migration User Guide

Account Migration 79
Reviewing the Account Migration Task
1. Select the Tasks tab.
2. Select the account discovery task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is Migration.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Accounts (number) - The number of accounts that were selected for matching and the number of
accounts passing through the various states of the task from New to Completed..
h. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Account Migration Task Events

1. Select the Tasks tab.
2. Select the account discovery task for which you want to review the events.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. For account migration tasks, the category is Migrate.
e. Summary - a descriptive statement about the event.

Domain Coexistence
Mergers and acquisitions are often accompanied by the unification of brands and corporate identities, including the
consolidation of email addresses. However, the transition from source to target tenant might take considerable time.
On Demand Migration offers domain coexistence services to close this gap, allowing your employees to send mail
from new addresses and access cross-tenant data before the migration is finished. The following services are
currently available on the account migration dashboard:

l Address Rewrite Service seamlessly changes the source users' email flow as if they're already fully migrated
to the target tenant. Outgoing email addresses are replaced with the recipient's email address in the target
tenant, while all incoming mail is automatically redirected to the source mailbox. Address rewriting can be

On Demand Migration User Guide

Account Migration 80
 started once the account is matched or migrated, giving you time to prepare and migrate mailboxes. The
Address Rewrite Service requires additional licensing.
l Calendar Sharing allows users from the source and target tenants to see each other's free or busy
information.

Address Rewrite Service

The Address Rewrite Service substitutes the From, To, and Cc addresses in the outgoing emails with the
addresses from the target or source tenant depending on the selected address rewriting scenario. Emails are
automatically redirected to the source or target mailbox. You can specify the users processed by the service. For
example, you can turn on the service for only Sales and Marketing team members.
IMPORTANT: Address Rewrite Service requires additional licensing. The service only works with accounts
that have been matched in the target tenant. See matching accounts for more information. Mailbox
provisioning is not required.

Address Rewrite Service Message Flow

Address Rewrite Service is intended for creating a coexistence space for domains in which all the email messages
coming from the source or target mail domain will look like they were sent from the unified mail domain according to
the selected settings. The Address Rewrite Service will take all the necessary steps to create this coexistence
space in the Exchange online environment, including creating and managing all the required connectors, mail flow
rules, mail-enabled users, and groups in source and target environments. The administrator should add or remove
source mail users to this coexistence space and activate or deactivate the Address Rewrite Service.
The mail message flow in a unified domain with an activated Address Rewrite Service is as described below:
Unified mail domain in the source tenant

1. When a user sends an email as [email protected] mail user, it is redirected to the Address Rewrite
Service server if it is addressed to external recipients.
2. When the Address Rewrite Service receives an email from [email protected], it checks user eligibility to
for the address rewriting service and then processes the email by rewriting @target.domain to
@source.domain for every user address that is found in the coexistence space. The addresses in "From",
"To" and "Cc" fields of the email message are rewritten for all external recipients. Then Address Rewrite
Service passes the processed email message to the source Exchange Online. Internal recipients that reside
in the source receive this email message with unchanged addresses.
3. Exchange Online at the source sends a message to external recipients as if it was sent by a user from
@source.domain, and all addresses of users added to coexistence scope in From, To and Cc are rewritten
for external recipients.
4. The External recipient is not aware about @target.domain and replies (or create a new email) to the
[email protected]
5. When the reply or a new mail arrives to the source mail domain it will be forwarded to the target. Target
recipient gets the message as if it was forwarded from the Exchange online at the source from
[email protected]

On Demand Migration User Guide

Account Migration 81
If the message...
Is sent outside the organization from a member of the coexistence group
Do the following...
Route the message using the connector Quest Coexistence Connector Outbound.
Except if...
Sender IP address belongs to one of Mail Relay IP addresses.

If the message...
Is sent outside the organization and is received by a member of the coexistence group specified in the
To or CC field
Do the following...
Route the message using the connector Quest Coexistence Connector Outbound.
Except if...
Sender IP address belongs to one of Mail Relay IP addresses.

Mail flow scenario

From: Mail Relay Servers
To: Microsoft 365
How to identify email sent from Mail Relay Servers
Identify incoming messages from Mail Relay Servers by verifying that the sending server's IP address is
within Mail Relay IP address ranges and the sender's email address is an accepted domain in your
organization.

Mail flow scenario

From: Microsoft 365
To: Mail Relay Servers
When to use the connector

On Demand Migration User Guide

Account Migration 82
 Use only when there is a transport rule (Quest Coexistence Rule From and Quest Coexistence Rule
ToCc) is set up that redirects messages to this connector. Routing method Route email messages
through Mail Relay Servers.

Mail flow scenario

From: Mail Relay Servers
To: Microsoft 365
How to identify email sent from Mail Relay Servers
Identify incoming messages from Mail Relay Servers by verifying that the sending server's IP address is
within Mail Relay IP address ranges and the sender's email address is an accepted domain in your
organization.

Unified mail domain in the target tenant

1. When a user sends an email as [email protected] it is redirected to Address Rewrite Service server if it
is addressed to external recipients.
2. When the Address Rewrite Service receives email from [email protected], its checks user eligibility for
the address rewriting service and then processes it by rewriting @source.domain to @target.domain for
every user found in the coexistence space. The addresses in "From", "To" and "Cc" of the email message
are rewritten for all external recipients. Then Address Rewrite Service passes the processed email message
to the target Exchange Online. Internal recipients that reside in the source receive this email message with
unchanged addresses.
3. Exchange Online at the target sends the message to external recipients as if it was sent by
[email protected], and all addresses of the users added to the coexistence scope in "From", "To" and
"Cc" are rewritten for external recipients.
4. External recipient is not aware about @sourcedomain and replies (or create a new email) to
[email protected].
5. When the reply or a new mail arrives to the target mail domain it will be forwarded to the source. Source
recipient gets the message as if it was forwarded from the target Exchange online from [email protected]

On Demand Migration User Guide

Account Migration 83
 If the message...
Is sent outside the organization from a member of the coexistence group
Do the following...
Route the message using the connector Quest Coexistence Connector Outbound.
Except if...
Sender IP address belongs to one of Mail Relay IP addresses.

If the message...
Is sent outside the organization and is received by a member of the coexistence group specified in the
To or CC field
Do the following...
Route the message using the connector Quest Coexistence Connector Outbound.
Except if...
Sender IP address belongs to one of Mail Relay IP addresses.

Mail flow scenario

From: Microsoft 365
To: Mail Relay Servers
When to use the connector
Use only when there is a transport rule (Quest Coexistence Rule From and Quest Coexistence Rule
ToCc) is set up that redirects messages to this connector. Routing method Route email messages
through Mail Relay Servers.

Mail flow scenario

From: Mail Relay Servers
To: Microsoft 365
How to identify email sent from Mail Relay Servers
Identify incoming messages from Mail Relay Servers by verifying that the sending server's IP address is
within Mail Relay IP address ranges and the sender's email address is an accepted domain in your
organization.

Mail flow scenario

From: Mail Relay Servers
To: Microsoft 365
How to identify email sent from Mail Relay Servers
Identify incoming messages from Mail Relay Servers by verifying that the sending server's IP address is
within Mail Relay IP address ranges and the sender's email address is an accepted domain in your
organization.

TIP: If Exchange Server Integration fails, click Try to fix and Quest will try to help you resolve the issue.

Using the Address Rewrite Service requires following steps:

# Step

1 Select Scenario for Address Rewriting

On Demand Migration User Guide

Account Migration 84
 # Step

2 Provision Address Rewrite Service

3 Add mailboxes to address rewriting
4 Optional: Add Address Rewrite Service's IP address to the target DNS SPF record
5 Activate address rewriting. You can deactivate address rewriting at any time or turn off
address rewriting for individual mailboxes

Address Rewrite Service Considerations

Each customer has a dedicated environment and inbound IP address for Address Rewrite Service.
The following groups, connectors and rules appear in Exchange Admin Centers after Exchange Server Integration
is configured:
CAUTION: Do not edit or remove the groups, connectors and rules related to Address Rewrite
Service otherwise the service may fail. These rules can be removed manually only if address
rewriting no longer needed.
On source tenant:

l Quest On Demand Coexistence group contains accounts (recipients) joined to Address Rewriting
l Inbound Quest Coexistence Connector helps control mail flow for Address Rewrite Service from
Microsoft 365 to the organization
l Outbound Quest Coexistence Connector helps control mail flow for Address Rewrite Service from
the organization to Microsoft 365
l Quest Coexistence Rules implement Address Rewriting messaging policy for accounts joined to
Address Rewriting

On target tenant:

l Quest Coexistence Connector helps control flow of email messages for Address Rewrite Service
from the organization to Microsoft 365

IMPORTANT: The service only works with accounts that have pairs in the target tenant. You should match
or migrate an account before adding it to address rewriting.

NOTES:

l Target mail-enabled users should be configured to redirect messages from target to the source
mailbox. See for details.
l In case an email is sent to a group of people, including a migrated user, that email is automatically
forwarded to the migrated user, and then if the migrated user clicks Reply all, he / she gets a copy of
his / her reply message. This is default behavior.

Address Rewriting Scenarios

Address Rewriting supports the following scenarios:

l Replace senders’ address with the target primary email address.

l Replace senders’ address with the source primary email address.

On Demand Migration User Guide

Account Migration 85
 NOTE: The address is only rewritten in the mail that goes to the recipients outside your organization. Internal
users receive the mail with the original address.

IMPORTANT: Microsoft 365 Advanced Threat Protection default settings may cause issues with the
Address Rewriting Service.
Please ensure that "Automatic forwarding" is set to "On" in the "Outbound spam filter policy" for your source
or target tenant depending on the rewriting scenario you choose.

Rewriting senders’ address to the target address

Use case: users from the source tenant need to communicate with external recipients from the name of the
target organization. It usually happens when the mail migration is not yet finished, but you want to use the
consistent branding.
To rewrite senders’ address to ones from the target select To target for the Rewrite senders’ address to on the
Domain Coexistence widget. You cannot change this setting after Address Rewrite Service is provisioned.
Check Senders' Address property on the Mailboxes tab to find the effective email address after rewriting. If the
account don't have the Exchange mailbox provisioned in the target tenant (mail user), the target primary SMTP
address is used for address rewriting.
IMPORTANT: To ensure that all incoming mail is automatically redirected to the source mailbox, set Mail
Flow to To source. See for details.

Rewriting senders’ address to the source address

Use case: migrated users need to communicate with external recipients from the name of the source organization.
It usually happens when you need to keep the original brand while merging all accounts in the target tenant.
To rewrite senders’ address to ones from the source select To source for the Rewrite senders’ address to on the
Domain Coexistence widget. You cannot change this setting after Address Rewrite Service is provisioned.
Check Senders' Address property on the Mailboxes tab to find the effective email address after rewriting.
NOTE:Check that the Mail Flow for the mailbox is set to To target. See for details.

Provisioning the Address Rewrite Service

IMPORTANT: After Address Rewrite Service provisioning starts, you cannot change the setting of the
sender's address to be rewritten.

1. Open the project dashboard.

2. Click Provision for Address Rewrite Service from the Domain Coexistence widget.
3. Wait until the service is provisioned and Exchange Server Integration is successfully configured.

The provisioning might take some time. In the meanwhile, you can select the mailboxes for the address rewriting.

On Demand Migration User Guide

Account Migration 86
Selecting Mailboxes for Address Rewriting
1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.

5. Click the Mailboxes tab or click Select in the Domain Coexistence tile.

6. Click Off in Address Rewrite facet to show the mailboxes that are ready for address rewriting.

IMPORTANT: Address Rewrite Service only works with accounts that have pairs in the target tenant. You
can click Not Supported in Address Rewrite facet to see the mailboxes that are not ready for address
rewriting.

7. Select the mailboxes and click Address Rewrite.

8. In Address Rewrite Management task, select Turn on address rewriting for selected mailboxes.
9. Click Next to view the task summary. Check selected options, name the task, and click Finish to
start the task.
10. The task is created. You can track its progress in the Tasks or monitor alerts and notifications in the Events.

You can add the mailboxes to address rewriting at any time. Note, that if the Address Rewriting Service is already
enabled, it might take a while before the rewriting will be enabled for the newly added mailbox. Check that Address
Rewrite status is On for the mailbox.

Configuring SPF Record

During the provisioning phase, we configure the target Exchange Server to correctly handle messages, processed
by Address Rewrite Service. If you want to be absolutely sure that the messages are not blocked by custom filters
and antiviruses, add the service's IP address to SPF record in target DNS.

l On Domain Coexistence widget, click Running to locate the event containing IP address of the Address
Rewrite Service server.
l Add the IP address to the SPF record in the target DNS. See provider's documentation for instructions.

Activating Address Rewriting

1. Make sure you have added the mailboxes to address rewriting. Click On in Address Rewrite to show the
joined mailboxes.
2. Go to the account migration dashboard and click Enable Coexistence in Domain Coexistence.

Deactivating Address Rewriting for Individual Mailboxes

1. Go to the migration project Dashboard
2. Click Accounts.

On Demand Migration User Guide

Account Migration 87
 3. Open Mailboxes
4. Click On in Address Rewrite facet to show the mailboxes for which address rewriting is enabled.

5. Select the mailboxes for which you want to turn off address rewriting and click Address Rewrite.
6. In Address Rewrite Management task, select the Stop address rewriting for the selected
mailboxes option.
7. Click Next to view the task summary. Check selected options, name the task, and click Finish to
start the task.
8. The task is created. You can track its progress in the Tasks or monitor alerts and notifications in the Events.

Deactivating Address Rewriting

1. Go to the migration project Dashboard.
2. Click Accounts.

1. Click Disable in the Domain Coexistence widget.

NOTE: You can turn Address Rewrite Service off at any time to stop sending outgoing messages with
substituted email address. The list of joined mailboxes is not affected.

CAUTION: Deactivate the Address Rewrite Service if you want to delete the migration project.

Calendar Sharing
Create a relationship between the source and the target tenants to allow users to retrieve calendar availability
information,

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Click Enable Calendar Sharing and verify the source and target domain names. Click Next to proceed.
6. Schedule when the task will be started. Click Next to view the task summary.
7. Name the task and check the selected options. Click Finish to save or start the task depending on schedule
option selected.

Resource Processing
When the account migration is complete, you may want to grant roles and access to resources like sites, libraries,
lists, and other content on the source tenant to the migrated accounts in the target tenant.
Resource processing does not copy resources to the target tenant. It simply provides the access to resources in the
source tenant by creating a linked guest user in the source tenant for each migrated or matched target account that

On Demand Migration User Guide

Account Migration 88
is selected for resource synchronization. The guest users in the source tenant are granted the same permissions as
the corresponding source accounts and become members of the same SharePoint groups.
The resource processing service can synchronize the access rights to the following resources on the source tenant:

l Microsoft SharePoint content like sites, libraries and lists.

l Resource roles
l Microsoft Office Applications

NOTE: Only permissions directly granted to the source account are transferred to the guest account.
Resource Processing is available for commercial tenants. Resource Processing is not available for GCC
High tenants or when credentials are missing or invalid.

In this topic:

l Preparing a CSV file with SharePoint sites

l Starting a New Resource Processing Task
l Reviewing the New Account Resource Processing Task
l Reviewing the New Account Resource Processing Task events

Preparing a CSV file with SharePoint sites

This step is required if you plan to copy permissions for multiple SharePoint sites. Verify that all users who have
access to these sites are also present in the CSV that contains the mapped accounts. If SharePoint users are
missing from the mapped accounts CSV, their permissions will not be copied.

1. Create a new CSV file and add the SharePoint sites using the file format as shown below:

2. Save the CSV file.

On Demand Migration User Guide

Account Migration 89
Starting an Account Resource Processing Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Accounts tile, or click Open from the Accounts tile to open the Accounts and User
Data dashboard.
5. Select the Accounts tab and select List View if not already selected.
6. Select the accounts you want to match and then click Process Resources from the List View > More
Actions menu. The New Account Resource Processing Task wizard opens.
NOTE: Process Resources remains deactivated if the target is a GCC High tenant.

7. Step 1: Guest Users

Send invitation email - Select this option to send an invitation email to the corresponding users in the
target tenant. Users in the target tenant can either accept the invitation or authenticate with Microsoft to
access secured applications. If this option is not selected, users in the target tenant must authenticate with
Microsoft to access secured applications.

On Demand Migration User Guide

Account Migration 90
8. Step 2: Processing Options

a. Select and configure the options as described below:

a. Process source SharePoint - The guest users are granted the same permissions as the
corresponding source accounts and become members of the same SharePoint groups. Only
permissions directly granted to the source account are transferred. It can take time for these
guest accounts to replicate to SharePoint, which can result in a User not found error
message for a guest account that has not yet been replicated during granting permissions. In
this occurs, retry the SharePoint processing later.
l Process SharePoint sites provided using CSV - select this option to process
multiple SharePoint sites from a CSV file.
l Click Browse and select the CSV file with SharePoint sites that you
prepared.
l Process specified SharePoint site - select this option to process a single
SharePoint site.
l SharePoint site URL - specify the root URL of the SharePoint site.
b. Process resource roles - Process Role-Based Access Control (RBAC) roles for the current
Azure subscription.
c. Process application assignment - select this option to ensure that the target users see the
same list of cloud applications on http://myapps.microsoft.com/ as their counterparts in the
source tenant. When the resource processing service assigns applications to the target
users, each application may check the access level of the user. Some applications may have
their own account databases and permission assignments and may require access rights to
be provisioned manually. See Consents and Permissions section for the minimum user
account permissions required to perform this task.
d. Process azure group membership - Select this option so target users are granted access
to source systems when an Active Directory group they are a part of is granted access. The

On Demand Migration User Guide

Account Migration 91
 process identifies the Active Directory groups the selected users (on the source) are part of
and adds the target users to those groups.
b. Click Next.
9. Step 3: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
10. Step 4: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
11. Step 5: Summary
a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name.
l Source tenant - name of the tenant where the statistics will be collected.
l Target tenant - name of the target tenant in this project.
l Assign Licenses - Value is Yes.
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Account Resource Processing Task

1. Select the Tasks tab.
2. Select the account discovery task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is Resource Processing.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.

On Demand Migration User Guide

Account Migration 92
 f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Account Resource Processing Task Events

1. Select the Tasks tab.
2. Select the account discovery task for which you want to review the events.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. For resource processing tasks, the category is Resource Processing.
e. Summary - a descriptive statement about the event.

On Demand Migration User Guide

Account Migration 93
 3

Mailbox Migration
Basic mailbox migration workflow consists of the following steps:

# Step

1 Collect Statistics

2 Migrate Mailboxes
3 Optional: Use Desktop Update Agent (DUA) to automatically reconfigure user Microsoft
Outlook Profiles to connect to the Exchange Online server in the target tenant.

What We Migrate
Migration limitations indicated below may not be an exhaustive list of limitations as some may appear in unique
customer migration scenarios, or arise due to platform or legacy support restrictions. In some cases, a solution to a
limitation may already be on the product roadmap.
Quest On Demand migrates the following Mailbox components:

Mailbox Type Support Comments

User mailbox ✔

Shared mailbox ✔

Distribution Group ✔

Microsoft 365 Groups ✔

Resource mailbox ✔ e.g. conference rooms, equipment

Contacts ✔

Component Support Comments

Inbox ✔

Folders ✔

Email ✔

Contacts ✔

Calendars ✔

Tasks ✔

On Demand Migration User Guide

Mailbox Migration 94
Component Support Comments

Journals ✔

Notes ✔

Rules ✔

Folder Permissions ✔

Public folders ✔

Calendar acceptance status emails ✔

Resource calendar permissions (e.g. for ✔

conference rooms)
Personal distribution lists ✔

Personal contacts ✔

Bounce notifications such as non-delivery ✔

reports or receipts (NDR)
Delivery Status Notifications (DSN) ✔

Custom rules like color categorization of ✔

emails, specific logic, sub-calendars and flags
Calendar notifications such as invites, ✔
responses, cancellations, etc.
PST Connection to Outlook Profile ✔

Calendar permissions sharing to more than 2 ✔

users
Pictures that have been added within a ✔
Business Card
Deleted items including recoverable deleted ✔
items.
Mailbox permission settings, sharing settings ✔
(such as aliases; delegates) and other mailbox
related setting

PST personal archives ✖ Quest Offers a solution for PST to M365

migration
Safe Sender or Blocked Lists ✖

RSS Feeds ✖

Client settings (e.g, default fonts), folder views, ✖ Migrated with Desktop Update Agent (DUA)
outlook customizations
User defined or custom fields ✖

Notifications scheduled more than one week in ✖ Default notifications that are set to 15 or 30
the future minutes will be migrated.
Outlook Quick Steps ✖

On Demand Migration User Guide

Mailbox Migration 95
Collecting Statistics
A Mailbox Collect Statistics Task conducts an assessment of mailboxes of selected accounts in the source
tenant and provides the following information:

l Size of the mailbox

l Number of items in the mailbox

Each Mailbox Collect Statistics Task generates events. Events are milestones that a task achieves as it runs. For
example, when a Mailbox Collect Statistics Task starts, an event is logged and it appears in the events list. When
the number of accounts that are selected for assessment is large, the Mailbox Collect Statistics Task divides the
total number of accounts into manageable sets. Each set is called a batch. When a batch of accounts is assessed,
another event occurs.
The Mailbox Collect Statistics Task and its events provide additional information about the mailbox for the set of
source tenant accounts that are assessed.
NOTE: Before you proceed, verify that the source tenant accounts have been discovered. For more
information see Discovering Accounts
In this topic:

l Create and run a Mailbox Collect Statistics Task

l Review the Mailbox Collect Statistics Task
l Review the events for the Mailbox Collect Statistics Task
l Review the statistics collected

Create a Mailbox Collect Statistics Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Mail tile, or click Open from the Mail tile to open the Accounts and User Data dashboard.
5. Select the Mailboxes tab and then select List View if not already selected.
6. Select the accounts in the list from where you want to collect statistics. You can use search, filtering or
collections to quickly navigate through the list of mailboxes. You can select the check box in the table header
to select all the accounts.
7. Click Collect Statisticsfrom the Actions ribbon. The New Collect Statistics Task wizard opens.
8. Step 1:Description
a. Select the check box Refresh mailbox statistics which have been already collected in the
past if needed.

On Demand Migration User Guide

Mailbox Migration 96
 b. Click Next.

9. Step 2:Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Mailbox
Collect Statistics Task.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Review the Mailbox Collect Statistics Task

1. Select the Tasks tab.
2. Select the Mailbox Collect Statistics Task that you want to review.

On Demand Migration User Guide

Mailbox Migration 97
 3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is Mailbox Assessment.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - The number of events that the task encountered.

Review the Mailbox Collect Statistics Task Events

1. Select the Tasks tab.
2. Select a task named Mailbox Collect Statistics Task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Mailbox Assessment.

On Demand Migration User Guide

Mailbox Migration 98
Review the statistics collected
1. Select the Mailboxes tab and then select List View if not already selected.
2. Inspect the results of the task in the table as described below:
a. Name - Name of the account in the source tenant.
b. All Items - Number of items in the mailbox. If there is no value the account has not yet been
assessed or the mailbox has not been used.
c. Size- Total size of all the items in the mailbox. If there is no value the account has not yet been
assessed or the mailbox has not been used.

Assessment
When you complete the collection of statistics for the mailboxes you can view the reports about the mailboxes. Open
the Assessment view to see the reports described below.

l Mailbox statistics
l Total mailboxes
l Total size
l Average size
l Maximal size
l Average Item Count
l To clean up
l The users not logged on to mailbox for 30 days
l The users not logged on to mailbox for 90 days

On Demand Migration User Guide

Mailbox Migration 99
 l The users never logged on to mailbox
l Disabled users with mailbox
l Inventory
l Mailboxes with archive
l To adjust
l Mailboxes with duplicate user name

When you are done with the assessment you are ready to start the migration.

Migrating Mailboxes
NOTE: Before you proceed, verify that the mail-enabled accounts in the source tenant have been discovered
and matched. For more information see Discovering Accounts

Considerations
l The following types of mailboxes are supported: Regular, Room, Equipment (Resource), Shared.
l In case of remigration, On Demand Migration remigrates mail, calendar, task, and sticky note items that
have changed in the source mailbox to the target mailbox. Also, calendar items that have been removed
from the source mailbox will be removed from the target mailbox. remigration of other types of items that
have been modified or deleted in the source mailbox is not supported.
l During the mail migration, users might receive email to both source and target mailboxes. Apparently the
users might want to receive the email sent to both mailboxes or keep custom forwarding, if any. To achieve
this, we automatically set up mail forwarding from target to source which works until the clients are switched
to the target tenant.

In this topic:

l Starting a Mail Migration Task

l Reviewing the Mail Migration Task

Starting a Mail 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. Click the Mail tile, or click Open from the Mail tile to open the Accounts and User Data dashboard.
5. Click the Mailboxes tab. The Mailboxes List opens. If you don't see a list of mailbox-enabled accounts, you
must run the New Account Discovery Task again.
6. Select the mailbox accounts in the list that you want to migrate. You can use search, filtering or collections to
quickly navigate through the list of mailboxes. You can also select the check box in the table header to select
all the mailbox accounts.
7. From the local toolbar, select Migrate Mail. The New Mail Migration Task wizard opens.

On Demand Migration User Guide

Mailbox Migration 100
8. Step 1: Licensing Plan
a. Set license at the target - select this check box to assign a selected license to migrated mailbox
accounts in the target tenant. Clear the check box to skip license assignments for migrated
mailbox accounts.
b. Select the licensing plan - this dropdown list appears if the Set license at target check box is
checked. Select the licensing plan from the dropdown list that you want to assign to migrated
mailboxes.
c. Specify how the selected licensing plan will be assigned to the target accounts:
l Assign the plan to accounts without Exchange Online option. Licensed users will
retain the existing plans - Retain the existing licenses and assign the selected plan only to
unlicensed accounts (default). Licensed users will retain the existing plans.
l Assign the plan to all accounts. Licensed users will be switched to the selected plan
- Replace all license assignments with the licenses from the selected plan. Licensed users
will be switched to the selected plan.

NOTE:
l Resource mailboxes that have not been licensed on the source tenant will retain the
unlicensed status.
l Licensed resource mailboxes will be handled according to the selected option.
l In case no usage location is set on the target the source value will be used for the
assigned license. Otherwise the target usage location value remain unchanged and
can be modified manually, if necessary.
l If no license plan is selected users that are unlicensed at the target will fail to migrate.
l Selected licensing option is only applicable to Exchange Online. It does not affect the
licensing plans picked for OneDrive Migration

d. Click Next.
9. Step 2: Migration Options
a. Specify a migration flow:
l From Primary Mailbox to Primary mailbox - migrate content of the primary mailbox
(default scenario.)
l From Archive mailbox to Archive mailbox - migrate content of the archive mailbox.
l From Archive mailbox to Primary mailbox - restore archived content to primary mailbox.
l From Primary mailbox to Archive mailbox - migrate some of the content of the primary
mailbox to archive. Useful with the specific Migration Options selected.
b. Specify which mailbox items you want to transfer to the target by selecting the appropriate check
box:
l Migrate Mail - select this option to migrate email items.
l Migrate Calendar - select this option to migrate calendar items. The organizer of the
calendar item will be mapped to the corresponding target tenant user account. Invitees in
calendar items are retained as the source tenant user.

On Demand Migration User Guide

Mailbox Migration 101
 NOTE: The source tenant links to Microsoft Team meetings in calendar items are
retained and must be migrated separately. For more information see Migrating
Meeting Links.

l Migrate Tasks/Notes - select this option to migrate tasks and notes.

l Migrate Contacts - select this item to migrate contacts.
l Migrate Recoverable Items - select this option to migrate recoverable items. If the check
box is unchecked these items will not be transferred.
l Reset Migration - Select this option only when you need to do a full re-migration and not a
delta sync of your source content to a target. E.g. You had to delete content from the target
mailbox and want to re-migrate the source again.
10. Step 3: Migration Settings
TIP: It can take a while to migrate mail to archive mailboxes. Source mailboxes that have archives
can be easily selected using Inventoryreport on Assessment view of Mailboxes. It would be useful
to rerun the Discovery task to update the information.

a. Specify which mailbox settings you want to transfer to the target by selecting the
appropriate check box:
l Migrate OWA Inbox Rules - select this option to migrate OWA Inbox rules. For all
mailboxes that are migrated to existing target mailboxes, On Demand Migration removes the
existing rules from the target tenant like OWA Inbox rules and the rules created in Outlook
from the target tenant including previously-migrated rules. Then all the rules from the source
are migrated to the target.
l Migrate Mailbox Delegation - select this option to migrate delegation permissions. Mailbox
delegation permissions like Full Access, Send As and Send On Behalf can be transferred
if the matched delegate exists in the target tenant. If the matched delegate does not exist,
mailbox delegation cannot be migrated and an error event will occur. If the target mailbox
delegation is not set, the mailbox delegation will be transferred as is. If the mailbox
delegation has been set in the target tenant before the migration starts, rules and exceptions
specified in Migrating Delegate Access Permissions topic in the On Demand Migration for
Email User Guide are applied to set the mailbox delegation.
l Enable Automapping for shared mailboxes - Auto-mapping is an Exchange &
Exchange Online feature. Once enabled, any auto-mapped mailbox will be opened
by the delegate's Outlook client in a persistent state with Full Access permissions
and cannot be closed by the user. If users want to remove the auto-mapped mailbox
from their Outlook client, administrative intervention is required to remove the Full
Access permission or clear the auto-mapping flag.
l Migrate Folder Permissions- select this option to migrate folder permissions. If folder
permissions in the target mailbox do not exist, then folder permissions from the source
mailbox will be transferred as is. If folder permissions were already set in the target mailbox
before the migration starts, rules and exceptions specified in Migrating Folder Permissions
topic in the On Demand Migration for Email User Guide are applied to set the folder

On Demand Migration User Guide

Mailbox Migration 102
 permissions.

NOTE: Migration of folder permissions for Recoverable Items is not supported.

l Migrate Auto-Reply - select this option to migrate auto-reply messages and settings.
b. Click Next.
11. Step 4: Mail Flow
a. Enable/Disable Mail Forwarding - select this check box to control mail forwarding. This check box
is selected by default. When this check box is selected, you can choose from the following options:
l Enable Mail Forwarding - Enable Mail Forwarding (on by default for the initial New Mail
Migration Task) from Target to Source. On Demand Migration assumes that end-users will
not be using their new target mailboxes immediately after the first "Migrate Mail" task (cut-
over), so forwarding is set on the new target mailbox to forward any new mail that is received
in the target back to the source. This way any new mail is assured to be delivered to the
active end-user mailbox.
l Mail forwarding direction - Set the mail forwarding direction by choosing From
target to source or From source to target. From the On Demand Migration table of
mailboxes, the forwarding email is in the Source Mailbox / Target Mailbox depending
on the mail forwarding direction selected. See the Mail Flow column value (To
Source or To Target) which can be switched with the switch mailboxes functionality
(see Mail Forwarding).
l Custom domain for forwarding - Specify the custom domain name for forwarding
email addresses. If the domain is omitted or does not exist, the primary SMTP
address will be used.
l Disable Mail Forwarding - Choose this option to remove any populated mail forwarding
address. Use this option to remove forwarding addresses in source mailboxes before the
migration and target mailboxes after the migration. You cannot deactivate mail forwarding
using the switch mailboxes functionality described in the topic .
b. Migrate Litigation Hold Settings - select this option to migrate Litigation Hold settings and data as
described below. This option can be selected only when Enable Mail Forwarding is selected and
Mail forwarding direction is set to From source to target.
l Litigation Hold Settings
l LitigationHoldDate - setting is copied as-is from the source mailbox to the
target mailbox.
l LitigationHoldDuration - setting is copied as-is from the source mailbox to the
target mailbox.
l LitigationHoldEnabled - setting is copied if the value is set to True on the source and
False on the target.
l LitigationHoldOwner - the migration service will check if the configured user in the
source tenant is mapped to a user in the target and set appropriately before migrating
the setting.
l RetentionUrl - setting is copied as-is from the source mailbox to the target mailbox.
l RetentionUrl - setting is copied as-is from the source mailbox to the target mailbox.

On Demand Migration User Guide

Mailbox Migration 103
 l Litigation Hold DataThe following data will be copied from the Recoverable Items folder:
l Versions
l Purges
l Discovery Holds

NOTE: The configuration settings for Discovery Holds will not be copied as part of this
feature. When the Litigation Hold option is enabled, the calendar data is synced only during
the final cut over.

CAUTION: Migration of Litigation Hold settings and data will fail if the target mailbox
doesn’t have the right license type.

c. Click Next.
12. Step 5: Mail Folders
a. Specify which mail folders to migrate and where they should be migrated by selection one of the
following options
l Migrate all folders - select this option to migrate all folders from the source to the tenant.
Mail will be migrated to a folders with the same name in the target tenant.
l Migrate all folders except - select this option to ignore the selected mailboxes and
optionally provide an alternate folder name to migrate all other folder contents. When you
select this option the following options are also available:
l Folders to ignore: Choose from Deleted Items, Junk Email, Drafts, Conversation
History, Sent Items, and Inbox. You can also specify one or more custom folder
names separated by a semicolon.
l Migrate specific folders - select this option to include the selected mailbox folders and
optionally provide an alternate folder name to migrate the specified folder contents. When
you select this option the following options are also available:
l Folders to include: Choose from Inbox, Sent Items, Drafts, and Deleted Items. You
can also specify one or more custom folder names separated by a semicolon.
l Migrate content to a custom folder - select this option to migrate content from source
mailbox to a custom folder. Calendar, contacts, and rules are not migrated into this folder. To
run incremental migration, a mail migration task should be created with the same folder
name. Any change in the folder name will be treated as a migration to a new custom folder.
l Custom folder name - specify the name of the custom folder where content will
be migrated.
l Migrate to folder - select this option to specify a custom target folder for well known source
folders such as Inbox, Deleted, Archive, and Sent Items. For example, the Inbox folder from
the source tenant can be migrated to the Inbox-Migrated custom folder in the target tenant. If
you do not provide a target folder name then the mail migration service will migrate the
contents of the source folder to a folder with the same name on the target.
b. Click Next.
13. Step 6: Date Range
Limit the date range for content transfer. You can set any of the following options:

On Demand Migration User Guide

Mailbox Migration 104
 a. Migrate mail before to set end date for the date range
b. Migrate mail after to set start date for the date range
c. Click Next.
14. Step 7: Notification
a. Select the options as described below:
l Send notification email after the mail migration is completed - select this option to
send a notification email when the mailbox migration task completes. The notification is sent
whether or not the mailbox migration succeeds unless the Only in a case of failure option
is selected.
l Only in a case of failure - select this option to send the notification email only when one or
more mailboxes cannot be migrated. When this option is selected, a notification email will not
be sent if all the mailboxes are migrated successfully.
l Recipients - enter a semicolon-delimited list of mailboxes where the notification will be sent.
The mailbox of the current user will be entered by default and can be changed.

NOTE: Notifications are sent from [email protected]. Recipients

must add this email address to the Safe Senders List.
To add the email address to your Safe Senders list in Microsoft Outlook, do the
following:

a. On the Home tab, click Junk, and then click Junk E-mail Options.
b. On the Safe Senders tab, click Add and add the no-reply@quest-on-
demand.com e-mail address.

The notification that is sent will contain the following information in the email body:
l Project id - the unique identified of the project.
l Task id - the unique identifier of the task.
l Type - the type of the task: Mail Migration.
l Created - the data and time when the task was created.
l Modified - the most recent date and time when the task was modified.
l Status - the state of the task.
l Last operation - The last recorded event in the task.
l Schedule - indicates when the task was run.
l Mailboxes - The number of mailboxes selected for this migration categorized by migration
status (New, Stopped, In Progress, Failed, and Completed) and count.

b. Click Next.
15. Step 8: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.

On Demand Migration User Guide

Mailbox Migration 105
 l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
16. Step 9: Reporting
Select the checkbox Generate detailed report of migration errors to generate a migration error report
when you run the Mail MigrationTask.
You can download the report from the Reports tab of the Accounts and User Data 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.

17. Step 10: Summary

a. Review the task summary. You can specify a custom task name.
b. Click Finish to save or start the task depending on the schedule option selected.

NOTE: Before the actual mail migration begins, a mailbox is activated by fetching a list of calendars using
Graph API and delegated type of permissions. This is necessary as per Microsoft's recommendation to set
the calendar configuration correctly before running the meeting link task.

Reviewing the Mail Migration Task

You can track a task's progress from the Tasks tab, view the summary on the Dashboard or monitor alerts and
notifications in Events.
You can track the migration of objects from the Mailbox State column in the Mailboxes list view. The column values
are as follows:

Column value Description

New Migration has not yet started.

Provisioning Mailbox is being provisioned.
Provisioning failed Mailbox provisioning failed

Migrating Migration of this object has started.

Migrated Migration is complete and successful.
Migrated with Issues Migration is completed with errors.
Migration failed Migration did not succeed
Migration stopped Migration canceled by the user
Switched Mailbox is switched between source and target.

On Demand Migration User Guide

Mailbox Migration 106
Migrating Meeting Links
When a calendar item with a link to a Microsoft Team meeting is migrated, the link to the original Team meeting in
the source tenant is retained. Use the Meeting Link Migration Task to update Microsoft Team meeting links in the
target tenant.
How it works: The meeting link migration task creates a new Team meeting with the original meeting details in the
target tenant. It sets the target user as the organizer. This new meeting invite must be accepted by all participants.
The original meeting migrated to the target is canceled. The cancellation email is automatically sent out to the
organizer and recipients.

Considerations
l The attendee list is not updated to match the target domain.
l A new meeting is created if the migrating user is the organizer of that particular Team meeting.
l A meeting is not recreated if the source meeting was created in Microsoft Teams through a Teams channel.
l On Demand Migration recreates present and future meetings, both one-time and recurring meetings.
Meetings that happened in the past are migrated with Calendar migration.
l Recurring meetings with modified instances are reset to original settings after migration.
l The subsequent runs of the Meeting Link Migration Task will skip the meetings which were
previously processed.
l Properties like a flag and categories are not supported with this migration.

IMPORTANT:
Mailbox migration with the Migrate Calendar option selected, must be completed before starting this task.

To migrate meeting links:

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 the Mail tile, or click Open from the Mail tile to open the Accounts and User Data dashboard.
5. Click the Mailboxes tab. From the Mailboxes List, select the accounts in the list that you want to migrate.
You can use search, filtering or collections to quickly navigate through the list of mailboxes. You can also
select the check box in the table header to select all the mailbox-enabled accounts.
6. From the Mailboxes List toolbar, click More Actions and then select Meeting Link Migration. The New
Meeting Link Migration Task wizard opens.
7. Step 1: Custom Email Message
Customize the message in the text box. The message will be sent in the cancellation email to the mailboxes
of target attendees. If mail forwarding from the target to the source is not configured for them, the attendees
in the source tenant will not receive the cancellation email. As a result, they will observe both the original
meeting, which was canceled, and the new one created by the On Demand service.

8. Step 2: Notification
Send notification email once the task is completed - select this option to send a notification email when
a discovery task completes.

On Demand Migration User Guide

Mailbox Migration 107
 l Only in a case of failure - Select this option to send the email if the discovery 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.

9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Review the task summary. You can specify a custom task name. Default name is Meeting Link
Migration Task.
b. Click Finish to save or start the task depending on the schedule option selected.

How to track the migration

You can track a task's progress from the Tasks tab and filter for tasks where Type = Meeting Link Migration. You
can view the summary on the Dashboard or monitor alerts and notifications in Events.

Mail Forwarding
To support the customer preferences related to mail forwarding, the following behavior is now supported for mail
migration task in case forwarding is not set using On Demand Migration (Mail Flow column is empty) and for
mailbox switch (standard and reverse scenarios) tasks:

Before After

Task Source. Target. Source. Target.

Type ForwardingSMTPAddres ForwardingSMTPAddres ForwardingSMTPAddress ForwardingSMTPAddress
s s

Mail Points to target * Not set / Set to any Not set (cleared) Source.PrimarySMTPAddress
migration SMTP address

Points to any SMTP Not set / Set to any Remains unchanged Source.PrimarySMTPAddress
address except for SMTP address
target *

Not set Not set / Set to any Not set Source.PrimarySMTPAddress

SMTP address

Switch Not set / Set to any Points to source** Target.PrimarySMTPAddres Not set (cleared)

On Demand Migration User Guide

Mailbox Migration 108
 Before After

Task Source. Target. Source. Target.

Type ForwardingSMTPAddres ForwardingSMTPAddres ForwardingSMTPAddress ForwardingSMTPAddress
s s

(From SMTP address s or one of the existing email

source to addresses from selected
target custom domain for
option) forwarding, if set

Not set / Set to any Points to any SMTP Target.PrimarySMTPAddres Remains unchanged
SMTP address address except for s or one of the existing email
source ** addresses from selected
custom domain for
forwarding, if set

Not set / Set to any Not set Target.PrimarySMTPAddres Not set

SMTP address s or one of the existing email
addresses from selected
custom domain for
forwarding, if set

Unswitch Points to target * Not set / Set to any Not set (cleared) Source.PrimarySMTPAddres
(From SMTP address s or one of the existing email
target to addresses from selected
source custom domain for
option) forwarding, if set

Points to any SMTP Not set / Set to any Remains unchanged Source.PrimarySMTPAddres
address except for SMTP address s or one of the existing email
target * addresses from selected
custom domain for
forwarding, if set

Not set Not set / Set to any Not set Source.PrimarySMTPAddres

SMTP address s or one of the existing email
addresses from selected
custom domain for
forwarding, if set

* Target.PrimarySMTPAddress or any of Target.EmailAddresses

** Source.PrimarySMTPAddress or any of Source.EmailAddresses

Switch Mailboxes
The switch mailbox task allows customers to set up mail forwarding as the final step in the migration and mark the
mailbox state as Switched. This task may not be required if forwarding was set during the mail migration task.

To start a Switch Mailbox 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. Click the Mail tile, or click Open from the Mail tile to open the Accounts and User Data dashboard.

On Demand Migration User Guide

Mailbox Migration 109
 5. Click the Mailboxes tab. The Mailboxes List opens. Select the mailbox accounts in the list that you want to
switch. You can use search, filtering or collections to quickly navigate through the list of mailboxes. You can
also select the check box in the table header to select all the mailbox accounts.
6. From the local toolbar, click Switch Mailboxes. The New Mailbox Switch Task wizard opens.
7. Step 1: Mail Flow
a. Select options as described below:
l Mail forwarding direction - Set the mail forwarding direction by choosing From target to
source or From source to target. From the On Demand Migration table of mailboxes, the
forwarding email is in the Source Mailbox / Target Mailbox depending on the mail forwarding
direction selected. See the Mail Flow column value (To Source or To Target) which can also
be switched as part of a migration task (see Migrating Mailboxes).
l Custom domain for forwarding - Specify the custom domain name for forwarding
email addresses. If the domain is omitted or does not exist, the primary SMTP address
will be used.
l Mark Mailbox State column as Switched – select this check box to change the Mailbox
State from its current value to “Switched”.
b. Click Next.
8. Step 2: Notification
a. Select options as described below:
l Send notification to original mailboxes – select this check box to configure a notification
to send to the user’s original mailboxes
l Send notification to new mailboxes – select this check box to configure a notification to
send to the user’s new mailboxes

The notification that is sent can be customized for the following attributes:
l Sender’s email address – the value that should be displayed as the Sender’s
email address
l Send from – the value that should be displayed as the Sender’s Display Name
l Subject – the text that should be displayed as the message Subject
l Message – the text that should be displayed in the message body
b. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
a. Run now - task runs immediately.
b. Run later - task must be started manually.
c. Schedule - task will be started at a future date and time. Enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Review the task summary. You can specify a custom task name.
11. Click Finish to save or start the task depending on the schedule option selected.

On Demand Migration User Guide

Mailbox Migration 110
Switching Applications in a Domain
Move Scenario
When performing a tenant-to-tenant migration that includes a domain move, On Demand Migration needs to refresh
the source and target usernames and email addresses after the domain move to ensure that the Desktop Update
Agent works as expected. To use the Desktop Update Agent after moving a domain from one tenant to another,
perform the following procedure:

1. Complete the Domain Move.

2. Confirm that the updated usernames and email addresses are shown in the source and target tenants.
3. Re-run the New Account Discovery Task wizard to refresh source usernames and email addresses.
4. Re-run the New Account Matching Task wizard to refresh target usernames and email addresses.
5. Run the New Switch Applications Task wizard. Select the options to Skip mailbox state validation and
Skip OneDrive state validation if the account migration states were reset to Matched. For more
information, see Configuring the Switch Applications Task in the Desktop Update Agent User Guide.

NOTE: If you run the New Switch Applications Task before the domain move is complete, you will not need
to re-run the task since the Desktop Update Agent will check the source and target user information at the
time the end-user runs the tool.

On Demand Migration User Guide

Mailbox Migration 111
 4

OneDrive Migration
When the user accounts are matched or migrated, you can transfer the content of their OneDrive for Business
stores to the target tenant.

What We Migrate
Migration limitations indicated below may not be an exhaustive list of limitations as some may appear in unique
customer migration scenarios, or arise due to platform or legacy support restrictions. In some cases, a solution to a
limitation may already be on the product roadmap.
Quest On Demand migrates the following OneDrive components:

Objects and content types

Object Support Notes

Document
Document size can be up to 100 GB.

Authorship properties: ✔
l Created Date
l Created by
l Last Modified Date
l Last Modified By

Document properties ✔

Document permissions ✔

Versions and Version History ✔

Folder

Properties ✔

Folder permissions ✔
Permissions

Direct Sharing Permissions ✔ Permissions for:

l Internal Users
l Groups

On Demand Migration User Guide

OneDrive Migration 112
 Object Support Notes

l Guest (External) Users

Custom level permissions ✔

Link Sharing Permissions ✔ Permissions for:

l Internal Users
l Groups
l Guest (External) Users

M365 security and compliance features

Legal Hold ✖

Retention Labels ✖

Microsoft Information Protection policies and ✖

labels
M365 Compliance Customer Lockbox ✖
Power Platform features

Power Apps ✖

Power Pages ✖

Power Automate (Flow) ✖

Power Virtual Agents ✖

Others

Microsoft public preview features ✖ In general, Microsoft public preview features are
not supported in production migrations. These
features may also take additional time to fully
develop and test for release to production.
Personal SharePoint Lists ✖

SharePoint subsites, lists and libraries added ✖

to a user's OneDrive

Limitations
Only the latest version of frequently updated files such as outlook PST files, database files and log files will
be migrated.

Considerations
Before starting the OneDrive migration consider the following:

l When active or expired Sharing Links are migrated, existing permissions are converted to direct permissions
in the target tenant.
l Migrating Sharing Link permissions for external users requires the external user be an Azure Active
Directory guest.

On Demand Migration User Guide

OneDrive Migration 113
 l Migrating Authors and Editors will only map to the Primary SMTP Address. Multiple SMTP addresses are
not currently supported.
l Migrating a OneDrive user Recycle Bin is not supported.
l Document with URLs longer than 400 characters cannot be migrated to a target tenant.
l Very large OneDrives with hundreds of thousands of files or files that are 500 GB or larger, should be divided
into two or more OneDrives to improve migration throughput.

Prerequisites
l You must match or migrate user accounts in the migration project to ensure that membership, content
ownership, and permissions are processed correctly.
l The target tenant should has the fully configured OneDrive feature with a valid license plan. Licenses can be
automatically assigned to the target users during the migration.
l Tenant administrator consents are granted for source and target tenants .The following consents should be
granted for OneDrive migration feature:
l Migration - Basic
l Migration - SharePoint

If tenant administrator consents are not granted or have expired, account discovery will be deactivated and
you will be unable to continue.
l Tenant administrator credentials must also be provided for both tenants in the Configure
Connections dialog.

Dashboard
The On Demand Migration Dashboard tab in the Accounts and User Data workspace provides summary
information about migration tasks and events.The OneDrive users tile indicates the number of OneDrive users and
the status of their migration.

OneDrive List View

The List View displays the summary of the OneDrive information from the source and target tenants. Initially, the List
View displays the list of accounts and other columns are blank. As you run the discovery, collect statistics and

On Demand Migration User Guide

OneDrive Migration 114
migration tasks, the list view will display more information about the accounts and the state of the OneDrive
migrations.
To open the List View, open the Accounts and User Data workspace. Then select the OneDrive tab and then select
List View if not already selected.
The List View has several predefined filters to help you search for accounts based on OneDrive account
information:

l Last Run Status - see description below.

l Migration State - see description below.
l Account Matching - returns the list of accounts that are either Matched or Unmatched.
l Collect Statistics Status - see description below.

The columns in the List View are as described below. Use the Edit Columns list view menu to show or hide
columns in the list:

1. Name - name of the account in the source tenant.

2. Migration State - indicates various stages in the migration process.
l <blank> - no task has been run yet. Use Unknown in the filter.
l Discovery Failed - Failed to retrieve source site or statistics data, or other errors occurred.
l Discovered - Retrieved statistics from source.
l Not Migratable - Source has no license or OneDrive not provisioned.
l Provisioning - Started provisioning OnDrive in the target tenant.
l Provisioning Failed - OneDrive provisioning failed due to license or credential errors.
l Provision Pending - No provisioning errors, but OneDrive not provisioned after 1 hour. Customers
must rerun the migration task within 24 hours or manually provision the target
l Provisioned - OneDrive provisioned and verified in target tenant.
l Queued - OneDrive is waiting for migration service resources to be available. For more information,
see How Queuing Works.
l Migrating - Source and target tenants analyzed and migration started.

On Demand Migration User Guide

OneDrive Migration 115
 l Migration Failed - Critical error occurred nothing has been migrated. See task event details for
more information.
l Migrated with Issues - Some content is migrated but errors or warnings were encountered during
migration. Use a reporting task to look for missing files or other errors.
l Partially Migrated - Migration is successful, but source item count is larger than target item count
after migration. See task event details for more information.
l Migrated - OneDrive migrated successfully to the target tenant.
3. Collect Statistics - the state of the task for the account. An empty value indicates that the account has not
yet been assessed. Accounts that were an assessment was attempted will display a status as described
below. You can filter the table by selecting one of the following values in the Collect Statistics Status filter.
Click Clear All to reset the filter if necessary.
l Completed - OneDrive is provisioned and the statistics were collected successfully.
l Not Licensed/Provisioned - OneDrive is neither licensed nor provisioned and the statistics could
not be collected.
l Unavailable - the named account is not available and the statistics could not be collected.
l Not Started - collection of statistics has yet to be attempted for the named account.
4. Provisioning - When OneDrive is provisioned for the user on the target, the value is set to Completed.
5. Items Migrated (%) - percentage of files that have been migrated to the target
6. Source Items - Number of items in the OneDrive for the source account. If there is no value the account has
not yet been assessed.
7. Source Size- Total size of all the files in OneDrive for the source account. If there is no value the account
has not yet been assessed.
8. Source Last Modified - indicates the date and time of the last modification of the source OneDrive. Every
time the statistics or migration task is run this value will be updated according to the source date.
9. Target items - Number of items in the OneDrive for the target account. If there is no value, you did not
select the option in the New OneDrive Collect Statistics Task wizard to collect item count statistics from the
target account, the account is not available, OneDrive has not been provisioned or the account has not yet
been assessed.
10. Last Run Status - indicates the status of the latest task. Valid values are New, In Progress, Completed,
Failed, or Stopped..
11. Source UPN - User Principal Name (UPN) of the source account.
12. Source Root Url - relative path of the source OneDrive root URL.
13. Target UPN - User Principal Name (UPN) of the target account.

Collecting Statistics
The OneDrive Collect Statistics Task conducts an assessment of OneDrive related to the selected accounts in the
source tenant and provides the following information:

On Demand Migration User Guide

OneDrive Migration 116
 l The number of items in the OneDrive for each account and the total number of items across all selected
accounts where the assessment was possible.
l The total size of all the items in the OneDrive for each account and the total size of all items across all
selected accounts where the assessment was possible.

Each OneDrive Collect Statistics Task generates events. Events are milestones that a task achieves as it runs.
For example, when a OneDrive Collect Statistics Task starts, an event is logged and it appears in the events list.
When the number of accounts that are selected for assessment is large, the OneDrive Collect Statistics Task
divides the total number of accounts into manageable sets. Each set is called a batch. When a batch of accounts is
assessed, another event occurs.
NOTE: Before you proceed, verify that the source tenant accounts have been discovered. For more
information see Discovering Accounts
In this topic:

l Starting a OneDrive Collect Statistics Task

l Reviewing the OneDrive Collect Statistics Task
l Reviewing the events for the OneDrive Collect Statistics Task
l Reviewing the statistics collected

Starting a OneDrive Collect Statistics Task

1. Log in to Quest On Demand and choose an organization if you have 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 the OneDrive tile, or click Open from the OneDrive tile to open the Accounts and User
Data dashboard.
5. Select the OneDrive tab and then select List View if not already selected.
6. Select the accounts in the list from where you want to collect statistics. You can use search, filtering or
collections to quickly navigate through the list of mailboxes. You can select the check box in the table header
to select all the accounts.
7. Click Collect Statisticsfrom the Actions ribbon. The New OneDrive Collect Statistics Task wizard opens.
8. Step 1:Description
a. Statistics are collected from the source tenant by default.

Include collection of item count from target OneDrive accounts - select this option to include
item count statistics from the target account.

On Demand Migration User Guide

OneDrive Migration 117
 b. Click Next
9. Step 2:Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.

b. Click Next.

On Demand Migration User Guide

OneDrive Migration 118
 10. Step Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Collect target statistics - indicates whether you have opted to include item count statistics
from the target account.
v. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.

b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the OneDrive Collect Statistics Task

1. Select the Tasks tab.
2. Select the OneDrive Collect Statistics Task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is OneDrive Assessment.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Accounts (number) - number indicates the count of accounts in the source tenant that are
inspected. The values indicate the assessment category of the accounts. The categories are:

On Demand Migration User Guide

OneDrive Migration 119
 a. Completed - Number of accounts where OneDrive is provisioned and the total size and item
count was successfully assessed.
b. Stopped - Number of accounts where OneDrive could not be assessed because it is neither
licensed nor provisioned.
h. Events (number) - The number of events that the task encountered.

Reviewing the events for the OneDrive Collect Statistics

Task
1. Select the Tasks tab.
2. Select a task named OneDrive Collect Statistics Task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is OneDrive Assessment.
e. Summary - a descriptive statement about the event. Notice that the most recent event provides a
summary of the assessment across all accounts that could be assessed. The assessment details
contain the Total items count and Total file size from the source, and the Total target items
count from the target tenant if data is available.

On Demand Migration User Guide

OneDrive Migration 120
Reviewing the statistics collected
1. Open the Accounts and User Data workspace.
2. Select the OneDrive tab and then select List View if not already selected.
3. Review the statistics collected for each user account. See OneDrive List View for a description of
the columns.

On Demand Migration User Guide

OneDrive Migration 121
Migrating OneDrive
You can migrate OneDrive for discovered and matched accounts with large selection of migration options. These
options give you control over the scope of files migrated, permissions, licensing and version management

Recommendation
The OnDemand migration service for OneDrive attempts to provision OneDrive for accounts being migrated if
the OneDrive has not been provisioned. You can manually provision the OneDrive before a migration as
described below:

1. Provision OneDrive for accounts in the target tenant that don't have a OneDrive provisioned.
l For a small number of target users, you can manually provision the OneDrive from the Office 365
admin console of the target tenant.
l For a large number of target users, run a PowerShell script to provision the OneDrive. For more
details, see https://docs.microsoft.com/en-us/onedrive/pre-provision-accounts
2. OneDrive must be provisioned at least 24 hours before starting a migration.

In this topic:

l Starting a OneDrive Migration Task

l Tracking the progress of the migration task
l Viewing the report

Starting a OneDrive Migration Task

1. Log in to Quest On Demand and choose an organization if you have 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 the OneDrive tile, or click Open from the OneDrive tile to open the Accounts and User
Data dashboard.
5. Open the OneDrive tab and verify that the List View has displays the list of user Accounts. See Discovering
Accountsif the list is empty.
6. Select one or more accounts for which you migrate the OneDrive contents. This enables the Migrate
OneDrive menu option.
NOTE: To migrate OneDrive for user accounts in a collection

a. Select the collection from the dropdown menu in the top right corner labeled Select
Collection.
b. Select the accounts to migrate from the collection. To check all accounts, select the checkbox
in the list header.
c. Proceed to the next step.

7. Click Migrate OneDrive to open the New OneDrive Migration Task wizard and follow the steps described
below. The New OneDrive Migration Task wizard helps you configure the migration options and settings for

On Demand Migration User Guide

OneDrive Migration 122
 OneDrive for Business. The default settings are optimized for fast migration. You can change the options
and settings to address specific migration needs.

8. Step 1: Migration Options

a. Choose a migration action

l Overwrite target files - Select this option to overwrite the file in the target tenant if it was
previously migrated.
l Skip if the target file is the same version or newer - This is the default selection. When
this option is selected, the migration service will not migrate a file if the file already exists on
the target tenant and has the same or newer version than the file in the source tenant.
Select this option to speed up the migration process especially if you are starting multiple
migration tasks.
l Overwrite if the target file is older or make a copy if the target file is newer - Select
this option to overwrite the file in the target tenant if it was previously migrated and the file in
the target is an older version, or create a copy of the source file if it was previously migrated
and the file in the target is a newer version. When a copy is created in the target it will be
renamed. For example, Sample.txt will be renamed to Sample_migration_copy.txt.
If the file versions in the source and target are the same, it is skipped.

On Demand Migration User Guide

OneDrive Migration 123
 NOTE: Do not rename a previously migrated file or folder before the migration
completes. If you rename a previously migrated file or folder before the migration
completes, it may be unexpectedly overwritten even though you select the second or
third option. New files or folders are not impacted. The migration service compares
both file versions and modified date to determine older or newer files.

b. [Optional] Files are migrated to the root folder. You can specify an alternate target migration folder
l Relative folder path - specify the relative path to a folder where the OneDrive contents will
be migrated.
c. Click Next.
9. Step 2: Version Options

a. Specify the scope of file migration

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

NOTE: Only the latest version of frequently updated files such as outlook PST files, database
files and log files will be migrated

l Latest version only - This is the default selection. The most recent version of the file will be
migrated. All other versions will be ignored.
l 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.
l 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.
l Latest version and preceding versions - The version count includes the latest
version and the preceding versions in chronological order restricted to the Size Limit

On Demand Migration User Guide

OneDrive Migration 124
 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.
l 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 file 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.
l 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.
l 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.
l 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 file version does not exceed the selected size limit,
then the file and its versions will be migrated.
b. Click Next.
10. Step 3: Attribute Options
This step determines how file and folder attributes are migrated and managed by the migration service.

On Demand Migration User Guide

OneDrive Migration 125
a. Account display: Select which account will be displayed in the Created by and Modified by
properties of migrated content:
l System Account - This is the default selection. The Created by and Modified by properties
of the migrated file or folder is displayed as System Account.
l Matching target account - The Created by and Modified by properties of the migrated file
or folder is displayed as the target account that was matched with the source account. If the
target account cannot be found, the migration service records a warning event and the
properties of the migrated file or folder is displayed as System Account.
b. Permission migration: Select how the sharing permissions will be transferred to the target users:
l Do not migrate permissions - This is the default selection. Permissions associated with the
file being migrated will be ignored.
l Update permissions for migrated content - The permissions of files that are migrated will
be updated. Some files may be skipped if you selected the Skip if the target file is the
same version or newer in the previous step. Sharing Links are not migrated unless
Convert Sharing Links permissions to direct permissions is selected.
l Update permissions for all content - All file or folder permissions in the target tenant will
be updated whether or not they were migrated if the corresponding file or folder is present in
the source tenant. Sharing Links are not migrated unless Convert Sharing Links
permissions to direct permissions is selected.
c. Auto rerun: Select whether to migrate permissions with the Auto rerun task to reduce the task load
l Migrate permissions with the Auto rerun task - the permissions will be migrated with the
Auto rerun task after the migration completes.
d. Permission conversion

On Demand Migration User Guide

OneDrive Migration 126
 l Convert Sharing Links permissions to direct permissions - Select this option to convert
Sharing Links permissions of files or folders in the source tenant to direct permissions in the
target tenant.

NOTE:

a. Users can access their shared content through the Shared With Me view in OneDrive.
Some restrictions apply.
b. Some sharing permissions are not converted if the user has shared the file or folder
with more than 30 users. Only 30 users will receive direct permissions from the
Sharing Links, while others will not be processed due to a Microsoft limitation.
c. If a Sharing Link permission is removed on the source file or folder after it is migrated,
the links to this file or folder are still visible in the Shared with me and Shared by me
views in OneDrive, but the file or folder cannot be accessed.
d. Group permissions are not displayed in the Shared with me view because Microsoft
currently does not support this functionality.
e. For shared folders, only the top level folder is displayed in the folder tree.
f. For files and folders that do not exist in target tenant before migration the source
permission will always be used.
g. For files and folders that exist in the target tenant before a migration, the following
example describes how file sharing permissions will be managed. The rules are the
same for internal and external users as permission holders, or groups (Microsoft 365
group or security group) as permission holders.
For files
If Overwrite target files for selected migration is selected, the source file sharing
permission will be used.
If Skip if the target file is the same version or newer is selected, the target file
sharing permission will be used.
For folders
If either Overwrite target files for selected migration or Skip if the target file is
the same version or newer option is selected, the target sharing permission will be
used as a base. Any addition of permissions in the source will be added onto the
target.

e. Click Next

On Demand Migration User Guide

OneDrive Migration 127
11. Step 4: Licensing Plan

a. Set license at the target - select this check box to assign a selected license to migrated mailbox
accounts in the target tenant. Clear the check box to skip license assignments for migrated
mailbox accounts.
b. Select the licensing plan - this dropdown list appears if the Set license at target check box is
checked. Select the licensing plan from the dropdown list that you want to assign to migrated
mailboxes.
c. Specify how the selected licensing plan will be assigned to the target accounts:
l Assign the plan to accounts without Exchange Online option. Licensed users will
retain the existing plans - Retain the existing licenses and assign the selected plan only to
unlicensed accounts (default). Licensed users will retain the existing plans.
l Assign the plan to all accounts. Licensed users will be switched to the selected plan
- Replace all license assignments with the licenses from the selected plan. Licensed users
will be switched to the selected plan.

NOTE:
l OneDrive for Business that have not been licensed on the source tenant will retain the
unlicensed status in the target tenant.
l Selected licensing option is only applicable to OneDrive migration. It does not affect
the licensing plans picked for Mail Migration.

d. Click Next.

On Demand Migration User Guide

OneDrive Migration 128
12. Step 5: Filter Items

a. Set up filters as described below:

l All items - select this option to ignore filters. This is the default option and all OneDrive
Content for the selected account will be migrated.
l Items to exclude - select this filter option to exclude files and folders from the migration.
Then specify the filter criteria. Items are excluded if any of the following criteria are fulfilled:
l Exclude specific folders- provide a semicolon-separated list of relative paths to
folders that you want to skip. You can use slash or backslash. If it is convenient for
you, use spaces after semicolons, e.g., filteredfolder; somefolder/subfolder
l Exclude specific file types - provide a semicolon-separated list of file extensions.
The values are not case sensitive. You can use spaces and dots, e.g., .exe; dll;
bat; doc; pdf
l Exclude files created
l select Before from the dropdown. Then click in the date field that appears to
open the date picker and select a date. Files created before this date will not
be migrated.
l select After from the dropdown and then click in the date field that appears
to open the date picker and select a date. Files created after this date will
not be migrated.
l Exclude files modified
l select Before from the dropdown. Then click in the date field that appears to
open the date picker and select a date. Files modified before this date will not
be migrated.

On Demand Migration User Guide

OneDrive Migration 129
 l select After from the dropdown. Then click in the date field that appears to
open the date picker and select a date. Files modified after this date will not
be migrated.
l Exclude files bigger than (MB) - enter a numeric value. The maximum value is
1000 MB. Only integer values are supported.
l Items to include - select this filter option to include files and folders from the migration. Then
specify at least one filter criteria. Items are included if any of the following criteria are fulfilled:
l Include specific folders- provide a semicolon-separated list of relative paths to
folders that you want to include. You can use slash or backslash. If it is convenient for
you, use spaces after semicolons, e.g., filteredfolder; somefolder/subfolder
l Include specific file types - provide a semicolon-separated list of file extensions.
The values are not case sensitive. You can use spaces and dots, e.g., .exe; dll; BAT
l Include files created
l select Before from the dropdown. Then click in the date field that appears
to open the date picker and select a date. Files created before this date will
be migrated.
l select After from the dropdown. Then click in the date field that appears
to open the date picker and select a date. Files created after this date will
be migrated.
l Include files modified
l select Before from the dropdown. Then click in the date field that appears
to open the date picker and select a date. Files modified before this date
will be migrated.
l select After from the dropdown. Then click in the date field that appears
to open the date picker and select a date. Files modified after this date will
be migrated.
l Include files bigger than (MB) - enter a numeric value. The maximum value is 1000
MB. Only integer values are supported.
b. Click Next.
13. Step 6: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
14. Step 7: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.

On Demand Migration User Guide

OneDrive Migration 130
 l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
l 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.
b. Click Next.
15. Step 8: Auto rerun

a. Auto re-run task if target user(s) are missing any files or folders - Select this option to rerun
the migration task for files or folders that failed to migrate on the first run. The migration task will auto
rerun once only. Failure of the files to migrate the first time could be because of intermittent network
issues or throttling. We recommend that this setting remains selected.

This setting is enabled but read-only if the Migrate permissions in the Auto rerun task option is
selected in Step 2: Attribute Options. Auto re-run is not available if an alternate migration location
has been specified in Step 1 or item filters have been configured in Step 5.
The migration service will issue an event warning for all files that fail to migrate. You can also check
the batches for how many files failed to migrate.

b. Click Next.

On Demand Migration User Guide

OneDrive Migration 131
16. Step 9: Reporting

Select the checkbox Generate detailed report of migration errors to generate a migration error report
when you run the OneDrive Migration Task.
You can download the report from the Reports tab of the Accounts and User Data 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.

17. Step 10: Summary

On Demand Migration User Guide

OneDrive Migration 132
 a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name. The default name is OneDrive
Migration Task.
l Source tenant - name of the tenant where the statistics will be collected.
l Target tenant - name of the target tenant in this project.
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
l Priority - the priority of this task.
l File migration - migration action when a file is migrated.
l Versions to migrate - options to migrate the version history.
l Account to display - account name that will be displayed in the Created by and Modified
by properties of migrated content:
l Alternative migration location - default is the root folder or an alternate target
migration folder
l Sharing permissions - how sharing permissions will be transferred to the target users.
l Auto-rerun - option to rerun the migration task for files or folders that failed to migrate on
the first run.
l Reporting - option to collect and retain data for report generation.
b. Click Back to change configurations if necessary or click Finish to save and start the task
as scheduled.

Tracking the progress of the migration task

While the OneDrive Migration Task is running, click Assessment to track the progress of the migration task.

The following summary reports are available and described below.

l OneDrive Users
l Migration Progress is updated in real time.
l Migration Statistics

OneDrive Users
The Users figure at the top of the OneDrive users pane reports on the total number of OneDrive users to migrate.
Account migration and matching reports on the number of OneDrive users matched and not matched.
OneDrive provision in target reports on the number of provisioned users.

On Demand Migration User Guide

OneDrive Migration 133
Migration Progress
The migration progress pane reports on the status of the migration of OneDrive users. It is updated in real time.

Statistic Description

Last Run This data relates to the Last Run Status column on the List View tab. Show data from the last run
Status status: new, in progress, completed, failed, stopped.

Progress Started Users = The users listed on the List View tab with Migration Progress % greater than
of Started zero.
Users The bar chart shows the Migration Progress % for users. It shows how many users have
Migration Progress % at fewer than 50%, 50% to 95%, 95% to 99%, and 100%. For example, if
the diagram shows 63 users at 100% then 63 users have Migration Progress % value of 100%.
How is Migration Progress % calculated? It is calculated as a ratio of the number of target items to
the number of source items. If 10 items have migrated to the target and there are 100 items to be
migrated on the source then the ratio for that user Migration Progress % is 10%.

Average % This is the average Migration Progress % value for users on the List View.
for started
users

On Demand Migration User Guide

OneDrive Migration 134
Migration Statistics
The migration statistics pane reports on statistics recorded for the last 14 days.

l Total migration file size for entire project (last 14 days)

l Total migration file count for entire project (last 14 days)

Dependent on the scope of the file migration the content of OneDrive storage is transferred in batches that
can be submitted for processing to OneDrive at the same time to be processed concurrently, it can take a
while for OneDrive to complete processing of submitted batches. Refer also to the Events tab while the
migration task is running.

On Demand Migration User Guide

OneDrive Migration 135
Viewing the report
1. Select the Tasks tab.
2. Select the OneDrive Reporting Task (or your custom name) that you want to review.
3. In the task details pane that opens click Events (number).
4. Select the event with the description: Link to download the report is in the Details pane. Report link is active
for 1 hour.
5. Click the report link in the details pane.

6. You can rerun the OneDrive Reporting Task after 1 hour to generate another report, and follow the same
steps described here to view the report.

Assessment
After you start a OneDrive migration, open the Assessment view to see the reports described below.

NOTE: Click the Assessment button again to refresh the reports during a migration.

On Demand Migration User Guide

OneDrive Migration 136
l OneDrive Users

l Number of users
l Number of user accounts that are matched or unmatched
l Number of OneDrive accounts provisioned or not provisioned in the target tenant
l Migration Progress

l Last Run Status - number of user accounts in state of the migration process
l Progress of Started Users (Source/Target Items Ratio)
l Average % for Started Users

On Demand Migration User Guide

OneDrive Migration 137
l Migration Statistics

l Current Migrating Users - number of users that are currently migrating.

l Scope - indicates the performance of the migration within the last 14 days
l Total Migration File Size - total files size packaged or migrated within the last 14 days
l Packaged - total file size submitted for migration
l Migrated - total file size actually migrated
l Total Migration File Count - total files packaged or migrated within the last 14 days
l Packaged - total number of files submitted for migration
l Migrated - total number of files actually migrated
l File Size (per hour) - performance chart that indicates the file size packaged and migrated per hour. Data is
displayed for the last 14 days.

l File Count (per hour) - performance chart that indicates the number of files packaged and migrated per
hour. Data is displayed for the last 14 days.

On Demand Migration User Guide

OneDrive Migration 138
l Average concurrent migrating users (per hour) - indicates the average number of users being
concurrently migrated per hour. The optimization is managed seamlessly by the migration service to avoid
bandwidth or throttling issues.

On Demand Migration User Guide

OneDrive Migration 139
 5

Microsoft Teams Migration

On Demand Migration for Teams securely migrates Microsoft Teams and associated Microsoft 365 Groups across
Microsoft 365 tenants. You can also use this dashboard for migration of content for Microsoft 365 Groups without
Teams functionality. (Microsoft 365 Groups Migration). Microsoft Teams migration requires additional licensing.
Basic Microsoft Teams migration workflow consists of the following steps:

# Step

1 Create a 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
temporary Migration Manager 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 Microsoft 365 Groups and Provision teams on the target tenant. Target teams will be
owned by the target temporary Migration Manager account that is used to perform the
provisioning.
l The temporary Migration Manager account in the source tenant will be added to all source
teams as a member, and source private channels as an owner.
l The temporary Migration Manager account in the target tenant will be added to all target
teams and Microsoft 365 Groups as a member and an owner, and 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.

l Target temporary Migration Manager account will own all private channels migrated to the
target.

On Demand Migration User Guide

Microsoft Teams Migration 140
 # Step

8 remigrate teams to incorporate supported changes made after the migration task (step 7) was
started.
9 Monitor the progress and track issues

What We Migrate
Migration limitations indicated below may not be an exhaustive list of limitations as some may appear in unique
customer migration scenarios, or arise due to platform or legacy support restrictions. In some cases, a solution to a
limitation may already be on the product roadmap.
In this topic:

l Objects and content types

l Migration from an Education tenant to an Education tenant
l Migration from a Commercial tenant to a GCC High tenant

Objects and content types

Object Support Notes

Announcements partial Customized background picture for

announcements are not migrated
Applications partial Only Word, Excel, PowerPoint, OneNote and
List tab applications linked to files in the same
channel are supported. If you rename a tab in
the source team and then re-migrate, the
renamed tab will be migrated. The target will
then have two tabs, one with the old name and
one with the new name.
Applications including Shifts for schedule ✖
management
Archived team ✔ Archived teams will first be migrated to the
target tenant as active teams. Then they will be
archived in the target tenant. Archived team can
only be migrated once and remigrating archived
teams is not supported.
Attached images, media files, documents partial Preview icons are not migrated.
Authorship partial Authorship in messages is migrated as a string
with author name and creation date. File
authorship is supported.
Bots ✖

Calls and devices ✖ Contacts, contact groups, call history, voicemail,

and custom setup are not migrated. Devices and
device setup are not migrated.

On Demand Migration User Guide

Microsoft Teams Migration 141
Object Support Notes

Chats ✔ Images, media files and documents referenced

in one-on-one or group chats are stored in your
OneDrive for Business folder. They must be
migrated using the On Demand Migration for
OneDrive service, before you migrate the chats.
File links in team chats will not work after chat
migration if the files are moved to another folder
in the source tenant.
Files that are linked to the private chats and
meetings are migrated but do no display in the
Files tab of private chats and meetings. In the
source tenant a member removed from a chat
can still see the history of the chat in the source.
In the target tenant, members cannot see the
history of chats they have been removed from.
Users deleted on the tenant are not migrated, so
do not appear as members of a chat on the
target. Deleted users remain visible as members
of a chat on the source. One-to-one chats,
where one of the users is deleted, are migrated
for the user that is still a member of the tenant.
If a domain move is done after a chat migration,
the Conversation Tabs in migrated chats will not
work because the URL of those tabs remain
mapped to the original target domain.
Private one-to-one chats are migrated as group
chats. All the messages in the migrated chats
are posted by the temporary Migration Manager.
Private one-to-one chats with a Skype user are
not migrated. The Microsoft Graph API List chat
messages do not support querying messages of
that type.
Private one-to-one chats initiated by an external
user (user from another tenant) are not
migrated. Private one-to-one chats not initiated
by an external user are migrated, and in the title
the external user’s real name is replaced with
the text "External user".
Loop components in chats are not supported.
Errors in chat migration will not be linked to a
particular user since chat always happens
among multiple users. As a result, those errors
will not be visible in Exported Error Logs since
the logs are exported per user.

Code snippets ✖

Conversations ✔ The target tenant's temporary Migration

Manager account is displayed as the owner of

On Demand Migration User Guide

Microsoft Teams Migration 142
Object Support Notes

all migrated messages on the target: The

original owner and creation time of a message
are displayed in the first line of the message
starting with "Originally posted by...".
Individual messages larger than 4 MB will not
migrate. Messages containing several inline
messages can exceed 4MB. The chat will
migrate without the large messages. An error
will display in the On Demand Migration for
Teams Events tab of the form: Request failed
with RequestEntityTooLarge status code
(Request Entity Too Large).

Custom tags for teams ✔ GCC tenants do not support tags.

Custom website tab ✔

E-mail attachments ✖

Emoji, GIF, Sticker, Praise, memes ✔

File preview partial Preview icons of files attached to a post are not
migrated. The file is migrated as a link.
Formatted text ✔

Guest accounts and conversations ✔

Images posted inline from buffer ✔

Inbox folder and Calendar from the group ✔

mailbox associated with a team
Link preview of public images ✔ Preview icons are not migrated. Only the link is
migrated.
Link preview of public sites partial Preview icons are not migrated. Only the link is
migrated.
Lists partial Lists must be created in the same SharePoint
site used by the team or Private Channel. You
must select the Standard and Customized (All
SharePoint Content) option in the Migration
Options step of the New Teams Migration Task
to allow the migration of Lists and their content.
Meeting conversations ✔ Conversations are migrated as private chats,
but cannot be written to the original Teams
meeting. Conversations in a channel stay in the
channel rather than a private chat, and are
migrated to the target channel with a Teams
migration task.
Meeting Notes in private meetings ✖

Meeting recordings partial Recordings of scheduled meetings in a team

channel, stored in SharePoint or OneDrive, are
migrated.

On Demand Migration User Guide

Microsoft Teams Migration 143
Object Support Notes

l Meeting recordings stored in Microsoft

Stream (Classic) are not migrated; the
link to the recording on the source team
channel is retained.
l On Demand does not support meeting
recordings in a group chat. Recordings
in group chats and one-to-one chats
cannot be migrated with the On Demand
Migration for Teams service. Since the
recording file is stored in the chat
organizer's OneDrive account, you can
use the On Demand Migration for
OneDrive service to migrate recordings.
l On Demand does not support meeting
recordings for "Meet now" meetings.

@mentions: ✔ All @mentions from the source will be created

as plain text with blue color in the target tenant
l Users (includes @Everyone) to avoid notification to end users during
l Channels migration.

l Teams

OneNote partial When the team name in source tenant is

different from the one in target tenant, a blank
default team’s notebook (with the target team
name) will be created in target tenant. The
original default team’s notebook (with the source
team name) will be migrated correctly by Team’s
migration. This results in two default team’s
notebook in target.
OneNote tabs migration fails if the team
contains a large number of items (folders or
files, some of which could be OneNote entities
such as notebooks, sections or section groups)
and the following error message is reported:
Request failed with Forbidden
status code (Forbidden). { "error":
{ "code": "10026", "message": "One
or more of the document libraries
on the user or group’s OneDrive
contains more than 20,000 OneNote
items (notebooks, sections, section
groups). Please try again
later."....Workaround: Before
proceeding with migration consider the following
Microsoft recommendations to avoid the
problem: https://docs.microsoft.com/en-
us/archive/blogs/onenotedev/onenote-api-calls-
fail-with-a-large-number-of-items-in-a-

On Demand Migration User Guide

Microsoft Teams Migration 144
Object Support Notes

sharepoint-document-library

OneDrive Shared Library partial OneDrive Shared Library must be created and
associated with a team in the same SharePoint
site. You must select the Standard and
Customized (All SharePoint Content) option in
the Migration Options step of the New Teams
Migration Task to allow the migration of
OneDrive Shared Library and its content.
Planner partial Planner Tab, Buckets, Tasks and Comments. If
there are more than 400 Planner tasks in a
bucket then On Demand migrates the first 400
tasks only. When migrating Planner tasks,
assignees in target tasks will receive a
notification after migration.

Private channels ✔ See Channel settings subsection below.

Reaction ✖

Rich card attachments ✖

Self-Chat ✖

Shared channels ✔ See Channel settings subsection below.

SharePoint document libraries (Files) ✔

Standard channels ✔ See Channel settings subsection below.

Team owners and team members ✔ Only for Microsoft 365 Groups that are migrated
/ matched. Teams and groups with dynamic
membership can be migrated but cannot be
merged.
The memberships is not updated in Teams
immediately after membership migration. It
takes a while before Microsoft synchronizes
memberships between groups and Teams.
Workaround: Wait for membership
synchronization.

Team picture ✔

Team settings partial Target team settings are not updated if you re-
run the provisioning task.
Allow members to upload custom apps and
Team code settings are not migrated.

Timestamps ✔

Whiteboards in private meetings ✖

On Demand Migration User Guide

Microsoft Teams Migration 145
Object Support Notes

Wiki sections and pages ✖

Files uploaded from mobile application

Media files ✔

Voice recordings ✖

Documents ✔
Channels and Channel Settings

General settings ✔ Channel isFavoriteByDefault property migration

is not supported. Workaround: Enable
Automatically show this channel in
everyone’s channel listoption for the channel
manually in your Teams client.

Standard channels ✔

Private channels ✔ The Teams client will not display the updates
immediately. It may take up to 24 hours before
the changes are reflected due to Microsoft
limitations. Private channel members not visible
in the Teams application unless you explicitly
search for a member.
Shared channel ✔ Shared Channels can only be provisioned in the
original team where the channel was created.
Shared Channel membership is not migrated.
Group Settings

Allow external senders to email this group ✔ General

Send copies of group conversations and ✔ General
events to group members
Hide from my organization's global address list ✔ General
Others

Microsoft public preview ✖ In general, Microsoft public preview features are

not supported in production migrations. These
features may also take additional time to be fully
developed and tested before being released to
production.

M365 security and compliance features for ✖

Teams

l Legal Hold
l Retention Labels
l Microsoft Information Protection
policies and labels
l M365 Compliance Customer Lockbox

On Demand Migration User Guide

Microsoft Teams Migration 146
 Object Support Notes

Power Platform features for Teams ✖

l Power Apps
l PowerPages
l Power Automate (Flow)
l Power Virtual Agents

Migration from an Education tenant to an Education tenant

Teams migration from one education tenant (Microsoft 365 for Education) to another is partially supported. The
following team types and supported content can be migrated:

l Standard Team
l Class Team
l PLC Team
l Staff Team

Limitations
l Provisioning of public teams is not supported for migration scenarios from one education tenant to another.
Only private teams can be provisioned for these scenarios.
l When using Microsoft Teams for Education, use On Demand Migration for Teams to discover and migrate
the EDU group. If you use On Demand Account Migration to discover and migrate the EDU group, then
provisioning the EDU teams will fail with a “Request failed with BadRequest status code (Bad Request)”
event error.
l During provisioning, the teams with the same type will be created in the target tenant. Provisioning of public
teams is not supported for migration scenarios from one education tenant to another.
l Assignment app, personal OneNote notebook linked to a Teams channel and the OneNote tab linked to
another team are currently not supported. Links to files in migrated messages are not supported in case
these links point to files located outside the default SharePoint URL. These links are missing in the target.

All other Education content is not supported for migration.

Migration from a Commercial tenant to a GCC High tenant

The table below lists the content types in Microsoft Teams that are available for migration from a Commercial tenant
to a GCC High tenant with the On Demand Migration for Teams service.

Content type Availability in Migration support

GCC High
tenant

Announcements ✔ ✔

Applications ✔ ✔

Applications including shifts for schedule management ✔ ✖

Associated SharePoint document libraries (files) ✔ ✔

On Demand Migration User Guide

Microsoft Teams Migration 147
Content type Availability in Migration support
GCC High
tenant

Attached images, media files, documents ✔ ✔

Authorship ✔ ✔

Bots ✖ ✖

Calendars ✔ ✖

Chats ✔ ✔

Code snippets ✔ ✖

Conversations ✔ ✔

Custom tags for teams ✖ ✖

Custom website tab ✔ ✔

Email attachments ✔ ✖

Emoji, Teams GIFs, memes ✔ ✔

Formatted text ✔ ✔

Group mailbox associated with team ✔ ✖

Guest accounts and conversations ✔ ✔

Images posted inline from buffer ✔ ✔

Link preview of public images ✔ Partial. Icon is not

migrated.
Link preview of public sites ✔ Partial. Icon is not
migrated.
Meeting conversations ✔ ✔

Mentions ✔ ✔
l Users
l Channels
l Teams

OneNote ✔ ✖

Planner (Planner Tab, Buckets, Tasks and Comments) ✔ ✔

Private channels ✔ ✔

Public channels ✔ ✔

Team owners and team members (Creation of Microsoft 365 ✔ ✔

Groups)
Team picture ✔ ✔

Timestamps ✔ ✔

On Demand Migration User Guide

Microsoft Teams Migration 148
 Content type Availability in Migration support
GCC High
tenant

Wiki sections and pages ✔ ✖

NOTE: Starting January 2024, neither Wiki tabs nor the

Wiki app will be accessible through Teams. Users will no
longer have the ability to export their wikis. However,
users will still be able to download their wiki files from
SharePoint. For more information, see
https://support.microsoft.com/en-us/office/export-a-wiki-
to-a-onenote-notebook-in-microsoft-teams-8cd8ab0c-
2314-42b0-a1d0-5c6c4c5e1547

Prerequisites
Verify the following requirements are met before migrating Microsoft Teams. If these actions are not performed,
discovery, provision and migration tasks will fail or some data might be lost!

l The following consents are granted before Teams migration can be started
l Migration - Basic,
l Migration - Mailbox Migration
l Migration - SharePoint
l Migration - Teams

TIP: If the consents are not granted or expired, Discover Teams action is disabled and the following
notification is displayed: Grant admin consent to the following Migration sub modules on the Tenants
page for both source and target tenants: Basic, SharePoint, and Teams. Open Tenants page and
grant the necessary Consents and Permissions so that the product can access the source and target
tenants. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is
granted, you can start discovering Teams.

IMPORTANT: The Tenant Administrator must open the OneNote application just once in the target tenant. It
does not have to be opened or run by every user. If OneNote is not initialized before granting consent for
Teams migration, the following error occurs: Unexpected response while attempting to
register the tenant: AADSTSxxxxxx: The app needs access to a service
("https://*.onenote.com/")

l User must be matched or migrated before using the On Demand Migration for Teams service.
l Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for
Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you
migrate the chats.
l Accounts joined to existing teams should be matched or migrated in the migration project.

On Demand Migration User Guide

Microsoft Teams Migration 149
Required permissions

Feature Required permissions

Migrate conversations Read all channel messages

Have full access to the Chat Service Aggregator
Have full access to the Skype Teams Service
Create chat and channel messages with anyone's identity and with any
time stamp
Migrate private chats Read all chat messages
Read and write user chat messages
Provision groups and teams Read and write directory data

Read and write all groups

Migrate files and OneNote items Read and write all OneNote notebooks
Read and write items in all site collections
View and modify notes for all users
Migrate groups and teams Read all users' full profiles
membership
Read or write user region
Add and remove members from all teams
Add and remove members from all channels

Temporary Migration Manager accounts

l It is recommended to create or use source and target temporary Migration Manager accounts.
l The temporary Migration Manager accounts should be granted the Global Administrator or Teams
Administrator role and Application Impersonation role on the tenants for which these account are used.
The temporary Migration Manager accounts in the source and target tenant should have Teams license from
the Microsoft 365 admin center.
l Do not change your temporary Migration Manager accounts before completing the migration project.
l You must remove the source and target temporary Migration Manager accounts for safety reasons
after the migration is completed. These accounts can be removed from teams as described in
Finalizing the Migration.

The target temporary Migration Manager account use is in and not limited to the following scenarios:

l The target temporary Migration Manager account that is used to perform Teams provisioning creates and
owns these provisioned target teams.
l The target temporary Migration Manager account is added to all target teams and Microsoft 365 Groups as a
member and an owner, and to all target private channels as an owner.
l The target temporary Migration Manager account is used to perform the Teams migration and displayed as
the owner of all migrated conversation and chat messages and planner tasks on the target.

On Demand Migration User Guide

Microsoft Teams Migration 150
 l The target temporary Migration Manager account is added to all the chats (both group chats and private
chats) as a participant during chats migration, and then removed from the migrated chats as soon as the
chat migration is complete. All migrated chats of the target temporary Migration Manager account are hidden
when the chat migration is complete.

Teams Workspace
In this topic:

l Dashboard
l Teams List View
l Teams Assessment
l Team Details
l Team Content

Dashboard

The components of the dashboard are as described below:

Notification panel - presents relevant information and shortcuts to migration activities.
Dashboard Menu - contains the following links to common activities in the migration process.

l Discover - Starts the New Teams & Groups Discovery Task wizard to collect information about accounts in
the source tenant. For more information see Discovering Teams and Groups

Dashboard Tiles

On Demand Migration User Guide

Microsoft Teams Migration 151
 l Getting Started - Presents quick start links to the various actions for preparing and migrating teams.
l Teams - Presents a summary of the teams in various migration states. Click Show All to open the Teams
List view to inspect the teams.
l M365 Groups - Presents a summary of the M365 Groups in various migration states. Click Show All to
open the Groups List view to inspect the groups.
l Tasks - Displays the five most recent tasks that were completed in the Teams workspace. The title displays
the total number of tasks. Click Show All to open the Tasks List view.
l Events - Displays the five most recent events that were completed in the Teams workspace. The title
displays the total number of events. Click Show All to open the Events List view.

Teams List View

The Teams List View is comprised of the following components:

Notification panel - presents relevant information and shortcuts to migration activities.
Filter panel - consists of predefined filters for the Teams List view and tabs to switch between the Teams List view
and the Assessment view. See Filtering for more information about working with filters. The predefined filters are:

l Teams - migration state of the team.

l Teams By Size - size of a team. Valid ranges are More than 1GB, 100MB - 1GB, 10MB - 100MB, Less than
10MB. The dropdown also shows the nunbver of teams in the list for each range.
l SharePoint - nature of the SharePoint site linked to the team. Valid values are Customized and Standard.

List View Menu - contains links to teams migration activities and the search box. Each activity is explained in
greater detail in subsequent topics. See Searching for more information about working with the search box.
List View - displays information about teams in the source and target tenants. Use the Edit Columns list view
menu to show or hide columns in the list. The columns are as described below:

On Demand Migration User Guide

Microsoft Teams Migration 152
l Team Name - name of the team in the source tenant.
l Migration State - status of the task in the migration process. Values are as listed below:
l Discovered - Team discovered in the source tenant.
l Exists in target - Team in the source tenant exists in the target tenant.
l Provisioning - Started provisioning team in the target tenant.
l Provisioned - Team provisioned successfully in the target tenant.
l Provisioned with issues - Team provisioned in the target tenant but there were issues during
provisioning.
l Provision failed - Started provisioning team in the target tenant.
l Queued - Team is waiting for migration service resources to be available. For more information, see
How Queuing Works.
l Migrating - team migration in progress.
l Partially migrated - team migration completed but some components were not migrated.
l Partially migrated with issues - team migration completed some components were not migrated
and due to issues during migration.
l Migrated - Team migrated successfully to the target tenant.
l Migrated with issues - Team migration completed but there were issues during migration.
l Migration failed - Team could not be migrated.
l SharePoint - nature of the SharePoint site linked to the team. Values are as described below:
l <no-value> - SharePoint content has not be discovered yet.
l Standard - There is at most 1 SharePoint site and 4 Lists in the SharePoint site collection
l Customized - There are more than 1 site and 4 Lists in the SharePoint site collection

NOTE: The SharePoint status is available only after the New Teams Provisioning Task is run.

l Channels - total number of channels in the source tenant team.

l Members - total number of members in the source tenant team.
l Source Files (GB) - total size in GB of files across all public channels in the source tenant.
l Target Files (GB) - total size in GB of files across all public channels in the target tenant.
l Messages - total number of messages in the source tenant team.
l Migrated Messages - number of messages migrated to the target tenant team.
l Target Messages - total number of messages in the target tenant team.
l Plans - total number of plans in the source tenant team.
l Migrated Plans - number of plans migrated to the target tenant team.
l Target Plans - total number of plans in the target tenant team.
l Tasks - total number of tasks in the source tenant team.
l Migrated Tasks - number of tasks migrated to the target tenant team.
l Target Tasks - total number of tasks in the target tenant team.

On Demand Migration User Guide

Microsoft Teams Migration 153
 l Source Url - SharePoint site URL of the source team. Available when the team is provisioned in the
target tenant.
l Target Url - SharePoint site URL of the target team. Available when the team is provisioned in the
target tenant.
l Progress (%) - migration progress indicated as a percentage.
l Last Activity - date and time of the last action performed on the team record.
l Created - date and time the team record was created.
l Target Team Name - name of the team in the target tenant.
l Source MailNickname - email alias of the associated Microsoft 365 Group in the source tenant.
l Target MailNickname - email alias of the associated Microsoft 365 Group in the target tenant. Available
when the team is provisioned in the target tenant.
l IsArchived - indicates whether the team is archived. Archived teams can be migrated like any other team.
l Source Team URL - URL of the source team.
l Target Team URL - URL of the target team. Available when the team is provisioned in the target tenant.
l Source Group ID - unique identifier of the team or group in the source tenant.
l Target Group ID - unique identifier of the team or group in the target tenant. Available when the team is
provisioned in the target tenant.
l Source SMTP Address - SMTP address of the Office 365 group of the source team.
l Target SMTP Address - SMTP address of the Office 365 group of the source team. Available when the
team is provisioned in the target tenant.
l Source Team Owner UPNs - User Principal Names of the source team owners. Up to 5 names are listed.
l Target Teams Owner UPNs - User Principal Names of the target team owners. Up to 5 names are listed.
Available when the team is provisioned in the target tenant.

Teams Assessment View

See the Premigration Assessment for Teams for the complete list of available reports.

Team Details
When you select a team from the List View, the Team Detail pane opens. The information in the pane is
described below:

l Description - name of the team in the source tenant.

l Visibility - indicates whether the source tenant team is Public or Private.
l Is Archived - indicates whether the source tenant team is archived.
l SharePoint Customized - status of the selected account. Valid values are New, In Progress, Failed
and Completed.
l Owner count - number of owners of the source team. A team can have up to 100 owners.
l Member count - number of members in the source tenant team.
l Migrated messages count - number of messages migrated to the target tenant team.
l Archive messages count - number of archived messages in the source tenant team.

On Demand Migration User Guide

Microsoft Teams Migration 154
 l Source Url - SharePoint site URL of the source team. Available when the team is provisioned in the
target tenant.
l Target Url - SharePoint site URL of the target team. Available when the team is provisioned in the
target tenant.
l Last Operation - the most recent operation performed on the team. Valid values are Discovered,
Provisioned, and Migrated.
l Events - count of the events that occurred during account processing through one or more tasks.
l Tasks - list of tasks invoked for the selected account.

Team Content
The Team Content tab presents a list of teams and its components along with the count of child items of the object
type. When you open the Team Content tab, the list view initially displays all the teams and their migration state
along with the total count of the team components of each team: Channel, Planner, Mailbox, Team membership,
SharePoint Content* and SharePoint Site*. For each team component you can additionally view its components and
their child item counts as well.

* Example: Consider a team with multiple private channels A and B.

If you select the SharePoint Standard option in the New Teams Migration Task wizard, then the following items are
displayed in the Team Content view with type "SharePoint List" after migration.

Type Name

SharePoint List Documents - team site name

SharePoint List Documents - private channel A site name
SharePoint List Documents - private channel B site name

If you select the SharePoint Standard and Customized option in the New Teams Migration Task wizard, then the
following items are displayed in Team Content view with type "SharePoint Site" after migration.

On Demand Migration User Guide

Microsoft Teams Migration 155
 Type Name

SharePoint Site Site - team site name

SharePoint Site Site - private channel A site name
SharePoint Site Site - private channel B site name

To display the contents of a specific team:

1. Select the team to open the details pane on the right hand side.
2. Click Show Content. The components of the selected team are displayed in the list view along with the
migration state and child item counts for each component. In the details pane, the Show Parent link is
activated and the Show Content link is deactivated.

NOTE: Components of a team can be displayed when teams are migrated through a new project created
after the Jan 10, 2023 release.

To display the parent of a specific team component:

1. Select the team component to open the details pane on the right had side.
2. Click Show Parent. The parent team is displayed in the list view along with the migration state and the total
count of the team components. In the details pane, the Show Content link is activated and the Show
Parent link is deactivated.

The components of teams are migrated when you start a migration task with the New Teams Migration Task wizard
and select the team component types to migrate.
NOTE: The Events property value in the detail pane for a selected child component will be zero.

Filter panel - consists of predefined filters for the Teams List view and tabs to switch between the Teams List view
and the Assessment view. See Filtering for more information about working with filters. The predefined filters are:

On Demand Migration User Guide

Microsoft Teams Migration 156
 l Status - migration state of the team.
l Type - object type: Team, Channel, Planner, Mailbox, team membership or SharePoint Content.

List View - displays information about teams in the source and target tenants. Use the Edit Columns list view
menu to show or hide columns in the list. The columns are as described below:

l Type - object type: Team, Channel, Planner, Mailbox, membership or SharePoint Content.
l Name - name of the object
l Migration State - status of the task in the migration process. Values are as listed below:
l Discovered
l Exists in target - object in the source tenant exists in the target tenant
l Mapped
l Provisioning
l Provisioned
l Provision failed
l Migrating
l Partially migrated
l Partially migrated with issues
l Migrated
l Migrated with issues
l Migration failed
l Items to migrate - the count of child items of the object. For each team, the count indicates the total
number of child components of the team. For each team components the item counts displayed are as
described below:
l Planner: number of Planner tasks
l Channel: number of messages
l Mailbox: the team mailbox. The count is always 1
l Membership: number of team members
l SharePoint Content: number of sites
l Processed - the number of items considered for migration.
l Progress (%) - migration progress in percentage. If a team component is not selected for migration in the
New Teams Migration Task wizard, this value does not exist for the component.

On Demand Migration User Guide

Microsoft Teams Migration 157
Discovering Teams
In this topic:

l Discovering all Teams

l Discovering Teams from a file
l Reviewing the Discover Teams task
l Reviewing the Discover Teams task events

Discovering all Teams

This is the simplest approach which uses the Discover Teams tasks to inspect the source tenant and discover
all the teams.

To start the Discover Teams task:

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click Discover Teams from the Teams tile in the Teams dashboard
-or-
Select the Teams tab and select the List View if not already selected. Then click Discover Teams >
Discover All from the Actions menu.

6. The New Teams Discovery Task wizard opens.

7. Step 1: Discovery Options

On Demand Migration User Guide

Microsoft Teams Migration 158
 a. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discover Teams.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Discovering Teams from a file

When you have a large set of teams but you want to migrate a subset of those teams, you can start the discovery
process by using a CSV file. The CSV file lets you specify the teams that you want to discover and ignore the rest.
This is a two-step process:
Step 1: Preparing the CSV file

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. From the navigation pane, click Active groups.
3. Select Microsoft 365 tab in the Active Groups page
4. Set the list filter to Groups with Teams.

On Demand Migration User Guide

Microsoft Teams Migration 159
 5. Click Export and then click Export groups in this list. A Groups.csv file will be downloaded to your
computer.

6. Edit the CSV file and retain the Group ID and Group name columns. Then retain the teams you want to
discover and delete the rest. If you retain a row that references a group without a team, the group will be
ignored during discovery.

7. Save the CSV file. You may rename the file if needed.

Step 2: Starting the Discover Teams Task

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click the Teams tab and select the List View if not already selected. Then click Discover Teams >
Discover from file from the Actions menu.
6. The New Teams Discovery Task wizard opens.

On Demand Migration User Guide

Microsoft Teams Migration 160
7. Step 1: Discovery Options

a. Click Browse and select the CSV that contains the Group IDs and Group names of the teams that
you want to discover.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

On Demand Migration User Guide

Microsoft Teams Migration 161
 10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discover Teams.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Discover Teams Task

1. Select the Tasks tab.
2. Select the task that you want to review. The default name is Discover Teams.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is discoverteams.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Discover Teams Task Events

1. Select the Tasks tab.
2. Select the task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the event details pane that opens, the information presented is as
described below:
a. Object - Name of the team or group discovered.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Application.
e. Source - Name of the On Demand Migration service

On Demand Migration User Guide

Microsoft Teams Migration 162
Discovering Teams and Groups
Every team is associated with a Microsoft 365 Group, but there are groups that are not associated with teams. In
this topic, the term team means a Microsoft Team and includes its associated group, and the term group means a
Microsoft 365 Group that is not associated with a team.
NOTE: This topic explains the process to discover both teams and groups. If you want to discover only
teams, see Discovering Teams. If you want to discover only groups that are not related to teams, see
Discovering Groups.
In this topic:

l Discovering all teams and groups

l Discovering teams and groups from a file
l Reviewing the Discover task
l Reviewing the Discover task events

Discovering all teams and groups

This is the simplest approach which uses the Discover tasks to inspect the source tenant and discover
all the teams.

To start the Discover task:

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click Discover > Discover All from the Teams dashboard.
6. The New Teams & Groups Discovery Task wizard opens.

On Demand Migration User Guide

Microsoft Teams Migration 163
7. Step 1: Discovery Options

NOTE: The Azure AD administrator account will be added to the discovered Teams and Groups.

a. All Teams - select this option to discover all Microsoft Teams.

b. All Groups - select this option to discover all Microsoft 365 Groups without Teams.
c. All Teams and Groups - select this option to discover Microsoft 365 Groups and Teams.
d. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

On Demand Migration User Guide

Microsoft Teams Migration 164
 10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Discover.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Discovering teams and groups from a file

This step is required if you plan to discover teams and groups using a CSV file. When you have a large set of teams
and groups but you want to migrate a subset of the objects, the CSV file lets you specify the teams and groups that
you want to discover and ignore the rest. You can then use this file in the New Teams & Groups Discovery Task as
described in this topic to discover the teams from the source tenant.

Step 1: Preparing the CSV file

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. From the navigation pane, click Active groups.
3. Select Microsoft 365 tab in the Active Groups page
4. Click Export and then click Export all groups. A Groups.csv file will be downloaded to your computer.

5. Edit the CSV file and retain the Group ID and Group name columns. Then retain the teams and groups you
want to discover and delete the rest.

On Demand Migration User Guide

Microsoft Teams Migration 165
 6. Save the CSV file. You may rename the file if needed.

Step 2: Starting the Discover Task

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click Discover > Discover from file from the Teams dashboard.
6. The New Teams & Groups Discovery Task wizard opens.
7. Step 1: Discovery Options

On Demand Migration User Guide

Microsoft Teams Migration 166
 a. Click Browse and select the CSV that contains the Group IDs and Group names of the teams that
you want to discover.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Discover.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Discover Task

1. Select the Tasks tab.
2. Select the task that you want to review. The default name is Discover.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is discoverteams.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.

On Demand Migration User Guide

Microsoft Teams Migration 167
 f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

4. If you select the options to collect statistics in the New Teams & Groups Discovery Task wizard, you will see
additional tasks: Collect Plan and Task statistics for Teams and Groups and Collect Message statistics for
Teams. Click each task to view the corresponding details in the details pane.

Reviewing the Discover Task Events

1. Select the Tasks tab.
2. Select the task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the event details pane that opens, the information presented is as
described below:
a. Object - Name of the team or group discovered.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Application.
e. Source - Name of the On Demand Migration service

On Demand Migration User Guide

Microsoft Teams Migration 168
Managing Teams with Collections
Migrating large numbers of teams requires careful planing. The teams could belong to different offices and
geographical locations or sensitive departments. Migrating teams of Finance or Legal departments require special
care. Organize the teams into collections to make large team lists more manageable.

Working with the Collection Dashboard

The Collection Dashboard shows the collection-specific summary, allows you to see teams added to it, create tasks
for them, and monitor the progress of tasks.

l To view the collection dashboard for an existing collection

a. Log in to Quest On Demand and choose an organization if you have multiple organizations.
b. From the navigation pane, click Migration to open the My Projects list.
c. Create a new project or open an existing project.
d. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
e. From the top-right corner of the workspace, click Select Collection and then select the collection to
view. The collection Dashboard is displayed.
f. Open the Teams tab. You will see the list of teams that belong to the collection.
l To see the tasks for collection-specific accounts, use the corresponding tile on the collection Dashboard or
open the Tasks tab.
l To see the events related to the collection, use the corresponding widget on the collection Dashboard or
open the Events tab.
l To rename or delete the collection, click the corresponding buttons in the menu.
l To return to the project dashboard, click the project name in the navigation bar.

On Demand Migration User Guide

Microsoft Teams Migration 169
Creating a Collection manually
1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
2. From the top-right corner of the workspace, click Select Collection > + New Collection
3. Enter a collection name and click Save to add this collection to the project.

Adding teams to Collections

You can add teams to collections in several ways:

l Select the teams and add to a new collection

l Select the teams and add to an existing collection
l Use a CSV file to add teams to a new or existing collection from the Teams tab
l Use a CSV file to add teams to an existing collection from the Teams collection dashboard

To add selected teams to a new collection:

1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
2. Click the Teams tab and select List View if not already selected.
3. Select the teams you want to add to the collection.
4. From the actions toolbar, click New Collection. The New Collection dialog opens.

5. Enter a collection name in the Collection name field and click Save to add the selected teams to the
collection.

To add selected teams to an existing collection:

1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
2. Click the Teams tab and select List View if not already selected.
3. Select the teams you want to add to an existing collection.

On Demand Migration User Guide

Microsoft Teams Migration 170
 4. From the actions toolbar, click Add To Collection. The Add to existing collection dialog opens.

5. Select a collection from the Collection name dropdown and click Save to add the selected teams to the
collection.

To add teams from a CSV file to a new or existing collection from the Teams tab:
This is a two-step process as described below to add teams to an existing collection from the Teams tab:
Step 1: Prepare the CSV file

NOTE: CSV file names with non-ASCII characters are not supported. Teams in the CSV that
have not been discovered cannot be added to a collection.

Use the format shown below to prepare the CSV file. The minimal set of columns required are shown.
TIP: You can export the selected teams to a CSV file and then add the Collection column and
retain the Source MailNickname column. All other columns in the exported CSV file will be
ignored so you can remove those columns if you want.

l Collection - Column header for the collection name

l Source MailNickname - Email alias of the M365 group of the team. You can get the Source
MailNickname property of the teams when you export teams to a CSV file. Source
MailNickname values are case-sensitive.

Step 2: Import the CSV file

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams workspace.
5. Open the Teams tab.

On Demand Migration User Guide

Microsoft Teams Migration 171
 6. From the actions toolbar, click More Actions > Import Collections. The Import Collections from File
dialog opens.
7. Select Teams/M365 groups from the Specify kind dropdown.

8. Click Browse and select the CSV file. The selected CSV file name appears.
9. Click Import.

NOTE: If a collection in the CSV does not exist, a new collection will be created with the name
specified in the CSV.

To add teams from a CSV file to an existing collection from the Teams collection dashboard:
This is a two-step process as described below to add teams to an existing collection from the Teams
collection dashboard:
Step 1: Prepare the CSV file

NOTE: CSV file names with non-ASCII characters are not supported. Teams in the CSV that
have not been discovered cannot be added to the collection.

Use the format shown below:

Source MailNickname - Email alias of the M365 group of the team. You can get the Source
MailNickname property of the teams when you export teams to a CSV file. Source MailNickname
values are case-sensitive.
Step 2: Import the CSV file

1. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
2. From the top-right corner of the workspace, click Select Collection and then select the collection.
3. Click Fill From File from Teams collection Dashboard menu. The Fill from File dialog opens.

On Demand Migration User Guide

Microsoft Teams Migration 172
 4. Click Browse and select the CSV file that you created.
5. Click Populate to add the teams from the file to the collection.

Exporting Teams
To export teams to a comma-separated values (CSV) file:

1. Click Teams from your migration project

2. Click the Teams tab. From the Teams List View select the teams you want to export.
3. From the Teams List View select More Actions and then select Export.
4. Open the CSV file by extracting it from the ZIP file that is downloaded to your computer.

The exported data contain the following information:

l Team Name - source team name

l Workflow - (deprecated) the most recent operation performed on the team
l Channel, Members, Messages, Plans, Tasks - counts of various content in the team.
l Size(MB) - size of all the content in the team.
l Last Activity - date and time of the last action performed on the team record.
l Created - date and time the team record was created
l Target Team Name - suggested target team name that will be provisioned in the target tenant
l Source MailNickname - email alias of the associated Microsoft 365 Group. This value will be used for the
mail enabled object and will be used as PrimarySmtpAddress for this Microsoft 365 Group. The value must
be unique across your tenant.
l Last Operation Description - description of the last operation performed on this team.

Mapping Teams
You can rename and map teams, or rename, map and merge one or more source teams to a specific team in the
target tenant in two ways:

l Mapping and renaming teams automatically

l Mapping, renaming and merging teams manually from a file

Mapping and Renaming Teams 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click the Teams tab and select one or more teams that you want to rename and map.

On Demand Migration User Guide

Microsoft Teams Migration 173
 6. Click More Actions and then click Rename and Map. The New Teams & Groups Rename and Map Task
wizard opens.
7. Step 1: Mapping options
a. Enter the information as described below:
l Add prefix - specify a prefix for the team name.
l Add suffix - specify a suffix for the team name.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a mapping task completes.
l Only in a case of failure - select this option to send the email if the mapping task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Rename
and Map Task.
ii. Source tenant - name of the tenant in this project.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The 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.

Mapping, Renaming and Merging Teams Manually from a File

To rename teams or merge one or more source teams to a specific team in the target tenant, a CSV file is used to
indicate the mapping between source and target teams, as described below.

On Demand Migration User Guide

Microsoft Teams Migration 174
 NOTE:
When teams are renamed and provisioned in the target tenant, Microsoft creates a default OneNote tab.
Since ODM migration service is not aware of this default tab, any OneNote content that is migrated will retain
the original name and will not appear in the default target OneNote tab of the renamed team.
There are two scenarios with OneNote migration when teams are merged:

a. When one or more teams are merged to a team with a different name in the target tenant, Microsoft
creates a default OneNote tab for the renamed target team. Since ODM migration service is not
aware of this default tab, any OneNote content that is migrated will retain the original name and will
not appear in the default target OneNote tab of the renamed team.
b. When one or more teams are merged to a team with a preexisting team in the target tenant, contents
in the OneNote tab in the target tenant is overwritten with the content from the source.

To create the mapping file:

1. Prepare a comma-separated values (CSV) file with the source and target team names.
TIP: Export selected teams to a comma-separated values (CSV) and then edit this file. See
Exporting Teams for more details.

2. The header row defines the names of the source and target attributes used for mapping. Subsequent rows
list the mapphing values of the attributes.
The columns are as follows:
l Source Mailnickname - unique name of the source team. The following column header variations
are supported: SourceMailNickname, Source MailNickname, Source MailNickName. The
column header is case sensitive.
l Target Mailnickname - unique name of the target team. The following column header variations are
supported: TargetMailNickname, Target MailNickname, Target MailNickName. The
column header is case sensitive. You can merge multiple source teams to a single target team when
you specify the same Target Mailnickname in a mapping file.
l Target Team Name - display name of the target team. The column header is case sensitive. If two
or more records have the same Target Mailnickname then the Target Team Name for each record
must be specified and must be the same.

Example 1: Row 2: Simple change of name

The name properties of the source team will change to the Target Mailnickname and Target Team Name
respectively.
Example 2: Rows 3 and 4: Different target teams with the same display name

On Demand Migration User Guide

Microsoft Teams Migration 175
 The Target Mailnicknames are different but the Target Team Names are the same. The Target
Mailnickname takes precedence and the teams will be mapped to distinct Target Mailnicknames but the
display name of each target team will be the same. It is recommended that you use unique display names to
avoid confusion.
Example 3: Rows 5, 6 and 7: Merge multiple source teams with the same target team
The Target Mailnickname is the same. The teams will be merged with the same target team with the
specified display name.

3. Save the CSV file.

NOTE: File names with non-ASCII characters are not supported.

To upload the mapping file:

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click the Teams tab.
6. Click More Actions and then click Map from File. The New Mapping from File Task wizard opens.
7. Step 1: Mapping file
a. Click Browse and select the CSV mapping file. The selected file name appears next to the
Browse button.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a mapping task completes.
l Only in a case of failure - select this option to send the email if the mapping task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

On Demand Migration User Guide

Microsoft Teams Migration 176
 10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name.
ii. Source tenant - name of the tenant in this project.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The 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.

Provisioning Teams
The provisioning task help you to perform the following:

l Create Microsoft 365 Groups on the target tenant.

l Resolve naming conflicts.
l Provision teams in the target tenant.

Considerations
1. After all source teams are discovered you can begin provisioning teams on the target tenant with a Teams
Provisioning Task. Verify that all associated accounts are matched or migrated before you create the
provision task.
2. When teams are provisioned, the account that is assigned the Migration Manager role will be added to the
source teams, private channels and shared channels to prepare for migrating the channel settings to the
target tenant.
3. If one or more new private channels or shared channels are added to a source team after provisioning, then
you must re-provision the team in the target tenant to ensure that the SharePoint content is discovered for
those new channels.
4. When teams are provisioned on the target tenant, a Discover SharePoint Contents Task is run. The
task discovers the corresponding SharePoint site collection and its contents listed in the SharePoint
Contents tab.
5. Teams in the target tenant may take up to 24 hours to be fully provisioned by Microsoft.

To start a Teams Provisioning Task:

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.

On Demand Migration User Guide

Microsoft Teams Migration 177
5. Select one or more teams from the Teams List View.
6. Click Provision. The New Teams Provisioning Task wizard opens.
7. Step 1: Provision Options

a. Choose from the following options if a team with the same name exists on target:
l Provision a new team on the target with the original name plus suffix - Select this
option to provision a new team on the target tenant by adding a suffix to the team name.
l New team display name suffix - The default suffix is Migrated. You can specify
another suffix.
l Merge to the existing team on target - Select this option to merge a team in the source
tenant with a team in the target tenant that has the same name. Then select an option if a
team channel with the same display name already exists in the target team:
l Provision a new channel on the target with the original name plus suffix -
Select this option to provision a new team channel on the target tenant by adding a
suffix to the channel name.
l New channel display name suffix - The default suffix is Migrated. You
can specify another suffix.
l Merge source channel conversations with the Target channel - Select this
option if the target channel is empty.

On Demand Migration User Guide

Microsoft Teams Migration 178
 b. Preferred location in target multi-geo tenant - Leave the preferred data location as Default if the
target tenant is a multi-geo tenant (see Microsoft 365 Multi-Geo). All teams and groups will be
migrated to the same region as the target admin. Alternatively, select the geo location configured for
the target tenant.
TIP: To migrate teams/groups to different regions, the best practice is to create a collection
for each region (see Managing Teams with Collections ) and add the teams/groups to the
appropriate collection. Example collection names are "Migrate to EUR", "Migrate to JPN" and
"Migrate to NAM". Use the collection as a filter to create the provision task.

c. Suppress Group Welcome Message - Select this option to prevent spamming users with welcome
messages when Teams are provisioned on the target tenant.
NOTE: Suppressing these messages may result in performance degradation due to issues
with Microsoft’s synchronization behavior. We suggest you check the performance during the
pilot migration.

d. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a provisioning task completes.
l Only in a case of failure - Select this option to send the email if the provisioning task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3. Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name.
ii. Source tenant - name of the tenant in this project.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

On Demand Migration User Guide

Microsoft Teams Migration 179
Removing Teams
To manage large lists of teams in a project, you can remove one or more teams from the teams list view that you
don't need for migration. The teams that are removed will remain in the source tenant and you must re-discover the
teams in the project when you need them for migration.
When teams are removed, all associated items, mappings and migration information will also be removed from the
project. When these teams are rediscovered, they will be treated as new teams in the project and the process of
provisioning and migration of the teams and related items must be repeated.

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
5. Select the Teams tab and select List View if not already selected.
6. Select the teams you want to remove.
TIP: Use filters, search or collections to quickly navigate through the list of teams.

7. Click More Actions and then click Delete. The New Remove Team Mappings Task wizard starts.
8. Step 1: Description
a. Click Next.
9. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
10. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
11. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Remove Teams.

On Demand Migration User Guide

Microsoft Teams Migration 180
 ii. Source tenant - name of the source tenant in this project
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Collecting Statistics
The Collect Statistics Task for Teams conducts an assessment of selected teams in the source tenant and
provides information like member count, content size (in GB), planner count and planner task count for the teams
selected in the source tenant, and optionally in target tenant if the team is already provisioned.
Each Collect Statistics Task generates events. Events are milestones that a task achieves as it runs. For
example, when a Teams Collect Statistics Task starts, an event is logged and it appears in the events list. When
the number of teams that are selected for assessment is large, the Teams Collect Statistics Task divides the total
number of teams into manageable sets. Each set is called a batch. When a batch of accounts is assessed, another
event occurs.
In this topic:

l Starting a Teams Collect Statistics Task

l Reviewing the Teams Collect Statistics Task
l Reviewing the events for the Teams Collect Statistics Task
l Reviewing the statistics collected

Starting a Teams Collect Statistics Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams workspace.
5. Select the Teams tab and then select List View if not already selected.
6. Select the teams in the list from where you want to collect statistics. You can use search, filtering or
collections to quickly navigate through the list of mailboxes. You can select the check box in the table header
to select all the accounts.
7. Click Collect Statisticsfrom the Actions ribbon. The New Collect Statistics Task wizard opens.
8. Step 1:Collect Statistics Options
a. Choose from the following options
l Include collection of statistics from target tenant - select this option to include the same
teams from the target tenant. Statistics will only be collected for the target tenant teams if a
provision task has been executed for the team previously.

On Demand Migration User Guide

Microsoft Teams Migration 181
 l Collection levels:
l Basic (Fast) - collect statistics about member count and content size (in GB) for the
teams selected in the source and target tenant if provisioned.
l Advanced (Slow) - collect statistics about member count and content size (in GB),
planner count and planner task count for the teams selected in the source and target
tenant if provisioned. The task requires more time to run.
b. Click Next
9. Step 2:Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. Default name is Collect
Statistics.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Teams Collect Statistics Task

1. Select the Tasks tab.
2. Select the Collect Statistics task for teams that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is collectstatistics.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. Status - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - The number of events that the task encountered.

On Demand Migration User Guide

Microsoft Teams Migration 182
Reviewing the events for the Teams Collect Statistics Task
1. Select the Tasks tab.
2. Select a Collect Statistics task for teams that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Application.
e. Source - the workspace from where the event was generated. The value is Teams Migration.

On Demand Migration User Guide

Microsoft Teams Migration 183
Reviewing the statistics collected
1. Open the Teams workspace.
2. Select the Teams tab and then select List View if not already selected.
3. Review the statistics collected for each team. The statistics displayed depends on the option selected in the
New Teams Collect Statistics Task wizard.

Premigration Assessment for Teams

On Demand Migration analyzes your environment and tracks potential problems, misconfiguration, and risks that
might adversely affect the migration. Use Assessment view to see the summary reports on the discovered data and
use the automatic filters to quickly select certain items.
The following reports are available for Teams:

l Workflow - (deprecated) Teams sorted by completed workflow

l Discovered
l Processed
l Migrated
l Teams- Teams sorted by processing status
l Idle
l In progress
l Needs your attention
l Teams By Size
l Teams By Last Activity Time
l Teams By Channel Count
l Teams By Member Count

Once you handle the issues, if any, go to List View screen. You are ready to start the migration.

On Demand Migration User Guide

Microsoft Teams Migration 184
Migrating Teams
When you migrate teams, files stored in the corresponding SharePoint document libraries and OneNote items
stored in asset libraries can be migrated. The SharePoint sites associated with teams may contain additional
objects that cannot be migrated with the On Demand Migration for Teams service.

Considerations
1. Channels are dedicated sections within a team to keep conversations organized. Channel membership can
be Standard, Private or Shared.
2. When teams are migrated, the account that is assigned the Migration Manager role is added to the team. If
dynamic membership is enabled, the rules are modified to include this account. This temporary role is
required for migrating teams by the On Demand Migration service.
3. Teams in the target tenant may take up to 24 hours to be fully provisioned by Microsoft after they are created
during a Teams provisioning task. We recommend that you migrate only those teams which are provisioned
at least 24 hours before they are migrated.
4. When teams are migrated, the SharePoint Contents list is updated, and the Migration state of the objects is
changed to Migrated. You can review the list and use the On Demand Migration for SharePoint service to
migrate additional SharePoint objects.
5. When a team with same name already exists in the target tenant and the merge option is selected for
migration, contents of the note in the target tenant is overwritten with the content from the source.

In this topic:

l Configuring the project for Teams migration

l Migrating Teams

Configuring the project

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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.

5. Click Configure Project from the dashboard menu. The Edit Project wizard starts
6. Step 1: Project Settings
a. Set Migration Defaults
Default Target User - Specify a user principal name (UPN) to use as the team owner when the
existing owner has no match in the target tenant.

b. Click Finish.

Migrating Teams
1. Log in to Quest On Demand and choose an organization if you have 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.

On Demand Migration User Guide

Microsoft Teams Migration 185
4. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Select one or more teams from the Teams List View.

TIP: It is recommended to select no more than 100 teams for the task to streamline the process. You
can create several tasks that will be executed concurrently. Use search and filtering to quickly
navigate through the list of teams.

6. Click Migrate. The New Teams Migration Task wizard opens.

7. Step 1. Migration Options

a. Choose from the following options:

l Channel Posts(Messages) - select this option to migrate the posts or messages in a
channel.
l Archive - select this option to migrate and archive channel messages as an HTML
file for each channel. The HTML file is added to the file list of the team's SharePoint
site in the target tenant. A new message from the target tenant Administrator is
added to each migrated channel with a link to its HTML file. A new tab called
Conversation History is created in the target channel and the archived messages are
displayed there.
l All messages - migrate and archive all messages across all
channels in the team
l Messages older than 15 days - migrate and archive messages across all
channels in the team that are older than 15 days.
l Messages older than 30 days- migrate and archive messages across all
channels in the team that are older than 30 days.
l Messages older than 60 days - migrate and archive messages across all
channels in the team that are older than 60 days.

On Demand Migration User Guide

Microsoft Teams Migration 186
 NOTE:
Messages that are more recent than the 15, 30 or 60 days option that is
selected will be migrated but not archived.
Links to files that are not yet migrated to the target will not work. remigrate
Teams using Channel Files to ensure the links work correctly. To learn more,
see Remigration.
If the migration task is successful and the archive HTML file is created in the
target tenant, it cannot be modified by subsequent migrations. If you attempt
another migration and select the Archive option, the Archive option is
ignored. All new and modified channel messages from the selected teams will
be migrated and posted to the corresponding team channels in the target
tenant. Messages already archived will be skipped unless they were
subsequently modified (edited or linked to replies or attachments) in the
source tenant.
If the migration task is unsuccessful and the archive file is not created,
subsequent migrations with the Archive option selected will attempt to create
an archive HTML file in the target tenant. Archive sub-options like All,
Messages older than 15 days, Messages older than 30 days or
Messages older than 60 days, are re-evaluated for all messages in the
channel. The new set of messages selected for archival may not be the same
set of messages identified in the previous archive attempt.

l SharePoint Content - select this option to migrate SharePoint content linked to teams
selected for migration.
l Standard (Channel files only) - select this option to migrate files, OneNote, Word,
Excel and PowerPoint tabs added to the channel.
l Standard and Customized (All SharePoint Content) - select this option to
migrate OneNote, Word, Excel, PowerPoint and List tabs added to the channel, and
site collections which includes any customized content such as descendant
websites and lists.

NOTE: For better performance and accountability the Get Total File Size task is
automatically scheduled to run 24 hours after the migration task completes.
For each team that is being migrated, the task calculates the total size of files across
all channels of the team from the source and the target tenants. These totals are
displayed in the Teams List view.
If you manually start the task before 24 hours of the migration task, you may not get
accurate results. The task retains its original schedule and runs 24 hours after the
migration task completes.

l Planner - select this option to migrate the Planner buckets, tasks, comments and the
corresponding Planner tabs in teams.
NOTE: For large Planner task migrations (e.g. 20,000+ tasks), see the KB article How
to use ODM to migrate large amounts of Teams Planner items. (339416).

l Group Mailbox - select this option to migrate the Microsoft 365 Group mailbox.
l Team Membership - select this option to migrate team members. If this option is not
selected, team members will not be migrated. If the team member or owner was not matched

On Demand Migration User Guide

Microsoft Teams Migration 187
 or migrated by an account migration task, a warning is reported: Cannot add *** as group ***:
User Mapping does not exist. Workaround: Match or migrate the account and then re-run the
Teams Provisioning task.
b. Click Next.
8. Step 2: File Version Options

a. Choose the migration option for file versions associated with teams selected for migration.
l Latest version only - select this option to migrate the most recent version of the file. All
other versions will be ignored. This is the default selection.
l More versions - select this option to migrate additional versions of a file based on the
options described below. Large version sets take a significantly long time to migrate.
l Number of versions - 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.
l Latest version and preceding versions - 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.
l Latest version and daily latest from preceding days - 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.
l 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

On Demand Migration User Guide

Microsoft Teams Migration 188
 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.
l All Versions - select this option to migrate the latest version of the file, and all previous
versions if the latest version does not exceed a specified size limit. This option requires
significantly more time to migrate all the versions.
l 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.
b. Click Next.
9. Step 3. File Conflict Options

a. Choose a conflict resolution option.

NOTE:
l Conflict resolution rules are applied only to files that have been previously migrated.
l Conflict resolution rules will not be applied if the All versions option is selected in the
previous step. All files in the target tenant will be overwritten if all files are migrated.
l Overwrite target files - all migrated files in the target tenant will be overwritten. Migration is
fastest with this option selected.
l Skip if target file is the same version or newer - ignore files in the target tenant with the
same or newer version. If the file does not exist in the target tenant, a copy of the source file
will be migrated.

On Demand Migration User Guide

Microsoft Teams Migration 189
 l Copy source file if target is newer - preserve the file in the target tenant if it is the same
or newer version and migrate a copy of the source file. When you choose this option, you
must choose from one of the following file suffix options: _Copy, _Source, _Older, _
Backup, and _1.
b. Click Next.
10. Step 4. Archiving Options

NOTE: If you archive the source team without using On Demand Migration (e.g. by using Microsoft
tools), then you can migrate the source team and archive the target team. If you archive the source
team using On Demand Migration then you can migrate the target team but you cannot archive the
target team.
a. Archive the source team after migration - select this option to archive the source team after
migration. If you select this option you cannot archive the target team.
l Make source SharePoint site read only - this option is available if option (a) is selected.
Select this option to set the associated SharePoint site to read only for the team members.
b. Archive target team if source team is archived - select this option to archive the source team
after migration. Archived teams cannot be updated or remigrated. This option is not available if
option (a) is selected.
l Make target SharePoint site read only - this option available if option (b) is selected.
Select this option to set the associated SharePoint site to read only for the team members.
c. Click Next.
11. Step 5: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a migration task completes.
l Only in a case of failure - select this option to send the email if the migration task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.

On Demand Migration User Guide

Microsoft Teams Migration 190
 12. Step 6: Reporting
Select the checkbox 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 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.

13. Step 7: Schedule

a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
l 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.
b. Click Next.
14. Step 8: Summary
a. Verify the task specifications as described below:
l Name - name of the task. You can specify a custom name. The default name is
Migrate Teams.
l Source tenant - name of the tenant in this project.
l Target tenant - name of the target tenant in this project.
l Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
l 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 teams are queued (Migration state = Queued). When the system
accepts new migration work, teams are taken from the queue based on the assigned priority
and age in the queue.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab.
IMPORTANT: The task state in the task list indicates the progress of this task. Completed state means this
task processing is completed. If the migration has any errors, the status column in the Teams List View will
indicate Migration partially failed.

On Demand Migration User Guide

Microsoft Teams Migration 191
Remigration
To remigrate messages, planner tasks and files, start a new teams migration task and follow the steps outlined in
Migrating Teams. Select whether to migrate messages with attachments from the various options.

NOTE:

l Do not reuse a previous migration task because the task options you need may be different.
l See What We Migrate to review the Teams objects that are supported.
l An incremental query is used automatically to find messages, tasks and files that were added or
changed.
l The initial synchronization must have completed successfully for the incremental synchronization to
succeed.
l Perform a remigration before you switch from the source to the target tenant.
l Do not delete teams in the target tenant after migration.

Messages
Messages that were previously migrated successfully will not be remigrated. Messages are remigrated as follows:

l New messages that are added since the last synchronization will be migrated.
l Messages that were partially migrated, for example the attachment was unavailable during a previous
migration, will be migrated. Updates to these messages by users in the target tenant will not be overwitten.

Planner Tasks
Planner Tasks in the target tenant that are created or updated will not be impacted. Planner Tasks from the source
tenant will be remigrated as follows:

l Previously migrated Planner Tasks that are updated on the source tenant will not be migrated to the
target tenant.
l New Planner Tasks will be migrated to the target tenant.

Files
Previously migrated list items and files with the same name and ID will be remigrated from the source
tenant as follows:

l Updates on source will be migrated to the target.

l Updates to target will be overwritten by the remigrated source items or files.

When Teams files are remigrated an incremental query retrieves files that have been added or changed in the
channels since the last synchronization. Follow the steps outlined in Migrating Teams and select Migrate
messages and files.

On Demand Migration User Guide

Microsoft Teams Migration 192
Discovering Chats
On Demand Migration for Teams helps you discover and migrate Microsoft Chats for one or more matched users
from a source tenant to a target tenant.
In this topic:

l Starting a Chats Discovery Task

l Reviewing the Chats Discovery Task
l Reviewing the Chats Discovery Task Events
l Reviewing the Chats list view
l Deleting inactive users

Starting a Chats Discovery Task

The Chats discovery task will list all user accounts that are matched with a user in the target tenant. If new users are
added to the source tenant after the Chats discovery task completes, you must rerun another Chats discovery task.
NOTE: Chats discovery can also return the number of chats and most recent activity within the last 30 days.
To activate this capability, you must configure Microsoft 365 for the source tenant, as described below:

1. In Microsoft 365 admin center of the source tenant, go to Settings > Org Settings and open the
Services tab.
2. Select Reports, and clear the checkbox Display concealed user, group, and site names in all
reports. This setting gets applied both to the usage reports in Microsoft 365 admin center and
Teams admin center.
3. Click Save changes.

To discover Microsoft Chats:

1. Sign 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
5. Select the Teams tab and then select the Chats tab.
6. From the local toolbar, select Discover. The New Chats Discovery Task wizard opens.
7. Step 1: Description
a. Read only. The Chats discovery task will list all user accounts that are matched with a user in the
target tenant.
b. Click Next.

On Demand Migration User Guide

Microsoft Teams Migration 193
 8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discover chats.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. For example, Now indicates that
the task will start immediately after you complete the wizard.
b. Click Back to revise or review a previous step.
c. Click Finish to complete the task wizard. The task will start as scheduled.

Reviewing the Chats Discovery Task

1. Select the Tasks tab.
2. Select the Discover Chats task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is discover teams.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.

On Demand Migration User Guide

Microsoft Teams Migration 194
 f. Schedule - Date and time when the task started. For example, Now indicates that the task started
immediately after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Chats Discovery Task Events

1. Select the Tasks tab.
2. Select the task named Discover Chats that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task.
e. Summary - a descriptive statement about the event.

Reviewing the Chats list view

The columns are described as below:

User Name - name of the user account.
Migration State - migration status of chats from discovery to successful migration. Values are Discovered,
Migrating, Partially migrated, Partially migrated with Issues, Migrated, Migrated with Issues, Migration Failed.

On Demand Migration User Guide

Microsoft Teams Migration 195
Worklflow - (deprecated) the most recent operation performed on a team. Valid values are Discovered, Partially
migrated, and Migrated.
ODM Licensed - indicates whether or not an On Demand Migration user account license has been consumed when
the account migration task is started. Values are Yes, No, Not required.
OneDrive Status - migration status of the OneDrive files for this user.
Mailbox Status - migration status of a user's mailbox. It is a best practice to migrate a mailbox before chats are
migrated for any user. Values are Discovered, Matched, Migrating, Migrated, Migrated with Issues, Migration Failed,
Switched, and Migration Stopped.
Account Matching - (deprecated) indicated whether the user has been matched with another user in the target
tenant. Value is Completed.
Migrated Chats - number of chats that have been migrated.
Archived Chats - indicates whether or not the archive option is selected during a chat migration. If the value is Yes,
chats belonging to this user cannot be archived again.
Message Count (< 30 days) - number of chat messages generated by the user in the last 30 days. There is a
latency of 24-48 hours from the time a message is created.
Last Activity (< 30 days) - most recent activity in the last 30 days. This data is provided by Microsoft based on user
activity in Microsoft Teams.
Total Chats - total number of chats in the source tenant.
Source UPN - User Principal Name (UPN) of the source account.
Target UPN - User Principal Name (UPN) of the target account.

Deleting inactive users

You can delete inactive users from the Chats list view to prevent the migration of the inactive user's personal chats.

To delete inactive users

1. Select one or more users in the list view that you want to delete.
2. Click More Actions > Delete.
3. Click Yes in the Delete Objects popup to confirm the action.

On Demand Migration User Guide

Microsoft Teams Migration 196
Managing Chats with Collections
Migrating large numbers of chats requires careful planning. Organize the user accounts into collections to make
large chat lists more manageable.

Adding chats to Collections

You can add user accounts with chats to collections in three ways:

l Select the user accounts and create a new collection

l Select the user accounts and add to an existing collection
l Use a CSV file to create one or more chat collections

To add selected user accounts to a new collection:

1. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
2. Open the Chats tab and select the user accounts that you want to add to a collection.
3. From the actions toolbar, click New Collection. The New Collection dialog opens.

4. Enter a collection name in the Collection name field and click Save to add the selected user accounts to the
collection.

To add selected user accounts to an existing collection:

1. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
2. If you need to create a new collection:
a. From the top-right corner of the workspace, click Select Collection > + New Collection
b. Enter a collection name and click Save to add this collection to the project.
3. Open the Chats tab and select the user accounts that you want to add to the collection.

On Demand Migration User Guide

Microsoft Teams Migration 197
 4. From the actions toolbar, click Add to Collection. The Add to existing collection dialog opens.

5. Select your collection from the Collection name dropdown and click Save to add the selected user
accounts to the collection.

To create one or more collections with a CSV file:

This is a two-step process as described below:
Step 1: Prepare the CSV file
NOTE: Using a CSV file provides the following additional benefits:

l Multiple collections can be created with the same CSV file.

l Existing collections can be specified in the CSV file to add additional user accounts
l Accounts can be listed in multiple collections

Use the format shown below to prepare the CSV file. The minimal set of columns required are shown.
TIP: You can export the selected user accounts to a CSV file and then add the Collection column
and retain the Source UPN column. All other columns in the exported CSV file will be ignored so you
can remove those columns if you want.

l Collection - Column header for the collection name

l Source UPN - User Principal Name (UPN) of the source account.

Step 2: Import the CSV file

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams workspace.

On Demand Migration User Guide

Microsoft Teams Migration 198
 5. Open the Chats tab.
6. From the actions toolbar, click More Actions > Import Collections. The Import Collections from File
dialog opens.

7. Select Chats from the Specify kind dropdown.

8. Click Browse and select the CSV file. The selected CSV file name appears.
9. Click Import.

NOTE: If a collection in the CSV does not exist, a new collection will be created with the name specified in
the CSV.

Migrating Chats
In this topic:

l Reviewing migration readiness

l Considerations
l Starting a Chats Migration Task
l Reviewing the migration results
l Troubleshooting

Reviewing Chats Migration Readiness

NOTE: Chat migrations are heavily throttled by Microsoft on source and target tenants. As a result, migration
throughput performance is very difficult to predict. Quest recommends migrating the last 15 or 30 days of
messages during the last phase of migrations. Use a separate migration task to archive some or all of the
remaining messages for users who require the messages for regulatory or business reasons.
Quest recommends purchasing Chat addon licenses which are 4x faster because archiving all remaining
messages will take a considerable amount of time.
Use the following information in the Chats list view to support your decision.

On Demand Migration User Guide

Microsoft Teams Migration 199
 Property Value Description

Workflow Discovered On Demand has discovered the chat.

OneDrive Status Completed The OneDrive migration service has migrated the files for this user. This
must be completed for On Demand to migrate chats for this user. You
can migrate OneDrive file sharing permissions before or after the Chats
migration.
Mailbox Status Migrated User mailbox migration is complete and successful.

In addition to the information that you reviewed, verify the following:

l The temporary Migration Manager accounts for source and target tenants that you will use to migrate Teams
Chat should be granted the Teams license. You should not change your temporary Migration Manager
accounts before completing the migration project.
l The temporary Migration Manager accounts should be granted the Global Administrator or Teams
Administrator role on the tenants for which these account are used.
l [optional] Verify that you have Microsoft Teams Private Chat licenses. Check Settings > Subscriptions.

Considerations
l It is a best practice to migrate Chats after all the content like OneDrive, Mailboxes, SharePoint, Teams, etc.,
is migrated and the user accounts are matched.
l During migration, the migration task will migrate any new messages added to Chats after completing a
Discovery task.
l Chats can be migrated multiple times. During remigration, new messages are added to previously migrated
live chats in the target, and new chats that were not migrated before are migrated.
l You can archive chats only once regardless of the time-range that you select. For example, if there is a chat
between A and B, then if you archive chats for A, all messages sent by both A and B in the same chat will be
archived. If you attempt to archive chats for B, only new messages between A and B will be migrated to the
live chat in the target tenant, but any messages between A and B that were previously archived will not be
archived again.
l When you select the Archive remaining messages option in the Migration Actions step of the New Chats
Migration Task wizard, the chat archive file will be uploaded to an available OneDrive of a chat participant,
and shared with other participants. During the process, Microsoft 365 will send a notification email to the
owner of the file.
l Due to Microsoft API limitations, the discovery task is automatically run for all users during a remigration to
discover new messages and new chats. Which is why we don't recommend remigration for small users sets.

Starting a Chats 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. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams workspace.
5. Select the Chats tab and select the user accounts whose chats you want to migrate.
6. Select Migrate from the action ribbon. The New Chats Migration Task wizard opens.

On Demand Migration User Guide

Microsoft Teams Migration 200
7. Step 1: Migration Options

a. Select one or more options as described below:

l Migrate chats with unmatched users - select this option to ignore users in a chat that have
not been mapped or matched with user accounts in the target tenant. The information about
the user from the source tenant is used to migrate the chat.
For example, if John chats with Dave, and Dave's user account has not been migrated to the
target tenant, then Dave will not be able to view his chats with John in the target tenant even
if his user account is migrated to the target at a later time.
Use this option if there are user accounts in chat messages that are redundant because the
user accounts will not been mapped, matched or migrated to the target account.
l Skip OneDrive status check - select this option to ignore any verification of OneDrive
accounts. Chat messages of users will be migrated regardless of their OneDrive status in the
target tenant. Links to OneDrive files attached to chat messages will work when the
OneDrive account has been migrated and the files are successfully migrated to the OneDrive
account in the target tenant.
NOTE: OneDrive accounts must be provisioned in the target tenant in advance when
using this option.

l Avoid adding external users to target chats - select this option to avoid adding external
users to the chats that are migrated to the target tenant. If this option is not selected, external
users must be mapped to external users in the target tenant before migration, otherwise you
will receive a warning and the migration will stop.
b. Click Next.

On Demand Migration User Guide

Microsoft Teams Migration 201
8. Step 2: Migration Actions

a. Select one or more action options as described below:

i. Migrate to live chat - select this option to migrate all or a subset of the chat messages from
the source tenant to the live chat in the target tenant. You choose a subset or all messages
based the date range option as defined below:
l Messages within last 15 days - the most recent chats within 15 days discovered
after the last migration will be migrated.
l Messages within last 30 days - the most recent chats within 15 days discovered
after the last migration will be migrated.
l Messages within last 60 days - the most recent chats within 15 days discovered
after the last migration will be migrated.

Messages are merged into manageable sets and then migrated. The effect of merging
messages is described in the example below:
Consider a set of original messages in the source tenant as shown below:

On Demand Migration User Guide

Microsoft Teams Migration 202
 When the message set is merged and migrated, they appear in the target tenant as shown
below. The migration service determines the merge set. Messages retain their chronological
order and the time stamp is converted to GMT.

ii. Archive remaining messages - select this option to archive the rest of the chat messages.
These messages are archived as an HTML file and are uploaded to an available OneDrive
selected from chat participants. Then the HTML file is shared with other chat participants.
Finally, a Conversation history tab is be created in the migrated chat in the target tenant
which can be used to access the HTML file in the chat.

On Demand Migration User Guide

Microsoft Teams Migration 203
 NOTE: Chat migrations are heavily throttled on source and target tenants. Migration
throughput performance is very difficult to predict. Quest recommends migrating the
last 15 or 30 days of messages during the last phase of migrations. Use a separate
migration task to archive some or all of the remaining messages for users who require
the messages for regulatory or business reasons.
You can exercise greater granular control over the remaining messages using the time-
range options described below:
l Last 30 days of remaining messages - the most recent 30 days of messages that
remain to be migrated will be archived.
l Last 60 days of remaining messages - the most recent 60 days of messages that
remain to be migrated will be archived.
l Last 90 days of remaining messages - the most recent 90 days of messages that
remain to be migrated will be archived.
l All remaining messages - all messages that remain to be migrated will be archived.
l Use additional Team Chats licenses for faster archiving - this option is displayed
when additional Chat addon licenses are detected. Select this option to increase the
throughput for archiving remaining chat messages.

Example 1: Assume that you are migrating chats on June 30.

If you select Migrate to live chat and Messages within 15 days, then all chat messages
from June 16 to June 30 will be migrated to the live chat in the target tenant.
If you also select Archive remaining messages and Last 30 days of remaining
messages, any remaining chats from May 17 to June 15 will be archived and available in
the Conversation history tab of the user in the target tenant. Chats before May 17 will not
be migrated.
Example 2: Assume that you are migrating chats on June 30.
If you select Migrate to live chat and Messages within 15 days but there are no chats
within the last 15 days, then no chats will be migrated to the live chat in the target tenant.
If you also select Archive remaining messages and Last 30 days of remaining
messages, any remaining chats from May 17 to June 15 will be migrated or archived to the
Conversation history tab of the user in the target tenant.
Example 3: Assume that you migrated all chats previously on June 20 and are migrating
chats again on June 30.
If you select Migrate to live chat and Messages within 15 days, only new chats
discovered after June 20 will be migrated to the live chat in the target tenant. The migration
service remembers the previous migration.
If you also select Archive remaining messages and All remaining messagesbut no chats
remain, then none will be migrated or archived.

b. Click Next.
9. Step 3: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a migration task completes.
l Only in a case of failure - select this option to send the email if the migration task fails to
complete successfully.

On Demand Migration User Guide

Microsoft Teams Migration 204
 b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
10. Step 4: Reporting
Select the checkbox 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 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.

11. Step 5: Schedule

a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
l 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.
b. Click Next.
12. Step 6: Summary
a. Verify the task specifications as described below:
a. Name - name of the task. You can specify a custom name. The default name is
Migrate chats.
b. Source tenant - name of the source tenant for the chats.
c. Target tenant - name of the target tenant where the chats will be migrated.
d. Scheduled start - date and time when the task will start. For example, Now indicates that
the task will start immediately after you complete the wizard.
b. Click Finish to complete the task wizard. The task will start as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab.

Reviewing the Migration Results

Once the migration task is complete, use the information on the Chats tab to verify the success of the migration. The
column in the chats migration list view are as follows:

On Demand Migration User Guide

Microsoft Teams Migration 205
 l User Name - name of the user from the source tenant.
l Migration State - status of the task in the migration process. Values are as listed below:
l Discovered
l Migrating
l Partially migrated
l Partially migrated with issues
l Migrated
l Migrated with issues
l Migration failed
l Workflow - the most recent operation performed on the group. Valid values are
l migrated - when all discovered chats have migrated.
l partially migrated - when some chats failed to migrate. The number of migrated chats is fewer than
the total number of chats.
l Migrated Chats - number of chats migrated for the user. This may be fewer than the total number of chats. If
a participant is not matched or OneDrive not migrated then migration of the chat is intentionally skipped and
the event documented on the Events tab.
l Archived Chats - indicates whether or not chats have been archived. When chats are migrated and
archived, the value changes to Yes for the selected user. Since chats can be archived only once, if you
attempt to re-archive migrated chats, a warning message appears in the migration task events.
l Source UPN - UserPrincipalName (UPN) of the source account.
l Target UPN - UserPrincipalName (UPN) of the target account.

Troubleshooting
Chats may not be successfully migrated due to a variety of reasons. Two example are described below.

Example 1: Members of a chat have not been matched or migrated to the

target tenant.

This is a common case where one or more members are not available in the target tenant. In such a case, the chat
will not be migrated. In this example, the chat migration for Joni Sherman indicates a failure. The Status column
indicates Migration failed. Joni has been chatting with the Administrator. However the Administrator account
has not been matched or migrated to the target tenant.

On Demand Migration User Guide

Microsoft Teams Migration 206
When you inspect the migration task details, it will indicate a failure. You can click the event icons to get more
information about the failure.

Resolution: When accounts are missing from the target tenant, you must map or migrate the account and rerun the
chat migration task.

Example 2: An error in a chat message prevents all subsequent chat messages

from being migrated.

In this example, chats for Joni Sherman indicate a migration problem. The Status column indicates Migration
partially failed. There are 36 chat messages but only 3 messages could be migrated. The migration task
completes successfully but no more messages are migrated. The service account that is used to migrate the chat
remains as a member of the chat in the target tenant.
When you inspect the migration task, you will notice that the task has completed successfully, but there are error
events in the task detail.
The Events list will indicate the error event, but more importantly you will notice that no more messages are
migrated after the error event.
Resolution: Inspect the chat messages of the user and resolve the issue. Then rerun the migration task for the same
user. If you are unable to address the issues with chat messages, contact Quest Technical Support.

On Demand Migration User Guide

Microsoft Teams Migration 207
 6

Microsoft 365 Groups Migration

On Demand Migration for Teams securely migrates content for Microsoft 365 Groups without Teams
functionality across Microsoft 365 tenants. You can also use this dashboard for migration of Microsoft Teams
and associated Microsoft 365 Groups migration (see Microsoft Teams Migration). Microsoft Teams migration
requires additional licensing.
The basic Microsoft 365 Groups (without associated Teams) migration process consists of the following steps:

# Step

1 Create a new migration project or open an existing project.

2 Grant necessary permissions in case these permissions are not already granted.
3 Discover Microsoft 365 Groups (without associated Teams) in the source tenant. These groups
are not provisioned in the target tenant at this stage.

4 Provision groups in the target tenant.

l The temporary Migration Manager account in the source tenant will be added to all source
Microsoft 365 Groups as a member
l The temporary Migration Manager account in the target tenant will be added to all
migrated target Microsoft 365 Groups as a member and owner.

These accounts can be removed from groups after the migration is completed.

5 Migrate Microsoft 365 Groups without Teams functionality

6 Automatically migrate files associated with content. All files associated with content are
transferred to the target according to the options, selected in the migration task.

7 Monitor the progress by tracking tasks and events.

What We Migrate
The following content associated with Microsoft 365 Groups without Teams functionality can be migrated:

Objects and content types

Object Support Notes

Group settings ✔

On Demand Migration User Guide

Microsoft 365 Groups Migration 208
 Object Support Notes

Inbox folder and Calendar from the group ✔ this content is always migrated
mailbox
OneDrive Shared Library ✔ OneDrive Shared Library must be created and
associated with a group in the same SharePoint
site.
Planner ✔

SharePoint site ✔ the entire site is migrated

Limitations
l Microsoft 365 group cannot be migrated in case the target group already exists. For all such groups the
Target group exists warning message is displayed in the grid. As a workaround, you can rename the
source group and re-create migration project.

Prerequisites
Verify the following requirements are met before migrating Microsoft Teams. If these actions are not performed,
discovery, provision and migration tasks will fail or some data might be lost!

l The following consents are granted before Teams migration can be started
l Migration - Basic,
l Migration - Mailbox Migration
l Migration - SharePoint
l Migration - Teams

TIP: If the consents are not granted or expired, Discover Teams action is disabled and the following
notification is displayed: Grant admin consent to the following Migration sub modules on the Tenants
page for both source and target tenants: Basic, SharePoint, and Teams. Open Tenants page and
grant the necessary Consents and Permissions so that the product can access the source and target
tenants. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is
granted, you can start discovering Teams.

IMPORTANT: The Tenant Administrator must open the OneNote application just once in the target tenant. It
does not have to be opened or run by every user. If OneNote is not initialized before granting consent for
Teams migration, the following error occurs: Unexpected response while attempting to
register the tenant: AADSTSxxxxxx: The app needs access to a service
("https://*.onenote.com/")

l User must be matched or migrated before using the On Demand Migration for Teams service.
l Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for
Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you
migrate the chats.
l Accounts joined to existing teams should be matched or migrated in the migration project.

On Demand Migration User Guide

Microsoft 365 Groups Migration 209
Required permissions

Feature Required permissions

Migrate conversations Read all channel messages

Have full access to the Chat Service Aggregator
Have full access to the Skype Teams Service
Create chat and channel messages with anyone's identity and with any
time stamp
Migrate private chats Read all chat messages
Read and write user chat messages
Provision groups and teams Read and write directory data

Read and write all groups

Migrate files and OneNote items Read and write all OneNote notebooks
Read and write items in all site collections
View and modify notes for all users
Migrate groups and teams Read all users' full profiles
membership
Read or write user region
Add and remove members from all teams
Add and remove members from all channels

Temporary Migration Manager accounts

l It is recommended to create or use source and target temporary Migration Manager accounts.
l The temporary Migration Manager accounts should be granted the Global Administrator or Teams
Administrator role and Application Impersonation role on the tenants for which these account are used.
The temporary Migration Manager accounts in the source and target tenant should have Teams license from
the Microsoft 365 admin center.
l Do not change your temporary Migration Manager accounts before completing the migration project.
l You must remove the source and target temporary Migration Manager accounts for safety reasons
after the migration is completed. These accounts can be removed from teams as described in
Finalizing the Migration.

The target temporary Migration Manager account use is in and not limited to the following scenarios:

l The target temporary Migration Manager account that is used to perform Teams provisioning creates and
owns these provisioned target teams.
l The target temporary Migration Manager account is added to all target teams and Microsoft 365 Groups as a
member and an owner, and to all target private channels as an owner.
l The target temporary Migration Manager account is used to perform the Teams migration and displayed as
the owner of all migrated conversation and chat messages and planner tasks on the target.

On Demand Migration User Guide

Microsoft 365 Groups Migration 210
 l The target temporary Migration Manager account is added to all the chats (both group chats and private
chats) as a participant during chats migration, and then removed from the migrated chats as soon as the
chat migration is complete. All migrated chats of the target temporary Migration Manager account are hidden
when the chat migration is complete.

Discovering Groups
In this topic:

l Discovering all groups

l Discovering groups from a file
l Reviewing the Discover Groups task
l Reviewing the Discover Groups task events

Discovering all groups

This is the simplest approach which uses the Discover Groups tasks to inspect the source tenant and discover all
the Microsoft 365 Groups.

To start the Discover Groups task:

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
5. Click Discover M365 Groups from the Groups tile in the Teams dashboard
- or -
Select the M365 Groups tab and select List View if not already selected. Then click Discover Groups >
Discover All from the Actions menu.

6. The New Groups Discovery Task wizard opens.

On Demand Migration User Guide

Microsoft 365 Groups Migration 211
 7. Step 1: Discovery Options

a. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discover Groups.
ii. Source tenant - name of the source tenant in this project.

On Demand Migration User Guide

Microsoft 365 Groups Migration 212
 iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Discovering Groups from a File

When you have a large set of groups but you want to migrate a subset of those groups, you can start the discovery
process by using a CSV file. The CSV file lets you specify the groups that you want to discover and ignore the rest.
This is a two-step process:
Step 1: Preparing the CSV file

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. From the navigation pane, click Active groups.
3. Select the Microsoft 365 tab in the Active Groups page.
4. Click Export and then click Export groups in this list. A Groups.csv file will be downloaded to your
computer.

5. Edit the CSV and retain the groups you want to discover that are not associated with Teamsand delete the
rest. You can filter that data based on the Has Teams column to get a list of groups that are not associated
with teams. If you retain a row that references a group associated with a team, the group will be ignored
during discovery. Then retain the Group ID and Group name columns.

On Demand Migration User Guide

Microsoft 365 Groups Migration 213
 6. Save the CSV file. You may rename the file if needed.

Step 2: Starting the Discover Groups Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
5. Click the M365 Groups tab and select List View if not already selected. Then click Discover Groups >
Discover from file from the Actions menu.
6. The New Groups Discovery Task wizard opens.

On Demand Migration User Guide

Microsoft 365 Groups Migration 214
7. Step 1: Discovery Options

a. Click Browse and select the CSV that contains the Group IDs and Group names of the groups that
you want to discover.
b. Click Next.
8. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
9. Step 3: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discover Groups.
ii. Source tenant - name of the source tenant in this project.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

On Demand Migration User Guide

Microsoft 365 Groups Migration 215
Reviewing the Groups Discovery Task
1. Select the Tasks tab.
2. Select the task that you want to review. The default name is Discover.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is discovergroups.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

4. If you selected the option to collect statistics in the New Groups Discovery Task wizard, you will see and
additional task for Collect Plan and Task statistics for Groups. Click the task to view the corresponding
details in the details pane.

Reviewing the Groups Discovery Task Events

1. Select the Tasks tab.
2. Select the task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the event details pane that opens, the information presented is as
described below:

On Demand Migration User Guide

Microsoft 365 Groups Migration 216
 a. Object - Name of the group.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Application.
e. Source - Name of the On Demand Migration service.

Discovering Teams and Groups

Every team is associated with a Microsoft 365 Group, but there are groups that are not associated with teams. In
this topic, the term team means a Microsoft Team and includes its associated group, and the term group means a
Microsoft 365 Group that is not associated with a team.
NOTE: This topic explains the process to discover both teams and groups. If you want to discover only
teams, see Discovering Teams. If you want to discover only groups that are not related to teams, see
Discovering Groups.
In this topic:

l Discovering all teams and groups

l Discovering teams and groups from a file
l Reviewing the Discover task
l Reviewing the Discover task events

Discovering all teams and groups

This is the simplest approach which uses the Discover tasks to inspect the source tenant and discover
all the teams.

To start the Discover task:

On Demand Migration User Guide

Microsoft 365 Groups Migration 217
1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click Discover > Discover All from the Teams dashboard.
6. The New Teams & Groups Discovery Task wizard opens.
7. Step 1: Discovery Options

NOTE: The Azure AD administrator account will be added to the discovered Teams and Groups.

a. All Teams - select this option to discover all Microsoft Teams.

b. All Groups - select this option to discover all Microsoft 365 Groups without Teams.
c. All Teams and Groups - select this option to discover Microsoft 365 Groups and Teams.
d. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.

On Demand Migration User Guide

Microsoft 365 Groups Migration 218
 9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Discover.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Discovering teams and groups from a file

This step is required if you plan to discover teams and groups using a CSV file. When you have a large set of teams
and groups but you want to migrate a subset of the objects, the CSV file lets you specify the teams and groups that
you want to discover and ignore the rest. You can then use this file in the New Teams & Groups Discovery Task as
described in this topic to discover the teams from the source tenant.

Step 1: Preparing the CSV file

1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source
tenant administrator.
2. From the navigation pane, click Active groups.
3. Select Microsoft 365 tab in the Active Groups page

On Demand Migration User Guide

Microsoft 365 Groups Migration 219
 4. Click Export and then click Export all groups. A Groups.csv file will be downloaded to your computer.

5. Edit the CSV file and retain the Group ID and Group name columns. Then retain the teams and groups you
want to discover and delete the rest.

6. Save the CSV file. You may rename the file if needed.

Step 2: Starting the Discover Task

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click Discover > Discover from file from the Teams dashboard.
6. The New Teams & Groups Discovery Task wizard opens.

On Demand Migration User Guide

Microsoft 365 Groups Migration 220
7. Step 1: Discovery Options

a. Click Browse and select the CSV that contains the Group IDs and Group names of the teams that
you want to discover.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

On Demand Migration User Guide

Microsoft 365 Groups Migration 221
 10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Discover.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Discover Task

1. Select the Tasks tab.
2. Select the task that you want to review. The default name is Discover.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is discoverteams.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. State - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

4. If you select the options to collect statistics in the New Teams & Groups Discovery Task wizard, you will see
additional tasks: Collect Plan and Task statistics for Teams and Groups and Collect Message statistics for
Teams. Click each task to view the corresponding details in the details pane.

On Demand Migration User Guide

Microsoft 365 Groups Migration 222
Reviewing the Discover Task Events
1. Select the Tasks tab.
2. Select the task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the event details pane that opens, the information presented is as
described below:
a. Object - Name of the team or group discovered.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Application.
e. Source - Name of the On Demand Migration service

Managing Groups with Collections

Migrating large numbers of groups requires careful planing. The groups could belong to different offices and
geographical locations or sensitive departments. Migrating groups of Finance or Legal departments require special
care. Organize the groups into collections to make large group lists more manageable.

Working with the Collection Dashboard

The Collection Dashboard shows the collection-specific summary, allows you to see group added to it, create tasks
for them, and monitor the progress of tasks.

l To view the collection dashboard for an existing collection

a. Log in to Quest On Demand and choose an organization if you have multiple organizations.
b. From the navigation pane, click Migration to open the My Projects list.

On Demand Migration User Guide

Microsoft 365 Groups Migration 223
 c. Create a new project or open an existing project.
d. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
e. From the top-right corner of the workspace, click Select Collection and then select the collection to
view. The collection Dashboard is displayed.
f. Click the M365 Groups tab. You will see the list of groups that belong to the collection.
l To see the tasks for collection-specific accounts, use the corresponding tile on the collection Dashboard or
open the Tasks tab.
l To see the events related to the collection, use the corresponding widget on the collection Dashboard or
open the Events tab.
l To rename or delete the collection, click the corresponding buttons in the menu.
l To return to the project dashboard, click the project name in the navigation bar.

Creating a Collection manually

1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
2. From the top-right corner of the workspace, click Select Collection > + New Collection
3. Enter a collection name and click Save to add this collection to the project.

Adding groups to Collections

You can add groups to collections in several ways:

l Select the groups and create a new collection for them

l Select the groups and add to an existing collection
l Use a CSV file to add groups to a new or existing collection from the Teams tab
l Use a CSV file to add groups to an existing collection from the Teams collection dashboard

To add selected groups to a new collection:

1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
2. Click the M365 Groups tab and select List View if not already selected.
3. Select the groups you want to add to the collection.
4. From the actions toolbar, click New Collection. The New Collection dialog opens.

5. Enter a collection name in the Collection name field and click Save to add the selected groups to the
collection.

On Demand Migration User Guide

Microsoft 365 Groups Migration 224
To add selected groups to an existing collection:

1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
2. If you need to create a new collection:
a. From the top-right corner of the workspace, click Select Collection > + New Collection
b. Enter a collection name and click Save to add this collection to the project.
3. Click the M365 Groups tab.
4. Select the groups you want to add to an existing collection.
5. From the actions toolbar, click Add To Collection. The Add to existing collection dialog opens.

6. Select a collection from the Collection name dropdown and click Save to add the selected groups to the
collection.

To add groups from a CSV file to a new or existing collection from the M365 Groups tab:
This is a two-step process as described below to add teams to an existing collection from the M365 Groups tab:
Step 1: Prepare the CSV file

NOTE: CSV file names with non-ASCII characters are not supported. Teams in the CSV that have
not been discovered cannot be added to a collection.

Use the format shown below to prepare the CSV file. The minimal set of columns required are shown.
TIP: You can export the selected groups to a CSV file and then add the Collection column and retain
the Source MailNickname column. All other columns in the exported CSV file will be ignored so you
can remove those columns if you want.

l Collection - Column header for the collection name

l Source MailNickname - Email alias of the M365 group. You can get the Source MailNickname
property of the teams when you export groups to a CSV file. Source MailNickname values are
case-sensitive.

On Demand Migration User Guide

Microsoft 365 Groups Migration 225
Step 2: Import the CSV file

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams workspace.
5. Open the M365 Groups tab.
6. From the actions toolbar, click More Actions > Import Collections. The Import Collections from File
dialog opens.

7. Select Teams/M365 groups from the Specify kind dropdown.

8. Click Browse and select the CSV file. The selected CSV file name appears.
9. Click Import.

NOTE: If a collection in the CSV does not exist, a new collection will be created with the name specified in
the CSV.

To add groups from a CSV file to an existing collection from the Teams Collection dashboard:
This is a two-step process as described below:
Step 1: Prepare the CSV file

NOTE: CSV file names with non-ASCII characters are not supported. Groups in the CSV that have
not been discovered cannot be added to a collection.

Use the format shown below:

MailNickName - Email alias of the M365 group. You can get the MailNickName property of the groups
when you export groups to a CSV file. MailNickName values are case-sensitive.

On Demand Migration User Guide

Microsoft 365 Groups Migration 226
Step 2: Import the CSV file

1. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
2. From the top-right corner of the workspace, click Select Collection and then select the collection.
3. Click Fill From File from the Teams collection Dashboard menu. The Fill from File dialog opens.
4. Click Browse and select the CSV file that you created.
5. Click Populate to add the groups from the file to the collection.

Exporting Groups
To export groups to a comma-separated values (CSV) file:

1. Click Teams from your migration project.

2. Click the M365 Groups tab. From the M365 Groups List View select the groups you want to export.
3. From the M365 Groups List View select More Actions and then select Export.
4. Open the CSV file by extracting it from the ZIP file that is downloaded to your computer.

The exported data contain the following information:

l Group Name - source Microsoft 365 group name.

l Workflow - (deprecated) the most recent operation performed on the Microsoft 365 group.
l Created - date and time the Microsoft 365 group record was created
l Target Group Name - suggested target team name that will be provisioned in the target tenant
l Source MailNickname - alias for the associated Microsoft 365 Group. This value will be used for the mail
enabled object and will be used as PrimarySmtpAddress for this Microsoft 365 Group. The value must be
unique across your tenant.
l Last Operation Description - description of the last operation performed on this group.

Mapping Groups
You can rename and map groups, or rename, map and merge one or more source groups to a specific team in the
target tenant in two ways:

l Renaming and mapping groups automatically

l Renaming and mapping groups manually from a file

Mapping and Renaming Groups 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 Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.

On Demand Migration User Guide

Microsoft 365 Groups Migration 227
 5. Click the M365 Groups tab and select one or more groups that you waIts really nt to rename and map.
6. Click More Actions and then click Rename and Map. The New Teams & Groups Rename and Map Task
wizard opens.
7. Step 1: Mapping options
a. Enter the information as described below:
l Add prefix - specify a prefix for the group name.
l Add suffix - specify a suffix for the group name.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a mapping task completes.
l Only in a case of failure - select this option to send the email if the mapping task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Rename
and Map Task.
ii. Source tenant - name of the tenant in this project.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The 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.

Mapping, Renaming and Merging Manually from a File

To rename Microsoft 365 groups or merge one or more source groups to a specific group in the target tenant, a CSV
file is used to indicate the mapping between source and target groups as described below.

On Demand Migration User Guide

Microsoft 365 Groups Migration 228
To creating a mapping file:

1. Prepare a comma-separated values (CSV) file with the source and target group names.
TIP: Export selected groups to a comma-separated values (CSV) and then edit this file. See
Exporting Groups for more details.

2. The header row defines the names of the source and target attribute used for mapping. Subsequent rows list
the mapping values of the attributes.
The columns are as follows:
l Source Mailnickname - unique name of the source group. The following column header variations
are supported: SourceMailNickname, Source MailNickname, Source MailNickName. The
column header is case sensitive.
l Target Mailnickname - unique name of the target group. The following column header variations
are supported: TargetMailNickname, Target MailNickname, Target MailNickName. The
column header is case sensitive. You can merge multiple source groups to a single target group
when you specify the same Target Mailnickname in a mapping file.
l Target Group Name - display name of the target group. The column header is case sensitive.

Example 1: Row 2: Simple change of name.

The source group display name and mailnickname are changed.
Example 2: Rows 3 and 4: Different target groups with the same display name.
The Target Mailnicknames are different but the Target Group Names are the same. The Target
Mailnickname takes precedence and the groups will be mapped to distinct target groups but the display
name of each target group will be the same. It is recommended that you use unique display names to
avoid confusion.
Example 3: Rows 5, 6 and 7: Merge multiple source groups with the same target group.
The Target Mailnickname is the same. The source groups will be merged with the same target group with
the specified display name.

3. Save the CSV file.

NOTE: File names with non-ASCII characters are not supported.

To upload a mapping file:

1. Log in to Quest On Demand and choose an organization if you have 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.

On Demand Migration User Guide

Microsoft 365 Groups Migration 229
 4. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
5. Click the M365 Groups tab.
6. Click More Actions and then click Map from File. The New Mapping from File Task wizard opens.
7. Step 1: Mapping file
a. Click Browse and select the CSV mapping file. The selected file name appears next to the
Browse button.
b. Click Next.
8. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a mapping task completes.
l Only in a case of failure - select this option to send the email if the mapping task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
9. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name.
ii. Source tenant - name of the tenant in this project.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or monitor
alerts and notifications from the Eventstab.

On Demand Migration User Guide

Microsoft 365 Groups Migration 230
Provisioning Groups
Before you start, verify that you have discovered all the Microsoft 365 groups without teams. Make sure that all
accounts that are members of these groups, have been discovered and matched with accounts in the target tenant.
Group members are not added to groups in this step. Use the migration task to migrate group membership.

To provision Microsoft 365 Groups:

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
5. Click theM365 Groups tab.
6. Select one or more groups from the Groups List View.
7. Click Provision. The New Groups Provisioning Task wizard opens.
8. Step 1: Provision Options

These options control the actions of the provisioning task if the selected groups already exist in the target
tenant. Groups that are not in the target tenant will be automatically provisioned.

Select and configure the options as described below:

a. Do not provision the group - The group will be skipped if it exists in the target tenant.
b. Provision a new group. A suffix will be added to the original name - A new group will be
provisioned with the specified suffix appended to the group name
l New group display name suffix - Specify a suffix to append to the group name. The default
suffix is (migrated).

On Demand Migration User Guide

Microsoft 365 Groups Migration 231
 c. Merge with the existing group - Select this option to set up a mapping between a source and
target group with the same name. When members are migrated with the migration task, the accounts
that are members of the source group will be added to the same group in the target tenant.
d. Suppress automatic Group Welcome Message sending - Select the check box to prevent group
members from receiving a welcome message.
e. Multi-geo options: Preferred location - If the target tenant is geo-enabled, select a location to
update the geo location of the selected groups in the target tenant. The default is None. See
Microsoft 365 Multi-Geo availability for the description of the geo locations in the dropdown list.
9. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a provisioning task completes.
l Only in a case of failure - select this option to send the email if the provisioning task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
10. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
11. Step 4: Summary
a. Verify the task specifications as described below:
l Name - Name of the task. The default name is Provision Groups. You can specify a
custom name.
l Source tenant - Name of the source tenant in this project.
l Target tenant - Name of the target tenant in this project.
l Scheduled start - Date and time when the task will start. Now indicates that the task will
start immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab.

On Demand Migration User Guide

Microsoft 365 Groups Migration 232
Removing Groups
To manage large lists of groups in a project, you can remove one or more groups from the groups list that you don't
need for migration processes. The groups that are removed will remain in the source tenant and you must re-
discover the groups in the project when you need them for migration.
If these groups are listed in other projects, they will be displayed in those projects.

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
5. Select the Teams tab and select List View if not already selected.
6. Select the groups you want to clear.
TIP: Use filters, search or collections to quickly navigate through the list of groups.

7. Click More Actions and then click Delete.

8. The Remove Objects confirmation dialog opens.
9. Click Remove to remove the selected groups from the list.

Collecting Statistics
The Collect Statistics task for M365 Groups conducts an assessment of selected group in the source tenant and
provides information like member count, planner count and planner task count for the groups selected in the source
tenant, and optionally in target tenant if the group is already provisioned.
Each Collect Statistics task generates events. Events are milestones that a task achieves as it runs. For example,
when a M365 Groups Collect Statistics Task starts, an event is logged and it appears in the events list. When the
number of groups that are selected for assessment is large, the M365 Groups Collect Statistics divides the total
number of groups into manageable sets. Each set is called a batch. When a batch of groups is assessed, another
event occurs.
In this topic:

l Starting an M365 Groups Collect Statistics Task

l Reviewing the M365 Groups Collect Statistics Task
l Reviewing the events for the M365 Groups Collect Statistics Task
l Reviewing the statistics collected

Starting a M365 Groups Collect Statistics Task

1. Log in to Quest On Demand and choose an organization if you have 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 the Teams tile, or click Open from the Teams tile to open the Teams workspace.

On Demand Migration User Guide

Microsoft 365 Groups Migration 233
5. Select the M365 Groups tab.
6. Select the groups in the list from where you want to collect statistics. You can use search, filtering or
collections to quickly navigate through the list of mailboxes. You can select the check box in the table header
to select all the accounts.
7. Click Collect Statisticsfrom the Actions ribbon. The New Collect Statistics Task wizard opens.
8. Step 1:Collect Statistics Options
a. Choose from the following options
l Include collection of statistics from target tenant - select this option to include the same
groups from the target tenant. Statistics will only be collected for the target tenant groups if a
provision task has been executed for the group previously.
l Collection levels:
l Basic (Fast) - collect statistics about member count and content size (in GB) for the
groups selected in the source and target tenant if provisioned.
l Advanced (Slow) - collect statistics about member count and content size (in GB),
planner count and planner task count for the groups selected in the source and target
tenant if provisioned. The task requires more time to run.
NOTE: When a Collect Statistics task is started with this option selected, the
temporary Migration Manager for the source tenant will be added to all
groups. The additional information collected by the tasks are used in the
migration process for teams and groups, and helps improve the performance
of the migration task.

b. Click Next
9. Step 2:Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
10. Step Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. Default name is Collect
Statistics.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

On Demand Migration User Guide

Microsoft 365 Groups Migration 234
Reviewing the M365 Groups Collect Statistics Task
1. Select the Tasks tab.
2. Select the Collect Statistics task for groups that you want to review.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is collectstatistics.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. Status - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - The number of events that the task encountered.

Reviewing the events for the M365 Groups Collect Statistics Task
1. Select the Tasks tab.
2. Select a Collect Statistics task for groups that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the task details pane that opens, the information presented is as
described below:
a. Object - Not applicable for this event.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.
d. Category - Type of task. the value is Application.
e. Source - the workspace from where the event was generated. The value is Teams Migration.

On Demand Migration User Guide

Microsoft 365 Groups Migration 235
Reviewing the statistics collected
1. Open the Teams workspace.
2. Select the M365 Groups tab and then select List View if not already selected.
3. Review the statistics collected for each team. The statistics displayed depends on the option selected in the
New Collect Statistics Task wizard.

Migrating Groups
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.
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.

On Demand Migration User Guide

Microsoft 365 Groups Migration 236
To migrate Microsoft 365 Groups:

1. Log in to Quest On Demand and choose an organization if you have 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 Teams from the project tiles. Click Open from the Teams tile to open the Teams dashboard.
5. Click theM365 Groups tab.
6. Select one or more groups from the Groups List View that are provisioned (State = Provisioned)
7. Click Migrate. The New Groups Migration Task wizard opens.
8. Step 1: Migration Options

a. Group mailbox - Select this option to migrate Group Mailbox.

b. SharePoint Content - Select this option to migrate associated SharePoint sites including files, One
Note, OneDrive Shared Library and other supported tools.
c. Planner - Select this option to migrate the group Planner.
d. Group Membership - Select this option to migrate group members. If this option is not selected,
group members will not be migrated.
9. Step 2: File Version Options
a. Choose the migration option for file versions associated with groups selected for migration.
l Latest version only - This is the default selection. The most recent version of the file will be
migrated. All other versions will be ignored.
l 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.
l 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.

On Demand Migration User Guide

Microsoft 365 Groups Migration 237
 l 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.
l 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.
l 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.
l 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.
l 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.
b. Click Next.
10. Step 3. File Conflict Options
a. Choose a conflict resolution option.
NOTE:
l Conflict resolution rules are applied only to files that have been previously migrated.
l Conflict resolution rules will not be applied if the All versions option is selected in the
previous step. All files in the target tenant will be overwritten if all files are migrated.
l Overwrite target files - all migrated files in the target tenant will be overwritten. Migration is
fastest with this option selected.
l Skip if target file is the same version or newer - ignore files in the target tenant with the
same or newer version. If the file does not exist in the target tenant, a copy of the source file
will be migrated.

On Demand Migration User Guide

Microsoft 365 Groups Migration 238
 l Copy source file if target is newer - preserve the file in the target tenant if it is the same
or newer version and migrate a copy of the source file. When you choose this option, you
must also choose from one of the following file suffix options: _Copy, _Source, _Older, _
Backup, and _1.
b. Click Next.
11. Step 4: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a migration task completes.
l Only in a case of failure - select this option to send the email if the migration task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
12. Step 5: Reporting
Select the checkbox 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 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.

13. Step 6: Schedule

a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
14. Step 7: Summary
a. Verify the task specifications as described below:
l Name - Name of the task. The default name is Migrate Groups. You can specify a
custom name.
l Source tenant - Name of the source tenant in this project.
l Target tenant - Name of the target tenant in this project.
l Scheduled start - Date and time when the task will start. Now indicates that the task will
start immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or
monitor alerts and notifications from the Eventstab.

On Demand Migration User Guide

Microsoft 365 Groups Migration 239
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.

On Demand Migration User Guide

Microsoft 365 Groups Migration 240
 7

SharePoint Migration
On Demand Migration offers a fast and convenient way to transfer SharePoint content between Microsoft 365
tenants. SharePoint migration functionality requires additional licensing.
IMPORTANT: Before migrating any SharePoint sites, you must ensure all impacted accounts exist in the
target tenant. Account matching or migration should be completed.
The Getting Started tile on the SharePoint migration Dashboard with Quick help helps you to prepare, start and
perform all the steps to migrate your SharePoint sites. The basic SharePoint migration workflow consists of the
following steps:

Step Description

1 Configure the SharePoint migration project defaults (optional)

2 Verify prerequisites are met
3 Discover sites (top-level sites) in the source tenant
4 Discover site contents like members, webs and lists (optional)
5 Map geo-locations (optional)
6 Map source sites to custom target sites (optional)
7 Match source sites to with existing target sites (optional)

8 Map Lists (optional)

9 Override migration defaults for specific migration tasks (if necessary)
10 Migrate site collections and their content
11 Monitor the progress and track issues

IMPORTANT: Quest recommends performing test and pilot migrations before starting the full-scale
migration of the production environment. This helps you better plan the migration project and align the
migration tasks with the organization requirements.

CAUTION: Finish all account migration tasks that are pending before starting the SharePoint
migration.

On Demand Migration User Guide

SharePoint Migration 241
What We Migrate
Migration limitations indicated below may not be an exhaustive list of limitations as some may appear in unique
customer migration scenarios, or arise due to platform or legacy support restrictions. In some cases, a solution to a
limitation may already be on the product roadmap.
Quest On Demand migrates the following SharePoint components:
NOTE: You can migrate files with a maximum size of 250 GB. Quest On Demand supports Shared with me
panel functionality on the user's Office portal OneDrive pages for the documents and folders shared using
SharePoint.
Microsoft public preview features are not supported.

Objects and content types

Object Support Notes

Site collections and sites

Modern experience: top-level sites and sub-sites

Document ID service feature ✔

Global and site term groups ✔

Hub settings and associations ✔

Language settings ✔

List templates ✔

Lists and Libraries ✔

Navigation elements ✔

People and groups ✔

Quick launch ✔

Regional settings ✔

SharePoint Designer settings ✔

Site collection admins ✔

Site collection feature activation ✔

Site collection owner ✔

Site columns ✔

Site content types ✔

Site feature activation ✔ Active site feature will be activated on the target
during migration but the impact of activating the
feature may not be supported on the target.
Site permissions ✔

Sub-sites ✔

On Demand Migration User Guide

SharePoint Migration 242
Object Support Notes

Themes gallery ✔

Title, description and logo ✔

Top navigation ✔

Web parts gallery ✔

Site templates
Sites and webs based on unsupported templates are not supported for migration and will be skipped unless they
are remapped. Unsupported site templates listed below is selective of common and popular templates.

Community site (COMMUNITY#0) ✔

Classic project site (PROJECTSITE#0) ✔

Classic team site (STS#0, ✔

SPSMSITEHOST#0)
Document Center (BDR#0) ✔

Enterprise Wiki (ENTERWIKI#0) ✔ Some limitations are applicable

Modern communication site ✔
(SITEPAGEPUBLISHING#0)
Modern Microsoft 365 group site (Group#0). ✔ The Group or Team site based on the Group#0
must already exist on the target before the
migration is allowed to be performed. The Group
or Team sites cannot be set to be cleared before
migration.
Modern team site without Microsoft 365 group ✔
(STS#3)
Publishing Portal (BLANKINTERNET#0, ✔ Some limitations are applicable
BLANKINTERNET#2, CMSPUBLISHING#0)
Point publishing sites ✖ Can be remapped.
(POINTPUBLISHINGHUB#0,
POINTPUBLISHINGPERSONAL#0,
POINTPUBLISHINGTOPIC#0)

Project Web App site (PWA#0) ✖ Can be remapped.

Record Center (OFFILE#1) ✔

Search Center (SRCHCEN#0, ✖ Can be remapped.

SRCHCENTERLITE#0,
SRCHCENTERLITE#1)
Content types

Advanced settings ✔

Column ✔

Column Order ✔

Document set settings ✔ The Document set setting to define default

content is not currently supported

On Demand Migration User Guide

SharePoint Migration 243
Object Support Notes

Name and description ✔

Column types of site, list, and content type

Choice ✔

Currency ✔

Date and time ✔

Hyperlink or picture ✔

Image ✔

Managed metadata ✔

Multiple lines of text ✔

Number ✔

Person or group ✔

Single line of text ✔

Yes/No ✔
List and libraries

Advanced settings ✔
l Folders
l Search
l Offline client availability
l List experience
l List attachments
l List item-level permissions
l List index non-default views
l Library Document Templates

Audience targeting settings ✔ Only Classic audience targeting is supported for

document libraries.
List alerts ✔

List columns ✔

List content types ✔

l New content type button order
l Default content type

List name, description and navigation ✔

List permissions ✔

List views ✔

On Demand Migration User Guide

SharePoint Migration 244
Object Support Notes

Modern list comments ✔

Pages libraries ✔

Validation settings ✔

Version history of documents (optional) ✔ Version history transfer means a significant

increase in migration time.
Version history of list items (optional) ✔

Version settings ✔
List templates

Announcements ✔

Contacts ✔

Custom list ✔

Custom list in data sheet view ✔

Discussion board ✔

Document Library ✔

Events and Calendar ✔

Issue tracking ✔

Links ✔

Picture library ✔

Promoted links ✔

Tasks ✔

Tasks with timeline and hierarchy ✔

Wiki page library ✔

Folder

Properties ✔

Folder permissions ✔
List item

Alerts on list items ✔

Attachments ✔

Authorship properties ✔
l Created date
l Created by
l Last modified data
l Last modified by

On Demand Migration User Guide

SharePoint Migration 245
Object Support Notes

Column data ✔

List item permissions ✔

Document

Alerts on documents ✔

Authorship properties ✔
l Created date
l Created by
l Last modified data
l Last modified by

Document ID service feature ✔

Document permissions ✔

Document properties ✔
Site pages

Modern site pages ✔

Classic pages ✔
Web Parts
Supported web parts have been verified to ensure all links and references to SharePoint entities are updated
during migration as required. Unverified web parts are migrated as is to the target tenant, links and references to
other SharePoint entities may remain linked to the entities on the source.

Modern web parts partial Supported web parts

Bing Maps Hero Quick Chart
Highlighted
Button Quick links
content
Recent
Call to action Image
documents
Code Snippet Image gallery Site activity
Kindle instant
Countdown Timer Sites
Preview
Divider Link Spacer
Document Library List Text
Embed List properties Twitter
Events Markdown Weather
File viewer News World Clock
Page
Group Calendar YouTube
Properties
People

Unsupported
web parts
Microsoft Organization
Conversations
Power Apps Chart

On Demand Migration User Guide

SharePoint Migration 246
Object Support Notes

Highlights My Feed Planner

Office 365
Microsoft Forms Power BI
Connectors
Saved for
Later

Classic web parts partial Supported web parts

About the Get started with
Page Viewer
community your site
Picture Library
Blog Archives Image Viewer
Slideshow
Blog Project
Join Community
Notifications Summary
Blog Tools Library Site Feed
Community
List Site Users
Tools
What's
Content Editor My Membership
happening

Unsupported
web parts
Media and Social
Business Data
Content Collaboration
category
category category
Content
Rollup Search category
category
Filters Server-driven
category content category

Custom web parts ✔

Workflow and Forms

Microsoft InfoPath Forms ✔ Migrating 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. For more information
see Migrating Record Center Retention Policies
and InfoPath Forms.

Microsoft Forms ✖

Nintex Classic Forms, Responsive Forms, and ✖

workflows
SharePoint 2010 Workflows ✖ SharePoint 2010 workflows are no longer
supported in SharePoint Online.
SharePoint 2013 Workflow definitions and ✔ Migration is attempted on a best effort basis and
subscriptions it is recommended that you must review the
workflow definitions after the migration.

On Demand Migration User Guide

SharePoint Migration 247
Object Support Notes

Workflow instances ✖ Any references to in-progress or completed

workflows are not migrated
M365 security and compliance features

Legal Hold ✖

M365 Compliance Customer Lockbox ✖

Microsoft Information Protection policies and ✖

labels
Retention Labels ✖
Power Platform features

Power Apps ✖

Power Automate (Flow) ✖

Power Pages ✖

Power Virtual Agents ✖

Limitations
l Checked out status for files in document libraries is not migrated.
l Currently checked out documents are not migrated. The last checked in version of the document is
migrated. If the file has never been checked, no version of the file is migrated.
l Reputation Settings for Community site migration are not supported
l Reporting of offensive content setting for Community sites is not supported
l Private views and personal sites are not migrated.
l Maximum number of items that can be migrated in a single list or library is 1 million
l Classic web parts in classic wiki pages are not migrated. This may affect the home pages of older classic
team sites (STS#0) where the home.aspx page is built on a Wiki page.
l Assigned translators in Language settings for Communication site are not migrated
l Comments on modern site pages are not migrated
l Migration from an education tenant to another education tenant is not supported for education templates.
l Migration of verified web parts is a best effort. A warning event will be posted for any site pages where an
issue occurred while migrating web parts. The warning event will identify the web part and possible cause of
the problem. Please review the identified web parts on the site pages and correct as needed.
l OnDemand Migration for SharePoint migrates the content starting with the root site and then proceeds to
any sub-sites. As a result:
l Links to SharePoint lists, libraries and sub-sites that have not been migrated to the target will not be
added to the Quick Launch menu.
l Navigation links and links in web parts to SharePoint content in sub-sites cannot be updated if the
linked sub-site has not been migrated.

On Demand Migration User Guide

SharePoint Migration 248
 l Migration of the Master Page Gallery is not supported because active master pages cannot be updated or
overwritten during the migration. Custom master pages should be manually added to the Master Page
Gallery in the target tenant and set as the new master page.
l Some Pages library files like Home.aspx, About.aspx and PageNotFoundError.aspx, and the Welcome
Page setting cannot be migrated if the sites are built with the following features or templates. You must
manually move these files and reconfigure the Welcome page setting if necessary.
l The SharePoint Server Publishing Infrastructure site collection feature is activated in the source.
l The site is based on the Wiki site template.
l The site is based on Publishing Portal templates.
l Managed navigation is based on term sets. The term set setting for Managed Navigation for the Publishing
Portal is not migrated. The term set is set to the default on the target. You must manually update the term set
setting in the target tenant if the selected term set setting in the source is no longer the default.
l There could be duplication in navigation links because links are managed from the site UI and from a
Publishing Portal specific Navigation site setting.
l Hub settings for sites located in non-central regions of a multi-geo tenant cannot be migrated. The hub
and spoke relationship for sites in non-central regions must be built manually after the site migrations
are complete.

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

Considerations
Your target tenant might already host SharePoint sites (site collections) or sub-sites created before the migration.
See the table below to see the migration action that will be used depending on the existing site properties and the
selected migration options.

Target site (sub- Clear existing site collection Migration action

site) exists option is selected

Yes No Merge, all supported properties will be

overwritten using source settings
Yes Yes Create and migrate
No - Create and migrate

Merging and remigration considerations

l Sub-sites based on unsupported site templates are skipped unless they are remapped.
l System settings including site columns, content types etc. from the source will overwrite settings that were
changed on the target.
l New site structure including list item and docs that only exist on the target remains unchanged.
l If a new list item with the same name is added on both source and target, the source item will be migrated
and added as a separate item (i.e. target will have two items with identical names).

On Demand Migration User Guide

SharePoint Migration 249
 l If a new document with the same name is added on both the source and target, the migration of the source
item will be skipped, and the warning that the item already exists on the target is reported. Document
libraries only allow one document per name.
l Conflict resolution setting on the List Options step of the New SharePoint Migration Task wizard controls
how list items and docs (same name and ID) that were previously migrated in this project are remigrated to
the target.
l Versions for remigrated List item and files will be removed and updated based on the settings selected in the
Version Options step of the New SharePoint Migration Task wizard

Prerequisites
l It is highly recommended to at least match all accounts in the project to ensure that membership and content
ownership are processed correctly.
l The target tenant should already have the fully configured SharePoint with the active license plan. Note, that
licenses are not automatically assigned to the target users during the migration.
l The following admin consents should be granted for SharePoint migration:
l Migration - Basic,
l Migration - SharePoint

In case necessary admin consents are not granted or expired, discovery will be disabled and the following
notification will be displayed: Grant admin consent to the Migration module on the Tenants page for both
source and target tenants: Basic and SharePoint. To grant admin consents open Tenants page and grant the
Consents and Permissions to allow the product to access the source tenant and the target tenant. You will be
redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start
discovering site collections.

Dashboard
The SharePoint migration dashboard presents quick links to help you prepare and migrate SharePoint content with
intuitive data points and key performance metrics.

On Demand Migration User Guide

SharePoint Migration 250
 TIP: Click Refresh Project to get the latest updates for the SharePoint workspace.

The dashboard sections are described below:

Notification panell - displays helpful information that may include links to manage the content migration
Dashboard Menu - contains links to the following actions:

l Discover site collections - starts the New Discovery Task wizard to collect information about SharePoint
sites in the source tenant. For more information see Discovering SharePoint Site Collections.
l Configure project - starts the Edit Project wizard for configuring migration defaults, SharePoint Admin
Center URLs and multi-geo settings. For more information see Configuring the migration Project.
l Refresh project - refreshes the SharePoint migration project settings.

Getting Started - presents quick start links to the various actions for preparing and migrating SharePoint content.
Global Term Store - indicates the status of the Term Store migration. You must migrate the Global Term Store
before you migrate SharePoint sites.

To migrate the Global Term Store:

On Demand Migration User Guide

SharePoint Migration 251
 1. Click Migrate Term Store from the Actions menu. The Migrate Term Store wizard opens.
2. Step 1: Notification
a. Send notification email once the task is completed - select this option to send a
notification email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task
fails to complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
3. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only
after you complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
4. Step 3: Summary
a. This step lists the following configured options for this task.
l Name - Specify a name for the task. The default name is Migrate Term Store.
l Source tenant - name of the source tenant.
l Scheduled start - expected start time of the task.
b. Click Back to change configurations if necessary or click Finish to save and start the task
as scheduled.

SharePoint site migration status - indicates the number of SharePoint sites being migrated with a color coded
status bar that indicates the migration count of the SharePoint sites.
Item Migration Progress - status count of SharePoint content that is discovered in the source tenant and migrated
to the target tenant. The following metrics are displayed:

l Discovered items on source

l Items selected for migration on source
l Migrated items on target

File Count (per hour) - performance chart that indicates the files migrated per hour.
Content migration (per hour) - performance chart that indicates the SharePoint items migrated per hour.

Configuring the Migration Project

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.

On Demand Migration User Guide

SharePoint Migration 252
3. Create a new project or open an existing project.
4. From the project Dashboard click Open in the SharePoint tile.

5. Click Configure Project on the SharePoint project dashboard menu. The Edit Project wizard starts
6. Step 1: Project Settings
a. Set Migration Defaults
Default Target User - Specify the default target user to use as the site collection owner when the
existing owner has no match in the target tenant. During the migration, On Demand Migration checks
whether accounts associated with the source site are matched with accounts in the target tenant.
Depending on the results, one of the following actions is performed:

SharePoint Matched owner found Matched owner Matched

Entity missing owner and
default
user
missing

Top-level sites Target account matched with source Default target user Migration
(site collection) owner Task fails
Sub sites System account System account

Lists System account System account

Folders Target account matched with source Default target user

owner

NOTE: Migrated list items and files will retain the source user metadata if the user has not
been matched with Accounts in the target tenant. This includes Created by, Modified by and
Person column metadata on list items and documents. The default target user is not used for
matching list items or files.

b. Set SharePoint Admin Center Urls

The SharePoint migration service builds the expected SharePoint Admin Center URL based on
SharePoint's default naming convention. If a customer has custom SharePoint Admin Center URLs,
these URLs should be set manually.
l Source SharePoint Admin Center Url - Enter the SharePoint Admin Center Url of the
source tenant.
l Target SharePoint Admin Center Url - Enter the SharePoint Admin Center Url of the target
tenant.

NOTE: On Demand Migration does not validate SharePoint Admin Center URLs. These
URLs are a subject of special request to Microsoft. Do not change the default URL if the
custom one is not yet approved by Microsoft.

c. Click Next.
7. Step 2: Multi-Geo settings
Migrated SharePoint sites can be mapped to geo locations in the target tenant with the Map Geo Location
Task. The task requires a CSV file that contains the mappings for the migrated sites. For more information

On Demand Migration User Guide

SharePoint Migration 253
 about the CSV file format see Mapping geo locations. You can control how the mapping in the target tenant
is determined by configuring the following settings:

a. When the SharePoint project is created a task (Name = Refresh Project) runs. The task determines
whether the target is enabled for geo location, and retrieves the set of active geo locations from the
target teanant.
l Default target geo location - choose a default geo location from the set of active geo
locations discovered in the target tenant.

NOTE: If a new geo location is added to the target tenant after the SharePoint project is
created, the task (Name = Refresh Project) must be rerun.

b. Choose an option for migrating sites to a multi-geo tenant.

l Use target geo location. If undefined use geo location of source site. Otherwise use
default target geo location - The Target Location column in the CSV file that is used for
geo mapping sites, will be used by the Map Geo Location Task to determine the geo
location of the migrated site in the target tenant. If the column value is blank or invalid, the
geo location of the site in the Source Location column will determine the geo location in
the target tenant. If the column value is blank or invalid, the Default target geo location
will be used.
l Use target geo location. If undefined use default target geo location - The Target
Location column in the CSV file that is used for geo mapping sites will be used by the Map
Geo Location Task to determine the geo location of the migrated site in the target tenant. If
the column value is blank or invalid, the Default target geo location will be used to
determine the geo location in the target tenant whether or not a geo location is specified for
the site in the Source Location column of the CSV file.
8. Click Finish.

Discovering Site Collections

The On Demand Migration for SharePoint service must have a reference list of all the site collections and sites that
can be migrated to the target tenant. There are two ways to discover the site collections in the source tenant:

l Discovering all site collections

l Discovering site collections from a file

NOTE: Before you begin, ensure the you have migrated all the accounts to the target tenant. At the
minimum, ensure that all SharePoint users are migrated. For more information see Account Migration.

Discovering all site collections

This is the simplest approach which uses the Discovery Task to inspect the source tenant and discover all the site
collections.

To start the Discover Site Collections 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.

On Demand Migration User Guide

SharePoint Migration 254
 3. Create a new project or open an existing project.
4. From the SharePoint tile on the project dashboard click Open. The SharePoint Dashboard opens.
5. Do one of the following:
l From the Dashboard menu, click Discover Sites > Discover All Sites.
l Click the SharePoint Contents tab. Then click Discover Sites > Discover All Sites.

The New Discovery Task wizard opens.

6. Step 1: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
7. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
8. Step 3: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. The default name is Discover Site Collections Task. You can
specify a custom name.
ii. Source tenant - name of the tenant where the site discovery occurs.
iii. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.
9. When the task completes, the SharePoint Contents list is updated. The Provision state of each site is set to
Discovered.

Discovering site collections from a file

When you want to migrate a few sites, you can run the discovery process by using a CSV file. The file contains the
site URLs and restricts the discovery of sites to the list of URLs provided in the CSV file. This is a two-step process:
Step 1: Preparing the CSV file
NOTE: CSV file names with non-ASCII characters are not supported. Using a CSV file provides the
following additional benefits:

On Demand Migration User Guide

SharePoint Migration 255
 l The CSV file could contain more columns. The extra columns are ignored. If there are multiple
columns with the headers URL, URI or SourceURL, all the columns will be processed.
l The URL could be either a relative URL or a URL with a fully qualified domain name. For the
root site (e.g. https://starzcorp.sharepoint.com) use "/" as the relative URL.
l The specified URL can be in upper, lower or mixed case. Case is ignored during discovery.

You can prepare the CSV file in two ways:

l 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. Edit the CSV file to list only the sites in the URL column that should be discovered. You can
either delete the other columns to maintain a cleaner list.
l Create a new CSV file
1. Enter the column header as URL or SourceURL. It is case insensitive.
2. Enter the URLs in the subsequent rows manually.

Step 2: Starting the discovery 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. Click theSharePointtile, or click Open from the SharePoint tile to open the SharePoint dashboard.
5. Do one of the following:
l From the SharePoint Dashboard menu click Discover Sites > Discover Sites from File.
l Click the SharePoint Contents and then click Discover Sites > Discover Sites from File.

The New Discovery Task wizard opens.

On Demand Migration User Guide

SharePoint Migration 256
 6. Step 1: Discovery Options
a. Click Browse and locate the CSV file that contains the site collections to be discovered.
b. Click Open in the File Explorer window to load the file into the wizard
c. Click Next.
7. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
8. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
9. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. The default name is Discover Site Collections Task. You can
specify a custom name.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.
10. When the task completes, the SharePoint Contents list is updated. The Provision state of each site is set to
Discovered.

Managing Sites with Collections

SharePoint site collections, sites and lists can be grouped in collections.
Migrating large numbers of SharePoint site collections requires careful planing. The site collections could belong to
different offices and geographical locations or sensitive departments. Organize the SharePoint site collections into
logical groups called collections to make large SharePoint site collections more manageable. SharePoint sites,
webs and lists can be grouped in collections.

On Demand Migration User Guide

SharePoint Migration 257
Working with the Collection Dashboard
The Collection Dashboard shows the collection-specific summary, allows you to see SharePoint site collections
added to it, create tasks for them, and monitor the progress of tasks.

l To view the collection dashboard for an existing collection

a. Log in to Quest On Demand and choose an organization if you have multiple organizations.
b. From the navigation pane, click Migration to open the My Projects list.
c. Create a new project or open an existing project.
d. From the project dashboard, click Open in the SharePoint tile to open the SharePoint workspace.
e. From the top-right corner of the workspace, click Select Collection and then select the collection to
view. The collection Dashboard is displayed.
f. Click the SharePoint Contents tab. You will see the list of SharePoint site collections that belong to
the collection.

l To see the tasks for collection-specific sites, use the corresponding tile on the collection Dashboard or open
the Tasks tab.
l To see the events related to the collection, use the corresponding widget on the collection Dashboard or
open the Events tab.
l To rename or delete the collection, click the corresponding buttons in the toolbar.
l To return to the project dashboard, click the project name in the navigation bar.

Adding SharePoint site collections to Collections

You can add SharePoint site collections to collections in three ways:

l Select the SharePoint site collections and create a new collection

l Select the SharePoint site collections and add to an existing collection.
l Use a CSV file to create one or more collections of SharePoint site collections.

To add selected SharePoint site collections to a new collection:

1. From the project dashboard, click Open in the SharePoint tile to open the SharePoint workspace.
2. Select the SharePoint Contents tab.
3. Select the SharePoint site collections you want to combine into a collection.
4. From the actions toolbar, click New Collection. The New Collection dialog opens.
5. Enter a collection name in the Collection name field and click Save to add the selected SharePoint site
collections to the collection.

To add selected SharePoint site collections to an existing collection:

On Demand Migration User Guide

SharePoint Migration 258
 1. From the project dashboard, click Open in the SharePoint tile to open the SharePoint workspace.
2. If you need to create a new collection:
a. From the top-right corner of the workspace, click Select Collection > + New Collection
b. Enter a collection name and click Save to add this collection to the project.
3. From the actions toolbar, click the SharePoint Contents tab and select the site collections that you want to
add to the collection.
4. Click More Actions > Add to Collection. The Add to existing collection dialog opens.

5. Select a collection from the Collection name dropdown and click Save to add the selected SharePoint sites
to the collection.

To create one or more collections with a CSV file:

This is a two-step process as described below:
Step 1: Prepare the CSV file
NOTE: CSV file names with non-ASCII characters are not supported. Using a CSV file provides the
following additional benefits:

l Multiple collections can be created with the same CSV file.

l Existing collections can be specified in the CSV file to add additional site collections
l SharePoint site collections can be listed in multiple collections

Use the format shown below:

SourceURL - site collection URL.

Collection - collection name.
Step 2: Import the CSV file

On Demand Migration User Guide

SharePoint Migration 259
 1. Click the SharePoint Contents tab.
2. From the actions toolbar, click More Actions and then click Import Collections. The Import Collections
from File dialog opens.
3. Click Browse and select the CSV file. The selected CSV file name appears.
4. Click Import.

NOTE: SharePoint site collection URLs in the CSV that have not been discovered cannot be added to the
collection.

To gather a site and all its children into a collection

1. From the top-right corner of the workspace, click Select Collection and then select the collection to view.
2. If needed, add one or more SharePoint site collections to the collection
3. Select one or more site collections.
4. Run the Discover SharePoint Contents task.

NOTE: SharePoint content discovered during a migration will be added to the collection as well if the parent
site collection is present .

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
a. Collect forms and workflow statistics - select this option to count the number of Infopath forms
and workflows associated with the selected sites.
b. Click Next.
9. Step 2: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.

On Demand Migration User Guide

SharePoint Migration 260
 l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
10. Step 3: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
11. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is Discover
SharePoint Contents Task.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. 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:
a. Clear any filters in the Filter panel
b. Set the Type filter to Site from the dropdown list. The list of sites and site collections are displayed.
c. Select a site by clicking the corresponding check box. The site details panel opens.

On Demand Migration User Guide

SharePoint Migration 261
d. 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.
l Type - SharePoint object type. Values are Site, Web, List, and Members.
l Name - name of the object type.
l Provision State - current state of the object. Values are Discovered, Matched, Provisioned
and Provisioned With Issues.
l Migration State - migration state of the object and its children. Values are:
l Not Migrated - migration has not started
l Discovered - SharePoint objects have been found in the source tenant.
l Matched - a SharePoint object in the source tenant has been matched with a
corresponding SharePoint object in the target tenant.
l Mapped - a site in the source tenant has been mapped to another site in the target
tenant. Source and target URLs are different.
l Provisioned - On Demand has created (updated) the SharePoint object (site, web,
list, users and groups) on the target without warnings or errors.
l Queued - waiting for service resources to be available. For more information, see
How Queuing Works.
l Migrating - migration is in progress
l Migration Failed - migration has failed.
l Migrated - migration is successful
l Migrated With Issues - this object or at least one child object had issues
with migration
l Partially Migrated - at least one child object has not been migrated

On Demand Migration User Guide

SharePoint Migration 262
 l 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
l Source Location - geo-location of the source object.
l Source Url - object url in the source tenant.
l Target Location - geo-location of the target object.
l Target Url - object url in the target tenant.
l Mapped to Different Url - Boolean to indicate if user has mapped the object to different url
on the target
l Template - SharePoint template used for the source object.
l Migration -
l 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.
l Site Language - default language of the source site.
l Hub - name of the hub group that the site belongs to if the source site is organized in a hub-
spoke relationship.
l Task Status - Status of the task that is working on this object. Values are New, Stopped, In
Progress, Failed, and Completed.
l Last Updated - most recent date and time when the object information was updated.
l Owner - owner account name
l Source Child Items - total of all the child lists and libraries in the site or web in the
source tenant.
l Target Child Items - total of all the child lists and libraries in the site or web in the
target tenant.
l Source InfoPath Forms - number of Infopath forms in the source tenant.
l Source SharePoint Workflows - number of workflows in the source tenant.
7. To view the contents for a specific content type:
a. Clear any filters in the Filter panel
b. 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:

l Mapping geo locations

l New Map Geo Location Task wizard

On Demand Migration User Guide

SharePoint Migration 263
 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.

Mapping geo locations

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:

l Source Url - column header for the urls of the site in the source tenant
l 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.
l 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
a. Click Browse and select the CSV file with the geo location mappings that you prepared.
8. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.

On Demand Migration User Guide

SharePoint Migration 264
 l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
9. Step 3: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. The default name is Map Geo Location. You can specify a
custom name.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Target tenant - name of the target tenant in this project.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Mapping Sites
By default, the OnDemand Migration for SharePoint service will migrate a site using the same relative url and name
as the source site. This step is particularly helpful when the source and target sites have different names or are
located at different places. You can also change the template of sites with unsupported templates. There are two
ways to map sites:

l Mapping a specific site from the UI

l Rename site and map url.
l Replace unsupported site template.
l Mapping one or more sites with a CSV file

A site cannot be mapped if it was previously migrated in the same project. See the Considerations topic for details
about migration behavior if the target site or sub-site that is mapped, already exists before the migration is started.

Mapping a specific site from the user interface

To change the name of a specific migrated site, relocate the site with a different Url or change an unsupported
template during migration, follow the steps described below.

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 view.

On Demand Migration User Guide

SharePoint Migration 265
6. Select a specific site and then click Map Site from the site detail pane.

7. The New Site Mapping Task wizard opens. Specify the information in the steps described below:
8. Step 1: Map Settings

On Demand Migration User Guide

SharePoint Migration 266
 a. Specify the new target site name and url :
l New Target Site Name - specify the new name of the target site (root website) if necessary,
or retain the original name.
l New Target Url - specify the relative url in the target tenant or retain the original value. You
can specify a different relative url in the target tenant to relocate the site if necessary.
b. Specify a supported target site template.
NOTE:
To find sites with unsupported site templates, clear the filters in the search ribbon. Then set
the following filters: Migration = Supported and Type = Sites
Template mapping is only available for unsupported templates. When you use a supported
template, the original site features may not be provisioned. However, supported lists and list
items can now be migrated to the target tenant.
Limitation: Sites with the "TeamsChanne#0" or "TeamsChanne#1" template cannot be
mapped to a different template. These TeamsChannel based sites are provisioned with the
ODM Teams provisioning task.

l New Target Site Template - choose a supported template. The options are:
Communication and Teams site (no Microsoft 365 group).
9. Step 2: Summary
a. Verify the task specifications as described below:
l Name - name of the task. The default name is Map Single SharePoint Object Task. You
can specify a custom name.
l New Target Site Name - new name of the target site (root website)
l New Target Url - the relative url in the target tenant.
l New Target Site Template - option to match sub-sites and other descendant structures.
b. 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 site. The Provision state of the selected site is set to Mapped.

Mapping one or more sites with a CSV file

To change the name of a migrated site or relocate the site with a different Url, 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: Sites cannot be merged or reorganized with a mapping file. Site templates cannot be changed with a
CSV file.

1. Download the CSV file from the SharePoint Admin Center

a. Log in to the SharePoint Admin Center of the source tenant.
b. From the navigation pane, click Active sites.
c. From the Active sites page menu, click Export to download the CSV file.

On Demand Migration User Guide

SharePoint Migration 267
 d. 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.
e. In the Source URL column keep only the sites that you want to map. Ensure that only relative
URLs are used.
f. Insert a blank column as the second column and specify the header as either TargetURL or Target
URL. This must be the second column.
g. Specify the corresponding target URLs. Ensure that only relative URLs are used.
2. Download the CSV file from the SharePoint Contents page
a. 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.
b. Click Export from the Actions ribbon.
c. Extract the CSV file from the downloaded ZIP file.
d. In the CSV file, delete all columns before the Source URL column. This must be the first column.
e. Insert a blank column as the second column and specify the header as either TargetURL or Target
URL. This must be the second column.
f. 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.
a. In the first column, specify the header as either SourceURL or Source URL.
b. In the second column, specify the header as either TargetURL or Target URL.
c. 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 from the source tenant.

l The URL /sites/StarzBrand has been renamed to /sites/StarzCorporate.

l The URL /sites/StarzAccounting has been renamed to /sites/StarzFinance.
l The URL /sites/Starzmarketing has been renamed to /sites/StarzMarketing.
l The URL /sites/Starzteam has been renamed to /sites/StarzTeam.

On Demand Migration User Guide

SharePoint Migration 268
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 sites 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.

On Demand Migration User Guide

SharePoint Migration 269
 7. Step 1: Mapping File
a. Click Browse and locate the CSV mapping file.
b. Click Open in the File Explorer window to load the file into the wizard
c. Click Next.
8. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
9. Step 3: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. The default name is Mapping from File Task. You can specify a
custom name.
ii. Source tenant - name of the tenant where the source URLs exist.
iii. Target tenant - name of the tenant where the target URLs may or may not exist.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. 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 Mapped.

Matching Sites
To check if the site already exists on the target or it is correctly mapped, match the source sites with the
corresponding target sites using a Matching Task. If a match is found the site state is set to Matched and the target
Url is updated. Discovered content for the selected sites can also be matched using the Include child site
structure setting in the New Matching Task wizard.
This step is optional. The SharePoint migration service will match and migrate the source site to the existing target
site (the target site and content will be replaced), or create the site as needed base on the default or site mapping.

To match sites:

On Demand Migration User Guide

SharePoint Migration 270
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 the SharePoint tile, 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 view.
6. Choose one or more sites by selecting the respective check box for the sites. You can select the check box
in the column header to select all sites.

7. Click Match from the Actions ribbon. The New Matching Task wizard opens.
8. Step 1: Matching Option
l SharePoint objects selected - indicates the number of sites selected for matching.
l Include child site structure - select this option to include matching discovered site content (webs
and other descendant objects) with the matching task. This will increase the task run time
significantly.
9. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

On Demand Migration User Guide

SharePoint Migration 271
 10. Step 3: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. The default name is Matching Task. You can specify a
custom name.
ii. Source tenant - name of the tenant where the source URLs exist.
iii. Target tenant - name of the tenant where the source URLs may or may not exist.
iv. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
v. Include site structure - option to match webs and other descendant objects.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.
11. You can track the progress in the Tasks tab, monitor alerts and notifications in the Events tab and view the
summary on the Dashboard.
12. 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 Webs
Webs or sub-sites that have not been migrated can be renamed, mapped to a different parent, or promoted to a site
in the target tenant. When these objects are migrated, they will be renamed, relocated to the new parent or
promoted to a site. The web is retained in the source tenant but set as Relocated (ie., not migratable)
The conditions for mapping a web to another web are as follows:

l Web has not been previously migrated.

l Web is not a root web.

If web is promoted to a site, then:

l Web must have a new name for the site.

l A new site and members object are cloned form the web's parent site.
l Web is cloned as the root web of the new site.
l Children of the web are re-parented under the cloned web.
l Migrate the new site to complete the migration of the promoted web

Example: Consider the promotion of a web (\sites\HR\Benefits) to a site (\sites\HR-Benefits). When the task
completes, the SharePoint Contents list will display the following:

Type Name Source URL Target URL

Site HR \sites\HR
Web HR \sites\HR
Site HR-Benefits \sites\HR \sites\HR-Benefit
Web HR-Benefits \sites\HR \sites\HR-Benefit

On Demand Migration User Guide

SharePoint Migration 272
Limitations

l Links from the source web may not be updated on target. For example, links to the old parent.
l For webs with unique SP Groups the groups may be duplicated.

To map a web

1. Open the SharePoint contents tab and locate the list. You can use the list filter Type = Web to narrow
down your search.
2. Select a web that has not been migrated. You can select only one web at a time. Then click Map Web from
the list detail pane.

3. The New Web Mapping Task wizard starts. Specify the information in the steps described below:
4. Step 1: Map Settings
a. Promote this web to a site collection - select this option to promote the web to a site. Webs with
unsupported templates cannot have the template remapped and be promoted to site, so this setting
will is displayed if the selected web has a supported template.
b. Specify the new name and relative url
l New Target Web Name - specify the new name of the target web if necessary, or retain the
original name if you want to relocate the web.
l New Target Url - Enter the new relative url of the web if you plan to relocate the web. This
option is not available if the web is promoted to a site.

On Demand Migration User Guide

SharePoint Migration 273
 c. Specify a supported target web template. This option is available if the selected site has an
unsupported template.
NOTE:
To find webs with unsupported web templates, clear the filters in the search ribbon. Then set
the following filters: Migration = Supported and Type = Web
When you use a supported template, the original web features may not be provisioned.
However, supported lists and list items can now be migrated to the target tenant.

d. New Target Web Template - choose Teams site (no Microsoft 365 group) from the dropdown.
e. Click Next.
5. Step 2: Summary
a. Verify the task specifications as described below:
l Name - name of the task. The default name is Map Single SharePoint Object Task. You
can specify a custom name.
l New Target Web Name - new name of the target web
l New Target Url - relative url of the site or web in the target tenant.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.
6. You can track the progress in the Tasks tab, monitor alerts and notifications in the Events tab and view the
summary on the Dashboard.
7. When the task completes, the SharePoint Contents list is updated. Compare the Source Urlcolumn with the
Target Url column for the selected web. The Provision state of the selected web is set to Mapped.

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

l The web in the target tenant must exist before the mapping otherwise mapping will fail.
l Previously migrated lists cannot be mapped to a different web.
l The source and target lists must have the same template type.
l The list mapping will be used by a migration task that includes the list.
l If lists are merged during migration, then
l List objects merged
l Content types
l List columns
l List Items (with permissions)
l List objects not merged
l List settings including Title and Description
l List Permissions

On Demand Migration User Guide

SharePoint Migration 274
 l Views
l Alerts

To map a list to a different site or web

1. Open the SharePoint Contents tab and locate the list. You can use the list filter Type = List to narrow down
your search.
2. Select a list that has not been migrated. You can select only one list at a time. Then click Map List from the
list detail pane.

3. The New List Mapping Task wizard starts. Specify the information in the steps described below:

On Demand Migration User Guide

SharePoint Migration 275
4. Step 1: Map Settings

a. Specify the new name and relative url

l New Target Url - Enter the new name of the list or retain the original name. You can specify
a different url in the target tenant to relocate the site if necessary.
b. Choose a the mapping option
l Migrate source list to target - select this option to migrate the contents of the source list to
the specified target list
l Merge source list contents with target list - select this option to merge the contents of the
source list with the specified target list.
c. Click Next.
5. Step 2: Summary
a. Verify the task specifications as described below:
l Name - name of the task. The default name is Map Single SharePoint Object Task. You
can specify a custom name.
l New Target Url - the relative url of the site or web in the target tenant.
l Map option - option to match sub-sites and other descendant structures.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.
6. You can track the progress in the Tasks tab, monitor alerts and notifications in the Events tab and view the
summary on the Dashboard.
7. When the task completes, the SharePoint Contents list is updated. Compare the Source Urlcolumn with the
Target Url column for the selected list. The Provision state of the selected list is set to Mapped.

On Demand Migration User Guide

SharePoint Migration 276
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 a granular or incremental migration. You can navigate
through SharePoint site objects and identify any site objects that failed to migrate.

Incremental migration
Incremental migration (or remigration) is typically used to synchronize and repair lists in the target tenant. When 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.

l All child lists can be repaired and refreshed during migration of sites and webs.
l Lists in the Migrated with Issues state will be repaired if the Refresh list items option is selected for the
migration task.
l Lists is in the Migrated state do not need to be repaired, and only an incremental migration will be done.

NOTE:The change token used by the migration service for incremental migration remains active for 60 days.
It is recommended to perform an incremental migration every 50 days to make sure the change token
remains active.
In this topic:

l Migrating Record Center Retention Policies and InfoPath Forms

l Starting a SharePoint migration task

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'

On Demand Migration User Guide

SharePoint Migration 277
 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:
l Token is stored in the SharePoint project
l 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.

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.

On Demand Migration User Guide

SharePoint Migration 278
 NOTES:

l 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.
l Creating and running multiple migration tasks at the same time may create a large load that may
trigger throttling in the Microsoft export interfaces.
l If the parent of the object selected for migration does not already exist on the target then the object
will not be migrated.
l Migration of a Group site collection will be skipped if the corresponding Group site collection does not
already exist at the target Url.
l 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

a. Choose a migration scope as described below:

l Migrate all - select this option to migrate the selected objects including any descendants or
content associated with these objects.

On Demand Migration User Guide

SharePoint Migration 279
 l 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.
l 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.
b. 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.
c. Click Next.
9. Step 2: Migration Options

a. Configure the migration options as described below:

l Default user account - Specify a default user account if the source user account cannot be
matched with a target user account.
l 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.
l 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.
b. Click Next.

On Demand Migration User Guide

SharePoint Migration 280
10. Step 3: Permission Options

a. Select how Sharing Links permissions are migrated. Direct permissions are always migrated.
l 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.
l 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.
l Do not migrate Sharing Links permissions - select this option to ignore Sharing Links
permissions.
l 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.
b. Click Next.
11. Step 4: List Options
This step applies to specific lists selected for migration from the SharePoint Contents list view.

On Demand Migration User Guide

SharePoint Migration 281
a. Choose from the following options to determine how changes to selected list items that were
previously migrated should be remigrated:
l Refresh list items - an incremental migration is performed to repair and update the target
list with missing or new items.
l Migrate all list items - all list items are remigrated.
b. Choose a conflict resolution option.
NOTE:
l Conflict resolution rules are applied only to lists that have been previously migrated.
l 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.
l Conflict resolution rules will not be applied to Site Pages and Site Assets system
libraries.

l Overwrite target files - all migrated files in the target tenant will be overwritten. Migration is
fastest with this option selected.
l 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.
l 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.
c. 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.

On Demand Migration User Guide

SharePoint Migration 282
 d. 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.
e. Click Next.
12. Step 5: Version Options

a. 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:
l Latest version only - This is the default selection. The most recent version of the file will be
migrated. All other versions will be ignored.
l 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.
l 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.
l 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

On Demand Migration User Guide

SharePoint Migration 283
 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.
l 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.
l 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.
l 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.
l 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.
b. Click Next.
13. Step 6: Notification
a. Send notification email once the task is completed - select this option to send a notification
email when a discovery task completes.
l Only in a case of failure - Select this option to send the email if the discovery task fails to
complete successfully.
b. Recipients - enter the email address of the recipients of this email. You can specify multiple
recipient email addresses separated by semicolon.
c. Click Next.
14. Step 7: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.

On Demand Migration User Guide

SharePoint Migration 284
 l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
l 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.
b. 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

a. This step lists the following configured options for this task.
l Name - Specify a name for the task. The default name is Migrate SharePoint
Contents Task.
l SharePoint objects selected - number of SharePoint objects selected for migration.
l Migration Scope - selected migration scope.
l 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.
l Default target user - UPN of the default target user if the source user cannot be matched to
a target user.
l Clear selected objects from target - whether or not the target site collection are deleted if it
exists is the target tenant.
l Upgrade classic team sites - whether or not classic team sites are migrated to modern
team sites.
l Migrate permissions - whether permissions are migrated or migrated objects will inherit
permissions from their parent.
l Migrate permissions only - whether or not permissions are migrated for previously
migrated webs and lists.
l Migrate Sharing Links permissions - how Sharing Links permissions are migrated.
l List migration - choice between migration of all list items or migration of incremental
changes with a refresh.
l Conflict Resolution migration action - how version conflicts are resolved. Indicates the
suffix if a copy of migrated list items are created.
l Migrate list and library comments - whether or not list and library comments should
be migrated.
l Migrate list item and document versions - version option selected.
l Scheduled start - expected start time of the task.

On Demand Migration User Guide

SharePoint Migration 285
 l Reporting - option to collect and retain data for report generation.
l Priority - the priority of this task.
b. Click Back to change configurations if necessary or click Finish to save and start the task
as scheduled.

Reviewing Migration Results

In this topic:

l About Provision and Migration states

l Review using the SharePoint Contents list view with filters
l Review using the SharePoint Content View
l Warning and errors

About Provision and Migration states

Use the Provision state and Migration state columns in the SharePoint Contents list view to determine the state
of any SharePoint object in the migration process.

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

State Description

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.
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 Provision state.

Provisioned On Demand has created (updated) the object with warnings or errors. See Warnings and errors.
with issues

Migration state
Use the Migration state property to track the progress of migrating the SharePoint object's content. Note that the
Migration 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 Migration state when the
provision 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

On Demand Migration User Guide

SharePoint Migration 286
 State Description

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 Provision and Migration states during migration
When migrating a site the web and list, the task state changes to Complete when the web or list provision 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 Migration state will not change to Migrated until the child content is migrated
When migrating a site or web, the Migration 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 Migration 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.

Reviewing results from the list view with filters

Once the migration task is complete, locate objects where Provision state = Provisioned with issues or
Migration state = Migrated with issues using a flat view of the objects and filtering.

To see all SharePoint objects in the SharePoint contents list view

l Remove the Type:Site filter.

To filter the list view to see all SharePoint objects with issues with provisioning

l Set the Provision state filter to Provisioned with Issues. You can filter further by setting a filter on an
object Type.

To filter the list view to see objects with issues with the migration

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

Review using the SharePoint content view

1. When the migration task is complete, locate objects in the SharePoint list view by setting the following filters:
l Provision state = Provisioned with issues
-or-
l Migration state = Migrated with issues

On Demand Migration User Guide

SharePoint Migration 287
 2. From the SharePoint contents tab
a. Select the object so the row is highlighted and the details pane opens to the right of the screen.
b. From the details pane click Show Contents
c. Continue following the webs into the site structure until you see
l an object where the Provision state = Provisioned with Issues, or
l a list where the Migration state = Migrated with Issues
d. From the details pane click Show Parent to return upward through the hierarchy.

Warnings and errors

To see the warnings and errors for a given object

From the SharePoint contents tab

1. Highlight the object to open the details pane on the right.

2. From the details pane click Events.

To see the number of list items on the source

From the SharePoint contents tab

1. Highlight the list object to see the details pane on the right.
2. The details pane provides a count of the number of the list items for this list on the source.

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.

On Demand Migration User Guide

SharePoint Migration 288
 8

Public Folders Migration

The Public Folders migration workflow consists of the following steps:

# Step

1 Create or open a migration project

2 Configure connections
3 Discover Public Folders
4 Migrate Public Folders
5 Monitor the progress and track issues

What We Migrate
All types of Public Folders (appointment, contact, journal, mail, note, task, and so on) can be migrated in case they
are supported in the target tenant.
Please consider the following migration specifics:

l If the public folder with the same path already exists on the target, the source public folder will not be
migrated. Check the Events tab.
l The first processed mailbox will be set as a primary for a public folder. Other mailboxes will be set as
secondary public folder mailboxes.
l Send As and Send on Behalf properties will only be transferred for mail-enabled Public Folders.
l Read and unread status is not migrated.

On Demand Migration User Guide

Public Folders Migration 289
Dashboard

From this dashboard you can:

l Keep track of your location within project and quickly return to the main project dashboard using
breadcrumbs on the top of the pane
l View list of discovered public folders with source and target paths, and last events related to the public folder
l Quickly navigate to the event lists
l Quickly navigate to the tasks list
l Create discovery tasks and public folder migration tasks
l Export feature data into comma-separated file
l Temporarily remove public folders from the migration project
l Search public folder
l Filter public folder by status, by matching state, or by mail settings
l Delete public folder

Prerequisites
Verify the following prerequisites before you start migrating Public Folders:

l Consents for the following permissions are granted for source and target tenants.
l Migration - Basic
l Mailbox Migration

On Demand Migration User Guide

Public Folders Migration 290
 If you want to verify or regrant consents for source and target tenants, see Consents and Permissions.
l Explicit credentials have been provided using Configure Connections.
l Target temporary Migration Manager account has Owner permission to the target public folder root.
l It is highly recommended to match / migrate all accounts in the corresponding migration project to ensure
that e folder permissions and account related mail settings will be migrated.

To configure connections:

1. Open the Dashboard tab from the Public Folders workspace

2. Click Configure Connections from the actions menu. The Configure Connections wizard for Public
Folders open.
3. Select any tenant that you want to reconfigure. Then click Edit and provide the necessary consents or
credentials.

Discovering Public Folders

Before proceeding with the migration, retrieve the list of public folders from the source tenant.

l Discovering all Public Folders

l Discovering Public Folders from a file
l Reviewing the Discover public folders task
l Reviewing the Discover public folders task events

TIP: If you want to rediscover public folders, rerun the existing discovery task.

Discovering all Public Folders

To create a new discovery task

1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic
experience or you are already on the public folder migration Dashboard, go to step 3.
2. Click Public Folders.
3. Click Discover Public Folders on the Dashboard. The New Discovery Task wizard starts.
4. Step 1: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.
l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.

On Demand Migration User Guide

Public Folders Migration 291
 5. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discovery Task.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

When the discovery task is complete, you will see the source tenant’s public folder summary on the Dashboard.

Discovering Public Folders from a file

When you have a large set of public folders but you want to migrate a subset of those public folders, you can start
the discovery process by using a CSV file. The CSV file lets you specify the public folders that you want to discover
and ignore the rest. This is a two-step process:
Step 1: Preparing the CSV file

1. Create a CSV file with the column title Source Path. Then enter the relative path of the folders that you want
to search. Some examples are shown below:

2. Save the CSV file with a suitable name.

Step 2: Starting the Discovery Task

1. Log in to Quest On Demand and choose an organization if you have 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 Public Folders from the project tiles, or click Open from the Public Folders tile to open the Public
Folders dashboard.
5. Click the Public Folders tab. Then click Discovery from the Actions menu and select Discover Public
Folders from File from the dropdown.
6. The New Discovery Task wizard opens.
7. Step 1: Discovery Options
a. Click Browse and select the CSV that contains the folder paths that you want to search.
b. Click Next.
8. Step 2: Schedule
a. Choose from one of three options to schedule the task. The scheduler will be activated only after you
complete the task wizard.

On Demand Migration User Guide

Public Folders Migration 292
 l Run now - task runs immediately.
l Run later - task must be started manually.
l Schedule - task will be started at a future date and time.
l Start - enter the start time for the task.
b. Click Next.
9. Step 4: Summary
a. Verify the task specifications as described below:
i. Name - name of the task. You can specify a custom name. The default name is
Discovery Task.
ii. Source tenant - name of the tenant where the statistics will be collected.
iii. Scheduled start - date and time when the task will start. Now indicates that the task will start
immediately.
b. Click Back to revise or review a previous step or click Finish to complete the task wizard and start
the task as scheduled.

Reviewing the Discovery Task

1. Select the Tasks tab.
2. Select the task that you want to review. The default name is Discovery Task.
3. In the task details pane that opens, the information presented is as described below:
a. Type - Type of the task. The type is Discover.
b. Created - Date and time when the task was created.
c. Modified - Date and time when the task was last updated.
d. Status - State of the task.
e. Last Operation - The action that was most recently performed in this task.
f. Schedule - Date and time when the task started. Now indicates that the task started immediately
after the task was created.
g. Events (number) - Number indicates the count of events that the task encountered. The values
indicate the type of the events and the event count for each type.

Reviewing the Discovery Task Events

1. Select the Tasks tab.
2. Select the task that you want to review.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events
for the selected task.
4. Select an event that you want to review. In the event details pane that opens, the information presented is as
described below:
a. Object - Name of the team or group discovered.
b. Task - Name of the task.
c. Time - Date and time when the event occurred.

On Demand Migration User Guide

Public Folders Migration 293
 d. Category - Type of task. the value is Application.
e. Source - Name of the On Demand Migration service

Removing Public Folders from the

Migration Project
You can temporarily remove any source public folders from the migration project, if necessary. Consider, public
folders cannot be removed permanently from the migration project, all existing source public folders will be added in
after next discovery.
To temporarily remove public folders from the migration project:

1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic
experience or you are already on the Public Folders migration Dashboard, go to step 3.
2. Click Public Folders widget.
3. Open Public Folders and select the items you want to remove from the migration project.
4. Click Delete
5. Click Delete to confirm the action.

Migrating Public Folders

CAUTION: Don’t start the migration before the discovery task is finished. It might result in incorrect
processing of migrated objects.
Make sure that all associated accounts are matched or migrated in account migration project and create the
Migration task:

1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic
experience or you are already on the public folder migration Dashboard, go to step 3.
2. Click Public Folders.

3. Open Public Folders and select the public folders you want to migrate.

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

4. Click Migrate.

5. Specify whether sub-folders will be migrated.

6. Specify whether public folder content will be migrated. You can clear this option for test migration to create
an empty public folder structure and transfer folder permissions.

7. Schedule when the task will be started. See for details.

8. 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. You can track its progress in the Tasks, view the summary on the Dashboard or
monitor alerts and notifications in the Events.

On Demand Migration User Guide

Public Folders Migration 294
 9

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

Featu Event Root Workaround

re cause

Micro Cannot Group Use the following PowerShell script and the group ID provided by the error
soft find the associ message to get the group name:
Team group ' ated
s {Group with
Migra ID}' on the Install-Module PowerShellGet -Force Install-Module -Name
tion the team ExchangeOnlineManagement
source. not $UserCredential = Get-Credential
Try to found Connect-ExchangeOnline -Credential $UserCredential
check Get-UnifiedGroup -Identity "b1552bc6-f932-4ac9-a4f2-
whether 24a5d2da2eed" | Format-List DisplayName,Id
the group
exists
using If this is a source group, fix your source data before proceed for migration.
PowerSh If this is a target group, check if this group exists in target. If this group exists,
ell cmdlet please contact our support. If this group doesn't exist, remove this group
'Get- associated team from target, and rerun provision and migration.
UnifiedGr
oup' as
describe
d in the
documen
tation

On Demand Migration User Guide

Troubleshooting 295
 10

Finalizing the Migration

Congratulations! The migration is complete.
If you have created a temporary Migration Manager account for the migration as described in the Consents and
Permissions topic, it is time to remove it because this account has elevated permissions and could pose
security risks.

Removing the temporary account from Teams

The temporary Migration Manager account added to all source and target teams respectively as members or
owners, can be removed. To remove the temporary Migration Manager account from the teams and groups use the
following script:

l Remove-Migration-Account-From-Teams

This script can be downloaded here: https://support.quest.com/on-demand-migration/kb/320327

IMPORTANT: To run this script, a user account with the Global Administratorrole is required for the source
tenant. For example, you can use the Tenant Administrator account.
Although the Remove-TeamUser command used in the script runs successfully, the Teams application
does not reflect the update immediately. The Teams application may need to be open for up to an hour
before changes are reflected.

On Demand Migration User Guide

Finalizing the Migration 296
 Appendix A: Working with
PowerShell
You can use the On Demand Migration (ODM) PowerShell module to interact with objects in your On Demand
Migration environment using PowerShell cmdlets. The cmdlets allow you to perform tasks, such as account
discovery, mail migration, OneDrive migration, task and event management in a PowerShell scripting environment.

Deploying the ODM PowerShell Module

The ODM PowerShell module must be requested from Quest and are not included with the ODM Subscription.
Loading the ODM module is the same as loading any other third-party PowerShell module. The module must be
loaded for each PowerShell session.

To enable the ODM PowerShell API:

1. Get the ODMApi.zip file from Quest Technical Support.

2. Unblock the file: Right-click the file > Properties > Unblock > OK.
3. Unzip the ODMApi to a folder on the local machine.
4. Start PowerShell (Run as administrator)
5. Set Powershell Execution Policy to unrestricted with the command set-executionpolicy
unrestricted
6. Install the ODMApi Module. For example, if your unzipped file is in the C:\OdmAPI folder, then use the
command: Import-Module C:\OdmAPI\OdmAPI -Global

Connecting to the ODM service

Before you can use the ODM PowerShell cmdlets to interact with your ODM environment, you must connect and
authenticate your access to your ODM host. The credentials you use must be granted a role with sufficient privileges
to work with the On Demand Migration services.

On Demand User Role Requirements

User must have the Migration Administrator role to access and run any of the On Demand Migration PowerShell
commands. On Demand ships with this role. See the On Demand Global Settings Current User Guide for more
information about setting up roles.

Authentication
The Microsoft Account Authentication Workflow requires user interaction for the initial authentication with Microsoft.
When Microsoft Account authentication is used all authentication is handled via Microsoft and the user’s Azure
Active Directory. This type of authentication supports MFA and is fully controlled by the user’s Azure Active
Directory Conditional Access Policies. Any password and lockout policies are also managed directly by the
customer through their Azure Active Directory.

On Demand Migration User Guide

Appendix A: Working with PowerShell 297
To connect to the ODM service
1. Run the following command to connect to your ODM Service. The default region is US.

Connect-OdmService

To connect to a specific region like Europe, run the command Connect-OdmService -Region EU. The
region value can be set in the OdmApi.psm1 file by editing this line: [string]$Region = 'us'. For
example to set default region to Europe replace the line to [string]$Region = 'EU'.

2. This command will redirect the user to the Microsoft Authentication workflow to authentication against the
user’s Azure Active Directory. In the authentication dialog, enter the credentials of the On Demand account
(not the tenant account)

If MFA is enforced, users will see an additional window

On Demand Migration User Guide

Appendix A: Working with PowerShell 298
Selecting the organization and migration project
Step 1: Get the organization id
1. Log in to Quest On Demand
2. From the Choose an organization page, note the organization id

- or, if you have already selected an organization -

1. Click the logged in user name from the top right corner of the page
2. Click the Organization Name from the drop-down to open the Edit Organization page. Then make a note of
the organization id

Step 2: Connect to the organization

In your PowerShell session console, enter the command

Select-OdmOrganization -OrganizationId '6a079d6e-e37a-475b-acba-8b08e9caa430'

Step 3: Select a migration project

Once connected to the Organisation, we need to connect to the Project, the project GUID is required, this is
obtained from the ODM GUI or running the command Get-ODMProject which will list all past and present projects
associated with the ODM organization, an example of this command is below:

Get-OdmProject | fl

Name : Source Corp ➜ Target Corp

Description : Excepteur sint occaecat
SourceTenantDefaultDomainName : sourcecorp.onmicrosoft.com
TargetTenantDefaultDomainName : targetcorp.onmicrosoft.com
Id : Elf813YBfQYAK6Q42Kun

Step 4: Connect to your project

Identify the project Id and connect to the project using the following command.

On Demand Migration User Guide

Appendix A: Working with PowerShell 299
Select-OdmProject 'Elf813YBfQYAK6Q42Kun'

On Demand Migration User Guide

Appendix A: Working with PowerShell 300
 About us
About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT
landscape. From database and systems management, to Active Directory and Microsoft 365 management, and
cyber-security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than
130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring
for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next
threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial
versions. You can access the Quest Support Portal at https://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a
day, 365 days a year. The Support Portal enables you to:

l Submit and manage a Service Request

l View Knowledge Base articles
l Sign up for product notifications
l Download software and technical documentation
l View how-to-videos
l Engage in community discussions
l Chat with support engineers online
l View services to assist you with your product

On Demand Migration User Guide

About us 301