Migrator for Notes to Exchange 4.15.2 - Scenarios Guide

Step 5: Run Migrator for Notes to Exchange's Data Migration Wizard to set Notes-to-Exchange mail forwarding and migrate data

IMPORTANT: If you are migrating data using file system access (rather than by server access): • Verify that all migrating users are logged off before running Migrator for Notes to Exchange’s Data Migration Wizard. If the data is accessible through the Domino server, Quest recommends you use server access to locate and migrate the data. If server access is impossible or impractical, and you need to use file system access to locate and migrate the data, you must make sure that all users in the current collection are logged off the system. • Also, make sure the NSF file is not open in the server’s cache. The dbcache flush command closes all files being held open by the server for users that are no longer logged onto the server. Running the dbcache flush command prevents the server from blocking Migrator for Notes to Exchange’s access to the NSF files during the migration run.

Run the Data Migration Wizard again to:

See the Data Migration Wizard chapter of the Migrator for Notes to Exchange Administration Guide for complete instructions and application notes.

Step 6: Distribute .pst files (if any)

If the Data Migration Wizard migrates any data to Outlook Personal Folder (.pst) files, then when the migration is complete you must either:

The Data Migration Wizard names any new .pst files using the common filename, if specified, or the specified filename format. if more than one file is generated per User ID, incremental numbers are appended to the filename. For example, Smith.pst, Smith-1.pst, Smith-2.pst, etc.

NOTE: The location of the PST files is reported in: • The User migration status per collection report, available from the View Summaries screen of Notes Migration Manager. • The Report Pack Report, available from the View Report Pack screen of Notes Migration Manager.

Was that your last migration collection?

If this is not your last migration collection: Repeat this entire Batch migration process for the next collection. If this is your last migration collection, but you have more Notes users to be migrated individually by Migrator for Notes to Exchange’s SSDM: See the SSDM (per-desktop) migration chapter in this Scenarios Guide.

If this is your last migration collection, and no users remain to be migrated by the SSDM (per-desktop) program, be sure to see the Post-migration activities below.

Post-migration activities

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: