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 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 to scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.

DeploymentPro & DMA

The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users, which is only necessary if end users are using Microsoft Outlook as their email client. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro. 

DeploymentPro currently can only officially be used with migration projects where Office 365 is the Destination and is not fully supported for Exchange at this time. If using DeploymentPro with Exchange (either On-Premises or Hosted) as a Destination, then a Proof of Concept should be run first. We do recommend using DeploymentPro in this scenario.

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.

Exchange environments can have complex AutoDiscover settings, along with UPN and SMTP address mismatches, which can require troubleshooting and reconfiguration before DeploymentPro can be made to work against such environments.

The DeploymentPro Guide and DeploymentPro FAQ will guide you through the proof of concept, as well as any other DeploymentPro questions, while the DMA Installation and Introduction to DMA articles provide resources and guidance on DMA.

Office 365 questions and troubleshooting

For questions about Office 365 migrations, visit our Office 365 Mailbox Migrations FAQ.

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

Set Up User Accounts

Set up user accounts on the destination Office 365 tenant and assign licenses. These can be created in several ways. (The following links are to external articles.)

Manually, one at a time.

By bulk import, via CSV file

By PowerShell script

Create an Administrator Account

Create an administrator account in Office 365 to be used for migration or use the global admin account for the tenant. The administrator account must have either full access to the user mailboxes or be granted impersonation rights. We recommend using impersonation as it will help reduce the likelihood of the migration being throttled by Microsoft. For specific steps to set impersonation manually, follow the steps in Prepare the Source.

Test Administrator Access

Test that the administrator can access user mailboxes.
Test access to the tenantname.onmicrosoft.com addresses, not to the domainname.com addresses. Make sure that the tenantname.onmicrosoft.com account is attached to each mailbox in Office 365. By default, it should be attached, but if not, it will need to be added as an alias to each account. This can be done through the Office 365 admin portal or via PowerShell scripts. 

Prepare the tenant to send and receive large mail items

Increase Message Size Limits

This is a two-step process. The reason for this is that if the message size limits of Exchange are increased, the IIS limits will also have to be increased to allow increased payloads. There are other non-standard settings that can also cause size restrictions for the IIS or EWS connections, but we are unable to troubleshoot or identify specific environment restrictions outside of these settings.

To display current message size limits:

  1. Open the Exchange Management Shell.
  2. Enter the following commands:

Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
Get-SendConnector | Format-List -Property Identity, MaxMessageSize
Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
Get-MailBox | Format-List -Property PrimarySmtpAddress, MaxSendSize, MaxReceiveSize

To increase message size limits on the Exchange Server:

  1. Open the Exchange Management Shell.
  2. Enter the following commands:

Set-TransportConfig -MaxReceiveSize 150MB -MaxSendSize 150MB
Get-SendConnector | Set-SendConnector -MaxMessageSize 150MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 150MB
Get-Mailbox | Set-Mailbox -MaxSendSize 150MB -MaxReceiveSize 150MB

 

Increase IIS Limits to Allow Accepting Payloads

There are three limits that should be increased in IIS:

  • maxRequestLength
  • maxAllowedContentLength
  • maxReceivedMessageSize

Follow these steps to increase the Exchange message size limits on your client access server:

  1. OpenWindows Explorer.
  2. Navigate to %ExchangeInstallPath%FrontEnd\HttpProxy\ews\
  3. Open the file Web.Config in a text editor, such as Notepad.
  4. Find the XML tag starting with for each change.
  5. Change the existing value to maxRequestLength="200000" -- this occurs in one place in the Web.Config file.
  6. Change the existing values to maxAllowedContentLength="200000000" -- this occurs one place in the Web.Config file.
  7. Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
    For example:
    <httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Anonymous" maxBufferSize="81920" transferMode="Streamed" />
    <httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Basic" maxBufferSize="81920" transferMode="Streamed" />
    etc.
  8. If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
  9. Save the file.
  10. IIS Reset is not needed, web.config changes are picked up by the next connection.

Follow these steps to increase the Exchange message size limits on your mailbox server:

  1. OpenWindows Explorer.
  2. Navigate to %ExchangeInstallPath%ClientAccess\exchweb\ews\
  3. Open the file Web.Config in a text editor, such as Notepad.
  4. Find the XML tag starting with for each change.
  5. Change the existing value to maxRequestLength="200000" -- this occurs in one place in the Web.Config file.
  6. Change the existing values to maxAllowedContentLength="200000000" -- this occurs one place in the Web.Config file.
  7. Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
  8. If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
  9. Save the file.
  10. IIS Reset is not needed, web.config changes are picked up by the next connection.
Increase Maximum Accepted Content Length

You may increase the maximum accepted content length by following these directions:

  1. Open Windows Explorer.
  2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
  3. Open the file Web.Config in a text editor such as Notepad.
  4. Go to the end of the file.
  5. Insert or edit the following XML code before the </configuration> tag:

    <system.webServer>
    <security>
    <requestFiltering>
    <requestLimits maxAllowedContentLength="104857600" />
    </requestFiltering>
    </security>
    </system.webServer>

If XML code is already present in the Web.Config file, edit it to match what is shown above.

Sample Web.Config before changes:

<configuration>
<system.web>
...
...
</system.web>
</configuration>

Sample Web.Config after changes:

<configuration>
<system.web>
...
...
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="104857600" />
</requestFiltering>
</security>
</system.webServer>
</configuration>

 

Increase Maximum Received Message Size

If you are running IIS7 and Windows 2008, you may need to increase WCF settings:

  1. Open Windows Explorer.
  2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
  3. Open the file Web.Config in a text editor like Notepad.
  4. Find all XML tags starting with maxReceivedMessageSize=
  5. Change existing values to maxReceivedMessageSize="104857600"
  6. Save the file.
  7. Open a Command Prompt (cmd.exe).
  8. Type: cd %windir%\system32\inetsrv
  9. Type: appcmd.exe set config "Default Web Site/ews" -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600
  10. Run: iisreset

 

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.

If you have more questions about licensing, including redeeming coupons, requesting refunds, or changing categories, see MigrationWiz - Licenses.

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.

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

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. 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 endpoint
    4. Select type Office 365
    5. Fill in the required fields.
    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 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.

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

​The Autodiscover process within MigrationWiz can be used to discover items from the Source environment, so that they can be imported into your projects.

There are few requirements in order for this to work:

  • The Source has to be Exchange 2007 or later.
  • The endpoint on the Source needs to use admin credentials.
  • For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
  • The admin mailbox must be listed in the public Global Address List (GAL).

One additional item to note here is that there is not a way to restrict the IP addresses that the connection will come from.  This means that the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using on of the other available options.

Autodiscover of items will not work while using Modern Authentication

Autodiscovery exposes the following items:

  • For mailbox migration, autodiscovery will list all mailboxes at the Source.

Steps to Run Autodiscover

  1. Navigate to the project you want to import users into.

  2. Ensure that you have created an endpoint for the source project.

  3. Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.

  4. Once discovered, click on the Import button, to import the items into your MigrationWiz project.

Add Advanced Options

Go to Support Options and add:

  • Set to use impersonation at Destination. Check the Use impersonation at Destination box. 
  • 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.

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.

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 DeploymentPro is not being used, users must now create new Outlook profiles, set up their signatures again, and reattach any PST files attached to their previous profile. 

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