Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - 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 3 (conditional/optional): Configure Microsoft DirSync for ongoing directory coexistence

NOTE: This step applies only if you used Microsoft’s DirSync tool to provision Office 365, and only if you will keep the local AD in addition to Office 365. For any other configuration, skip ahead to step 4.

Refer to Microsoft’s documentation to configure the Microsoft Online Services DirSync tool for regularly scheduled synchronizations between your local, proprietary Active Directory and Office 365. Remember that you might also configure a "two-step" coexistence between GroupWise and Office 365—as described above in step 6 of the Batch Migration Process, for the Set user visibility feature.

Step 4 (optional): Prepare for any future migration

NOTE: Optional (But Recommended) Step: Even if you are certain you will have no need for any future migration, this step is still a good precaution.

In preparation for the possibility of future migration requirements (e.g., archives), you may want to consider (either):

Step 5: Post-migration "cleanup"

To "clean up" after the last user has been migrated:

If you were using SMTP mail coexistence (with or without Quest CMG): Delete any temporary routing MX domains (e.g., This is the temporary subdomain you created in the Pre-Migration Preparations to support routing between GroupWise and Office 365 during the transition. Now that all users have been migrated to Office 365 and inbound traffic is routing directly to Office 365, the mail-forwarding rules and temporary subdomain should no longer be required.
If you no longer need the GroupWise environment: After you have verified GroupWise is inactive, you may take a final backup and decommission the environment.

SSDM (per-desktop) migration

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating