This topic explains how to use the Transporter Management Console or the Transporter Management Shell to migrate Notes personal mail archives to Microsoft Exchange Server 2007 mailboxes.
Use the first procedure listed below to migrate Notes personal mail archives to Exchange Server 2007 mailboxes. Use the second procedure to migrate Notes personal mail archives to Exchange Server 2007 using the Transporter Management Shell.
Before You Begin
Install a Lotus Notes 6.x or 7.x client as a “single user” on a server that is running Exchange Server 2007. The client must have a user ID that is listed in the Domino Directory's Access Control List with Reader or higher access.
Verify that the Lotus Notes client can access the Domino Directory (names.nsf) on the Lotus Domino server identified as the Domino Directory server, and any other address books that you intend to migrate.
Usually, the databases to be migrated should not be locally encrypted, unless the client is configured with an ID file capable of decrypting the database.
The Active Directory user used to perform the migration must have permission to impersonate the users whose personal mail archives are being migrated. This permission can be set using a Exchange Management Shell command of the form:
Add-ADPermission –Identity 'DN_of_ClientAccessServer' ‑User 'domain\username' ‑ExtendedRights ms‑Exch‑EPI‑Impersonation
To use the Transporter Management Console to migrate selected Personal Mail Archives
In the Transporter Management Console, click Toolbox, and then, in the center pane, double-click Migrate Notes Mail Archive.
You may be prompted to Enter Domino Credential. Type the password associated with the local Lotus Notes client, and then click OK.
On the mail archive Options screen, enter the following information:
- Mail Archive to extract: Browse for
the archive file to be migrated. Typically, this is the NAMES.NSF
from the client workstation.
- Domino mail domain: Contacts in Domino
may not contain the Domino domain information, if the contacts are
in the same domain as the Personal Address Book owner. Entering the
domain of the user here ensures that contacts will remain usable
- Archive Owner: Browse for the user to
determine the mailbox that the contact data will be migrated
- Target Exchange Mailbox Database: If
the user has not yet had a mailbox created, one will be created on
the server you browse to.
- Specify Client Access Server (CAS):
Optionally, a specific CAS can be used to inject the mail. This
allows you to reduce the number of servers that require the
- Mail Archive to extract: Browse for the archive file to be migrated. Typically, this is the NAMES.NSF from the client workstation.
Click Next. On the summary page, click Next to perform the migration.
To use the Transporter Management Shell to migrate Personal Mail Archives
To use the Transporter Command Shell, use the Move-NotesMailArchiveToExchange cmdlet. For example:
Move-NotesMailArchiveToExchange –DominoMailDomain 'Domino domain' ‑ContentOwner 'email@example.com' –SourceFileName 'source_path'
For detailed syntax and parameter information, see Move-NotesMailArchiveToExchange.
Addresses in Personal Address Books and Active Directory User Objects
Addresses stored in personal mail archives will not be able to be replied to unless the Notes address has been copied to the associated user or contact object in Active Directory. Ordinarily, this copying of addresses will occur during Directory Synchronization tool and as part of the function of migrating users.
“Fuzzy” address matching may resolve to users whose names have been modified. For example, the following may resolve, depending on configuration setting on the Domino side:
- Contact: Bonnie L Skelly/Certifier
- Person document: Bonnie Skelly/Certifier
During user migration, all addresses in the FullName field of the Person document associated with the user being moved will be copied to Active Directory.
Generally, old names and addresses are in the FullName field, so this would not be a problem — but there may be cases when the names and addresses are not. To resolve this issue, simply create a new address on the Active Directory user or contact object.