This is the complete onboarding task flow for migrating mailboxes from Open-Xchange to On-Premises Exchange.
Complete each step in the order listed. 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.
DeploymentPro can possibly be used to configure the Outlook profiles, however, it is not officially supported for use with Exchange.
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.
MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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. For more information, visit Project Sharing in MigrationWiz.
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
- 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.
- 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 MigrationWizNotes:
- Disable throttling against the admin account. Refer to Option 1 in KB004945.
- Verify mailbox accessibility using EWS. KB004304
- If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type select Open-Xchange.
- Enter the URL.
- Click Endooints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
- Enter the OWA URL KB004392
- 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.
- For the Source endpoint:
- For the Destination endpoint:
- Via Group Policy Object (GPO).
Note: This is the recommended methodology because no end user interaction is required. KB005412
- Via email. KB005411
- Launch DeploymentPro.
- 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.
- Go to All Products > Device Management, click on DeploymentPro on the far left side 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:
- Activate DeploymentPro module for users.
- Either select all users or select individual users.
Note: You will need to have User Migration Bundle licenses to use DeploymentPro. DeploymentPro standalone licenses are no longer available. KB004647
- Click the Schedule Cutover button.
- 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 the MX record cutover.
- Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutover button.
- Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
- Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
- Set the Project Advanced Options. KB004834
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.