Sign in to Quest On Demand and create migration project:
To create migration project with new Migration UI
|
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
Each migration project handles a single pair of source and target tenants.
New migration project is now created. Click Go to configure the connections.
Account 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:
Objects to Match/Migrate | Features to Enable | |
---|---|---|
Accounts Migration | Accounts, Groups, Mail | Domain Coexistence for Address Rewrite, Resource processing, Calendar Sharing, Hybrid |
SharePoint Migration | SharePoint 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 |
Before 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
|
TIP: Click on you pair of tenants in the breadcrumbs for return to main project Dashboard. |
|
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. |
The following advanced options can be configured for 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.
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.
To 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:
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy