Open-Xchange to On-Premises Migration Guide
- This is the complete onboarding task flow for migrating mailboxes from Open-Xchange to On-Premises Exchange.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- 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 requires licenses to be purchased before it can be used. Refer to Scenario 2 in KB004875 to read why it is recommended (but not mandatory).
Prepare the Source Environment
- Test mailbox access.
- Make sure the necessary ports are opened in order to connect to the Open-Xchange server.
Prepare the Destination Environment
- Set up user accounts.
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
Set up a remote PowerShell session with Exchange 2010+. KB005111
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 PowerScript 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 against the admin account. Refer to Option 1 in KB004945
If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:
Verify mailbox accessibility using EWS. KB004304
- Increase maximum accepted content length. KB004609
- Increase maximum receive message size. KB004532
- Increase maximum accepted request length. This is only valid if your Destination server is running Exchange 2007. KB004610
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select Open-Xchange.
Enter the URL.
- For the Destination endpoint:
Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
Enter the OWA URL KB004392
Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare The Destination Environment of this guide.
- Purchase licenses. From your MSPComplete dashboard, click on Purchase > Mailbox Migration > select MigrationWiz-Mailbox and enter the number of licenses you wish to purchase. Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro Bundle). KB004647
- 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 video
- Via email. KB005411
- Launch DeploymentPro.
Go to All Products > DeploymentPro and follow the prompts to launch.
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.
Configure the customer DeploymentPro module:
- Enter the Domain.
- Select the Source endpoint.
- Checkmark the Auto-populate box.
- 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.
- Save and continue.
Activate DeploymentPro module for users.
Schedule the profile cutover date.
On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.
Watch this video to see a walk-through of the steps below.
Create the Mailbox Migration project. KB004380
Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
Set the Project Advanced Options. KB004834
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
Run Verify Credentials. KB004511
Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
Pre-Stage pass: Select the users > Click on 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 on Start Migration. KB004938
MX Record Cutover. Change over the MX records on the DNS provider's portal. Also include the AutoDiscover (CName) setting.
Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
Run Retry Errors. KB004658
Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
If problems persist, contact Support. KB004529
If you are 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.
Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626
- The following options are the most valuable for this migration scenario:
- Set Maximum concurrent migrations. We recommend setting this to a very low value, such as 5, to ensure that server utilization does not go above 80%. If the Source Open-Xchange server is running low on resources, it can result in email migrated as blank. 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.