The Hosted Exchange application can coexist with the Hosted Exchange module within the same Odin Automation instance, which enables providers that use the module to gradually migrate their Hosted Exchange customer base from the module to the application.
The following must be considered before migration:
- This version of the Hosted Exchange application uses the infrastructure of the Hosted Exchange 2016 module, which includes servers with Microsoft Exchange Server 2016, Odin Automation packages installed on the servers, up to and including the Hosted Exchange 2016 module's resources.
- There is no direct migration path from the Hosted Exchange 2010/2013 module to the Hosted Exchange application. Providers that use the Hosted Exchange 2010/2013 module and want to migrate to the Hosted Exchange application need to first migrate to the Hosted Exchange 2016 module, and then migrate to the Hosted Exchange application.
-
During migration, the module's resources are replaced with the application's resources. Almost every resource of the module has a counterpart in the application, with the following exceptions:
- The application does not have direct counterparts of the following module resources: ActiveSync Access, IMAP4 Access, Outlook Access, Outlook Web Access, and POP3 Access. Instead of the resources, the respective settings of the application's mailbox types can be used.
- The Maximum Allowed Mailbox Size and Maximum Allowed Public Folder Size resources of the Hosted Exchange module are replaced with the respective settings of the application's configuration profiles.
- For the Hosted Exchange module, a subscription can be upgraded so that one Hosted Exchange module resource type is replaced with another Hosted Exchange module resource type without unprovisioning existing resources if both the resource types are based on the same resource class. For instance, if a subscription is upgraded so that a Hosted Exchange Basic / Mailboxes resource type is replaced with a Hosted Exchange Advanced / Mailboxes resource type, all existing mailboxes of the subscription remain on respective Exchange servers. For the Hosted Exchange application, such upgrades are not supported. For instance, if a subscription is upgraded so that a Hosted Exchange Mailbox A resource type is replaced with a Hosted Exchange Mailbox B resource type, where both the resource types are based on the same resource class and intended for the same APS type, all existing mailboxes are removed from respective Exchange servers.
- The module is managed through the Odin Automation XMLRPC API, whereas the application is managed through the APS REST API.
- During migration, customer accounts with Hosted Exchange subscriptions are switched from CCP v1 to UX1 for Customers.
-
The application does not support the following:
- Shared domains
- Linked mailboxes
- Internal relay domains
- Customer Directory Integration
- IDSync through the Odin Automation XMLRPC API
- Creating users whose login emails (or sign-in emails) are based on International Domain Names.
- Creating users and their mailboxes using information provided in a CSV file if the users' login emails are based on International Domain Names.
To learn how to migrate from the Hosted Exchange 2016 module, please refer to the Odin Automation Hosted Exchange Integration Provider's Guide >> Switching Subscriptions from the Hosted Exchange 2016 Module to the Hosted Exchange Application.
To migrate from the Hosted Exchange 2010 module to the Hosted Exchange 2016 module, please use the instructions at https://docs.cloudblue.com/oa/8.0/premium/content/MS-Exchange-Hosting-Guide/Exchange-2010-to-Exchange-2016-Transition.htm.
To migrate from the Hosted Exchange 2013 module to the Hosted Exchange 2016 module, please use the instructions at https://docs.cloudblue.com/oa/8.0/premium/content/MS-Exchange-Hosting-Guide/Transition-2013-2016/Exchange-2013-to-Exchange-2016-Transition.htm.
To learn more about the Hosted Exchange application's APS REST API, please refer to APS REST API.