Overview:

Mail migration scope
Pre-migration configuration
Use the Cloudiway platform to migrate your mail
Troubleshooting

For more information about security, please refer to this article. And, about migration performance, this article.

1. Mail migration scope

1.1. What can be migrated?

When migrating from G Suite to G Suite, all the following mail-related items can be migrated:

Emails
Contacts
Calendars
Secondary Calendars
Labels
Delegations
Rooms and resources
Archives (each mailbox requires one separate archive license)
Tasks

1.2. Considerations

Migration takes place between existing mailboxes. This means that mailboxes must exist in the target at the time of migration. Before starting a migration, please ensure that all mailboxes to be migrated have had their target mailbox created in the target domain (steps are included in this guide).

1.3. Audience

This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.

Although we provide support for our own products, we do not provide support for third-party products such as PowerShell or server administration of Google or Exchange.

If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contactable via presales@cloudiway.com. This will ensure a fast, cost-effective, and stress-free implementation.

2. Pre-migration configuration

2.1. Before you start

Before you start, you will need to ensure you have the details outlined in the following table.

Name	Description	Location
Cloudiway login	Stores details and provides communication between the systems you already use.	https://apps.cloudiway.com
Knowledge base access	Our extensive knowledge base is always accessible, with videos, troubleshooting tools, samples and more.	https://kb.cloudiway.com
G Suite API console	Required to enable APIs and to download the G Suite private key. This can be accessed via your Google Admin account.	https://console.developers.google.com
Google Admin console	The Admin console is where administrators manage Google services for people in an organization.	https://admin.google.com

2.2. G Suite — Set permissions for the service account

1. Go to https://admin.google.com and log in with your Super Admin console credentials
2. Click on Security, then Advanced settings (you might need to click on Show more to see this)
3. Click on API Permissions
4. Click MANAGE DOMAIN WIDE DELEGATION, then Add New
5. In the Client ID: paste 114818336788408865729
6. Add the following scope into the OAuth Scopes (comma-delimited) field:

https://www.googleapis.com/auth/admin.directory.resource.calendar.readonly,
https://www.googleapis.com/auth/calendar,
https://www.googleapis.com/auth/gmail.labels,
https://www.googleapis.com/auth/tasks.readonly,
https://www.googleapis.com/auth/contacts.readonly,
https://www.googleapis.com/auth/gmail.imap_admin,
https://www.googleapis.com/auth/gmail.readonly,
https://www.googleapis.com/auth/admin.directory.user.readonly

7. Click on the Authorize button

NOTE: 1. Each scope must be separated by a comma.
2. Some scopes require slashes (/) at the end and others don’t: please use the above strings.
3. If you add another scope later, existing scopes will be removed: you need to add the whole list at the same time.
4. The last scope “admin.directory.user.readonly” is required only if you want to import users.

Regarding your other G Suite account, the process is relatively the same except the scope:

https://www.googleapis.com/auth/admin.directory.resource.calendar,
https://www.googleapis.com/auth/calendar,
https://www.googleapis.com/auth/gmail.labels,
https://www.googleapis.com/auth/tasks,
https://www.googleapis.com/auth/gmail.insert,
https://www.googleapis.com/auth/gmail.readonly,
https://www.googleapis.com/auth/contacts,
https://www.googleapis.com/auth/gmail.imap_admin

3. Use the Cloudiway platform to migrate your mail

3.1. Create your G Suite source connector

For Cloudiway to migrate your email, it needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors, which are configured on apps.cloudiway.com. You will need to set up a connector for each source tenant you wish to migrate and each target tenant that mail should be migrated to. Follow the steps below to configure a G Suite source connector.

From your browser, go to https://apps.cloudiway.com and login
Click on Mail Migration on the left, then Sources
Click on the + New option at the bottom of the screen
Click on Google Gmail and type a meaningful name in Connector name
Click on the Create button
Click on the Save button at the bottom of the screen Your source connector has now been created.

3.2. Create your G Suite target connector

With the source connector now configured on the Cloudiway platform, it’s time to create and configure the target connector. Use the same process to create your target connector.

3.3. Configure the global settings for migration

Now that you have set up at least one source and target connector, you’re ready to configure your global settings. Using the Cloudiway platform, this is simply a matter of selecting what you want to migrate.

By default, the global migration settings are configured to migrate everything but the Trash folder. You can toggle these from the Global Settings option on the Cloudiway platform. You can also specify which emails to migrate according to their date and timestamp (in UTC).

Most of the options are self-explanatory. The Convert Email Address option needs further explanation. When activated, this option rewrites email addresses found in the header and replaces source email addresses with their corresponding target email addresses.

For example, if Bob sends an email to his colleague to Chloe from his source address bob@source.com to chloe@source.com and a week later, after migration, chloe@target.com replies to Bob, the Cloudiway platform has already updated SMTP header in Bob’s original email in her inbox, so her reply will be sent to bob@target.com.

For migrations where the only email address change is the domain name (such as Bob’s email address above), the Cloudiway platform uses the domain name defined in the target connector to convert source email addresses.

For migrations where both the domain name and the username change (for example, bob@source.com becomes newbob@target.com), the Cloudiway platform already uses a mapping table to link each user. This mapping table is also used by the Convert Email Addresses option in this situation. Therefore, it’s important that all users exist in the mapping table before migration begins (this guide contains instructions).

Note that users in the mapping table do not require a license until you’re ready to migrate them. Therefore, you can assign the free ‘No license’ option to all your users prior to migration. Having a complete mapping table is also required if you plan to use Cloudiway’s free/busy calendar tool in conjunction with mail migration.

The Convert Email Address option is switched on by default (and is best left on). Make sure your user list is up to date to benefit from this functionality.

Convert X500 Email Address is not used for the G Suite Migration

From the same Mail Migration area of https://apps.cloudiway.com, click on Global settings by default

The global migration settings are configured to migrate everything but the Trash folder. You can toggle these and change the date and time settings in Edit mode. Please refer to the text above these steps for more information on the Convert Email Addresses option.
Click on the Edit button at the bottom of the screen The grey buttons will turn blue, indicating you can now edit these to your preferred global migration plan.
Update any settings you wish to alter, remembering that time and dates are set to the UTC time zone
Click on the Save button at the bottom of the screen to update your global settings

3.4. Import or create your users

There are a number of ways to add users that you wish to migrate. These include:

CSV file upload;
Cloudiway’s Import Users tool (using IAM); and,
Create a single user.

Regardless, each user will need to be assigned a license type — Trial (limited to 100 MB), Education, Standard, Archive, or No License (used for adding users to your mapping table regardless of migration plans).

3.4.1. Option 1: CSV import

If you have a CSV file of all your users, you can upload the file to Cloudiway. The file must have the following fields in the header row:

FirstName;LastName;SourceEmail;TargetEmail;BatchName

Note that many browsers limit CSV file uploads to 5000 lines, so files larger than that should be split up and uploaded separately. Data already uploaded will not be overwritten, so you can upload as many files as required.

The BatchName field can be left blank. If required, you can use this field to name different batches so they can be run in a certain order. A sample CSV file is available for download during the steps outlined below.

Ensure you’re still in the Mail Migration area of apps.cloudiway.com and go to User List
Click on Manage and Upload CSV in the bottom left corner and select Upload CSV
If required, click on Download sample CSV and add your users to the CSV file using the sample headers (FirstName;LastName;SourceEmail;TargetEmail;BatchName)
When you have a complete CSV file with the correct headers, click on the Upload button
Locate your CSV file within your own file system, and double-click on it to select it
Select the appropriate connectors in the Source and Target fields
Select the license type from the License drop-down list
Click on the Upload button.
If the CSV file format is not correct, you will see an error message on your screen:
If you see any error messages, check your CSV file to ensure it has five columns, each with a separator (including the last) and try uploading again
Once the CSV file format is correct, you will see a confirmation message at the top of your screen:
Check your email. When you have received confirmation that the upload has been completed, you can refresh the Cloudiway platform to display your imported users

3.4.2. Option 2: Import Users tool

Cloudiway’s Import Users tool helps you to retrieve users from your source tenant. The functionality works via Identity Access Management. The tool requires you to specify any transformation rules you wish to apply. It will then add new users in the Mail Migration User List view within the Cloudiway platform.

This is an advanced tool that is best used in partnership with Cloudiway consultants. If you are interested in using this option, please get in touch with your Cloudiway contact.

3.4.3. Option 3: Single user creation details

Many of our first-time customers create a single user for testing purposes. This provides a means of watching the migration process without affecting all users. Single users can also be created for migrations affecting just a few users.

Go to the User List of the Mail Migration menu
Click on Manage in the bottom left corner and select Create Single to display the following screen:
Fill in all details for a new user
Click on the Create button
The new user will be added to the Mail Migration / User List screen:
Repeat steps 1 to 4 for any more users you’d like to create

3.5. Recreate your resources (using provisioning)

The Cloudiway platform provides a free resource creation tool to customers performing mail migrations from G Suite to Office 365. Recreate rooms and equipment using the steps below.

From the same Mail Migration area of https://apps.cloudiway.com, click on Global Actions
Click on the Create Rooms & Equipment option to display the following dialogue box:
Select the source that contains the rooms and equipment to be provisioned
Click on the Create button to trigger the process
The dialogue box will disappear and you will receive a confirmation on your screen that the process has begun.
You can watch further progress by refreshing the Global Actions screen, where a progress bar will be displayed during processing, and ‘DONE’ will be displayed when the process is complete.
Click on the User List sub-menu of the Mail Migration area and verify that all resources have been created.

3.6. Activate and monitor your migration

Now that you have performed all the pre-migration steps within your tenants and within Cloudiway, you’re ready to migrate. We recommend you run a test migration on a single user first to check that your configuration produces the outcome you expect.

To start your migration, select the users or batch you wish to migrate and click on the Start button. Your batch will be scheduled and will begin as soon as resources are available. By default, a hundred migrations can be run concurrently per connector.

Don’t forget that Cloudiway migration platform supports delta passes and that migrations are therefore incremental; every time you restart the migration of a mailbox, only items that haven’t already been copied to the target will be migrated. The platform, therefore, does not duplicate items in the target.

3.7. Migrate permissions globally

You can globally migrate permissions for mailboxes through the Cloudiway platform.

NOTE: Once you start the process of setting permissions, it cannot be stopped.

From the same Mail Migration area of https://apps.cloudiway.com, click on Global Actions:
Click on the Migrate Permissions option on the screen to display the following dialog box:
Click on the Set button to trigger the Cloudiway platform into setting permissions on all mailboxes

4. Troubleshooting G Suite to G Suite

Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides and downloads.

Please visit the entire knowledge base here (where you can search for keywords or read through topics): https://kb.cloudiway.com/

The knowledge base also contains information on how you can ask for further support, should you require it.lick on Security, then Advanced settings (you might need to click on Show more to see this)

G Suite to G Suite Migration Guide

1. Mail migration scope

2. Pre-migration configuration

3. Use the Cloudiway platform to migrate your mail

4. Troubleshooting G Suite to G Suite