Migrator for GroupWise 4.7.1 - Scenarios Guide

Step 1: Run Directory Connectors to sync the GroupWise directory and the local AD

NOTE: This step applies only if you will use Microsoft’s DirSync tool to provision Office 365 from a local AD. If provisioning by some other method, skip to the next step below.

CMG’s Directory Connector can be configured to automatically run directory updates at scheduled intervals between GroupWise and the local AD. But many admins also update the directories at this step of the process to ensure both directories are current before proceeding with the migration for this group.

Many migration projects extend over a period of several weeks or months, so migrating organizations often experience staff additions and departures during the transition period. Any directory changes that occur while the migration is in-process may introduce data inconsistencies between GroupWise and the local AD, but these can be reconciled using CMG’s Directory Connector. See Quest CMG documentation for full details.

Step 2: Run Directory Exporter to refresh 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:

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.

Optional Modifications to the user-list CSV file:

NOTE: If any of the Optional Modifications listed here applies to your migration, it will usually 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 for subset user-list files, as described above.

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 the article titled Which columns are required and which can be added or modified in the CSV user list? in the Migrator for GroupWise Knowledge Base.

Step 4:Prepare local AD accounts for Microsoft's DirSync

NOTE: This step applies only if you are using Microsoft’s DirSync tool to provision Office 365 from a local AD. If provisioning by some other method, skip ahead to step 5.

If your local Active Directory still includes any objects that you do not want copied to Office 365, remove them now. The DirSync you will perform in the next step below will copy all user objects from the local server.

Run Migrator for GroupWise’s Admin-Driven Batch Migrator to prepare the accounts in your local AD for provisioning into Office 365 by Microsoft’s DirSync tool. On the Batch Migrator’s Exchange Administrative Operations screen, mark the checkbox for Prepare local Active Directory accounts for MS DirSync.