Starting Migration Project
Sign in to Quest On Demand and create migration project:
To create migration project with new Migration UI
- On Migration click Create Migration Project
- On My Projects page, click New Project.
- In the New Project dialog select source and the target tenants added to your organization (see Adding a Tenant). Click Save and Continue.
- 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.
- 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.
- 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
- Select Migration and click Go.
- On Migration Projects page, click New Project.
- 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.
- In the New Project dialog select source and the target tenants added to your organization (see Adding a Tenant).
- 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 Types
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 |
Configuring Connections
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. |
- Click Accounts
- Click Configure Connections on the account migration Dashboard.
- 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 Required 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. |
- When both source and target connections are configured, click Finish.
Advanced Options
The following advanced options can be configured for connections:
- 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.
- 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.
Sharing Availability Information
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:
- Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience, go to step 3.
- Click Accounts to open account migration Dashboard
- Click Enable Calendar Sharing and verify source and target domain names. Click Next to proceed.
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
- Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.