When planning user collections and destination resources for a migration you should have a general sense of the volume of data each user will migrate. Notes Migrator for Exchange offers a Notes Data Locator Wizard that finds source data stores, and determines the per-user data volumes within the stores it finds.
Run the Notes Data Locator Wizard now to find the source data, and then View Summaries | User and Resource Detail to review the per-user data volumes.
Then adjust your Migration Plan (if necessary) to accommodate any unexpected or atypical data volumes.
The Notes Data Locator Wizard is documented in in the NME Administration Guide, chapter 7, and the View Summaries features are part of Notes Migration Manager, documented in chapter 1 of the Admin Guide.
Step 13 (If Necessary): Move Users’ Archives and PABs to a Centralized, Accessible Location
The Data Migration Wizard can migrate users’ personal address books (PABs) from Notes to Exchange, but it must be told where it can find the source PABs:
in the file system using a shared folder or local copy, or in a directory accessible through the Domino server. (The program can also migrate PABs from diverse, per-user locations, but only if you specify the location for each user—as explained in the last step of these Pre-Migration Preparations.) Meanwhile, the Wizard can migrate users’ archives only if they reside in some centralized location where NME can find them.
If your Notes/Domino network is not already configured for your users’ archives and PABs to reside in centralized, accessible locations, and if you do not want to have to specify their diverse locations per user, you (or your users) should move them now, before you run the Data Migration Wizard.
Notes Migrator for Exchange contains a PAB Replicator form that can help end users copy their PABs to a centralized location. An administrator can use a Send PAB Replicator Wizard to distribute the form to end users, with instructions for its use. See chapter 9 of the NME Administration Guide for operating instructions and field notes for the Send PAB Replicator Wizard.
This ability to review found data stores and use that information in your migration planning was new in version 4.0. In previous versions, the locating of data was performed just prior to the data migration, with no opportunity to review the found data before migration. But data location is a pre-migration step now, so the administrator can review data locations and verify ownership of archives and PABs prior to migration.
Step 14: Locate Notes Data Stores
After users’ PABs have been copied to a centralized location, an administrator must run the Notes Data Locator Wizard again, so the Wizard can pick up the new locations of the PABs. See chapter 7 in the NME Administration Guide for more operating instructions and field notes for the Notes Data Locator Wizard.
We recommend that you schedule the Notes Data Locator Wizard to find users' PABs. (This scheduling procedure is also described in the same Admin Guide chapter.) You can then review the console to determine which users have yet to post their PABs to the Notes server.
Step 15: Provision Groups in Exchange
Run the Collection Wizard and AD Groups Provisioning Wizard to provision Notes groups (distribution lists) into Exchange as distribution groups. The operating instructions and application notes for these Wizards appear in the NME Admin-istration Guide—chapter 5 for the Collection Wizard and chapter 6 for the AD Groups Provisioning Wizard.
Step 16 (If AD Is Configured for a Resource Forest and User Forest): Prepare the SQL Server Database for Mailbox-Enabling
For the Data Migration Wizard to properly enable mailboxes, and to properly associate the resource accounts with the user accounts, you must configure the Global Default Settings in Notes Migration Manager, and prepare (or verify) the per-user values in a column of the exported directory data.
See Appendix A of the NME Administration Guide for more information and instructions, under How Do I Prepare the SQL Server Database for Mailbox- Enabling (If AD Is Configured for a Resource Forest and a User Forest)?
Quest MessageStats Lotus Notes Migration Report Pack can generate a report to show all the PABs that have been located. You can define the report format to your specifications, and then schedule MessageStats to regenerate the report daily and email it to you—so you can track the progress of your users.
ONLY IF: Your target environment is configured for a resource forest and a user forest, with corresponding user accounts.
Step 17 (If Necessary): Specify Per-User Data in the SQL Server Database
The Data Migration Wizard can migrate user data from a variety of locations in the Notes/Domino source environment, and the locations must be specified to the program. (This is explained in chapter 3 of this Guide—see the Location of Notes User Data topic.) The Directory Export Wizard and Notes Data Locator Wizard will find available source data via the server and file system, but the Data Migration Wizard will ask which source location to use for each data type: mail, PABs, and archives.
If any of the users’ Notes data files do not reside in a centrally accessible location, you can specify a unique location per user in the SQL Server database.
You can specify per-user data locations for any combination of PABs, archives, and mail files, and this information must be added to the SQL database before the users are migrated. If any of your users’ Notes data files reside in diverse, per-user locations, specify the per-user data now, before the batch-migration procedure. Appendix A of the NME Administration Guide explains the process, under How Do I Specify Per-User Locations for Notes Source Data?
The Data Migration Wizard also lets you specify diverse per-user destinations for the PST files the Wizard will create during the migration. Ordinarily an admin specifies a central location for the program to create all PSTs, under which the program creates directory subtrees reflecting the hierarchical Notes user names.
But if you would rather put each PST in a separate directory (for example, in each user's home directory), then the destinations can be specified in the SQL Server database prior to migration. More information and complete instructions appear in Appendix A of the NME Administration Guide, under How Do I Specify Per-User Destination Locations for Users’ PST Files?
Step 18 (If Necessary): Prepare customattrs.tsv file to migrate Notes custom attributes
Use a text editor to create a unicode (not ANSI) file named customattrs.tsv, in the default installation folder for the Data Migration Wizard (typically C:\Pro-gram Files\Quest Software\Quest Notes Migrator for Exchange), and/or in the folder containing notesdtapp.exe if you want to migrate Notes custom attributes via the SSDM. Either or both migrator applications can refer to this file to map the source attributes to free (unused) properties in the MAPI target mailboxes.
See How Do I Migrate Notes Custom Attributes? in Appendix A of the NME Administration Guide for more information and instructions to create a customattrs.tsv file.
ONLY IF: You want to migrate Notes custom attributes.
Step 19 (If Necessary): Configure SSDM Scheduling
Many organizations choose to use the Self-Service Desktop Migrator (SSDM) for some portion of their migration, for various reasons as explained in chapter 3 of this Guide (see the Batch vs. Per-Desktop Migration topic). Notes Migrator for Exchange includes an SSDM Scheduling utility that lets you control users’
execution of the SSDM, to more evenly distribute the demand on network and server resources. Each user collection is assigned a migration "window": a specific date and time period when its members are permitted to migrate. When a user runs the SSDM, the program identifies the user by his or her login credentials, and checks the schedule to see whether the user is early, late, or "in the window" for his or her migration.
The Scheduling Utility also lets you set a limit to the number of concurrent migration runs, to prevent processing bottlenecks that might otherwise occur if too many users happened to run the SSDM at the same time. In addition to verifying each user’s scheduled window when running the SSDM, the program also compares the number of runs currently underway to the admin-set limit, to determine whether another SSDM run can begin under the limit. If the limit would be exceeded, the user is offered the option of "parking" in a waiting list, so that his or her migration program would run in the next available slot.
If you want to regulate your end users’ use of the SSDM in this way, run the SSDM Scheduling utility now, before you begin the migration. The NME Administration Guide provides instructions for this utility in its chapter 13.