GroupWise to G Suite Migration Guide

Introduction

This is the complete onboarding task flow for migrating mailboxes from GroupWise (version 7.0 and later) to G Suite.

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

GroupWise can be running on Windows or Linux.

When migrating from GroupWise to G Suite, MigrationWiz migrates via a Universal Mapper. Due to the limitations of the Universal Mapper, only mail items will be migrated (i.e., no calendar or contacts will be migrated).

  • Note: Here are the specifics on what will be migrated: Inbox, Folders, Email.

The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. It is not required to install DMA for this migration scenario. However, BitTitan will be adding several modules to DMA, and these will be important to power MSPComplete feeds (which will provide further information to you about upsell and cross-sell opportunities).

What items are migrated with MigrationWiz?

MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because we do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Environment

  1. Enable the SOAP endpoint on each Post Office Agent (POA). Start GroupWise ConsoleOne > Navigate to GroupWise Agent Settings > Checkmark the Enable SOAP option to enable SOAP access.
    Note: If the Source environment has multiple POAs, it will be necessary to open a SOAP port (typically 7191) on each POA.
  2. Generate the user list. This can be generated through your GroupWise ConsoleOne portal.
    Note: GroupWise migrations require both the email address AND the username, e.g., email address = testuser001@mydomain.com AND username = testuser001.
    • If there are multiple POAs and they are not linked:
      • You will need to generate a user list for each POA.
      • You will then use these lists to add the users to each MigrationWiz mailbox project.
      • You will create multiple Source endpoints, one for each POA, and include the IP address of the POA as part of the GroupWise SOAP URL, under the MSPComplete section of this guide. It will follow this format: <http or https>://<IP address>:7191/soap
    • If there are multiple POAs and they are linked:
      • You will only need to generate one user list, which should include all users from all POAs.
      • You will then use this list to add the users to a single MigrationWiz mailbox project.
      • You will create only one Source endpoint and include the external IP address of the POA as part of the GroupWise SOAP URL, under the MSPComplete section of this guide. It will follow this format: <http or https>://<IP address>:7191/soap
    • Single POA: If there is only one POA, you will only need to generate one user list and migrate all users from one MigrationWiz mailbox project.
    • Multiple POAs:
  3. Create a Trusted Application Key. This is used to migrate from GroupWise using administrative credentials.

    • Use the GroupWise graphical interface to register a Trusted Application key called "MigrationWiz".
      • Ensure that the application name is set to "MigrationWiz."
      • Make a note of the key value for the application key textbox. This will need to be entered under the Source endpoint in MSPComplete.
    • Use our command line tool to generate the Trusted Application Key.
    • To register a Trusted Application key called "MigrationWiz" using our command line tool, follow the directions in KB004445.
    • If the source is GroupWise 8 SP1 or later
    • If the source is an earlier version than GroupWise 8 SP1

 

Prepare the Destination Environment

  1. Create users on G Suite. Refer to G Suite admin help article here.
  2. Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.
    Notes: If you are migrating to multiple domains, repeat these steps for each domain.

 

MSPComplete Steps

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427
    • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select GroupWise 7+
    • It is necessary to add all domains that will be part of the migration on either the Source or the Destination. This means that, if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, it is important to ensure that both of these are added under “Your Domains” when creating the endpoints. When adding a domain, you need to click the "+" button.

    • Enter the GroupWise SOAP URL. KB004482
    • Click the Provide Credentials radio button, and enter the Trusted Key for the Trusted Application Key that was set up under the "Prepare the Source Environment" section of this guide.
    • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type select G Suite/Gmail.
    • It is necessary to add all domains that will be part of the migration on either the Source or the Destination. This means that, if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, it is important to ensure that both of these are added under “Your Domains” when creating the endpoints. When adding a domain, you need to click the "+" button.

    • Enter the administrative email address.
      Note: This is the account that has admin access level to the Google admin portal.
    • For the Source endpoint:
      Note:
      If there are multiple Post Office Agents (POAs), and they are not linked, create separate Source endpoints for each POA.
    • For the Destination endpoint:
  3. Purchase licenses. We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:
  4. Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by these options:
    • Via Group Policy Object (GPO).
      Note: This is the recommended methodology because no end user interaction is required. KB005412
    • Via email. KB005411

 

MigrationWiz Steps

  1. Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
    Note: If there are multiple Post Office Agents (POAs) that are not linked, you will create multiple Mailbox Migration Projects and match the Source endpoint to the project that corresponds to the users on the POA.
  2. Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
    Note: GroupWise migrations require both the email address AND the username, e.g., email address = testuser001@mydomain.com AND username = testuser001.
  3. Set the Project Advanced Options. KB004834
    • Add folder mapping: FolderMapping="^INBOX/->" under Support/Support options.
      Note: This will map folders to the root label on the Destination mailboxes, rather than under inbox/labelname. KB005068
    • Add folder mapping: FolderMapping=”^Cabinet->Inbox” under Support/Support options.
      Note:
      This will map folders under the cabinet subfolder on GroupWise, to the Inbox on the Destination. KB005793
    • Set Maximum concurrent migrations. We recommend setting this to a very low value, such as 10, to ensure that server utilization does not go above 80%. If the Source server has enough server resources, set this parameter based on the bandwidth guideline of three (3) mailboxes per 1Mbps of bandwidth. Therefore, for example, if there is a 10Mbps connection, we recommend setting the maximum concurrent migrations parameter to be 30. If the Source server has very few available server resources (e.g., it is running low on memory or it has very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
    • The following options are the most valuable for this migration scenario:
  4. Run Verify Credentials. KB004511
  5. Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
  6. Pre-Stage pass: Select the users > Click the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click Start Migration. KB004938
  7. MX Record Cutover. Change over MX records on the DNS provider's portal. Also include the AutoDiscover (CName) setting.
  8. Send email to end users to let them know what to expect for their Outlook profile reconfiguration.
  9. Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. KB004938
  10. Run Retry Errors. KB004658
  11. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
  12. If problems persist, contact Support. KB004529
  13. If users will be using Microsoft Outlook with G Suite, they will need to follow instructions here, to download and install G Suite Sync for Outlook and create a new Outlook profile that connects to G Suite.
  14. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626

 

 

Was this article helpful?
0 out of 0 found this helpful