Quest® 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

Quest® On Demand Migration

Administrator Guide

© 2020 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

Refer to 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 Administrator GuideUpdated - May 2020

https://www.quest.com/

https://www.quest.com/legal

https://www.quest.com/legal/trademark-information.aspx

Contents

About On Demand Migration 6

Before you Start 8Required Permissions 8Obtaining Impersonation Role for Mail Migration 9Assigning Roles Using PowerShell 10

Signing up for Quest On Demand 11Organizations and Regions 11Adding a Tenant 11Upgrading Throttling Policies 11

Working with On Demand Migration 13Test and Pilot Migrations 16Migration Project Management 17Project Dashboard 18Collection Dashboard 20

Task Management 21Task Scheduling 21Task Editing 21

Event Management 22Searching 23Filtering 24

Starting Migration Project 25

Configuring Connections 27Advanced Options 27

Sharing Availability Information 28

Collecting Account Information 29

Pre-Migration Assessment 30

Accounts Migration 31Account Migration Project Dashboard 33Granular Permissions 34Using Collections 35Populating Collections from File 35

Exporting Mapping for Selected Objects 36

OnDemandMigration Administrator Guide 3

Matching Accounts 36Using the Manual Mapping 37Clearing the Matches 38

Migrating Accounts 38Guest User Account Migration Considerations 39

Hybrid Account Migration 40Integration with Migration Manager for AD 41Deploying Migration Manager for Active Directory 41Configuring Hybrid 42Installing Hybrid Migration Service 43Matching Hybrid Accounts 43Clearing the Matches for Hybrid Accounts 44

Migrating Hybrid Accounts 44

Domain Coexistence 46Address Rewrite Service 46Address Rewriting Scenarios 49Provisioning the Address Rewrite Service 50Selecting Mailboxes for Address Rewriting 50Configuring SPF Record 51Enabling Address Rewriting 51Disabling Address Rewriting for Individual Mailboxes 51Disabling Address Rewriting 51

Mail Migration 53Deploying Client Update Agent 54Migrating Mailboxes 54Switching Clients 57Configuring Notifications for Mailbox Owners 58

OneDrive Migration 59Migrating OneDrive 60Sharing Permission Considerations 62Tracking OneDrive Migration 62

Resource Processing 63Processing Resources 63Processing SharePoint Online 64Processing Application Assignments 64

Public Folders Migration 66What We Migrate: Public Folders Migration 67


Public Folders Migration Dashboard 67Prerequisites 68Configuring Connections for Public Folders Migration 68Discovering Public Folders 69Removing Public Folders from the Migration Project 69Migrating Public Folders 70

SharePoint Online Migration 71What We Migrate 72SharePoint Online Migration Dashboard 76Prerequisites 77Discovering Sites 78Setting Migration Defaults 78Matching Sites 79Using the Manual Mapping for Sites 80

Exporting Site Collection Mapping 81Removing Sites from the Migration Project 81Migrating Sites 81

Microsoft Teams Migration 83What We Migrate: Microsoft Teams Migration 85Teams Migration Interface Walkthrough 89Prerequisites 90Discovering Teams 90Exporting Mapping for Teams 91Using Manual Mapping for Teams 91Pre-Migration Assessment for Teams 92Provisioning Teams for Target Tenant 93Migrating Microsoft Teams 94Migrating Associated Files 95Renamed Channel Migration 95

Troubleshooting 95

Finalizing the Migration 97

About us 98Technical support resources 98


About On Demand MigrationQuest® 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 Azure AD 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 feature

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

OneDrive for Business migration feature

l Analyze OneDrive for Business on your source tenant

l Transfer OneDrive for Business data and settings.

Content MigrationPublic Folders migration feature

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.

SharePoint migration feature

l Analyze SharePoint Online on your source tenant

l Map existing SharePoint Online sites (previously site collections) in the source and target tenants for further processing

l Migrate SharePoint Online sites (previously site collections) to the target tenant

l Provide robust SharePoint Online migration management interface and in-depth progress reporting.

Microsoft Teams migration feature

OnDemandMigration Administrator GuideAbout OnDemandMigration 6

l Analyze Microsoft Teams on your source tenant

l Create Office 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 Global Settings documentation.

OnDemandMigration Administrator GuideAbout OnDemandMigration 7

https://support.quest.com/technical-documents/on-demand-global-settings/current/

Before you StartTo access your Azure Active Directory or Office 365 tenant via On Demand Migration, use an Azure Administrative account that has the Global Administrator role.

TIP: Quest recommends creating a temporary account for On Demand Migration and use it to grant all consents for the migration project and for content migration features. Once the migration is finished, simply delete this account.

If you do not have such account, create it with Microsoft Azure administrative portal.This section provide you with the following information :

l permissions required to perform specific On Demand Migration tasks;

l accessing On Demand service;

l selecting your organization and region;

l adding your tenants;

l upgrading throttling policies to minimize Office 365 throttling impact to overall migration process.

Required PermissionsThis section lists the universal permissions for administrative accounts to perform main On Demand Migration tasks:

TIP: In case you want to make permissions more granular using minimum administrative permissions refer to Granular Permissions. This section provides minimum permissions for processes that can be performed using Accounts migration dashboard.

Task Minimal Permissions

Add tenant to On Demand

Global Administrator role for both source and target Azure AD administrative accounts. Refer to Adding a Tenant for details.

Configure tenant / grant admin consent

Global Administrator role for both source and target Azure AD administrative accounts. Refer to Adding a Tenant for details.

Discover accounts Granted “Migration - Basic” consent and Global Administrator role for both source and target Azure AD administrative accounts

Get statistics on Mailboxes

Global Administrator role for both source and target Azure AD administrative accounts

Enable calendar sharing

Global Administrator role for both source and target Azure AD administrative accounts

Migrate accounts Granted “Migration - Basic” consent and Global Administrator role for both source and target Azure AD administrative accounts

Migrate hybrid accounts

Granted “Migration - Basic” consent and Global Administrator role for both source and target Azure AD administrative accounts, on-premises administrative accounts with write permissions for ADAM / AD LDS server used by Quest Migration

OnDemandMigration Administrator GuideBefore you Start 8

Task Minimal Permissions

Manager, and all prerequisites specified in Deploying Migration Manager for Active Directory

Migrate mailboxes Granted “Migration - Basic” consent , Global Administrator role (with Office 365 mailbox and Impersonation Role in Exchange Online). To perform Autodiscover during mail migration an Office 365 mailbox is required. Refer to Obtaining Impersonation Role for Mail Migration for details.

Migrate OneDrive storages

Global Administrator role for both source and target Azure AD administrative accounts“Migration - Resource Processing for SharePoint” consent granted for source and target tenants.

Process Resource Roles

Granted “Migration - Basic” consent, Global Administrator role for both source and target Azure AD administrative accounts, User Access Administrator role for "Quest On Demand - Migration - General [Automation]"

Process source SharePoint Online (without migration)

Granted “Migration - Resource Processing for SharePoint Online” consent, turned on external sharing for SharePoint Online and Global Administrator role for both source and target Azure AD administrative accounts

Migrate SharePoint Online

Granted for source and target tenants:

l Migration - Basic

l Migration - Resource Processing for SharePoint,

The target tenant should already have the fully configured SharePoint Online with the active license plan. Refer to Prerequisites for details.

Process Application Assignments

Granted “Migration - Basic” consent and Global Administrator role for both source and target Azure AD administrative accounts. Refer to Adding a Tenant for details.

Migrate Microsoft Teams and Office 365 Groups with Teams functionality

Granted for source and target tenants:

l Migration - Basic

l Migration - Resource Processing for SharePoint

l Migration - Teams

Global Administrator roles and Teams licenses for both source and target Azure AD administrative accounts. Refer to Prerequisites for details.

Migrate Public Folders Granted for source and target tenants:

l Migration - Basic

Owner permission to the target public folder root for target Azure AD administrative account. Refer to Prerequisites for details.

Obtaining Impersonation Role for Mail MigrationMail migration requires Application Impersonation, so that knowledge of the users' credentials is not required. Impersonation role should be configured manually as described below:


1. Login to the Office 365 Exchange Admin Portal.

2. Go to permissions, then click “+” icon under admin roles to add a new role

3. In the Role Group dialog, provide a meaningful name and an optional description for your Role Group. For example, “Impersonation for migration”.

4. Click “+” icon under Roles, select ApplicationImpersonation and add it to the role group.

5. Click “+” icon under Members, select an administrative account that will perform the migration and add it to the role group.

6. Click Save.

NOTE: It may take some time before the changes are applied to take effect.

Assigning Roles Using PowerShellTo assign the required roles to an Azure AD administrative account you can use the PowerShell script as described below. You need to run this script as a Global Administrator for the tenant, for which you want to grant the necessary permissions.This command assigns all minimum required permissions to Azure AD administrative account [email protected]. You can specify only the minimum roles required for the processes that you want to perform. $serviceAccountUpn = "[email protected]" function AssignAzureAdRole($RoleName, $UserPrincipalName){ $role = Get-AzureADDirectoryRole | Where {$_.displayName -eq $RoleName} if (!$role) { $RoleTemplate = Get-AzureADDirectoryRoleTemplate | Where-Object {$_.DisplayName -eq $RoleName} $role = Enable-AzureADDirectoryRole -RoleTemplateId $RoleTemplate.ObjectId } if ((Get-AzureADDirectoryRoleMember -ObjectId $role.ObjectId).UserPrincipalName -notcontains $UserPrincipalName) { Add-AzureADDirectoryRoleMember -ObjectId $role.ObjectId -RefObjectId (Get-AzureADUser -Filter "userPrincipalName eq '$UserPrincipalName'").ObjectID }} function AssignExchangeRoles($RoleName, $UserPrincipalName, $Roles){ $group = Get-RoleGroup -Filter "Name -eq '$RoleName'" if (!$group) { $group = New-RoleGroup $RoleName } $group | Update-RoleGroupMember -Members $UserPrincipalName -Confirm:$false $Roles | ?{ $group.Roles -notcontains $_ } | %{ New-ManagementRoleAssignment -SecurityGroup $group.Id -Role $_ }} Import-Module AzureADImport-Module ExchangeOnlineManagement # Assign AzureAD rolesConnect-AzureAD


https://outlook.office365.com/ecp/

AssignAzureAdRole 'Guest Inviter' $serviceAccountUpnAssignAzureAdRole 'SharePoint Service Administrator' $serviceAccountUpn # Assign Exchange Online rolesConnect-ExchangeOnlineAssignExchangeRoles 'QuestODMServiceAccount' $serviceAccountUpn ( 'ApplicationImpersonation', 'Mail Recipients', 'Federated Sharing', 'Security Group Creation and Membership', 'Mail Recipient Creation', 'Transport Rules', 'Remote and Accepted Domains', 'Distribution Groups'

)

Signing up for Quest On DemandTo get access to On Demand Migration, you need to sign up for the Quest On Demand service. For that, 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.

Organizations and RegionsWhen you sign up for the On Demand service for the first time, you create an organization and you become the On Demand organization administrator. You can add additional organization administrators.For more information about managing your organization see Organizations and regions section in On Demand Global Settings User Guide.

Adding a TenantTo create your migration project, specify source and target tenants. For latest information on adding or removing tenants, please see the Tenant Management section in On Demand Global Settings User Guide.

Upgrading Throttling PoliciesIn order to minimize Office 365 throttling impact to migration and to raise the overall migration throughput, we highly recommend to upgrade your Office 365 tenant throttling policies. Please contact Microsoft support with


https://quest-on-demand.com/

http://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide/signing-up-for-quest-on-demand

http://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide/signing-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



https://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide

https://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide

http://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide/signing-up-for-quest-on-demand/organizations-and-regions

http://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide/tenant-management

the request to raise the limits for the following throttling parameters to 'Unlimited':

l EwsMaxBurst

l EwsRechargeRate

l EwsCutoffBalance

The upgrade can be done for the time of your migration only.


Working with On Demand MigrationThe On Demand Migration introduces a new Migration UI that provides high-level, intuitive project management for migrating accounts and content from one tenant to another. Now 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. Also now you can use new My Projects list view for the birds-eye view on all your migration projects.By default new Migration UI is now turned on. In case you prefer to use a classic user interface, turn off the new Migration UI by means of the slider in the top right corner of the main migration project Dashboard and return to the classic migration UI, to the project management interface and in-depth progress reporting you are used before.

OnDemandMigration Administrator GuideWorking with OnDemandMigration 13

New Migration UI: Basic migration workflow

# Step

1 Create Migration project. Step 1: Configure connections

2 Create Migration project. Step 2: Grant permissions

3 Create Migration project. Step 3: Finalize migration project creation to perform pre-migration assessment and discovery. The discovery task can now be started automatically.

4 Share free/busy information from users’ calendars

5 Organize accounts into collections

6 Match source accounts with the existing target accounts

7 Migrate accounts


# Step

8 Start Address Rewriting for Domain Coexistence

9 Migrate mail

10 Grant target users access to source tenant’s resources (resource processing)

11 Migrate OneDrive for Business storages

12 Migrate Microsoft Teams and Office 365 Groups with Teams functionality

13 Migrate SharePoint Online

14 Migrate Public Folders

15 Configure hybrid connections and enable Hybrid

16 Monitor the progress and track issues

Classic Migration UI: Basic migration workflowBasic migration workflow consists of the following steps:

# Step

1 Configure connections


# Step

2 Share free/busy information from users’ calendars

3 Perform pre-migration assessment

4 Organize accounts into collections

5 Match source accounts with the existing target accounts

6 Migrate accounts

7 Migrate mail

8 Grant target users access to source tenant’s resources (resource processing)

9 Migrate OneDrive for Business storages

10 Monitor the progress and track issues

11 Start Address Rewriting for Domain Coexistence

IMPORTANT: Quest recommends that any full scale migration should be preceded by test and pilot migrations to ensure that your migration tasks and procedures will accommodate the organization requirements.

Test and Pilot MigrationsAny 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."


Migration Project ManagementThe On Demand Migration introduces a new Migration UI that provides high-level, intuitive project management for migrating accounts and content from one tenant to another. Now 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. Also now you can use new My Projects list view for the birds-eye view on all your migration projects.By default, new Migration UI is now turned on. In case you prefer to use a classic user interface, turn off the new Migration UI by means of the slider in the top right corner of the Project Dashboard and return to the project management interface and in-depth progress reporting you are used before.

In case you use new Migration UI, for the birds-eye view on all your migration projects, go to My Projects. On the My Project list you can:

l View all migration projects that are already created for your organization

l Create new migration project

l Analyze migration project state and view robust statistics for account migration and content migration features for every migration project. Migration project features are available depending on your subscription.

l Open main migration project Dashboard using OPEN PROJECT link

l Quickly navigate to Dashboards for managing migration project features (Accounts, Mail, OneDrive, SharePoint Online, or Teams) using links above feature state widgets. Use breadcrumbs for return to main project Dashboard.

TIP: Click on you pair of tenants in the breadcrumbs for return to main project Dashboard.

l Delete migration projects. To delete migration project click control in the top right corner of migration project tile and select delete project. Consider, that all project data will be lost in case the project is deleted. This action cannot be undone.


CAUTION: Disable Address Rewrite Service, if enabled, in case you want to delete the migration project.

In case you use classic user interface, for the birds-eye view on your account migration project, go to account migration project Dashboard. Refer to the Account Migration project Dashboard in case you are using new Migration UI for details

Project DashboardNew Migration UI

All information about the migration project features is summarized on the main project Dashboard. The main Dashboard content depends on your subscription.

On the main migration dashboard you can:


https://support.quest.com/technical-documents/on-demand-global-settings/current/user-guide/settings

l Get started the migration project using Welcome widget

l Navigate to the following migration dashboards using widgets:

l Accounts and User Data migration ( including Mail migration and OneDrive migration)

l Public Folders migration

l SharePoint migration

l Teams migration

l Track the project flow in the Tasks widget.

l Monitor the migration process, detect, and troubleshoot the issues with the Events widget.

Account Migration dashboard in classic Migration UI

# Control

1 Breadcrumbs Keep track of your location within project and quickly return to the previous steps.

2 Menu Configure, manage, and control every aspect of the migration project. Match and migrate Azure AD accounts, process resources with Accounts, migrate mail with Mailboxes,migrate OneDrive for Business storages with OneDrive, monitor and troubleshoot the project with Events, and control the flow of the migration with Tasks.


# Control

3 Notification area Action items, alerts, tips, tricks, and other notifications are displayed in this area.

4 Action pane Set up and fine tune the migration with these commands.

5 Collection list View existing account collections and add new account collections. See Collection Dashboard for details

6 Getting Started widget

Don’t know where to start? Check our Quick Help.

7 Accounts widget See the summary on accounts and quickly navigate to the list of accounts

8 Mailboxes widget See the summary on mailboxes and quickly navigate to the list of mailboxes

9 OneDrive widget See the summary on OneDrive for Business storages and quickly navigate to the list of OneDrive users

10 Tasks widget See the status summary for the current migration flow and quickly navigate to all tasks

11 Errors widget See the summary on warnings and errors and quickly navigate to all migration events

12 Domain Coexistence widget

Start Address Rewrite Service, monitor the service and quickly navigate to the list of mailboxes that already have associated target pairs and can be added to the service. See Domain Coexistence for details

Collection DashboardThe migrated environment may be very big and complex. The accounts might belong to different offices and geographical locations. Some groups of employees, like top management, Finance or Legal divisions should be given special care when migrating. To make large environments more manageable, organize the accounts into collections. For details how to create collections and use them see Using Collections

Working with Collection DashboardA collection acts like “migration project within migration project”. The Collection Dashboard shows the collection-specific summary, allows you to see accounts added to it, create tasks for them, and monitor the progress for the selected subset of accounts.

l To see accounts included in the collection, click Browse Accounts or just open Accounts tab. You will get the list of accounts that belong to the collection.

l To see the tasks for collection-specific accounts, use the corresponding widget on the collection dashboard or open Tasks tab.

l To see the events related to the collection, use the corresponding widget on the collection dashboard or open Events tab.


l To rename, or delete the collection, click the corresponding buttons in the toolbar.

l To populate the collection with discovered accounts using comma-separated CSV, file click Fill from File. Refer to Using Collections for details.

l To return to the project dashboard, click the project name in the navigation bar.

Task ManagementFrom the Tasks list you can control the individual steps of the migration project:

l Track the task progress and view the results of finished tasks. Select a task to see a details pane in the right pane of the screen for the detailed information and statistics. Use search or filtering to quickly navigate through the list of tasks.

l Start, stop, and delete tasks.

l Edit tasks.

To optimize performance you can schedule start for all tasks as necessary. For details see Task Scheduling.

Task SchedulingTo 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 nowTo create and start the task automatically when the wizard is finished.

l Schedule To create and start the task automatically as scheduled.

l Run laterTo create and start the task manually.

Task EditingFrom the Tasks list you can edit previously created tasks to reuse them.The following scenarios are possible:

1. Editing of finished task.

2. Editing of running task

3. Editing of not started task

Finished task editingYou can edit finished task in case it is finished successfully or failed to reuse it. Please consider the following, depending on 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 start for changed task in case Schedule option is selected. All changes will be applied after the task is restarted.

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

Running task editingYou can edit running task to reuse or restart it. Please consider the following, depending on 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 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 undone this operation after the wizard is finished and reset the edited task to initial settings.

Not started task editingYou can edit task in case it is not started to change your settings. Please consider the following, depending on 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 undone this operation after the wizard is finished and reset the edited task to initial settings.

Event ManagementEvents 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. Refer to 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, statuses for batches that are processed will be reported approximately every 5 minutes.

SearchingThe lists of accounts, mailboxes, task or events might be very long and hard to manage. Use Search box above this list to look for items matching the certain 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.

Advanced Search

You can refine your results by using the advanced search operators. Refer to Lucene Tutorial for the full information on search syntax.

To search for

Operators Examples Result

Part of a word

*

*serv* Matches items containing "serv".

Exclude specified content

-, NOT (case-sensitive)

-mail* ( NOT mail*)

Excludes items that contain the word starting with “mail”.

Include specified

+ +mail* Matches items containing “mail” along with the basic search query.


http://www.lucenetutorial.com/lucene-query-syntax.html

To search for

Operators Examples Result

content

Multiple keywords

Space, OR (case-sensitive), AND (case-sensitive)

mail user, mail OR user, mail AND user

Matches items that contain either “mail” or “user” in case of OR. Matches items that contain both “mail” and “user”. in case of AND. This is the default search behavior for phrases.

Exact phrase

Quotation marks "item hard deleted"

Matches items that contain the exact phrase "item hard deleted".

Search by Date Range

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

FilteringYou can quickly filter out the certain items based on the predefined criteria. The applied filters are shown before the search box.

To apply a filter, simply click the desired facet on the left of the list. To clear it, click the close icon in the filter box.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.


Starting Migration ProjectSign in to Quest On Demand and create migration project:

To create migration project with new Migration UI

l On Migration click Create Migration Project

l On My Projects page, click New Project.

l In the New Project dialog select source and the target tenants added to your organization (see Adding a Tenant). Click Save and Continue.

l Provide Azure administrative account credentials for you source and for your target tenants. In case you skip this stage migration project will be created, but discovery task cannot be created automatically. In case you skip this stage, migration project will be created, but discovery task cannot be created automatically.

l Grant admin consent for your source and target tenants using Grant Permission... links. In case you skip this stage migration project will be created, but discovery task cannot be created automatically. Refer to Required Permissions for details.

l Click Finish and Close. In case all required data is provided discovery task will be started automatically.

NOTE: In case you switch to classic user Interface after creating new project with new Migration UI you will see that all types of migration project were created for the source and target tenant pair.

New migration project is now created. In can be opened automatically if Open project option is selected. Otherwise it can be opened from My Projects view by means of Open Project link on necessary project tile.

To create account migration project with classic Migration UI

l Select Migration and click Go.

l On Migration Projects page, click New Project.

l In the New Project dialog select the project type from drop-down list. It is recommended to start with account migration project, and then, after discovered accounts are matched or migrated, you can add other project types.

l In the New Project dialog select source and the target tenants added to your organization (see Adding a Tenant).

l Type in your project description and click Save.

Each migration project handles a single pair of source and target tenants. New migration project is now created. Click Go to configure the connections.

Classic Migration UI Project TypesAccount migration project type is a parent project for all other project types. All other project types use mapping created in account migration project. It is recommended to start with this project, and then, after discovered accounts are matched or migrated, you can add child projects you want to migrate the following:

OnDemandMigration Administrator GuideStartingMigration Project 25

https://quest-on-demand.com/

Classic Migration UI Project Type

Objects to Match/Migrate Features to Enable

Accounts Migration

Accounts, Groups, Mail Domain Coexistence for Address Rewrite, Resource processing, Calendar Sharing, Hybrid

SharePoint Online Migration

SharePoint Online sites (previously site collections) and related entities

Microsoft Teams Migration

Microsoft Teams, Office 365 Groups with Teams functionality, and related content

Public Folders Public Folders and related content

OnDemandMigration Administrator GuideStartingMigration Project 26

Configuring ConnectionsBefore proceeding with the migration, you should provide Azure AD administrative credentials for the source and the target tenants and grant consent for the application.In case you use new Migration UI all necessary connections were configured when you create migration project. You can re-comfigure connections from the account migration Dashboard, if necessary, as described below.

Configuring connections for source and for target tenants


1. Click Accounts

2. Click Configure Connections on the account migration Dashboard.

3. In the Configure Connections dialog select the tenant and click Edit. Provide or change administrator credentials, specify advanced options in case you want to limit the maximum number of PowerShell connections and/or specify EWS endpoint, and grant necessary permissions to allow the product to access the tenant. You will be redirected to the Microsoft web site for granting admin consent.

CAUTION: Do not exceed maximal number of concurrent PowerShell connections allowed for your organization to avoid throttling issues.

TIP: To increase the maximal number of allowed concurrent connections, if necessary, open a support ticket to Microsoft.

Once admin consent is granted, you can proceed.

NOTE: Consent status may automatically expire after 90 days. If you are not finished with the migration, grant consent again.

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

Advanced OptionsThe following advanced options can be configured for connections:

l 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 Office 365 quota is 3 open connections per user.

l Specify Custom EWS URL

Specify custom EWS endpoint for connecting to Exchange Web Services (EWS), in case you do not want to use EWS endpoint located by Autodiscover service automatically.

OnDemandMigration Administrator GuideConfiguring Connections 27

Sharing Availability InformationTo allow users retrieving each other's calendar free/busy information, create a relationship between the source and the target tenants. It can be easily done from On Demand Migration migration project management interface:

1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience, go to step 3.

2. Click Accounts to open account migration Dashboard

3. Click Enable Calendar Sharing and verify source and target domain names. Click Next to proceed.

4. Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.

5. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

OnDemandMigration Administrator GuideSharing Availability Information 28

Collecting Account InformationIn case you use new migration UI, accounts can be enumerated using automatic discovery after the migration project creation. This task also can be created or re-run, if necessary, to incorporate the latest changes.Before proceeding with the migration, enumerate all accounts and retrieve relevant information from the source tenant. The discovery collects all necessary account data and optional statistics on connected mailboxes for your source tenant to avoid misconfiguration and prevent possible issues.

CAUTION: Don’t start the migration before the discovery task is finished.

1. Click Discover Accounts on the dashboard to create a new discovery task.

2. To enrich the basic account information with details from Microsoft Office 365/Exchange Online, select Include statistics on mailboxes.

NOTE: Mailbox statistics discovery might be a lengthy process.

3. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.

TIP: Give informative names for the tasks. It will greatly simplify the project management and event filtering in the future.

4. Click Finish. A new widget appears on the project dashboard to show the task status.

5. Click the task name on the widget to see the details or use Show all link.

Once the discovery task is complete, you will see the source domain’s accounts summary on the project Dashboard and can perform Pre-Migration Assessment.

CAUTION: Don’t start the migration before the discovery task is finished. It might result in incorrect processing of migrated objects.

OnDemandMigration Administrator GuideCollecting Account Information 29

Pre-Migration AssessmentOn Demand Migration 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 on the discovered data.The following reports are available for Accounts:

l To clean up

l Disabled accounts

l Users with non expiring passwords

l To adjust

l Duplicate group names

l Duplicate user names

l Users without first name

l Users without last name

l Account statistics (inventory data)

l Number of users

l Number of groups

l User data

l External Accounts

l Tenant members

The following reports are available for Mailboxes:

l Mailbox statistics

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

l The users never logged on to mailbox

l Disabled users with mailbox

l To adjust

l Mailboxes with duplicate user name

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

OnDemandMigration Administrator GuidePre-Migration Assessment 30

Accounts MigrationOn Demand Migration can migrate discovered accounts and the following types of discovered groups:

l Security groups

l Mail-enabled security groups

l Distribution groups

l Azure AD Office 365 Group Type objects, the membership is supported for the accounts that have a pair on the target tenant. Email address for migrated Office 365 Group object will be created in default target domain. Refer to Microsoft Teams Migrationfor details on how to migrate Office 365 Groups with Teams functionality (associated with Teams)

NOTE: Migration of security groups with dynamic membership is not supported.

Basic account migration workflow consists of the following steps:

OnDemandMigration Administrator GuideAccountsMigration 31

# Step

Create collections to streamline the migration process


# Step

Match accounts / groups by attribute

Import mapping from file

Migrate accounts / groups

CAUTION: Do not delete matched or migrated accounts or groups from the migration project. If you need to do this anyway, clear the matching for those accounts.

NOTE: In all cases, target groups will be owned by the target Azure AD administrative account that is used to perform the migration.

Account Migration Project DashboardThis topic is intended for new migration UI. In case you are using classic migration UI refer to Project Dashboardfor details on Account migration project dashboard.

New Migration UI: Account Migration Dashboard

On the account migration dashboard you can:

l Organize the accounts into collections that act as “projects within project”. The collections allow you to structure big environments.

l Analyze your environment and find out the potential misconfiguration and problems that may adversely affect the migration.

l View all your accounts and user data (Mail, OneDrive), sort, reorder, search, and filter them.

l Start and manage Address Rewrite Service using Domain Coexistence widget to organize mail flow from selected source mailboxes as if the target mailbox is already used by sender.

l Configure and enable Hybrid Using Hybrid widget to migrate hybrid accounts.

NOTE: Address Rewrite Service requires additional subscription.

l Temporarily remove objects from the migration project

l Track the project flow in the Tasks list.

TIP: Give informative names for the tasks. It will simplify the project management and event filtering in the future.

l Monitor the migration process, detect, and troubleshoot the issues with the Events list.


List view for accounts migration

Granular PermissionsThis section lists the minimum permissions required for Azure AD Administrative accounts to perform specific On Demand Migration tasks. You can use PowerShell to assign these roles to your Azure AD administrative account. All of the listed roles are required, but you can select any of the roles separated by -OR-.

Product Feature Minimum Permissions for source Minimum Permissions for target

Exchange Online processing (Exchange Online license must be assigned)

Address Rewriting Transport RulesRemote and Accepted DomainsDistribution GroupsSecurity Group Creation and Membership

Transport RulesRemote and Accepted DomainsDistribution GroupsSecurity Group Creation and Membership

Calendar sharing Federated Sharing Federated Sharing

Discovery View-Only Recipients -OR- Mail Recipients

Account Migration View-Only Recipients -OR- Distribution Groups

Security Group Creation and MembershipMail Recipient Creation

Mail Migration ApplicationImpersonation Mail RecipientsApplicationImpersonation


Product Feature Minimum Permissions for source Minimum Permissions for target

Mailbox Switch Mail RecipientsApplicationImpersonation

Mail RecipientsApplicationImpersonation

Mailbox Permissions Migration Mail Recipients Mail Recipients

Azure AD Roles

Account Migration (guest users migration)

Guest inviter

Resource processing Guest inviter

SharePoint Online Roles (SharePoint Online license must be assigned)

OneDrive Migration (provisioning only)

SharePoint Online administrator

Using CollectionsThere are two approaches:

l You can select discovered accounts and create a new collection for them

l You can create a new empty collection and then populate it with discovered accounts using comma-separated CSV file.

To create a new collection based on selected accounts:

1. Click Accounts on necessary migration project

2. Select accounts you want to combine into the collection. You can use search for filtering out the accounts by certain criteria or simply hand-pick the individual accounts or mailboxes from the list.

3. Click +New Collection in the top right corner of the list view and enter the informative collection name. Click Save to add this collection to the project.

To create a new empty collection and then populate it with accounts:

1. On the Accounts migration dashboard click More Actions | Add To Collection.

2. Enter the informative collection name. Click Save to add this collection to the project.

3. Populate it using comma-separated values (CSV) file as specified in Populating Collections from File.

Populating Collections from FileYou can populate any existing collection using a comma-separated values (CSV) file with account attributes.


NOTES:

l CSV file can contain one or more columns. There are no special requirements for header names.

l One of column must contain case insensitive user principal name data that will be used for matching.

l File names with non-ASCII characters are not supported.

To populate collection from CSV file

1. Prepare a comma-separated values (CSV) file with data ofdiscovered accounts you want to add to the collection. File can contain accounts that have not been discovered, but these accounts won"t be added to the collection. One of the columns should contain the user principal names (UPNs). For example:

userPrincipalName,email,objectID

[email protected],[email protected],d6801a8b-5cb1-48f4-9757-4465564c5c63

2. Select a collection you want to populate on Dashboard and click it to open the Collection Dashboard

3. Click Fill from File to populate the collection with discovered objects you specified in the file created on Step 1.

4. Click Browse to open the comma-separated CSV file created on Step 1.

5. Browse for file and click Open. Selected file name appears next to the Browse button.

6. Click Populate to populate the collection.

The collection is populated. You can see added objects on the Collection Dashboard.

NOTE: The objects that do not exist in the source and/or target tenants and the source accounts that are not enumerated during the Discovery are ignored without producing an event.

Exporting Mapping for Selected ObjectsTo export the mapping as a comma-separated values (CSV) file, select objects in the grid and click More Actions | Export.You can customize this file and use it as a base for manual mapping.

Matching AccountsYour 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. To create Matching Task:

NOTE: Email address of existing object remains unchanged by default.


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 account migration Dashboard, go to step 3.

2. Click Accounts widget.

3. Click Accounts

4. Select the accounts you want to match and click Match Accounts.

TIP: Use search or collections to quickly navigate through the list of accounts.

5. Select Match by attributes. By default, you are matching the accounts using the attribute value. For example, identical display name or email address. You can also create more complex matching rules, for example using different attributes on source and target. Click Next to proceed.


7. Check the matching rule, scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

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

Using the Manual MappingIn some cases, the matching accounts attributes may differ. For example, it might happen when you have created some of the accounts manually as a part of initial migration to the new tenant. To handle such environments, you can provide a file with the custom mapping between source and target accounts.

1. Prepare a comma-separated values (CSV) file with the matched account pairs. The first row defines the names of the source and target attribute used for mapping. Subsequent rows list the matching values of the attributes (one pair per row.) For example:

<sourceAttributeName>,<targetAttributeName>

[email protected],[email protected]

[email protected],[email protected]

NOTES:

l Supported source attributes: userPrincipalName, objectId.




4. Open Accounts and click More Actions | Map from File. Do not select any accounts from the list – you have already specified them in the file created on Step 1.

5. Click Browse to open the mapping file created on Step 1.




8. Check selected options. Click Finish to save or start the task depending on schedule option selected.

The task is created. You can track the progress in the Tasks list or view the summary on the Dashboard.

NOTE:

l The account pairs that do not exist in the source and/or target tenants as well as the source accounts that are not enumerated during the Discovery are ignored without producing an event.

l If you import the mapping from file, an active collection, selected accounts, search, and filters are ignored. The matching is always performed for all pairs provided in the file.

Clearing the MatchesIn some cases, you might want to remove the mapping for individual accounts. It might happen when fixing the result of erroneous matching or fine-tuning the outcome of a previous task. To clear unwanted matches, create a special matching task.



3. Open Accounts and select the items for which you want to remove the mapping.

4. Click Match Accounts and select Clear existing matches option. Click Next to proceed.



NOTE: Once the task is complete, the matched accounts will revert to the New status and the matching is cleared for selected pairs.

You can see a task status on the Tasks screen. For more information refer to details panel in the bottom of the screen.

Migrating AccountsCAUTION: Don’t start the migration before the discovery task is finished.

When the matching is done, it is time to migrate source accounts that do not have the pairs on the target tenant. Create a new migration task:



3. Click Accounts.


4. Select accounts you want to migrate.

TIP: Use search, filtering or collections to quickly navigate through the list of accounts.

5. Click Migrate Accounts and provide vanity domain name instead of default *.onmicrosoft.com. Typically it is a domain name of your organization.

IMPORTANT: The custom domain name must be set up on the target tenant. See Quickstart: Add a custom domain name to Azure Active Directory for details.

6. Click Next to proceed.


8. Check selected options and name the task. 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.

IMPORTANT: On Demand Migration 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 Office 365 tools or third-party Single Sign On tools.

Guest User Account Migration Considerations

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

Before adding a guest user account to the migration task, please consider the following:

l Guest user account cannot be migrated in case an original account for this guest user account is already a member of the target tenant. It is recommended to use a matching task to pair these accounts, if necessary.

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.


https://docs.microsoft.com/en-us/azure/active-directory/add-custom-domain


Hybrid Account MigrationOn Demand Migration integrates with Quest Migration Manager to process on-premises users and groups synchronized with Azure AD (hybrid accounts).

NOTE: Migration of Dynamic Distribution groups is not supported.

Hybrid account migration to federated domain is supported. Consider, that cloud objects that are not synchronized with on-premises objects cannot be migrated to federated domain.

Use Hybrid widget on the dashboard to configure and monitor connections to your on-premises environment. Basic hybrid account migration workflow consists of the following steps:

# Step

Deploy Quest Migration Manager for Active Directory in case it is not already deployed

Download Quest Hybrid Migration Service and deploy it

OnDemandMigration Administrator GuideHybrid Account Migration 40

# Step

Download and install secret to integrate with Quest Migration Manager for Active Directory

Configure Hybrid connections for source and target on-premises environments

Enable Hybrid

Match hybrid accounts in case the target hybrid accounts exist

Migrate hybrid accounts

Integration with Migration Manager for ADBefore you start hybrid account migration make sure the Quest Migration Manager for Active Directory is already deployed as described in Deploying Migration Manager for Active Directory.

Deploying Migration Manager for Active DirectoryPrerequisites

l On-premises administrative account used for integration should have all required permissions specified in System Requirements and Access Rights document for administrative account and should have write permission to the project database.

IMPORTANT: Extended Active Directory schema with Exchange attributes in the target is required in case of target on-premises environment without Exchange Server.

l Quest Migration Manager version 8.14 with Product Update 20190218 or above.

l Windows PowerShell 2.0

l .Net Framework 2.0

Installation Requirements

1. When prompted, specify your name and company. Click Licenses to verify your license information in the dialog displayed: browse for a valid license file, and then click Close.


http://support.quest.com/technical-documents/preparing-migration/8.14/system-requirements-and-access-rights/accounts-required-for-migration-manager-operation

2. Next, on the Select Features step, select the Migration Manager for Active Directory only excluding all other components and sub-components.

3. On the next step, select Express option of the product installation scenario. Express means that setup will do the following:

l Installs all the components that are permitted by the license file.

l Installs all other required components, such as the AD LDS or ADAM instance, SQL Server, and the Directory Synchronization Agent.

l Configures default migration project.

Refer to Quest Migration Manager documentation for installation instructions and for system requirements and access rights required to for Quest Migration Manager.

CAUTION: Migration Manager installation should not be performed while some system updates are installed or configured.

Configuring Hybrid 1. Click Configure on Hybrid widget on Project Dashboard to open Configure Hybrid dialog.

2. Click Get Service button to download Quest Hybrid Migration Service and install it on the same machine where Quest Migration Manager is deployed.

3. Click Get secret button to download the secret for integrating On Demand Migration with Quest Migration Manager. The downloaded onpremservicekey.txt file should be moved to %CommonProgramFiles(x86)%\Aelita Shared\Migration Tools\Relay folder.If you suspect the secret is compromised, re-issue it through Configure Hybrid dialog. The previously issued secret will be immediately revoked and the hybrid connection will be suspended until you replace the file in %CommonProgramFiles(x86)%\Aelita Shared\Migration Tools\Relay folder.

NOTE: The same secret can be used for all migration projects created for one organization, provided that the Quest Hybrid Migration Service is installed on only one machine.

1. Click Next.

2. Provide the source Domain or Domain Controller FQDN and administrative account credentials for your source on-premises environment. Click Save to proceed.

3. Provide the target Domain or Domain Controller FQDN and administrative account credentials your target on-premises environment.

4. Configure advanced options, in case you have migration projects for more than one tenant pair. Provide the custom directory attributes (service attributes) for storing service information and conflict resolution. It is reasonable to specify only attributes that are not currently used in target environment. Refer to Service Attributes subsection of Quest Migration Manager documentation for more details. Click Save to proceed.

5. Click Next.

6. Select Turn On the hybrid migration option to enable Hybrid Migration for this migration project. Click Finish.

TIP: You can turn off hybrid whenever you no longer need it. On Demand Migration returns to usual cloud-only migration mode


https://support.quest.com/migration-manager-for-ad/8.14/technical-documents

http://support.quest.com/technical-documents/preparing-migration/8.14/installation-guide/

http://support.quest.com/technical-documents/preparing-migration/8.14/system-requirements-and-access-rights/

http://support.quest.com/technical-documents/preparing-migration/8.14/system-requirements-and-access-rights/

http://support.quest.com/technical-documents/migration-manager-for-ad/8.15/user-guide/pre-migration-activities/domain-pairs/configuring-a-domain-pair

7. Hybrid widget displays whether connections are configured and hybrid is enabled. If both status icons are green, run the discovery task to enumerate all hybrid users and groups.

Installing Hybrid Migration ServiceTo install Hybrid Migration Service, run the downloaded file.

1. Accept the license agreement. Click Next.

2. Provide the administrative account with write permissions for ADAM / AD LDS server used by Quest Migration Manager.

Matching Hybrid AccountsCAUTION:

l Don’t start the matching task before the discovery task is finished

l All hybrid account that were matched before hybrid is configured and enabled should be re-matched

Your target tenant might already contain accounts created for the source tenant users. You can map them to the corresponding source accounts to avoid duplication in the target. Create Matching Task:



3. Open Accounts.

4. Select the hybrid accounts you want to match and click Match Accounts.

TIP: Use search, filtering or collections to quickly navigate through the list of accounts. Environment filter help you to select users synchronized with Active Directory.

5. Select Match by attributes and select the source and target attributes. The following attributes are supported:

l displayName

l mail

l mailNickName

l immutableId

l employeeId

NOTE: The matching is performed by synchronized on-premises account attributes.

Click Next to proceed.



7. Check the matching rule, scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

The matching 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.When the task is finished, encrypted information about matching is written in the custom directory attributes (service attributes) of the target accounts. See Configuring Hybrid for details.

Clearing the Matches for Hybrid AccountsIn some cases, you might want to remove the mapping for individual accounts. It might happen when fixing the result of erroneous matching or fine-tuning the outcome of a previous task. To clear unwanted matches, create a special matching task.

1. Open Accounts and select the hybrid accounts for which you want to remove the mapping.

2. Click Match Accounts and select Clear existing matches option. Click Next to proceed.



NOTE: Once the task is complete, the matched accounts will revert to the New status and the matching is cleared for selected source and target hybrid account pairs.

You can see a task status on the Tasks screen. For more information refer to details panel in the bottom of the screen.When the task is finished, encrypted information about matching is removed from the custom directory attributes of selected target accounts. See Configuring Hybrid for details.

Migrating Hybrid AccountsCAUTION: Don’t start the migration before the discovery and matching tasks are finished.

When the hybrid is configured and enabled, it is time to migrate source users synchronized with Azure AD (hybrid accounts.) Create a new migration task:



3. Open Accounts.

4. Select the hybrid accounts you want to migrate. Make sure, the source user accounts are assigned valid licenses.

TIP: Use search, filtering or collections to quickly navigate through the list of accounts. Environment filter help you to select users synchronized with Active Directory.


5. Click Migrate Accounts and provide your domain name instead of default *.onmicrosoft.com, if necessary.

NOTE: The custom domain name must be set up on the target tenant. See Quickstart: Add a custom domain name to Azure Active Directory for details

6. Provide the distinguished name of on-premises target OU for migrated accounts, e.g., OU=SubOu,OU=Custom. By default, the container: CN=Users is used, but you can define a custom organizational unit.

NOTE:Target object will be moved in selected target OU even in case it resides in another target OU





IMPORTANT: On Demand Migration copies passwords of on-premises users synchronized with Azure AD to target on-premises OU during migration, but created objects will be blocked (sign-in not allowed). Incoming mail will be forwarded to mailbox on the source until mail migration is completed for the migrated hybrid user accounts.




Domain CoexistenceMergers and acquisitions are often accompanied by the unification of brands and corporate identities, including the unification of email addresses. However, the full transition from source to target tenant might take a considerable amount of time. To close this gap, On Demand Migration offers the domain coexistence services, 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 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. The outgoing mail addresses are substituted with the target ones, while all incoming mail is automatically redirected to the source mailbox. The address rewriting can be started once the account is matched or migrated, giving you time to prepare and migrate mailboxes without a rush. Address Rewrite Service requires additional licensing.

l Calendar Sharing allows users from the source and target tenants to see each other's free/busy information.

Address Rewrite ServiceAddress Rewrite Service substitutes the "From", "To" , and "Cc" addresses in the outgoing emails with the addresses from the target or source tenant depending on selected address rewriting scenario. All incoming mail is automatically redirected to the source or target mailbox according to specified mail forwarding direction. You can specify the users that are processed by the service, for example, only turn it on for Sales and Marketing team members. Address Rewrite Service requires additional licensing.

IMPORTANT: The service only works with accounts that have pairs in the target tenant. Mailbox provisioning is not required, mail users are also supported. Check the documentation on matching or migrating accounts.

Basic Address Rewriting workflow consists of the following steps:

OnDemandMigration Administrator GuideDomain Coexistence 46

# Step

Select Scenario for Address Rewriting

Provision Address Rewrite Service

Add mailboxes to address rewriting

Optionally: add Address Rewrite Service's IP address to the target DNS SPF record

Enable address rewriting. You can disable address rewriting at any time or turn off address rewriting for individual mailboxes

Address Rewrite Service Workflow

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 alike they was send from the unified mail domain according the selected settings. Address Rewrite Service will take all the necessary steps for creating this coexistence space in Exchange online environment including creating and managing all necessary connectors, mail flow rules, mail-enabled users and groups both in source and target environments, leaving on behalf of administrator only adding or removing source mail user to this coexistence space and activating / deactivating Address Rewrite Service.The basic mail message flow in domain coexistence with Address Rewrite Service looks like:Unified mail domain on the target tenant


1. When user sends an email as user@source domain mail user it redirected to Address Rewrite Service server in case it is addressed to the external recipients.

2. Address Rewrite Service receives email from user@source domain, check mail user eligibility to make address rewriting and then process it by rewriting @source mail domain to @target mail domain for every address of users added to coexistence space. These addresses in "From", "To" and "Cc" of the email message are rewritten for all external recipients. Then Address Rewrite Service pass the processed email message to target Exchange Online environment. Internal recipients that reside in source receive this email message with unchanged addresses.

3. Target Exchange Online sends message to external recipients as it was sent by user from @target mail domain, all addresses of users added to coexistence scope in "From", "To" and "Cc" are rewritten for external recipients.

4. External recipient doesn’t aware about @source and replies (or create a new email) to the @target mail user.

5. When the reply or a new mail arrives to target mail domain it will be forwarded to the source. Source recipient gets message as it was natively forwarded from target Exchange online environment from corresponding user@target email user

Unified mail domain on the source tenant

1. When user sends an email as user@target domain mail user, it redirected to Address Rewrite Service server in case it is addressed to the external recipients.

2. Address Rewrite Service receives email from user@target domain, check mail user eligibility to make address rewriting and then process it by rewriting @target mail domain to @source mail domain for every address of users added to coexistence space. These addresses in "From", "To" and "Cc" of the email message are rewritten for all external recipients. Then Address Rewrite Service pass the processed email message to source Exchange Online environment. Internal recipients that reside in source receive this email message with unchanged addresses.

3. Source Exchange Online sends message to external recipients as it was sent by user from @source mail domain, all addresses of users added to coexistence scope in "From", "To" and "Cc" are rewritten for external recipients.

4. External recipient doesn’t aware about @target and replies (or create a new email) to the @source mail user.

5. When the reply or a new mail arrives to target mail domain it will be forwarded to the target. Target recipient gets message as it was natively forwarded from source Exchange online environment from corresponding user@source mail user

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

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 Office 365 to the organization

l Outbound Quest Coexistence Connector helps control mail flow for Address Rewrite Service from the organization to Office 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 Office 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.

NOTE: Target mail-enabled users should be configured to redirect messages from target to the source mailbox. See Switching Clients for details.

Address Rewriting ScenariosAddress 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.

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.

Rewriting senders’ address to the target addressUse 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 Switching Clients for details.

Rewriting senders’ address to the source addressUse 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 Switching Clients for details.

Provisioning the Address Rewrite ServiceIMPORTANT: 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.

Selecting Mailboxes for Address Rewriting 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 account migration Dashboard, go to step 3.


3. Open Mailboxes tab or click Select in the Domain Coexistence widget.

TIP: To optimize the matching, migration and address rewriting, organize accounts into a collection.

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

5. Select the mailboxes and click Address Rewrite.

6. In Address Rewrite Management task, select Turn on address rewriting for selected mailboxes.

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.

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 RecordDuring 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. Refer to provider's documentation for instructions.

Enabling Address Rewriting 1. Make sure you have added the mailboxes to address rewriting. Click On in Address Rewrite facet to

show the joined mailboxes.

2. Go to the account migrationdashboard and click Enable Coexistence in Domain Coexistence widget.

Disabling Address Rewriting for Individual Mailboxes



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.

Disabling Address Rewriting 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 account migration Dashboard, go to step 3.


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: Disable Address Rewrite Service in case you want to delete the migration project.


Mail MigrationBasic mailbox migration workflow consists of the following steps:

# Step

Deploying Client Update Agent

Migrating Mailboxes

Configure mail forwarding from target to source

OnDemandMigration Administrator GuideMailMigration 53

# Step

Configure notifications for mailbox owners

Switch mailboxes

Deploying Client Update AgentOnce the migration is complete, Outlook clients should be redirected to the new Exchange Online. You can control this switch automatically through On Demand Migration console – all you have is to deploy a small utiltity called Client Update Agent to the end-user machines.

Downloading the Agent



3. Go to the accounts migration dashboard and click More Actions | Download Agent action.

4. Click Download.

IMPORTANT: The Client Update Agent package comes with the certificate for securing connections between the agent and On Demand Migration. If you suspect that the certificate might be compromised – download the package again, selecting Reissue the certificate option. The previously issued certificate will be immediately revoked.

Deploying the Agent

The Client Update Agent package comes with the agent’s executable that checks the migration status and performs the switching odmclient.exe and the certificate for securing connections between the agent and On Demand Migration certificate.pfx. Now you can automatically distribute then across all clients:

1. Deploy the certificate to all end-user machines with Group Policy.

See https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy for details.

2. Create a logon script for client computers.For detailed information on command-line parameters, refer to the document (readme.txt) that comes with the package.

Migrating MailboxesMake sure that all associated accounts are matched or migrated and create the Mail Migration task:


https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy

https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy



3. Open Mailboxes and select the mailboxes you want to migrate.

TIP: Use search, filtering or collections to quickly navigate through the list of mailboxes.

4. Click Migrate Mailboxes.

5. Select the active licensing plan with Exchange Online options that will be used on the target tenant. Re-run the discovery task to update available licensing plan data, if necessary.

6. Specify how the licenses will be assigned to the target users during the mailbox provisioning:

l Replace all license assignments with the licenses from the selected plan. Licensed users will be switched to the selected plan.

l Retain the existing licenses and assign the selected plan only to unlicensed accounts (default). Licensed users will retain the existing plans.

IMPORTANT: Consider the following:

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.

Selected licensing option is only applicable to Exchange Online. It does not affect the licensing plans picked for OneDrive Migration. Click Next.

7. Specify the migration scenario.

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.

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 re-run the Discovery task to update the information.

8. Specify which mailbox items (email, contacts, calendar appointments, recoverable items, tasks, and so on.) you want to transfer to the target.


CAUTION:

l Recoverable items, mailbox delegation, and folder permissions are not included by default, thus they are not transferred to the target. If you want to keep this data select corresponding option on this step.

l For all mailboxes that are migrated to the existing target mailboxes, On Demand Migration removes all the existing rules (OWA Inbox rules and the rules created in Outlook) from the target first (including previously-migrated rules), and then migrates all the rules from the source to the target.

Consider the following:

l Mailbox delegation permissions (Full Access, Send As, and Send On Behalf) can be transferred only in case the matched delegate exists on target. In case matched delegate does not exists, mailbox delegation cannot be migrated and an error will be reported. In case the target mailbox delegation is not set, the mailbox delegation will be transferred as is. In case the mailbox delegation as been set in target before the migration starts, rules and exceptions specified in Migrating Delegate Access Permissions section of On Demand Migration for Email User Guide are applicable to set mailbox delegation.

l Folder permission in case the target permission does not exist will be transferred as is. In case the folder permissions were already set in target before the migration starts, rules and exceptions specified in Migrating Folder Permissions section of On Demand Migration for Email User Guide are applicable to set folder permissions.

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

Click Next.

9. Specify which mail folders should be transferred during mail migration processing, if necessary. Click Next.

10. Limit the date range for content transfer. You can set any of the following options:

l Migrate mail before to set end date for the date range

l Migrate mail after to set start date for the date range

11. Schedule when the task will be started. See Task Scheduling for details.

12. 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 mail 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.

Mailbox Migration Considerations

l The following types of mailboxes are supported: Regular, Room, Equipment (Resource), Shared.

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. To achieve this, we automatically set up mail forwarding from target to source which works until the clients are switched to the target tenant.


http://support.quest.com/technical-documents/on-demand-migration-for-email/user-guide/configuring-and-running-migrations/selecting-migration-options/migrating-delegate-access-permissions

http://support.quest.com/technical-documents/on-demand-migration-for-email/user-guide/configuring-and-running-migrations/selecting-migration-options/migrating-folder-permissions

Switching ClientsThe mail migration is complete and you have deployed Client Update Agent in your on premises environment. Now it is time to switch the Outlook clients to the target Exchange Online.

NOTE: Client Update Agent may incorrectly switch the client profile during the transfer of the vanity domain name from the source tenant to the target tenant. It is not recommended to create a Mailbox Switch task during domain name transfers.

Create a Mailbox Switch Task:



3. Open Mailboxes.

4. Select the migrated mailboxes.

NOTE: Only migrated mailboxes can be switched. Use filtering by Completed status to see all migrated mailboxes.

5. Click Switch Mailboxes.

6. Specify mail forwarding direction:

l From source to target – standard switching scenario. The clients are automatically switched to the target tenant and all mail sent to the source addresses is forwarded to the target.

l From target to source – reverse scenario. The users are connected to the source tenant and all email sent to the target addresses are forwarded to the source.

TIP In case of Outlook 2013 usage, the external Autodiscover service is required for reverse scenario. You can use Microsoft Office Outlook Connectivity Tests (Office 365 tab) to check whether Service Connection Point (SCP) is available from the cloud. Otherwise the switch fails and the following message is returned by server: Autodiscover service returned: Unauthorized.

7. Provide the custom domain name for forwarding, typically your corporate domain name. Click Next.

IMPORTANT: The custom domain name must be set up on the target tenant. See Quickstart: Add a custom domain name to Azure Active Directory for details.

8. Configure notification messages (optional), if necessary. See Configuring Notifications for Mailbox Owners for details.



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


https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftestconnectivity.microsoft.com%2F&data=02%7C01%7CEkaterina.Burmistrova%40quest.com%7C3e917448419947d5a0d808d79827a324%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637145168327319848&sdata=6UgUGHf8tAcwKF4YwpYU%2B4A%2BC7B7DNUiUqpqt00vMk8%3D&reserved=0



Configuring Notifications for Mailbox OwnersOn Demand Migration allows to configure notification messages that appear after successful switch in:

l in new target mailboxes and / or in original source mailboxes (used now) in case you have selected Source to target mail forwarding direction on Mail Flow page

l in "new" (destination) source mailboxes and / or in original target mailboxes (used now) in case you selected Target to source mail forwarding direction on Mail Flow page

The following can be configured :

l Sender's email address - specifies email to replay (optional). In case no replay needed you can skip this field. In this case no email address will be displayed in the message.

l Send from: - specifies sender that will be displayed to user

l Subject: - specifies message subject

l Message: - specifies message text (plain text only)


OneDrive MigrationOnce the users are matched/migrated, you can transfer the content of their OneDrive for Business storages to the target tenant.

Before starting the OneDrive migration, consider the following:

l Migration may take a considerable amount of time, depending on the volume of data in storages. Some processes depends on actual Microsoft bandwidth.

l We only migrate files and folders present at the source OneDrive when the migration is started. Any changes made on the source during and after the migration are ignored.

l Re-migration overwrites all files in the target OneDrive. If OneDrive for Business sync client is already switched to the target tenant, all files will be re-synced, except for files, which target path is longer than 260 characters. Such files should be removed before restarting the migration to be updated. The existing copies of files stored on the local machines will be moved to the Recycle Bin.

OnDemandMigration Administrator GuideOneDriveMigration 59

l Migration of files, which target path is more than 400 characters is not currently supported. These files will be skipped.

l Only sharing permissions that are specified directly for accounts and groups that have matches on target are transferred. Refer to Sharing Permission Considerations for details.

l If a user or group is migrated and they have files shared with the group members, they will not be able to see them after migration. This functionality is not supported by Microsoft. The sharing can be restored manually after the migration is finished.

l Previous file versions are only migrated if their size is 80MB or less.

l Custom file properties (metadata) are not transferred to the target.

l Preferred data location (PDL) information is ignored for Multi-Geo tenant migration.

IMPORTANT: SharePoint system account will be set in Modified by information for all migrated content.

Migrating OneDriveMake sure that all associated accounts are matched or migrated and create the OneDrive Migration Task.



3. Open OneDrive and select accounts for which you want to migrate the storages.

4. Click Migrate OneDrive.

5. Select migration scope. The following migration options are available:

a. The latest version only (default)

b. The latest version and the previous version.

c. All versions

IMPORTANT: Previous file versions are only migrated if their size is 80MB or less. If the size of the specific version exceeds 80MB, that version is skipped.

6. Select file migration action to speed up the migration process. The following options are available:

l The source files that match the target files will be overwritten. This is only applicable to the migration scope selected above.

l Skip if the target file is the same version or newer

The source file that match the target file will be overwritten only in case the source file is newer than target one. This is only applicable to the migration scope selected above.

7. Select the migration action for file sharing permissions. The following options are available:

l Do not migrate permissions.

Sharing permissions for migrated content will not be transferred. Sharing permissions for the content that is not migrated under this task remain unchanged.


l Update permissions only for migrated content.

Sharing permissions for migrated content will be updated as specified in Sharing Permission Considerations. Sharing permissions for the content that is not migrated under this task remain unchanged.

l Update permissions for all content.

Sharing permissions for all content will be updated as specified in Sharing Permission Considerations.

8. Specify whether matched account will be displayed in Created by and Modified by properties of the migrated content. Consider that only properties related to matched / migrated users that have a mailbox with valid Microsoft Exchange Online license can be transferred. If there is no such users in target and the default target account is not set to be used instead, System Account will be displayed.

9. Pick the active OneDrive for Business licensing plan that will be used on target tenant. Re-run the discovery task to update available licensing plan data, if necessary.

10. Specify how the licenses will be assigned to the target users during the OneDrive for Business migration. Selected licensing option is only applicable to OneDrive migration. It does not affect the licensing plans picked for Exchange Online.

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.Click Next to proceed.

11. Specify which folders or files should be skipped during OneDrive migration processing. The following options are available:

l Exclude specific folders... : specify semicolon-separated list of fully qualified paths to folders 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...: specify semicolon-separated list of file extensions (case-incentive) to skip specified file types. If it is convenient for you, use spaces and dots, e.g., .exe; dll; BAT

l Exclude files created before: select the date to skip obsolete files, e.g., May 01, 2018

l Exclude files modified after: select the date to skip unnecessary files, e.g., July 01, 2018

l Exclude files bigger than (MB): skip very large files. The maximum value is 1000 MB; only integer values are supported.


13. Verify the current permissions that are necessary for completing the task and adjust them if necessary. Refer to Required Permissions for details.

14. Click Next. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts, details, and notifications in the Events.

TIP: From Events list you can quickly navigate to the originating OneDrive Migration task or affected object, who owns the OneDrive storage processed. Refer to Tracking OneDrive Migration for details.


Sharing Permission ConsiderationsSharing permissions can be transferred for Office 365 groups, security groups and user accounts that have matches on the target tenant. The sharing permissions of the groups and users that have no match on the target tenant will be ignored and related warnings are reported.In case any sharing permission will be removed on the source after the file or folder is migrated, the links to this file or folder are still visible in Shared with me and Shared by me views on OneDrive for Business Online, but the file or folder cannot be accessed.

NOTE:

l Group permissions are not displayed in Shared with me view because Microsoft currently does not support this functionality.

l For shared folders, only the top level folder is displayed in the folder tree.

For migrated files and folders that do not exist in target before migration, source permission will always be used. Consider the following specifics on how file sharing permissions will be handled for migrated files and folders that exist in target before migration:For users as permission holder (internal/external) and groups as permission holder (Office 365 group or security group) sharing permissions will be handled as follows:

l For files if Overwrite target files for selected migration... option is selected, source file sharing permission will be used.

l For files if Skip if the target file is the same version or newer option is selected, target file sharing permission will be used.

l For folders if Skip if the target file is the same version or newer or Overwrite target files for selected migration... option is selected, target sharing permission will be used as a base, any addition of permissions inside the source will be added onto the target.

For existing files and folders, the inherited permissions will follow the same rules.

Tracking OneDrive MigrationDepending on selected migration options, file size, and number of permissions, the content of OneDrive storages is transferred in separate batches that can be submitted for processing to Microsoft OneDrive at the same time. These batches will be processed concurrently, it can take a while before Microsoft OneDrive complete processing of submitted batches. To help tracking current status for every user, the following statistics events are currently supported:

l Aggregated statistics for batches that are processed will be reported every 5 minutes for every OneDrive storage selected for migration task. This events contain batch processing statistics and information on batch packages that are queued or processed by Microsoft OneDrive more than 30 minutes, if any.

l Batch package status is reported separately for all batches that are not transferred by Microsoft OneDrive in more than 30 minutes after submission. The status is retrieved for batches that are queued or processed by Microsoft more than 30 minutes only. Depending on Microsoft processing speed the status can be "Queued" or "Processing".


Resource ProcessingOnce the account migration is complete, you might want to grant target accounts access to source tenant’s resources and applications.Basic resource processing workflow consists of the following steps:

IMPORTANT: Resource processing does not copy resources to the target tenant. It simply provides the access to source resources by creating a linked guest user in the source for each migrated / matched target account. These 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.

Refer to the Processing Resources for step by step instruction how to configure resource processing.

Processing ResourcesOn Demand Migration can process the following resources on the source tenant:

l Microsoft SharePoint Online

l Resource roles related to selected accounts

l Applications assigned to selected accounts.

OnDemandMigration Administrator GuideResource Processing 63

To create a new processing task:



3. Select accounts for which you want to process the resources on Accounts tab.

4. Click Process Resources

5. Specify the affected resources:

a. Process SharePoint Online

Provide the root URL of the SharePoint site. Refer to Processing SharePoint Online for details on site configuration and required permissions.

b. Process resource roles

Process Role-Based Access Control (RBAC) roles for current Azure subscriprion.

c. Process application assignment

Refer to the Processing Application Assignments for details.




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

Processing SharePoint OnlineProcessing SharePoint online allows target users access sites, libraries, lists, and other content on the source tenant by creating a linked guest user in the source for each migrated / matched target account. Then the guest user is granted the same direct permissions as the corresponding source account to access source SharePoint resources. In order to process SharePoint Online resources, you must perform the following:

1. Turn on external sharing in SharePoint admin center. For details, see Turn external sharing on or off for SharePoint Online.

2. Grant consent for On Demand Migration to process SharePoint Online resources.

Refer to Required Permissions section for the minimal permissions required to perform this task.

Processing Application AssignmentsApplication assignments processing ensures that the target users see the same list of cloud applications on http://myapps.microsoft.com/ as their source counterparts. Refer to Processing Resources for more details.


https://support.office.com/en-us/article/turn-external-sharing-on-or-off-for-sharepoint-online-6288296a-b6b7-4ea4-b4ed-c297bf833e30

https://support.office.com/en-us/article/turn-external-sharing-on-or-off-for-sharepoint-online-6288296a-b6b7-4ea4-b4ed-c297bf833e30

http://myapps.microsoft.com/

NOTE: On Demand Migration assigns applications to the target users, but it’s up to each particular application how to check the access level. Some applications may have their own account databases and permission assignments, thus their access rights must be provisioned manually.

Refer to Required Permissions section for the minimum user account permissions required to perform this task.


Public Folders MigrationPublic Folders migration project help you migrating Public Folders from the source tenant to the target tenant. Basic Public Folders migration workflow consists of the following steps:

# Step

Create Public Folders migration project

Configure connections

Discover Public Folders

Migrate Public Folders

Monitor the progress and track issues

OnDemandMigration Administrator GuidePublic FoldersMigration 66

What We Migrate: Public Folders MigrationAll 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.

Public Folders Migration DashboardNew Migration UI

l Go to the migration project Dashboard in case you use new migration UI.


Using this new intuitive interface 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

PrerequisitesBefore you start Public Folders migration, make sure that:

l Target Azure AD administrative account has Owner permission to the target public folder root.

l TIt is highly recommended to match / migrate all accounts in the corresponding to ensure that e folder permissions and account related mail settings will be migrated.

Configuring Connections for Public Folders MigrationBefore proceeding with Public Folders migration, check Azure AD administrative credentials for the source and the target tenants and grant consent for the application. You can do this from the Tenants page or using the link in Configure Connections dialog.

IMPORTANT: Azure AD administrative accounts should have a mailbox with valid Microsoft Exchange Online license

In case you use new Migration UI all necessary connections were configured when you create migration project. You can re-comfigure connections from the account migration Dashboard, if necessary, as described below.

Configuring connections for source and for target tenants


1. Click Accounts

2. Click Configure Connections on the account migration Dashboard.

3. Select Source and click Edit. Verify source administrator credentials, change them, if necessary, and grant necessary permissions to allow the product to access the tenant. You will be redirected to the Microsoft web site for granting admin consent. Note, you should be logged as source administrative account to grant necessary permissions. Click Save.

The following permissions should be granted for the source tenant:

l Migration - Basic

l Migration - Mail Migration

4. Select Target and click Edit. Verify target administrator credentials, change them, if necessary, and grant necessary permissions to allow the product to access the tenant. You will be redirected to the Microsoft web site for granting admin consent. Note, you should be logged as target administrative account to grant necessary permissions. Click Save.


The following permissions should be granted for the target tenant:

l Migration - Basic

l Migration - Mail Migration

Discovering Public FoldersBefore proceeding with the migration, retrieve the list of public folders from the source tenant.

TIP: If you want to re-discover the public folders, simply re-run the existing discovery task.

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

3. Click Discover Public Folders on the Dashboard.


5. Check scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.


6. Click Finish. You can monitor the task status using task widget on project dashboard.


Once the discovery task is complete, you will see the source domain’s public folder summary on the Public Folders Migration Project Dashboard.


Removing Public Folders from the Migration ProjectYou 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.



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


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





SharePoint Online MigrationOn Demand Migration offers a fast and convenient way to transfer SharePoint Online content between Office 365 tenants. SharePoint migration functionality requires additional licensing.

IMPORTANT: Before migrating any SharePoint sites, you must ensure all affected accounts exist in the target tenant. In case you use classic product UI, Account Migration project for your source and target tenant should exists. Account matching /migration should be completed.

NOTE: SharePoint Online migration projects use the concepts and terminology of the Classic experience (site collections.) .

Getting Started widget on SharePoint migration Dashboard with Quick help helps you to prepare, start and perform all steps to migrate your SharePoint sites successfully.Basic SharePoint Online migration workflow consists of the following steps:

OnDemandMigration Administrator GuideSharePoint OnlineMigration 71

https://support.quest.com/technical-documents/on-demand-global-settings/user-guide/settings/subscriptions

https://support.office.com/en-us/article/sharepoint-classic-and-modern-experiences-5725c103-505d-4a6e-9350-300d3ec7d73f

# Step

Create SharePoint Online migration project

Set the migration defaults (optional)

Grant necessary permissions

Discover site collections (top-level sites) on the source tenant

Map source sites to the existing target sites by URL (optional)

Provide the custom site mapping using CSV file (optional)

Override migration defaults for specific migration tasks (if necessary)

Migrate site collections and their content


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 the account migration before starting SharePoint Online migration.

What We MigrateQuest On Demand migrates the following SharePoint content:

Supported Entity Supported Entity Properties

Site collections and sites(Modern experience: top-level sites and subsites)

l Title, description and logo

l Site collection owner

l Site collection admins

l Site collection feature activation NOTE: Active Site Collection on the source will activated on the target during migration but the impact of activating the feature may not be supported on the target.



l Site feature activation NOTE: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.

l People and groups

l Site permissions

l Regional settings

l Language settings

l SharePoint Designer settings

l Quick launch NOTE: Quick Launch links may be partially migrated. Links to SharePoint list, libraries and subsites that do not exist in the target will be broken.

l Top navigation NOTE:Top navigation links may be partially migrated. Links to SharePoint list, libraries and subsites that do not exist in the target will be broken.

l Navigation elements

l Site columns

l Site content types

l List templates

l Subsites

l Lists and Libraries

Site templates l O365 group site (Group#0). Some limitations are applicable

l Modern team site – no O365 group (STS#3, SPSMSITEHOST#0)

l Classic team site (STS#0)

Content types l Name and description

l Advanced settings

l Document set settings NOTE: The Document set setting to define default content is not currently supported

l Column

l Column Order

Column types of site, list, and content type

l Single line of text

l Multiple lines of text

l Choice

l Number



l Currency

l Date and time

l Yes/no

l Person or group

l Hyperlink or picture

List and libraries l List name, description and navigation

l Version settings

l 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

l Validation settings

l Audience targeting settings NOTE: Only Classic audience targeting is supported for document libraries.

l List permissions

l List content types

l New content type button order

l Default content type

l List columns

l List views

l List alerts

List templates l Generic list

l Document Library

l Announcements

l Events/Calendar

l Contacts

l Discussion board

l Links



l Picture library

l Issue tracking

l Tasks

l Tasks with timeline and hierarchy

Folder l Properties

l Folder permissions

List item l Authorship properties

l Created date

l Created by

l Last modified data

l Last modified by

l Column data

l List item permissions

l Attachments

Document l Authorship properties

l Created date

l Created by

l Last modified data

l Last modified by

l Document properties

l Document permissions

Limitations

l The default site language on the source and the target tenant should match.

l On Demand Migration only discovers site collections (top-level sites) based on the templates STS#0, Group#0, SPSMSITEHOST#0, and STS#3. NOTE: 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. Migration of site collections based on other templates is not supported.

l Private views and personal sites are not migrated.

l Change the look/Theme setting is not currently supported

l Only the latest versions of sites are migrated.

l Checked out status for files in document libraries is not migrated.


SharePoint Online Migration DashboardNew Migration UI



l View list of discovered site collection with last information, completed workflows, site collection information, and last events related to the site collection



l Create discovery tasks, matching tasks, and site collection migration tasks

l Export feature data into comma-separated file and use this file for manual mapping

l Temporarily remove sites from migration project

l Search site collection

l Filter site collection by workflow ,or by matching state

l Delete site collection


Classic user interface

# Control

Breadcrumbs Keep track of your location within project and quickly return to the previous steps.

Menu Configure, manage, and control every aspect of the SharePoint migration project. Match and migrate site collections, monitor and troubleshoot the project with Events, and control the flow of the migration with Tasks.

Notification area Action items, alerts, tips, tricks, and other notifications are displayed in this area.

Action pane Set up and fine tune the migration with these commands.

site (previously site collections) widget

See the summary on site (previously site collections) and quickly navigate to the list of site collections

Tasks widget See the status summary for the current migration flow and quickly navigate to all tasks

Errors widget See the summary on warnings and errors and quickly navigate to all migration events

Prerequisites l It is highly recommended to match / migrate all accounts in the corresponding to ensure that

membership and content ownership are processed correctly.


l The target tenant should already have the fully configured SharePoint Online with the active license plan. Note, that licenses are not automatically assigned to the target users during the migration.

l Consents already get granted for source and target tenants.The following admin consents should be granted for SharePoint Online migration feature:

l Migration - Basic,

l Migration - Resource Processing for 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 Process Resources for SharePoint. To grant admin consents open Tenants page and grant necessary 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.

Discovering SitesBefore proceeding with the migration, discover all site collections (top-level sites) in the source tenant. The discovery process enumerate all sites and retrieves the relevant data. Once the discovery task is complete, you will see the sites summary on the SharePoint Online Migration Project Dashboard and all sites will be shown in the Site Collections list.

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 SharePoint migration Dashboard, go to step 3.

2. Click SharePoint widget.

3. Click Discover Site Collections on the project dashboard to create a new discovery task.







Setting Migration DefaultsTo simplify the site migration, you can set a default site owner that will be used if the actual owner (user account) is not found in the target. See the details on user mapping below.

CAUTION: If both the actual owner account and the default owner are not found in the target, the migration task will fail.




3. Click Configure Project on the project dashboard.

4. In the Edit Project dialog, provide the user from the target tenant and click Save.

You can set a different default owner for a group of sites by overriding this setting in the migration task.

User Mapping Workflow

During the migration, On Demand Migration gets the accounts associated with the migrated (source) site and then looks up their pairs in the target tenant. Depending on the results, one of the following actions is performed:

l If a matched target user is found, On Demand Migration sets it as an owner of the migrated site.

l If a matched user is not found on target, On Demand Migration switches the site owner to the default account.

l If the actual owner account has no match on the target and the default owner is missing, the migration task fails.

This table describes how ownership is handled by On Demand Migration depending on the SharePoint entity:

SharePoint Online Entity

Matched owner found Matched owner missing

Matched owner and default user missing

Top-level sites (site colections)

Target account matched with source owner

Default target user Migration Task fails

Subsites System account System account

Lists System account System account

Folders Target account matched with source owner

Default target user

Files Target account matched with source owner

Default target user

List Items Target account matched with source owner

Default target user

Matching SitesYour target tenant might already host top-level sites (site collections) created before the migration. To ensure that no data is lost or duplicated, map them to the corresponding source site collections with the Matching Task:



3. Open Site Collections.

4. Select the site you want to match and click Match.


TIP: Use search to quickly navigate through the list of site collections.

5. By default, the matching is performed based on the URLs. Use manual mapping to match with a different criteria. Click Next to proceed.


7. Check selected options, scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

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

Using the Manual Mapping for SitesIn most cases, identical URL is good enough mapping criteria. However, the site naming / structure on the target might be different while the content is the same (for example, /sites/IS site is renamed to /sites/helpdesk.) To handle such differences, provide a file with the custom mapping between source and target site collections.

1. Prepare a comma-separated values (CSV) file with site collection pairs. The first row contains the name of the source and target attribute used for mapping (currently only URLs are supported.) Subsequent rows list value pairs for those attributes (one pair per row.) For example:

sourceURL,targetURL

/sites/tdemo,/sites/newsite

/sites/accounting,/sites/finance

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



4. Open Site Collections and click Map from File. Do not select anything from the list – you have already provided all required data in the file.

5. Click Browse to open the mapping file created on Step 1.





NOTE:

l If the site pair is not found (source, target or both sites are missing), it is ignored without producing an event. This might also happen if the source site exists, but was not enumerated during discovery.

l The matching is always performed for all pairs provided in the file. Any selection, search, and filters set in the interface are ignored.


Exporting Site Collection MappingTo export site collection mapping into comma-separated values (CSV) file for analytics or archival purposes open Site Collections 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 ProjectYou 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:



3. Open Site Collections and select the items you want to remove from the migration project.

4. Click More Actions | Delete

5. Click Delete to confirm the action.

Migrating SitesDouble-check that the account migration is finished (or at least that all SharePoint users are migrated) and create the Migration task:



3. Open Site Collections and select the items you want to migrate.

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

4. Click Migrate.

5. Provide the target account (FQDN) that will be used as the default owner (if the actual owner is not found.) The value set in the task is preferred over the project setting.By default, this filed is already populated with the default target user configured on the project level.

6. Specify whether child entities are migrated. By default, the entire collection stricture is migrated.

7. Specify whether the existing target sites are cleaned up (all exciting content removed) before migration.

CAUTION: If this option is selected, all content of the target site is removed and replaced by source site's content! Use with extreme caution.



TIP: It is recommended by Microsoft to schedule tasks to run overnight and on weekends to reduce the workload during business hours.


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. Events help you get relevant information in case the tasks are performed over a considerable period of time. ODM SharePoint migration processes are running if you see “Batch <x> in progress” event messages being logged approximately every 5 minutes.


Microsoft Teams MigrationOn Demand Migration for Teams securely migrates Microsoft Teams across Office 365 tenants. Microsoft Teams migration requires additional licensing.

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

Basic Microsoft Teams migration workflow consists of the following steps:

OnDemandMigration Administrator GuideMicrosoft TeamsMigration 83

https://support.quest.com/technical-documents/on-demand-global-settings/user-guide/settings/subscriptions

# Step

Create Microsoft Teams migration project

Grant necessary permissions in case these permissions are not already granted

Discover teams 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.

Export teams mapping to CSV file

Map teams manually using exported CSV fileYou 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.

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

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

l Target Azure AD account will be added to all target teams and Office 365 Groups as a member and owner.

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

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

l Target Azure AD account will own all private channels migrated to the target.

Automatically migrate associated filesAll files, associated with selected teams are transferred to the channels. If the channel do not exist, it will be provisioned.



What We Migrate: Microsoft Teams MigrationObjects and content types

Object Supported? Comments

Team owners and team members (creation Office 365 groups)

Only for accounts that are migrated / matched

Public channels

Private channels The Teams application will not reflect the updates immediately. The Teams application may need to be open for up to a 20 hours before changes are reflected due to Microsoft limitations.

Conversations

Associated SharePoint document libraries (Files)

Team picture

Timestamps

Team settings partially See Team settings section below

Guest accounts and conversations

Planner (including Planner tab app)

OneNote Before to start OneNote migration you should regrant Migration.Teams admin consent on Tenants.

Chats

Applications partially Planner, Word, Excel, and PowerPoint tab apps

Wiki sections and pages

Bots



Applications including Shifts for schedule management

Calendars

Mail

Formatted text

Authorship partially Authorship in messages is migrated as a string with author name and creation date

Link preview of public sites

User mentions

Mentions of Teams and channels

Images posted inline from buffer

Emojy, Teams GIFs, memes

Link preview of public images

Attached images, media files, documents

E-mail attachments

Code snippets

Meeting conversations

Meeting recordings

Files uploaded from mobile application:

Media files

Voice recordings



Documents

Rich card attachments:

vnd.microsoft.card.hero

vnd.microsoft.card.thumbnail

application/vnd.microsoft.card.adaptive

vnd.microsoft.card.animation

vnd.microsoft.card.audio

vnd.microsoft.card.video

vnd.microsoft.com.card.receipt

vnd.microsoft.com.card.signin

NOTE:If you re-run the migration, only new messages are processed. The modified messages are unchanged; deleted messages remain visible.

Team Settings

Category Setting Supported?

Team picture Team picture

Team description Team description

Member permissions Allow members to create and update channels

Member permissions Allow members to create private channels

Member permissions Allow members to delete and restore channels

Member permissions Allow members to add and remove apps


Category Setting Supported?

Member permissions Allow members to upload custom apps

Member permissions Allow members to create, update, and remove tabs

Member permissions Allow members to create, update, and remove connectors

Member permissions Give members the option to delete their messages

Member permissions Give members the option to edit their messages

Guest permissions Allow guests to create and update channels

Guest permissions Allow guests to delete channels

@mentions Show members the option to @team or @[team name] (this will send a notification to everyone on the team)

@mentions Give members the option to @channel or @[channel name]. This will notify everyone who's shown the mentioned channel in their channel lists.

Team code Team code

Fun stuff Enable Giphy for this team

Fun stuff Filter out inappropriate content using one of the setting below

Fun stuff Enable stickers and memes

Fun stuff Allow memes to be uploaded


Teams Migration Interface WalkthroughNew Migration UI



l View list of discovered teams with last information, completed workflows, team information, and last events related to the teams

l Switch to assessment view to track potential problems, misconfiguration, and risks that might adversely affect the migration



l Create discovery task, provision tasks, and teams migration tasks

l Export feature data into comma-separated file and use this file for manual mapping

l Search teams

l Filter teams by workflow, team state or size

l Select team to view details on the right pane. Refer to this pane for extended details related to the selected object .


Assessment View for Microsoft Teams

Refer to the Pre-Migration Assessment for Teams for the complete list of available reports.

PrerequisitesVerify the following requirements are met before starting the migration. If these actions are not performed, discovery, provision and migration tasks will fail or some data might be lost!

l Consents are already granted for source and target tenants.The following consents should be granted before Teams migration feature can be used

l Migration - Basic,

l Migration - Resource Processing for SharePoint,

l Migration - Teams.

TIP: If the admin 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, Process Resources for SharePoint, and Teams. Open Tenants page and grant the necessary 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.

l Azure AD administrative accounts should be granted Global Administrator role on the tenants for which these account are used.

l The source and the target Azure AD administrative accounts should have Teams license.

l Match and/or migrate the affected accounts in the migration project.

Discovering TeamsBefore proceeding with the migration, retrieve the list of teams from the source tenant.

CAUTION: Don’t start the migration before the discovery is finished. It might result in incorrect processing of migrated objects.


1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.

2. Click Teams widget.

3. Click Discover Teams on the project dashboard to create a new discovery task.






Once the discovery task is complete, you will see the source tenant’s teams summary on the Microsoft Teams Migration Project Dashboard.Discovery also checks the target tenant for potential conflicts (the identical team names on the source and target tenants.) The conflicting teams are marked with "Target team exists" in the Teams list. To see all conflicts, click Needs your attention on the left.The conflicts are resolved during the provisioning.

Exporting Mapping for TeamsTo export the teams mapping as a comma-separated values (CSV) file, select the required teams on the Teams tab on Teams migration Dashboard and click Export.You can customize this file and use it as a base for manual mapping.Exported data will contain source team name (may be team IDisntead), suggested target team name to provision and MailNickName MailNickName parameter specifies the alias for the associated Office 365 Group. This value will be used for the mail enabled object and will be used as PrimarySmtpAddress for this Office 365 Group. The value of the MailNickName parameter has to be unique across your tenant.

Using Manual Mapping for TeamsIn some cases, you might want to rename the teams on target or merge them with the existing teams with different names. To achieve this goal, provide a file with the custom mapping between source and target teams. You might use the exported team mapping as a template.

1. Export a comma-separated values (CSV) as described in Exporting Mapping for Teamsand edit it to prepare for manual mapping.


IMPORTANT: When editing a CSV file, the following should be considered:

l To ensure manual mapping will be completed successfully do not remove any columns from exported csv file.

l You can edit necessary entries, if necessary. In case any objects are added by mistake, please remove entire rows related to these objects.

l You can merge multiple source teams to a single target team. Just provide the same target team name in a mapping file.




4. Open Teams tab and click Map from File.Do not select any teams from the list – you have already specified them in the file created on Step 1.

5. Click Browse to open the mapping file prepared on Step 1.





Pre-Migration Assessment for TeamsOn 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 - 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.

Provisioning Teams for Target TenantAfter all source teams are discovered you can start to provision teams on the target tenant.Provision task help you to perform the following:

l Create Office 365 groups on the target tenant.

l Resolve naming conflicts.

l Provision teams to the target tenant.

l Provision team membership and ownership for provisioned teams.

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



3. Open Teams and select the teams to provision associated Office 365 group and teams on the target. Provisioned teams will be owned by target Azure AD administrative account. This account also will be added to the provisioned team as a member along with the members matched with source team members. In case any matched account cannot be found on the target, this account cannot be processed and related event will be reported.

TIP: Use search, filtering or collections to quickly navigate through the list of teams.

4. Click Provision.

5. Decide what to do if the team with the identical name already exists on the target. You have 3 options:

l Do nothing. Leave the target team as is.

l Merge to the existing target team. All users from the source team will be added to the target team during provision. Refer to Merging Considerations below for details of team channel naming after merge.

l Create a new team. A new team will be created on the target by appending the provided text to the original team name. For example, "HR - Migrated".

6. Select whether automatic Group Welcome Message will be suppressed to avoid disturbing users by automatic Microsoft messages about adding to the provisioned Teams .However, suppressing these messages results in performance degradation due to issues with Microsoft’s synchronization behavior. We recommend do not suppress these messages to avoid issues related to team synchronization. For teams provisioned by tasks created in previous releases, for which Group Welcome Messages were suppressed by default, these email messages may be received in some cases, depending on stage of processing by Microsoft.





Merging Considerations

If Merge to the existing target team option is selected in case of conflicting source and target team names the team on the source tenant will be merged into the team in the target tenant. All users from the source team will be added to the target team during provision. Refer to the Renaming and Merging Considerations subsection of Migrating Microsoft Teams for details on how to conflicting channel names are resolved during migration.

Migrating Microsoft Teams 1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using

classic experience or you are already on the Teams migration Dashboard, go to step 3.


3. Open Teams and select the teams with provisioned state you want to migrate. Migration will be skipped for all teams that are not yet provisioned

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

4. Click Migrate. Pay attention, files associated with the selected teams will be migrated as a separate System: Team Files Migration task, which will be created automatically when this task starts.

5. Select whether to migrate attachments. In case you do want to migrate any attachments, click Next

6. Select whether to migrate Word, Excel, and PowerPoint tab apps in the team channels. This option is selected by default.

7. Select whether to migrate Planner including all related content. This option is selected by default.

8. Select whether to migrate OneNote including all related content. This option is selected by default.

9. Select whether to merge reply message in threads in one combined message per thread to avoid throttling and improve performance. This option is selected by default.

NOTE:

l Combined reply will only show first one link preview if there are 2 or more link preview due to Microsoft limitation.

l Combined messages appear as Important if any reply in the thread is Important.



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


NOTE: Teams migration starts after completion of the associated automatic Team Files Migration task. It can take a while to migrate files depending on the total size.

Renaming and Merging Considerations

If the channel with the same name already exists on target, the source channel will be migrated to a new one with a name: <source team name> - migrated.

Unique channel names remains unchanged.

Migrating Associated FilesOn Demand Migration for Teams now migrates the files associated with migrated teams using System: Team Files Migration task. This task is created and completed automatically.For the full list of supported content refer to What We Migrate: Microsoft Teams Migration

Renamed Channel MigrationWhen a channel is renamed, Microsoft does not rename the corresponding SharePoint Document folder for this channel, this is a known issue. For example, when Channel “Channel_1” is renamed to “Channel_Renamed”, the folder name under the “Files” tab is still “Channel_1”. After migration is completed, all messages and files can be opened correctly. Consider, that these files cannot be displayed on the target Files tab. This is because all the files are still stored and migrated under ““Channel_1” folder. “Channel_Renamed” folder does not exist until you click the “Channel_Renamed” channel’s Files tab, then the system will generate an empty folder for it. But no files will be stored there. To avoid files and message association breaking it is not recommended to rename folders manually. If necessary, you can copy necessary files to “Channel_Renamed' folder, but these files won't associated with messages.

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


To find Task ID and Project ID Task ID and Project ID you can find in task details.

To find organization IDIf 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.


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

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

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

OnDemandMigration Administrator GuideFinalizing theMigration 97

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamuser?view=teams-ps

https://docs.microsoft.com/en-us/powershell/module/teams/remove-teamuser?view=teams-ps

About usAb o u t u s

Quest provides software solutions for the rapidly-changing world of enterprise IT. We help simplify the challenges caused by data explosion, cloud expansion, hybrid datacenters, security threats, nd regulatory requirements. We are a global provider to 130,000 companies across 100 countries, including 95% of the Fortune 500 and 90% of the Global 1000. Since 1987, we have built a portfolio of solutions that now includes database management, data protection, identity and access management, Microsoft platform management, and unified endpoint management. With Quest, organizations spend less time on IT administration and more time on business innovation. For more information, visit www.quest.com.

Technical support resourcesTechnical 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

OnDemandMigration Administrator GuideAbout us 98

https://www.quest.com/company/contact-us.aspx

https://support.quest.com/