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

This migration scenario will migrate the Inbox, Folders, and Email items. 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).

GroupWise may be running on Windows or Linux.

There are some tools and resources that will make the migration easier. Before you start your migration, we suggest you read the following information and linked guides. 

First Migration?

We have created a guide on scoping, planning, and managing the migration process. If this is your first migration, we recommend carefully reading this guide.

The MSPComplete section guides you through the DMA use, but for questions and further guidance see our Device Management Agent Installation and Introduction to DMA articles.

MigrationWiz

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 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. 

We are not able to support migrations with two-factor or multifactor authentication. 

The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.

Prepare the Source Environment

Enable the SOAP Endpoint

Enable the SOAP endpoint on each Post Office Agent (POA).

1. Start GroupWise ConsoleOne.
2. Navigate to GroupWise Agent Settings.
3. Checkmark the Enable SOAP option to enable SOAP access.
4. If the Source environment has multiple POAs, you must open a SOAP port (typically 7191) on each POA.

Generate the User List

This can be generated through your GroupWise ConsoleOne portal. GroupWise migrations require both the email address AND the username, e.g., email address = testuser001@mydomain.com AND username = testuser001.

Credentials

1. Create a Trusted Application Key. This is used to migrate from GroupWise using administrative credentials.
2. Use the GroupWise graphical interface to register a Trusted Application key called "MigrationWiz".
3. Ensure that the application name is set to "MigrationWiz."
4. Make a note of the key value for the application key textbox. This will need to be entered under the Source endpoint in MSPComplete.
5. For GroupWise 8 Support Pack 1 or later, use the graphical user interface tool to register trusted applications.
6. For previous versions, use our command line tool to generate the Trusted Application Key.
   1. Go to the target GroupWise server.
   2. Log in as a GroupWise administrator.
   3. Verify the user has full access to the GroupWise domain folder.
   4. Extract zipped files to a local temporary folder.
   5. Run the EXE with the GroupWise database folder as an argument (ie., GenerateTrustedAppMigrationWizKey.exe C:\Novell\Databases).

Example

• C:\>GenerateTrustedAppMigrationWizKey.exe C:\Novell\Databases
• MigrationWiz Trusted App Key Generator
• Configuring: C:\Novell\Databases
• Key Generated
• Key: 865A15420BA50008B…007BCF0085003000​

If this does not work in your environment

If the command does not work, you can use the NETWIN32.DLL command line tool included in the Novel Netware client. If you get the following error: “The program cannot start because NETWIN32.DLL is missing from your computer. Try reinstalling the program to fix this problem” confirm that:

1. The GroupWise client is installed on the computer.
2. The Novell Netware client is installed on the computer.

If these are both installed, follow the next steps:

1. Go to a Windows machine.
2. Log in as a GroupWise administrator.
3. Mount a drive letter to the remote target GroupWise server (for example, net use X: \\GW-Server\c$ /u:Administrator).
4. Follow the previously outlined steps using X:\Novell\Databases instead.

Prepare the Destination Environment

Create Users on G Suite

Follow the directions from Google to create the users. 

Set up OAuth 2.0 Access

Google is currently updating its UI for some users. The following guide contains steps for both the old and the new UX. Before you begin the process, verify the interface you have.

For reference, we included Screenshots. 

MSPComplete Steps

Create Customer

1. Click the Add button in the top navigation bar.
2. Click the Add Customer button on the All Customers page.
3. Select the appropriate workgroup In the left navigation pane and click All Customers.
4. Click Add Customer.
5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
6. Click Save.
7. Repeat the steps 1 through 4 for each customer you want to add. 

Purchase Licenses

We recommend 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. For questions on licensing, visit MigrationWiz Licenses.

In case, you want to purchase the licenses follow the next steps:

1. Sign in to your BitTitan account. 
2. In the top navigation bar, click Purchase.
3. Click the Select button and choose User Migration Bundle licenses.
4. Enter the number of licenses you want to purchase. Click Buy Now.
5. Enter a Billing address if applicable.
6. Click Next.
7. Review the Order Summary and enter a payment method.
8. Click Place Your Order.

MigrationWiz Steps

Create a Mailbox Migration Project

When there are multiple non-linked Post Office Agents (POAs), you should create multiple Mailbox Migration Projects and match the Source endpoint to the project corresponding to the users on the POA.

1. Click the Go to My Projects button.
2. Click the Create Project button.
3. Click on the type of project that you wish to create. For this migration:

• Mailbox: Mailbox projects are used to migrate the contents of the primary user mailbox from the previous environment to the new environment. Most mailbox migrations can migrate email, calendars, and contacts.

For mailbox migrations, use administrative credentials to access mailboxes. In most migration scenarios, the admin account must have full access rights to the Source mailboxes. 

1. Click Next Step.
2. Enter a Project name and select a Customer.
3. Click Next Step.

Endpoints

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you select an existing endpoint consider only ten endpoints are shown in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created along with any unique spellings or capitalization you may have used.

1. Select a source endpoint or create a new endpoint.
   1. To create a new source endpoint:
   2. Click New.
   3. Name the endpoint.
   4. Select type GroupWise 7+.
   5. It is necessary to add all domains that will be part of the migration on 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.
   6. Enter the GroupWise SOAP URL.
   7. 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.
   8. Click Add.
2. Click Next Step.
3. If there are multiple Post Office Agents (POAs), and they are not linked, create separate Source endpoints for each POA.
4. Select an existing destination endpoint or create a new destination endpoint.
   1. To create a new destination endpoint:
   2. Click New.
   3. Name the endpoint.
   4. Select type G Suite/Gmail.
   5. Enter the administrative email address. This is the account that has an admin access level to the Google admin portal.
   6. Click Add.
5. Click Next Step.
6. Click Save and Go to Summary.

Add Users

Add the user accounts that will be migrated to the project. This may be done in several ways, depending on the size of the project. Steps for each option are in the accordion below, simply click to show the option you select and follow the guidance there.

GroupWise migrations require both the email address AND the username, e.g., email address = testuser001@mydomain.com AND username = testuser001.

Small Migrations

For small migrations, it is easy to add users one at a time using Quick Add. The steps for this are below. 

Larger Migrations

For larger migrations, we recommend either using the  Bulk Add option.

Support Tab

Consider that each Support Option includes the "=" character and is to be entered under the Support tab in the section named Support Options.

Add additional blank fields for new Support Options by clicking on the "+" button. In case you want to delete a field click the trash can icon.

Optional Settings

• FolderMapping="^INBOX/->" Folder mapping maps folders to the root label on the Destination mailboxes, rather than under the inbox/label name. 
• FolderMapping=”^Cabinet->Inbox” In this case, folder mapping maps folders under the cabinet subfolder on GroupWise, to the Inbox on the Destination.

Performance Tab

• 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 30. If the Source server has limited available server resources, we recommend setting this value to a lower value to avoid overwhelming the server with requests.

Run Verify Credentials

1. Open the Project containing items you wish to validate.
2. Select the items you wish to validate.
3. Click the Start button in your dashboard.
4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration.

Run Migration

Pre-Stage pass

1. Select the users you wish to migrate.
2. Click the Start button from the top.
3. Select Pre-Stage Migration.
4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago.
5. Click Start Migration.

MX Record Cutover

Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.

Email end users to let them know what to expect for their Outlook profile reconfiguration. 

Full (Delta) Pass

1. Select the users.
2. Click the Start button from the top.
3. Select Full Migration.
4. Click Start Migration.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Outlook Configuration

If users will be using Microsoft Outlook with G Suite, they will need to follow the instructions here, to download and install G Suite Sync for Outlook and create a new Outlook profile that connects to G Suite.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.