Migrating from Consumer Gmail – CloudM

The following instructions are designed to assist you in migrating mail from Consumer Gmail.

Please make sure that the following prerequisites are complete before continuing onto the CloudM Migrate setup.

Prerequisites

Consumer Gmail username and password for each account.
Less secure app access should be enabled for each gmail account we're about to use - https://myaccount.google.com/lesssecureapps
In order to connect to the Gmail account, log in to each account in the same web browser. Only the log in action is required, so it is ok to close the tab once logged in and log into the next required account.

Destination Platform Prerequisites - Microsoft 365

These steps should be completed in your Destination environment.

Setting up Application Impersonation

Application Impersonation can be configured for your admin account within CloudM Migrate. Select 'Setup Administrative Permissions' in the Destination Platform Settings page.

Application Impersonation can also be configured manually as below. If Impersonation is not available in your environment, please follow the steps for Delegated Access.

Alternative Application Impersonation Setup

First login to the Microsoft 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 Microsoft 365

First login to the Microsoft 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.

Microsoft 365 Groups Azure App Registration

The following steps are required to migrate from / to Microsoft 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)'

If you have not already done so, please insure that all permissions have been granted by clicking the 'Grant admin consent for (Company name)' button.

Microsoft 365 Groups as a Source

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

Microsoft 365 Groups as a Destination

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

Destination Platform Prerequisites - Google Workspace

These steps should be completed in your Destination environment.

You will be required to set up a Service Account. Please refer to the Setting up the Service Account and enable the APIs within Google Workspace for CloudM Migrate article.

CloudM Migrate Hosted makes migration as simple as possible. The only other prerequisite is the installation of the CloudM Migrate Hosted application. When accessing CloudM Migrate Hosted for the first time, you will be prompted to install the app, simply authorise and you are all set.

Source Platform - Consumer Gmail

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

When migrating from Consumer Gmail, all settings are preconfigured. You simply need to enter user credentials to test.

User Email - A Gmail email address
User Password - The password of the Gmail account

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 Migrate Support.

Destination Platform - Google Workspace

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.

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

If your Google Workspace system is brand new or for any reason the users being migrated have not been created in Google Workspace, CloudM Migrate can create your users for you. Simply go to advanced settings, to the user settings section and enable Create Users.

Select which users to migrate

It's now time to add which users you'd like to migrate.

Unfortunately when migrating mail from Consumer Gmail you will not be able to use the Get Users button from the actions menu. You can manually import users via a CSV file using the Import Users option or simply add them individually via the plus icon.

Selecting a star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user so that their migration can start immediately.

At this point you can choose what to migrate for each user, when migrating from Consumer Gmail you can migrate only mail .

Enter your user's full email address within the Export Name field. If you have already created your Google Workspace users then you will just need to enter their username.

Select how much mail to migrate

CloudM Migrate lets you decide how much mail 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.

Start your migration

We know that you may want to start your migration in the middle of the night, or over the weekend, but we don't expect you to stay up in order to do so. With CloudM Migrate you can decide to schedule exactly when you'd like the migration to occur.

Start the migration.

Review your migration results

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.