Migrator for Notes to Exchange 4.15.2 - Scenarios Guide

Step 1: Provision Notes groups into Office 365

Groups are typically provisioned separately, after all users have been migrated in the Batch migration process (the preceding section of this chapter). Since the only data associated with a group is its member list, the "migration" of a group consists only of its being provisioned into the target directory. We can use Migrator for Notes to Exchange’s Groups Provisioning Wizard to provision groups either directly from Notes to Office 365, or to a local "staging" AD, from which we can then use Microsoft’s AD Sync tool to provision the groups from the local AD to Office 365.

Before running the Groups Provisioning Wizard, you can divide the groups into collections using Migrator for Notes to Exchange’s Collection Wizard for more convenient processing. If necessary, you can update group membership and attributes in the SQL database (via TSV export and import) prior to provisioning the groups into Active Directory. For operating instructions and application notes, see the Groups Provisioning Wizard chapter of the Migrator for Notes to Exchange Administration Guide.

NOTE: Microsoft's AD Sync tool must be run twice to completely provision nested Notes groups (i.e., Group A contains Group B) in Office 365.

If you need to provision groups before all Notes users have been migrated, be sure to check the Message Delivery Restrictions for any Exchange group to which you want Notes users to be able to send messages. Any such Exchange group must be of the universal distribution type to be mail-enabled. To change settings, beginning in the Exchange Management Console:

Step 2 (optional): configure ongoing directory coexistence

If you are going to keep a local Active Directory up and running, you can configure the Microsoft Online Services AD Sync tool to regularly synchronize the local and hosted ADs. Refer to Microsoft’s documentation to configure the Microsoft AD Sync tool for these ongoing synchronizations.

If you also intend to keep your Domino directory running for a time, or indefinitely, you should also configure Quest’s CMN Directory Connector to regularly update the Domino directory and your local AD.

Step 3: Update mail routing

Migrator for Notes to Exchange is commonly used to automatically update mail forwarding in both systems to ensure proper routing during the migration. Migrator for Notes to Exchange can set and remove forwarding rules in both environments, as long as the mail routing domains or smart hosts are properly configured.

When the users and groups are all migrated, routing can be permanently updated to direct external incoming (Internet) mail to Office 365 instead of to the Notes environment. This step includes modifying the MX record(s) to redirect the inbound external mail. In some environments, updating mail routing also includes updating routing tables and/or firewall modifications.

Most organizations prefer to update mail routing only after the last user has been migrated, to minimize change before and during the migration process. But the MX modification actually can occur at any time after all Notes users have been provisioned into Office 365 as mail-enabled objects. (If routing is updated to send inbound mail to Office 365 before a particular user is provisioned, there will be no forwarding address in Office 365 to relay the user’s mail back to Notes.) The timing of this step therefore depends on how you provisioned Office 365:

Step 4: Post-migration "clean up"

To "clean up" after the last user has been migrated: