Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - Pre-Migration Planning Guide

About this guide Introduction Critical considerations Other strategic and tactical issues Known limitations of the migration process Summary of features and capabilities


Items moved in GroupWise: An item moved to a different folder in GroupWise after it has been migrated will be regarded by Migrator for GroupWise as a new item, so any subsequent migration of the item will proceed as a first-time migration rather than a remigration. The originally migrated item will remain in Exchange in its original location, so a subsequent migration will generate a duplicate in Exchange. The RemigrateMode parameter would have no effect in this case, since Migrator for GroupWise regards the subsequent migration as a new, first-time migration.
Items deleted in GroupWise: An item that is deleted in GroupWise after it has been migrated will remain in Exchange. Since a deletion in GroupWise is actually a "move" (to the Trash folder), any subsequent migration will generate a duplicate item in the Exchange Deleted Items folder—the same as for "moved" items as described above. Again, the RemigrateMode parameter would have no effect, since Migrator for GroupWise regards the subsequent migration as a new, first-time migration.
Items changed in GroupWise: When an item is changed in GroupWise after it has been migrated (e.g., updated date/time/subject of an appointment), the RemigrateMode parameter determines how any remigration will proceed. By default (RemigrateMode=1), the previously migrated copy is left in Exchange and the changed item will not be migrated. In update mode (RemigrateMode=0) however, Migrator for GroupWise detects the previously migrated copy in Exchange, deletes it as an earlier (obsolete) duplicate, and then remigrates the updated source item.

Known limitations of the migration process

Most of the known limitations of any migration process are due to feature inconsistencies between the source and target environments. GroupWise and Exchange offer similar features, but their implementations differ, and sometimes a feature in one environment is simply not offered in the other. Sometimes a migration tool can remediate these differences, but sometimes the differences are so great as to make remediation impossible or impractical.

In the latter case, we characterize the issue as a "known limitation"—seemingly inherent to the process, and therefore unlikely to be resolved in a future Migrator for GroupWise release. Known limitations of the migration process facilitated by the current release of Quest Migrator for GroupWise are:

The Directory Exporter will not add given names and surnames to existing user records in csv data files that were created by prior runs of the Directory Exporter from versions and earlier—before the Directory Exporter collected given names and surnames. Therefore, if you have already run the Directory Exporter from one of those earlier versions and want to re-run it now, be sure to first delete the usersto­migrate.csv and addresstranslation.csv files, so your next run of the Directory Exporter will re-create them from scratch. The Directory Exporter ignores user data for users who already appear in a previously generated csv file, so would not update a user record to add the two new fields, but will create a new csv file (with the two new columns) if it can't find a previously generated one.
Outlook archiving is not applied to migrated messages within the age range set for auto-archiving, because Outlook determines message age by Last Modified time, which it updates to the migration date/time upon migration. Since all migrated messages become zero days old as soon as they are migrated, and Outlook won't let the Batch Migrator reset that property to its true pre-migration date/time, the Outlook archiving feature skips the messages until they have "re-aged" to the archive age (typically 30 days) following migration, at which time all of the migrated messages will be archived.
The formatting of non-UTF-8 text in a message body is lost when the ExportRTF parameter is set to 0 (default), but UTF-8 characters do not migrate if ExportRTF=1. The ExportRTF parameter determines whether Migrator for GroupWise will migrate RTF message bodies.
Migrator for GroupWise does not migrate the My Subject field on the Personalize tab of a message.
The DisplayName of a contact may not migrate correctly from a GroupWise source with the French-language GroupWise client installed.
One or more parentheses in a message Sender name will distort the Sender's DisplayName in Outlook when the message is migrated. This appears to be a bug in the GroupWise API. For a Sender "Smith (Dave)" or "Smith (Dave" the DisplayName resolves to "Dave". For a Sender "Smith (" the DisplayName resolves to the recipient's DisplayName instead of the Sender's.


Summary of features and capabilities

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating