Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16 - Scenarios Guide

About the Migrator for Notes to Exchange documentation Scenarios overview Migration to a proprietary Exchange
Migration to a proprietary Exchange target Pre-migration preparations Batch migration process Post-migration activities
Migration to Microsoft Office 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

When the pre-migration preparations are complete ...

When you have completed the pre-migration preparations as described in this chapter, go on to the Batch migration process below, and/or see chapter 4 for information about SSDM (per-desktop) migration.

Batch migration process

Migrator for Notes to Exchange includes two migration engines:

The Data Migration Wizard migrates batches of users simultaneously, performs important administrative functions (mailbox creation, routing updates, etc.), and also migrates public distribution lists.
The Self-Service Desktop Migrator (SSDM) runs in memory on end users’ local workstations and migrates content for one user. SSDM streamlines the process of migrating local content, reduces burden on the migration team, and includes a Silent Mode to minimize end user interaction and requirements.

Either migration engine can be used independently for the entire data migration, or the two may be used together to meet a variety of project requirements, as discussed in the Pre-Migration Planning Guide (see the Batch vs. Per-Desktop Migration topic in chapter 3).

This section provides process instructions for the batch-migration portion of a migration to Office 365, where an administrator uses the Data Migration Wizard to perform the migrations for multiple batches (Migrator for Notes to Exchange collections) of users. SSDM (per-desktop) migration, described in chapter 4, may also be part of your Migration Plan.

The flow chart below summarizes the batch-migration process for an Office 365 target. The step numbers in the flow chart correspond to the step numbers in the narrative process instructions that follow.

This batch-migration procedure is repeated for each user collection to be migrated, as shown by the looping arrow in the flow chart.

NOTE: Remember, Notes groups (distribution lists) are typically migrated separately, after all users have been migrated. The Post-migration activities described at the end of this chapter include the migration of groups.

Step 1 (optional): Re-run directory connectors

Conditional Step: Applies only if you provisioned Office 365 from a local AD, and used Quest’s CMN when provisioning your local AD, in which case this step is optional but recommended. Otherwise, skip ahead to the next step below.

Many organizations experience staff additions and departures during a migration transition period, and employees move from one office to another or are promoted or reassigned. Any directory changes that occur during the migration project, after the initial directory updates in the Pre-Migration Preparations, may introduce data inconsistencies between the source and target environments. These can be reconciled using this "two-step" directory update between Domino and Office 365:

Both CMN’s Directory Connector and Microsoft AD Sync can be configured to automatically run directory updates at scheduled intervals. However, you should also run directory updates manually at this step to ensure the directories are consistent just prior to migrating each collection.

NOTE: An object that is synched to Office 365 with proxyAddresses will lose the proxyAddress upon the next sync if the UPN is changed to match the Office 365 login—which disables mail routing from Domino to Exchange.

Step 2: Refresh Migrator for Notes to Exchange's SQL data

To make sure your target Exchange will be provisioned with current object data, update the information in Migrator for Notes to Exchange’s SQL database before migrating each user collection. If you have updated the directories in the preceding step (optional), this process will also relay all directory changes into the SQL database. To update the SQL server database:

Related Documents