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.
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.
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.
When migrating from a Notes environment with Symantec E-Vault, Exchange propagation issues may interfere with Migrator for Notes to Exchange setting custom attributes when the destination mailbox has never been accessed either by Outlook or by the migration application. One simple work-around would be to first run a "dummy" migration (e.g., use a date filter where date > 1/1/2100) to open all the target mailboxes before running the real migration.
Migration to an Exchange environment configured with a CAS array requires a few extra steps. See, in Appendix A of the Migrator for Notes to Exchange Administration Guide, the topic How Do I Migrate to an Exchange Environment with a CAS Array?