GroupWise to Office 365 Migration Guide

 

Introduction

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

GroupWise can be running on Windows or Linux.

The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.

  • Note: The steps in this guide for DMA and DeploymentPro are only necessary if end users are using Microsoft Outlook as their email client.

We recommend that you use DeploymentPro to reconfigure the Outlook profiles in this migration scenario if end users are using Microsoft Outlook as their email client.

  • Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

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.

 

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 is 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@Sourcedomain.com AND username = testuser001.
    • 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
    • Single POA
    • 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.
    • Source = GroupWise 8 SP1 or later
    • Source = earlier version than GroupWise 8 SP1

 

Prepare the Destination Environment

  1. Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
  2. Set up accounts on Office 365 and assign licenses. These can be created in several ways:
  3. Prepare the tenant to send and receive large mail items. KB005139

 

MSPComplete Steps

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427
    1. Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select GroupWise 7+
    2. Enter the GroupWise SOAP URL. KB004482
    3. 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 Office 365 > fill in the required fields.
    • 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 either of these options:
    • Via Group Policy Object (GPO).
      Note: This is the recommended methodology because no end user interaction is required. ​KB005412
    • Via email. KB005411

 

DeploymentPro Steps

  1. Launch DeploymentPro.
    1. Go to All Products > DeploymentPro and follow the prompts to launch.
    2. Select a customer from the list by clicking on the customer name.
      Note: The status column will show Enabled when a customer account has had DMA deployed to users.
    3. Configure customer DeploymentPro module:
      1. Enter the Domain.
      2. Select the Destination endpoint.
      3. Checkmark the Auto-populate box.
      4. In the Client Interface Configurations section, upload your company logo and add supporting text.
        Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
      5. Save and continue.
  2. Activate the DeploymentPro module for users.
    1. Either select all users or select individual users.
      Note: is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.
    2. Click the Schedule Cutover button.
  3. Schedule the profile cutover date.
    • Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutover button.
      Notes:
      • The DeploymentPro module will install on user devices immediately and then run silently until this date.
      • The profile cutover date should be set to a date and time that is shortly after MX record cutover.
  4. On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

 

HealthCheck for Office 365 Steps

  1. Go all All Products > Device Management, then click HealthCheck for Office 365 and follow the prompts to launch.
  2. Select a customer from the list by clicking on the customer name.
    Note: The status column will show enabled when a customer account has had DMA deployed.
  3. Review results.
    Note: If any computers have a red X on their row, you should review the detailed results by clicking on the pie chart in the far right-hand part of the row.
  4. Include upgrading action items and costs in your Statement of Work.
  5. Perform remediation steps.

 

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@mining88.com AND username = testuser001.
  3. Set the Project Advanced Options. KB004834
    The following options are the most valuable for this migration scenario:
    • Set to use impersonation at Destination. Check the Use impersonation at Destination box. KB004727
    • Set Maximum concurrent migrations. We recommend setting this to a very low value, such as 10, to ensure that server utilization does not go below 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.
    • Add to Support Options:
      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
  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. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.
  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 not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.
  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