Introduction

This article outlines the complete task flow for migrating mailboxes from GroupWise (version 7.0 and later) to On-Premises Microsoft Exchange, versions 2013+.

GroupWise may be running on Windows or Linux.

There are some tools and resources that will make the migration easier. We suggest reading through the following information and linked guides before beginning your migration. 

First migration?

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

Exchange questions and troubleshooting

Our Exchange Mailbox FAQ, Exchange Migration Setup and Planning, and Exchange Mailbox Migration Troubleshooting guides contain a number of common questions and concerns, along with more information, guidance, and steps to resolve issues such as throttling.

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. 

The maximum individual file size that MigrationWiz can support is 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, 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.

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.

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

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

1. Set up user accounts.
2. Create an admin account for migration that has full access permissions to all mailboxes.
3. Set up a remote PowerShell session with Exchange 2010+.

Grant access

To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz

In the PowerShell script above, change the -User account to match the name of the admin account that was set up for migration.

Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.

Disable Throttling

Disable throttling against the admin account.

To disable all throttling parameters for an admin account called "MigrationWiz":

1. Open the Exchange Management Shell.
2. Type the following command and press Enter.

   New-ThrottlingPolicy MigrationWizPolicy

3. Type the following command and press Enter.

   Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

4. Type the following command and press Enter.

   Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

Verify mailbox accessibility using EWS

1. Browse to https://login.microsoftonline.com.
2. Log in as admin email address.
3. Enter the exact same password as specified in MigrationWiz.
4. Enter the Admin.
5. Click on Users, then Active Users.
6. Search for users entered in MigrationWiz to make sure the admin email address and the end user´s email address specified in MigrationWiz are not misspelled by searching for them.
7. Make sure all users have licenses assigned to them. All mailboxes on the Source system are created as mail users in Office 365. When you assign a license to the mail user, it will become a mailbox user. We need a mailbox at the Destination in order to be able to migrate data.
8. If you are not using impersonation, make sure the admin account has a license assigned to it. This can even be a temporary trial license.

Large Items

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.

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 the endpoint.
   4. Select type GroupWise 7+
   5. Enter the GroupWise SOAP URL.
   6. 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.
   7. 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 Exchange Server 2013+.
   5. Enter the OWA URL.
   6. Click the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.
   7. 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 Autodiscover or Bulk Add option.

Autodiscover will add all users found on the source tenant. This can then be edited in the project to remove users not being migrated. All users will be added with the source and destination email addresses set to match the source email. This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend 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.

Add Advanced Options

Go to Support Options and add:

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

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.

Request Statistics

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