Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16.3 - SSDM User Guide

About the Migrator for Notes to Exchange documentation Scenarios overview Migration to a proprietary Exchange
Migration to a proprietary Exchange target Pre-migration preparations Batch migration process Post-migration activities
Migration to Microsoft 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

How to migrate from disconnected NSFs or PSTs to Exchange

In the MNE Notes Migration Manager (before you run the Data Migration Wizard):

On the Exchange Server Configuration screen, ensure the Always use these values check box is not selected.
Under Discover Notes Information:
On the Find NABs screen, load and enable the offline copy of the Notes Address Book. Locate and load the offline copy manually using the Add NAB button. (The Find NABs button does not work since the Notes server is offline.)
On the Find Domains screen, click Find Internet Domains to load the domains from the offline NAB.
On the Export Notes Directory screen, click Export Directory, to launch the MNE Directory Export Wizard, and:
Click Edit to edit Task Parameters. In the configuration file, add the parameter offline=1 to the bottom of the [Notes] section. Save and close the file and click Next.
On the Specify Notes Login Information screen for Domino Server, enter the name of the original Domino server from which the NAB files were copied. Specify the offline migration ID file and password for the User ID file and Password fields.
In the Notes Migration Manager, under User Collections on the Locate Notes Data Stores screen, click Locate data stores to launch the Notes Data Locator Wizard for the designated user collection.
On the Select Notes Data Store Type(s) to Locate screen, select Find new data stores and gather statistics, and set the Add/Replace mode to Replace data previously found....
Ensure that Scan file system directories that I specify is selected and click Next.
Note: You must specify the root folder, one folder above where the mail files are located. Also, the mail files must reside in a directory whose name matches the one from which the mail files came.

Phased (staged) migration

The term phased migration or staged migration refers to the process of pre-migrating or pre-populating data to target Exchange mailboxes before the final cutover migration. The staged migration can occur across the bandwidth or, in many cases, be implemented in conjunction with the offline method previously described.

With a staged approach, most of the data can be pre-populated to the target mailboxes which reduces the volume of data that must be transferred during the final migration. Users remain active in Notes throughout the transition period, receiving and sending mail and managing their calendars in Notes while their older data is migrated to Exchange. After the older data is migrated, a smaller volume of remaining data can be migrated quickly so that a large numbers of users (or all users) can be migrated together within a shorter window. Since Migrator for Notes to Exchange migrates copies of Notes data (does not delete the originals), the older data is still available to users in Notes throughout the transition period.

With a phased migration, it is beneficial to separate older mail from newer mail. You can accomplish this using one of two methods:

Replica method: The agreements created to replicate NSFs can be configured to limit the data included in the replica NSF. With this approach, the replicated data can be limited to the subset of information you want to include in the pre-cutover phase.
Date filter method: The Data Migration Wizard has integrated filtering options to specify date limits and ranges for messages to be migrated—to migrate only messages on or after (or before) a certain date, or within a range of dates. Date filters are applied only to mail and calendar items, and not to user contacts.

Migrator for Notes to Exchange also contains Smart Remigration technology so that previously migrated items are detected and not duplicated if they are inadvertently migrated again.

End-user communication is critical in a phased migration to ensure the users understand the migration schedules. Depending on the migration timing and configuration, modifications and deletions made in Notes between the migration events may not be reflected in Exchange after the final migration.

In a phased-migration, the Exchange accounts and mailboxes must be created to accept the migrated data before end users start using their Exchange accounts. Run the Migration Wizard at least twice for each user group:

First Pass: Mailbox-enable the user accounts on Exchange, set mail-for­warding rules on Exchange (to forward mail back to Notes until the user is migrated), and migrate older user data to the new server.
Second Pass: Reverse the mail routing (to forward mail from Notes to Exchange) and migrate the remaining data.

Silent mode options in per-desktop migrations

The Self-Service Desktop Migrator (SSDM) offers a Silent Mode configuration. This optional configuration is used to minimize end user involvement when the SSDM is deployed, while maintaining the flexibility and other benefits of a distributed migration.

When Silent Mode is configured, the migration team configures the application in advance within the notesdtapp.ini file to determine what data will migrate, the target for each migrated data type, and the filters and other configuration elements for the migration.

The SSDM Silent Mode options are described in chapter 4 of this guide.

Migration to a proprietary Exchange

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating