Migrator for Notes to Exchange 4.15.2 - Scenarios Guide

Pre-migration preparations

NOTE: The information in this chapter applies only if migrating to Microsoft’s Office 365. If you are migrating to a proprietary Exchange, see chapter 2 (Migration to a proprietary Exchange) instead.

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’s Office 365. Note that the step numbers in the flow chart correspond to the step numbers in the process instructions that follow.

NOTE: Steps that apply only in particular circumstances are clearly marked with this "If" branching-arrows icon and a note explaining when the step applies.

Step 1: Establish Office 365 account

Contact Microsoft to establish your Office 365 account (if you haven’t already).

If you intend to provision Office 365 from an existing local Active directory, your Office 365 setup will include installing Microsoft’s AD synchronization tool. See your Microsoft documentation for guidance in the installation and configuration of that AD sync tool.

Step 2: Verify all system requirements are satisfied

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

Step 3 (if provisioning from a local AD):Install and configure the local Active Directory

Install and configure the local proprietary AD at this time, with the Exchange schema, if it isn’t already up and running. Provisioning the local AD will occur at a later step in this procedure.

IMPORTANT: If you upgrade from Exchange 2010 RTM to a later Exchange version while the migration is in progress, you must also upgrade the AD schema to match.