Migrator for Notes to Exchange 4.15.2 - Pre-Migration Planning Guide

Migrating Notes attachments

The Domino/Notes environment can be configured to handle message attachments by saving only one copy of the attachment on the Domino server, and then making the single attachment available to the sender and all recipients. This Domino Attachment and Object Service (DAOS) is transparent to end users and can save some storage space compared to the alternate method: replicating the attachment for each recipient. However, DAOS tends to slow down migration speed. If speed is critical, the replicated attachments method is preferred.

Migrator for Notes to Exchange will find and migrate Notes attachments saved by either method. For multiple Outlook recipients, an attachment will be replicated for each recipient.

Migrating mail-In databases

Mail-in databases in Notes work like shared folders in Outlook—as a repository for items that can be accessed by multiple users. Migrator for Notes to Exchange migrates Notes mail-in databases like resources. The Directory Export Wizard recognizes mail-in databases as distinct from other (user) mailboxes, and identifies them as "mail-in database"s 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 admin 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 ForwardingAddress attribute in Notes’ Document Properties for the mail-in database.

Migrating mail-in DB owners

Migrator for Notes to Exchange's Directory Export Wizard captures the owner of a Notes mail-in database, and the Data Migration Wizard can migrate the owner's identity when it migrates the mail-in DB. The Directory Export Wizard captures these owner identities in any case, but their migration to Exchange is an option that is enabled or disabled by a boolean program parameter in the [Exchange] section of Task Parameters and Global Defaults:

By default (MigrateMailInDBOwner=1), the wizard will migrate the identity of mail-in database owners. To disable this feature, set MigrateMailInDBOwner=0.

Migrating to Exchange personal archive mailboxes

Migrator for Notes to Exchange lets you choose a migration destination (within Exchange) for each of the three primary data types to be migrated: archives, address books, and server-based data. Each type can be migrated to: users' server-mail mailboxes, or users' pst files, or to users' personal-archive (server-based) mailboxes.

Personal archives is a feature introduced in Exchange 2010 that lets a user keep archived items in a separate mailbox—where they are more secure and accessible than in .pst files.

The personal archives mailbox is one of three destination options in Migrator for Notes to Exchange's Data Migration Wizard, on the Select Destinations for Migrated Data screen, in the Destination drop-down lists. The Destination of each data type—Archives, Address books, and Server-based data—is set independently.

The Data Migration Wizard can also automate creation of the personal archive mailboxes, if they do not already exist in Exchange. On the Specify Exchange Mailbox Information screen, the Enable Exchange 2010 or later Personal Archive checkbox lets you tell Migrator for Notes to Exchange to create the personal archive mailboxes.

In the SSDM, the migration destination is not selectable in the GUI, but is controlled by three pairs of parameters in the [General] section of the notesdtapp.ini file. See Configure Data Destinations for Different Data Types in chapter 4 of the Migrator for Notes to Exchange Scenarios Guide for details.

You can specify a language for personal archive folder names using the [General] LanguageCode parameter. See the Programming Parameters Reference guide.