Recurring Nightmare

One of the significant issues facing organizations after migrating from GroupWise to Exchange is updates to recurring meetings.

As a result of the way GroupWise stores and links recurring and custom recurring meetings, they have been migrated (by Quest and other vendors) to single instance meetings in Exchange. All of the occurrences are present after the migration, but they are no longer linked as a series of appointments. Differences in the calendar models between GroupWise and Exchange make it challenging to cleanly preserve the recurring behavior of these appointments.

At first glance, this may sound like more of an inconvenience. However, this quickly becomes problematic as users attempt to update recurring meetings after the migration. If a meeting organizer needs to change the room, invite new attendees, modify the time, or delete the series; they soon realize how time-consuming this process has become. The organizer must find and update each future instance individually.

The cleanest approach is often deleting the migrated instances and creating a new recurring meeting in Exchange, but that requires searching for each instance and manually deleting it. In addition, this leads to confusion as attendees receive a cancellation notice for each instance of the series. These issues can quickly become frustrating to users and disruptive to the organization.

With the release of GroupWise Migrator for Exchange 4.1 (in June), these issues become problems of the past - unless you use a competing solution for your migration  .

GroupWise Migrator for Exchange now includes advanced technology to convert recurring and custom recurring meetings from GroupWise into equivalent meetings in Exchange. This includes building the recurrence rules required by Exchange, adding exceptions as required, and ensuring all instances of the meetings a linked as part of a recurring series. As a result, users will be able to open and update individual instances or the entire series as if the appointments were created natively in Exchange.

Let the (post) GroupWise migration party begin!

About the Author