Migrator for Notes to Exchange 4.16 - Administration Guide

How do I perform an offline migration?

Migrator for Notes to Exchange supports offline migration—a strategy in which Notes source data that was previously extracted from Notes is migrated directly to the Exchange target. An offline strategy can be valuable:

An offline migration can be accomplished by either of these two approaches:

See the Offline migration topic in chapter 1 of the Migrator for Notes to Exchange Scenarios Guide for more information, including requirements and guidelines, for offline migrations.

How do I migrate resources?

Exchange 2010 and later permit the differentiation of resources into three types: Room, Equipment and Online Meeting. The Directory Export Wizard copies the resource type designations from Domino into the object records in the SQL database, and the Provisioning Wizard then provisions the objects into Active Directory with the type designations intact. When the Data Migration Wizard later mailbox-enables those objects, the mailboxes are created with the correct resource type.

In a typical scenario, AD security objects have already been created for all users and resources, and a dirsync creates mail-enabled AD contacts that correspond to existing security objects. The Provisioning Wizard then merges the contact information (including resource types) into the existing security objects, and deletes the contacts, leaving a single mail-enabled security object in AD per user or resource. After that merge process has created mail-enabled security objects, the Data Migration Wizard can mailbox-enable the objects.

Note: If a resource appears in a collection, but no corresponding security object or contact yet resides in AD, the Provisioning Wizard can be configured to overlook the missing entities. This feature is enabled or disabled by a checkbox on the wizard’s Choose the Container for User Objects screen:

Mark the checkbox if you want the wizard to create a new mail-enabled object in AD when none is found by the wizard to correspond with a user (resource) in the collection. Leave the checkbox unmarked to disable that feature. Any such new objects will be created in the container specified by the User Container text box (on the wizard’s Choose the Container for User Objects screen).

NOTE: Use this Create new objects... feature only if no corresponding contact or user object already exists in AD. If an AD user object exists without a corresponding contact, the wizard will simply mail-enable the existing object.

How do I migrate mail-in databases?

Migrator for Notes to Exchange migrates Notes mail-in databases like Resources to Exchange as Shared mailbox. The Directory Export Wizard recognizes mail-in databases as distinct from other (user) mailboxes, and identifies them as Mail-in Databases in Notes Migration Manager, in the Object Type column of the Objects found table.

When migrating a mail-in database, verify that the source address in the TSV file matches the name associated with the mail-in database folder to be migrated. The name can be verified in the Notes administrator account under the Mail-In Database section. The mail-in database will be matched up using either of:

Note that the application does not perform a lookup in the names.nsf file, but instead looks for the matching address in the mail-in-database NSF file.

NOTE: The Data Migration Wizard will set forwarding on a mail-in database if it is told to do so, by setting the MailAddress attribute in Notes’ Document Properties for the mail-in database.

How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV files?

It is rare but possible that data corruption or incongruities in the SQL database may make it easier to simply delete the database contents and re-export data from the Notes/Domino source, although in that case it would be tedious in most environments to have to manually recreate collections, one at a time. The Manage User Collections and Manage Group Collections screens in Notes Migration Manager therefore let you export all Migrator for Notes to Exchange-defined collections (all at once) to a TSV file, and later restore them to the SQL database (also all at once), to spare you the time and trouble of having to manually recreate collections in the event the SQL database is deleted and reloaded.

See Group Collections: Manage Groups and User Collections: Manage Users in chapter 1 for the export and import procedures.