Chat now with support
Chat with Support

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

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migration Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Hybrid Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Upgrading Throttling Policies

In 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 the request to raise the limits for the following throttling parameters to 'Unlimited':

  • EwsMaxBurst
  • EwsRechargeRate
  • EwsCutoffBalance

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

Working with On Demand Migration

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

New Migration UI: Basic migration workflow

# Step
1 Create Migration project. Step 1: Configure connections
2 Create Migration project. Step 2: Grant permissions (see Required 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
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
14 Migrate Public Folders
15 Configure hybrid connections and enable Hybrid (see Configuring Hybrid )
16 Monitor the progress and track issues
Classic Migration UI: Basic migration workflow

Basic migration workflow consists of the following steps:

# Step
1 Configure connections
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 Migrations

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

  • 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.
  • A pilot migration uses a small portion of real users and real data in the live production environment.

In either case - a test or pilot migration - the data to be migrated should be a representative sample of the production data, and the test or pilot migration should be run with the Quest applications set for the same configuration and process options that you intend to use for the production migration. it is recommended to select test or pilot users whose usage and data types make them representative of the total user population. Then create and run matching / migration tasks for those accounts, including all range of tasks you are planning to perform. When the tasks are completed, review errors and warnings, if any. See Event Management section for more information.

Quest recommends that you use both test and pilot migrations:

Perform one or more test migrations in a separate test environment, migrating test copies of real users and their real data. The separate test environment ensures that no test process will affect the data or configurations of your production environment. If a test exposes any problems under migration, you can make amendments and then repeat the test by simply dumping the test environment and recreating it from scratch.

When you are confident that your test migrations have sufficiently refined your planned migration, perform a pilot migration for 20 or 30 users to verify if your planned migration is satisfactory for your "real world."

Project Management

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

  • View all migration projects that are already created for your organization
  • Create new migration project
  • 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.

  • Open main migration project Dashboard using OPEN PROJECT link
  • Quickly navigate to Dashboards for managing migration project features (Accounts, Mail, OneDrive, SharePoint, 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.

  • 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

Related Documents