GroupWise to G Suite Migration Guide

Introduction

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.

First migration?

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

The MSPComplete section guides you through the use of DMA, but for questions and further guidance, see our DMA 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 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. 

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

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, it will be necessary to 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.

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:

  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 doesn’t work on your environment:

The command line tool requires the NETWIN32.DLL, which is packed by Novel Netware client. If you get the following error: “The program can’t 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:

  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 UX and the new UX. Be sure to verify which interface you have before beginning the process. Screenshots are included for reference. 

OAuth 2.0 Steps

BitTitan products use OAuth 2.0 to authenticate to G Suite  and utilize the G Suite (IMAP) endpoint in MigrationWiz. This is applicable to both mailbox and document migration projects. In order to obtain access to your G Suite data, it is necessary to add specifically allowed API scopes to the MigrationWiz project.
Notes:

  • These steps must be followed whenever there is a migration project either to or from G Suite that will utilize the G Suite (IMAP) endpoint. For instructions on using the Gmail API endpoint, see  MigrationWiz - Mailbox Migration - Set up Google API for migrating mailboxes.
  • Enabling access is required for both G Suite mailbox and Google Drive document migration projects.
  • Mailbox migration projects require that a G Suite administrator grant access to the BitTitan client ID and scopes listed in this article.
  • Document migration projects require that a G Suite Super administrator grant access to the BitTitan client ID and scopes listed in this article and enable the API access. The steps to do this are included at the bottom of this article.

Steps in the G Suite Admin Console

Complete these steps to grant BitTitan client ID access to the appropriate scopes:

  1. Go to https://admin.google.com and authenticate as a Super Administrator.
  2. Click Security.
    If you do not see the security icon on your admin console home page, you do not have the necessary rights on your account to make these changes. Request Super Administrator access from the customer to implement these changes.
  3. Click Advanced settings.
    Google limits accessing and changing this setting to only G Suite Super Administrator accounts.
  4. You will now have one of two options, depending on whether your tenant has been updated to the new Google API or not. 
  5. Old Google Tenant:

    • Go to the G Suite admin page at google.com
    • Click on Security
    • Click on Advanced Settings
    • Click Manage API Client Access.

    OR If your account shows the latest UI updates from Google, as shown below:New_Google_Admin_APP_Access_Control.JPG

    • Go to the G Suite admin page at google.com
    • Click on Security
    • Click Advanced Settings
    • Under ‘Domain-wide delegation’, click Manage domain-wide delegation
    • On the Manage domain-wide delegation page, click Add new
  6. Click MANAGE DOMAIN WIDE DELEGATION.
  7. Click Add New.
  8. Enter 113321175602709078332 into the Client ID field. 
  9. Enter the following groups of scopes into the OAuth Scopes (comma-delimited) field,
    • G Suite as the Destination (full scopes):
      https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/, https://www.googleapis.com/auth/gmail.settings.sharing, https://www.googleapis.com/auth/gmail.settings.basic
  10. Click Authorize.
    The client name is 113321175602709078332 (make sure there are no leading or trailing spaces, as this may cause the error "URL ends with an invalid top-level domain name."). This will grant BitTitan products access to the appropriate scopes.

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. In the left navigation pane, select the appropriate workgroup and then 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 steps 1 through 4 for each customer you want to add. 

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

To purchase licenses:

  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.

Deploy DMA to users

GPO is the recommended methodology because no end user interaction is required. However, DMA may also be deployed via email, which requires users to manually install it on their computers.

Via GPO
  1. Download the DMA setup file from MSPComplete.
    1. In MSPComplete, click on All Customers from the navigation sidebar. 
    2. Click on the customer name for which you wish to deploy DMA.
    3. On the horizontal menu bar, click Users.
    4. Click Add Users, and then click Add Users via Device Management Agent
    5. On the Add Users via Device Management panel, click Device Management setup file to download the DMA setup file to your local drive. Please note that this file should not be renamed or altered in any way or it could cause issues when DMA is installed. These instructions are more detailed than those listed in the Add Users via Device Management Agent panel. 
  2. Step 2: Create a network share that is accessible to all of your customer’s computers and put the DMA setup file in the share folder.
    1. Log on to the file server as an administrator.
    2. Click Start and search for Server Manager.
    3. Click Server Manager from the search results.
    4. Click File and Storage Services
    5. Click Shares
    6. Next to Shares, click Tasks
    7. Click New Share
    8. Continue through the New Share Wizard prompts until finished, then click Create
    9. Right-click on the new share in Server Manager, and click Open Share
    10. Put the DMA setup file in the share.
    11. Write down the share's network path. This will be needed when creating the scheduled task.
  3. Step 3: Create a Group Policy Object that forces the domain joined computers in a security filter to execute the DMA setup file through a scheduled task.
    1. Log on to the Active Directory Domain Controller as an administrator.
    2. Click Start and search for Group Policy Management.
    3. Click Group Policy Management
    4. Right-click on the desired Active Directory domain, and then click Create a GPO in this domain, and link it here.
    5. Enter a name for the GPO, and then click Ok. By default, the GPO will apply to all users and computers that successfully authenticate to the Active Directory domain.
  4. To narrow the scope of computers that install DMA, select Authenticated Users, and click Remove
    1. To confirm the removal, click Ok.
  5. To add a new security filter, click Add.
    1. Type the name of the security group that the target computers are a member of and click Check names
    2. Click Ok.
  6. Right-click on the new GPO, and then click Edit
    1. In the console tree, under Computer Configuration, click PreferencesControl Panel > Scheduled Tasks.
    2. Right-click Scheduled Tasks and click on New, and then click on Immediate Task (At least Windows 7).
    3. Enter a name and a description for the Scheduled Task.
    4. Click Change User or Group
    5. Type "system" in the Object name text box.
    6. Click Check Names. Make sure that the system object name resolves to NT Authority\System.
    7. Under Security options, click Run whether a user is logged on or not and add a check next to Run with highest privileges.
    8. In the Configure for drop-down menu, select Windows 7, Windows Server 2008 R2
    9. Click the Actions tab
    10. Click on New.
    11. In the Action drop-down menu, select Start a program
    12. In the Programs/script text box, enter the network path for the DMA setup file. If you use the Browse button to find the location of the script, then it will add the path as c:\xxxx. This is incorrect since the script needs to include the UNC path and not the local path. Be sure to replace the c:\ format with the \\servername\sharename\ format.​
    13. If the customer's computers use a proxy, you must add a command line parameter into the Add arguments field to ensure that DMA is able to transmit data through the proxy. Read the How do I deploy the Device Management Agent on computers that use a proxy?​​ article for more information.​
    14. Click Ok.
    15. Click the Conditions
    16. Add a checkmark next to Start only if the following network connection is available, and then select Any connection.
    17. Click Ok
  7. Close Group Policy Management Editor, and then close Group Policy Management.
  8. The DMA setup file will execute on user computers at the next Group Policy refresh, typically every 90 minutes, with a random offset of 0 to 30 minutes.
Via Email

To deploy the BitTitan Device Management Agent (DMA) through email, you ask users to manually install the agent. We recommend installing DMA through a group policy object because it’s automated and non-intrusive.

  1. Click Customers on the navigation sidebar.
  2. Click the customer name for which you wish to deploy DMA.
  3. Click Users.
  4. Add a checkmark next to the user(s) that should receive the email.
  5. Click the Enable Device Management Through Email button.
  6. In the Enable Device Management via Email panel, enter your email address in the Reply-To Address field.
  7. Confirm that all of the users you chose are listed in the To field.
  8. To personalize the email message that the customer's users will receive, type your changes into the message body text box. If the customer's computers use a proxy, you must add instructions to run the DMA installer with command line parameters that ensure DMA is able to transmit data through the proxy.
  9. Click Send Agent Email.
  10. Important: DO NOT change the name of the DMA setup file sent via email, or let users share the file. Each file is only for the user and machine it is sent to.
  11. The customer’s users will receive the email asking them to manually install the agent.​ The users and their computer information will start populating in MSPComplete under the customer’s context soon after the agent is installed and running.

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.

MigrationWiz Steps

Create a Mailbox Migration project

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.

  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 needs to 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 are selecting an existing endpoint, keep in mind that only ten endpoints will show 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 endpoint
    4. Select type GroupWise 7+
    5. 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.
    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 endpoint
    4. Select type G Suite/Gmail
    5. Enter the administrative email address. This is the account that has 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.

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

Quick Add
This option allows you to add items one at a time. You have to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.
Bulk Add

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click on Add .
  4. Click on Bulk Add .
  5. Follow the instructions on the page.

 

Add Advanced Options

Set the Project Advanced Options

Go to Support Options and add:

  • Folder mapping: FolderMapping="^INBOX/->". This will map folders to the root label on the Destination mailboxes, rather than under inbox/label name. 
  • Folder mapping: FolderMapping=”^Cabinet->Inbox”. This will map folders under the cabinet subfolder on GroupWise, to the Inbox on the Destination.
  • 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.

Run Verify Credentials

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click on 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 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.

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

Notify users

Send email to end users to let them know what to expect for their Outlook profile reconfiguration. Samples and screenshots can be found in our DeploymentPro documentation, if you are utilizing that tool. 

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

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