|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|
|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.
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.
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."
The On Demand Migration provides robust project management interface and in-depth progress reporting:
note: Address Rewrite Service requires licensing.
TIP: Give informative names for the tasks. It will simplify the project management and event filtering in the future.
|1||Breadcrumbs||Keep track of your location within project and quickly return to the previous steps.|
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.
|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|
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