Hosted Exchange: Supported Providers & FAQs

This article addresses FAQs about configuring Hosted Exchange as a source platform for migration in CloudM Migrate.

Q: What Hosted Exchange providers does CloudM Migrate support?

CloudM Migrate has pre-configured settings for the most common Hosted Exchange providers to simplify the migration process. If your provider is on this list, you can select it directly, and the necessary server details will be automatically populated.

Supported Providers:

• 1&1
• AppRiver
• Apptrix
• Claranet
• CobWeb
• Giacom
• GoDaddy
• Intermedia
• MailStreet
• MailStream
• MindShift
• Ozhosting
• Rackspace
• RTW Hosting
• Sherweb
• SilverSky/SoftLayer
• Time Warner Cable
• VAR Dynamics
• WebCentral

Note on GoDaddy: While GoDaddy is supported as a legacy Hosted Exchange provider, they also offer a hosted Microsoft 365 environment. If you are using GoDaddy's Microsoft 365 offering, you can successfully use our standard Microsoft 365 source platform for your migration.

Q: What if my provider isn't on the list?

If your Hosted Exchange provider is not listed, you can still perform a migration from the provider using an alternative source platform.

You may be able to use one of the following options depending on your host's infrastructure:

• Select Microsoft 365 as the source platform.
• Select Microsoft Exchange (2010-2019) as the source platform. (Note: You must confirm the exact Exchange version with your provider).
• Select IMAP, PST Archive, or Mail Archive as the source platform.

Note: Migrating from a different source platform will require a change to be made to your migration license. In such cases, please reach out to our Sales team for assistance.

Q: What is the recommended authentication method for migrating Hosted Exchange mailboxes?

For the supported Hosted providers listed above, CloudM Migrate automatically pre-fills the correct credentials—typically Basic Authentication paired with Application Impersonation.

If you are setting up a custom Exchange 2010-2019 connection, Application Impersonation is the recommended credential method. It allows a single administrator account to securely access and migrate data from multiple user mailboxes without requiring individual user passwords.

Fallback Method: If your specific hosting provider refuses to grant Impersonation rights, Delegated Access should be used. Note that you must grant the designated admin account full access permission to all user mailboxes you plan to migrate.

Understanding Limitations with Unlisted Providers

Migrating from third-party or syndicated hosting providers can be challenging due to strict administrative restrictions. If standard migration platforms fail, it is usually due to the following reasons:

1. Microsoft 365 (Entra ID) Restrictions: Modern M365 migrations require you to register an Application in Azure AD (Entra ID) to grant API access. Hosted providers often block the Global Admin rights necessary for you to create these applications.
2. Exchange 2010-2019 Restrictions: For older Hosted Exchange setups, migrating multiple mailboxes at once seamlessly requires ApplicationImpersonation rights. Multi-tenant providers rarely grant this due to security and architectural concerns.
3. The Fallback - IMAP, PST, or Mail Archives: If your provider blocks API access and refuses Application Impersonation, your final options are migrating via IMAP (which only moves emails and folders, and requires individual app passwords) or utilizing a PST Archive / Mail Archive Export.