1. What is the maximum attachment size allowed by the Destination system? 
• ​Most email systems impose size limits. For example, if the Destination system has a 30MB limit, any item/attachment larger than 30MB will fail to migrate.
2. What is the connection timeout for the Source and Destination system? 
• ​​For security reasons, most email systems close opened connections after a predetermined amount of time. For example, if the Destination system only has 512Kbps of network bandwidth and closes connections after 30 seconds, we may be unable to transfer large items/attachments before the connection is closed.

MigrationWiz will automatically make multiple attempts to migrate large items. Upon completion of a migration, you may resubmit it in error retry mode to try to migrate failed items. This is always free of charge.:

When migrating from or to Office 365 use the steps provided here to increase the Max Send and Max Recieve quotas, Change message size limits in Office 365.

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, or changing categories, see MigrationWiz - Licenses.

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 (if supported) or 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:

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

Request Statistics

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