Migrating from Hosted Exchange

Check Provider

When migrating from Hosted Exchange CloudM Migrate has preset configurations for the most popular providers, you can simply select your provider and the server and authentication details will be pre-populated. If your provider is not supported you can enter the details manually, but you will need to obtain the Autodiscover or Direct EWS URL, and authentication method supported.

Setting up Application Impersonation

Alternative Application Impersonation Setup

First login to the Office 365 Exchange Admin Portal. Go to 'permissions' on the left hand side bar and click the + symbol in order to add a new role group. Enter 'CloudMigratorImpersonation' in both the Name and Description fields.

Next, click the + symbol under 'Roles', select ApplicationImpersonation, click 'add' and the click 'OK'.

Next, click the + symbol under 'Members', select your administrator user, click 'add' and then click 'OK'.

Click 'Save' and you will see the impersonation role listen in admin roles. Application impersonation is now set up.

Setting up Delegated Access

Delegated access gives a user account permission to access another. Delegated access must be set up if you are not using an Enterprise plan of Office 365

First login to the Office 365 Exchange Admin Portal. Go to 'recipients' then under 'mailboxes', double-click the user you wish to delegate access to then go to 'Mailbox Delegation' and click the '+' symbol under 'Full Access'

Next, select your administrator user, click 'add' and then click 'OK'

Click 'Save' and your administrator user now has the required access for the migration to occur, repeat this process for all users you wish to migrate.

Office 365 Groups Azure App Registration

The following steps are required to migrate from/to Office 365 Groups.

• Login to the Microsoft Azure portal for your chosen domain.
• Click 'Azure Active Directory'and then'App registrations'

• Click 'New registration'
  • Enter a name for your application (This can be changed at any time).
  • Supported Account Types should be left as the default 'Accounts in this organizational directory only (NAME OF COMPANY)'
  • Redirect URI is not required.
  • Click 'Register'
• On successfully registering your application you will be redirected to the below screen.
• NOTE : Open Notepad and Copy 'Application (client) ID'. This is the 'Client Id' required in the CloudM Migrate configuration.

• Click 'Certificates & secrets'
• 'New client secret'
• Select 'Never'
• Click 'Add'
• Client Secret will be generated and the client secrets table populated like below.
• NOTE : Copy the value generated and paste the value into notepad. This is the 'Client Secret' required in the CloudM Migrate configuration.

• Click 'API Permissions'
• Remove the default 'User.Read' by selecting the row and clicking 'Remove permission'
• Click 'Add a permission', under 'Microsoft APIs' select 'Microsoft Graph'
• Click 'Application Permission'
• Under 'Select Permissions' type the name of the permission you would like to add. Once all added, click 'Grant admin consent for '(Name of company)'

• Directory.Read.All
• Directory.ReadWrite.All
• Group.Read.All
• Sites.ReadWrite.All

• AuditLog.Read.All
• Directory.Read.All
• Group.Read.All
• Group.ReadWrite.All
• Sites.ReadWrite.All

If you have not already done so, create a new configuration item by clicking the plus button and then "create a new configuration to get started".

Select the Hosted Exchange configuration item.

You should also supply a license key here before you continue. If you do not supply a key you will be able to setup and configure CloudM Migrate but will not be able to perform a migration.

To enter this key, hover over the orange gear in the actions column and navigate to "View license" (one icon to the left) and you will be prompted to apply a license. Alternatively, you can click the name of the unlicensed configuration.

Choose Hosted Exchange as the migration source and enter your Hosted Exchange settings into CloudM Migrate and then click next.

If your Hosted Exchange provider is listed, select it from the list of providers and the server details will be populated. If your provider is not listed, select 'My Provider is Not Listed' and enter the below details.

• Autodiscovery Service URL – In order to connect to the correct server, autodiscovery is used to obtain the server information. Input the URL to the autodiscovery service for your domain. The value for your Microsoft Exchange server is like https://yourserver/autodiscover/autodiscover.xml.
• Admin Username – Enter the full email address of your Microsoft Exchange admin user.
• Admin Password – Enter the password of the admin user.
• Domain Name – Enter the domain name you will be migrating from. This should be the Internet domain name, not the local domain name.
• Test User Name – Enter an email address of an active user within your Microsoft Exchange system. This account is used to test connections as in most cases the admin account will not be mailbox enabled.

CloudM Migrate will now perform a small connection test to verify that the details you have entered are correct. If this fails you may have entered something incorrectly. If you are failing to resolve the issue please contact CloudM Support via the chat icon.

Select Google Workspace as your destination platform.

Select where you would like your data to be migrated. If you have purchased Google Workspace for Business or Google Vault you may want to migrate data directly into Google Vault.

To enable Google Vault for your domain, please see the following article: http://support.google.com/vault/bin/answer.py?hl=en&answer=2584132

Enter information for your Google Workspace admin account.

• Domain Name - The domain name you will be migrating from. This should be the Internet domain name, not the local domain name.
• Admin Username - An administrator account for the domain specified, this will usually be an email address for a Super Admin.
• Service Account Email Address - Before attempting to configure CloudM Migrate, you should have created a Google Cloud platform project and created a service account for it. Input the service account's email address in this field.
• Private Key - The file path to the P12 key that was generated and downloaded when creating the OAuth service account.

If you cannot find the private key, go back to Google Cloud Platform service accounts, select your project (if not already selected), use the option button on the right of the service account and click Create Key. Select P12 and download the key file.

Once you have configured the settings, select Next. CloudM Migrate will perform a connection test against your domain to verify that everything has been entered correctly.

Select Office 365 as your destination platform.

Enter information for your O365 admin account.

• Admin Username - The email address of an administrator within your Office 365 environment.
• Admin Password - The password for the administrator account specified earlier.
• Domain Name - The domain name of your Office 365 environment, this might be the part after the @ in your administrator email address. If migrating from several different domains, several migrations will be needed.
• Test Username - A non-admin user who is already present in the system.

CloudM Migrate will perform a connection test against your O365 domain to verify that everything has been entered correctly.

• All users to be migrated in the source tenancy will have a primary SMTP email address ending in their current domain e.g. 'user@company.com'. Check that each of these also has at least one alias. This will be needed later to avoid having to delete users in order to stop mail going to their original mailboxes
• Provision users mailboxes in the target tenancy with their primary SMTP email addresses based on the '.onmicrosoft.com' domain.
• Configure CloudM Migrate with the target domain based on the new tenancy's '.onmicrosoft.com' domain. This will be used for both the bulk migration pass and the delta pass.
• On completion of the delta pass, all the users should have their current primary SMTP address switched to their alias. This will in-effect stop mail from being received and be the start of the mail 'down-time'.
• Remove the 'company.com' domain from all users in the source tenancy. It is essential that no objects remain assigned to this domain otherwise you will not be able to remove the domain from the tenancy.
• Remove the 'company.com' domain from the source tenancy.
• Add the 'company.com' domain to the target tenancy
• Assign the 'company.com' domain to all the users in the target tenancy and make this the primary SMTP email address
• This ends the 'mail down-time' as mail will now successfully flow to the users again in the new tenancy.

CloudM Migrate lets you decide how much content you'd like to migrate to your shiny new system.

If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific address replacements in the respective section of the advanced settings.

For more information on domain and address replacements, see this page.

During the migration process CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.

For more information about this page, please visit the summary page.