Migrator for Notes to Exchange 4.15.2 - Administration Guide

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.