Any migration scenario requires prior preparation of the source and target environments, implementation of a coexistence strategy, configuration of admin accounts, and preparation of the required software. These procedures can be time consuming because they include configuring necessary accounts and permissions across multiple environments, configuring applications running concurrently to facilitate the migration, and other considerations. However, they are typically performed only once, before the first users are migrated, so they need not complicate the entire migration process.
Before you begin these preparations, remember to decide your strategy to accommodate the Exchange free/busy limitation, as explained in the Migrator for Notes to Exchange Pre-Migration Planning Guide (in chapter 2, see Provisioning the Target Active Directory).
The flow chart below illustrates these pre-migration preparations for migration to Microsoft Office 365. Note that the step numbers in the flow chart correspond to the step numbers in the process instructions that follow.
If you intend to provision Office 365 from an existing local Active directory, your Office 365 setup will include installing Microsoft AD synchronization tool. See your Microsoft documentation for guidance in the installation and configuration of that AD sync tool.
All of the system requirements must be satisfied before you begin this process. System Requirements are documented in the Migrator for Notes to Exchange Release Notes (for the most recent released version of the product). System Requirements include the admin accounts that will be used to run the Quest applications and access data and features in the Notes/Domino and Exchange/AD environments. As such, they require particular permissions, also specified in the System Requirements. If these accounts do not already exist, be sure to create and configure them now.
Conditional Step: This step applies only if you intend to provision Office 365 from a local proprietary Active Directory. If you will provision by some other method, skip ahead to step 4.