Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Scenarios Guide

About this guide Scenarios overview Migration to a proprietary Exchange target
Pre-migration preparations Batch migration process Post-migration activities
Migration to Office 365
Migration to Office 365 Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Step 1: Run Directory Connectors to update directories with recent changes

Many migration projects extend over a period of several weeks or months, so it is common for organizations to experience staff additions and departures during the transition period. Any directory changes that occur during the migration project may introduce data inconsistencies between the source and target environments, but these can be reconciled using CMG’s Directory Connector.

Many admins configure CMG’s Directory Connector to automatically run directory updates at scheduled intervals. But it may be useful to also initiate updates manually at this step in the process to ensure both directories are consistent before proceeding with the migration for this group.

Please refer to Quest CMG documentation for more information about the Directory Connector.

Step 2: Run Directory Exporter to update CSV Files with recent changes

Migrator for GroupWise’s Directory Exporter extracts user and group information from GroupWise and populates CSV files that serve as input to the migration process. When user and group modifications occur in the GroupWise environment, it is important to run Directory Exporter again to update the contents of the CSV files. This ensures accurate input to the migration applications.

For more information about the Directory Exporter and how to use it, including screen-by-screen field notes, see the Directory Exporter chapter of the Migrator for GroupWise Administration Guide.

Step 3: Prepare a migration group user-list .csv file

Migrator for GroupWise’s Admin-Driven Batch Migrator references a CSV file to determine the subset of users to migrate in the current migration group. Each time the Batch Migrator runs, it prompts for the particular CSV user-list file containing the users to whom the program should apply its functions.

Remember that Migrator for GroupWise’s Directory Exporter creates a UsersToMigrate.csv file each time it runs, beginning in the Pre-Migration Preparations but also when refreshing user data as in step 2 above. The UsersToMigrate.csv contains records for all GroupWise users, but an administrator typically uses the Batch Migrator to migrate subset groups of a few dozen users at a time. (See Grouping Users for Batch Migration in chapter 3 of Migrator for GroupWise’s Pre-Migration Planning Guide for information about determining the optimum size of user batches.) You can use the UsersToMigrate.csv file as a template to create subset user-list CSV files for the Migrator for GroupWise Batch Migrator. To prepare a user-list file, use Microsoft Excel to:

Open UsersToMigrate.csv and Save As a new CSV filename (for example, migr01.csv for your first migration group, or migmktg.csv for users in the Marketing Department). You must save the file in CSV format, not as an Excel Workbook or any other file type.
NOTE: If either of the next two subtopics applies to your migration, it may be more efficient to make those modifications to the master UsersToMigrate.csv file (for the entire universe of users) before using that file as a template to create subset user-list files, as described above.

If you will access GroupWise data by proxy: You can use the CSV file generated by Migrator for GroupWise’s AddProxy utility as your user-list file—modified if necessary to accommodate any special circumstances as noted below. The AddProxy Utility chapter of the Migrator for GroupWise Administration Guide explains how each successful run of the program, per user, generates a record of the user in a file, designated in your addproxy.ini file as the SuccessLog. This file thus contains a current list of all users who have granted the necessary proxy rights, and are thereby eligible for migration by proxy.

Some administrators want to provision users in the same user-list CSV file to two or more Exchange mailstores. The Admin-Driven Batch Migrator program supports this when separate destination mailbox stores are specified in the user-list CSV file. The HomeMDB column of the user-list CSV file can be used for this purpose.

The HomeMDB column specifies the Exchange mailbox store for each migrating user, and is used when mailbox-enabling users by the Exchange Administrative Operations of the Admin-Driven Batch Migrator. Example:

Note that the Exchange admin credentials supplied to the Admin-Driven Batch Migrator must have sufficient rights to create mailboxes on the Exchange server(s) specified in this HomeMDB column. If the HomeMDB column is left blank, the value specified in Migrator for GroupWise's GUI will be used for the destination Exchange mailbox store.

Review these circumstances and determine if any of them apply to your migration scenario:

If any of these or similar circumstances apply in your migration, please see Knowledge Base solution #SOL14994 (via Quest support portal) for a description of the columns in the UsersToMigrate.csv file.

Step 4: Run Admin Batch Migrator to create mailboxes (and other administrative functions)

Before migrating data for any group of users, you must create destination mailboxes for them in Exchange. At this step, we run Migrator for GroupWise’s Admin-Driven Batch Migrator twice: first for certain GroupWise and Exchange administrative functions (depending on your needs), and then again to create the mailboxes.

In a typical scenario we select these features for the first run:

Set [GroupWise] user password (Optional/Conditional): Modifying passwords is necessary only if the Trusted Application API is not a viable option due to GroupWise version or other considerations. Some organizations, however, prefer to change the GroupWise password for migrating users to encourage use of the Exchange environment.
Set user visibility in the GroupWise directory: The visibility setting is especially important when Quest CMG is used to update both directories with modifications. As mailboxes are created in Exchange for migrating users, you may also want to set the GroupWise visibility to None for the same user population. This eliminates the possibility of duplicate entries appearing in the GroupWise directory for migrated users after subsequent runs of the CMG Directory Connector. The timing of this operation should be coordinated with CMG’s Exchange-to- GroupWise Directory Connector so that Exchange entries for migrated users are synchronized back to GroupWise shortly before or after the visibility change.
Remove user free/busy forwarding to GroupWise (applies only if free/busy coexistence has been configured): Free/busy forwarding to GroupWise will soon be unnecessary for the users in this group, since they will soon have Exchange mailboxes, and will then track their free/busy data in Outlook.

And then for the second run we select these features:

Set forwarding from GroupWise to Exchange (for this user group): The GroupWise users in this group will have Exchange mailboxes after this run of the Batch Migrator. Inbound external mail may or may not have already been redirected to Exchange (optional in step 14 of the Pre-Migration Preparations above). But in any case GroupWise-to-Exchange routing is necessary during the transition period, to route internal mail sent from not-yet-migrated GroupWise users to these already-migrated Exchange recipients.
Mailbox-enable existing Active Directory accounts. Creates Exchange mailboxes for this group of migrating users.

See the Administrator-Driven Batch Migrator chapter in the Migrator for GroupWise Administration Guide for complete instructions and application notes for these features.

NOTE: For an Offline Migration (only): After you run the Batch Migrator for these admin functions: Verify the GroupWise Post Office is configured to allow Direct Connections, and copy the Post Office data files to an intermediate storage location. Then, if using a portable storage medium, transport the medium to some location where you have a high-bandwidth connection between your Migrator for GroupWise workstation and the target Exchange server.
Related Documents