Google Workspace to Microsoft 365 mail migration user guide
1. Google Workspace to Microsoft 365 mail migration with Cloudiway
Google Workspace to Microsoft 365 mail migration
Cloudiway’s mail migration solution helps businesses perform elaborate technical migrations through a simple SaaS interface. As a result, mail migrations require no additional software installation or overhead, and migrations can be performed securely and quickly.
The Cloudiway new platform is flexible enough to support all types of migration paths. Your migration strategy will depend on your business setup, type, and size.
Whichever migration path you choose, Cloudiway provides all the essential features including license assignment, archive migration, calendar coexistence (Free/Busy scheduling) and contact synchronization (GALSync).
Two of the most common migration strategies are cutover and staged migrations. Cutover strategies involve migrating all mailboxes over a weekend, ready for your users on Monday morning. Staged strategies provide more flexible migration options, as discussed on this page.
Cloudiway’s mail migration solution helps businesses perform elaborate technical migrations through a simple SaaS interface. As a result, mail migrations require no additional software installation or overhead, and migrations can be performed securely and quickly.
The Cloudiway new platform is flexible enough to support all types of migration paths. Your migration strategy will depend on your business setup, type, and size.
Whichever migration path you choose, Cloudiway provides all the essential features including license assignment, archive migration, calendar coexistence (Free/Busy scheduling) and contact synchronization (GALSync).
Two of the most common migration strategies are cutover and staged migrations. Cutover strategies involve migrating all mailboxes over a weekend, ready for your users on Monday morning. Staged strategies provide more flexible migration options, as discussed in the following article.
Cloudiway has developed a number of tools to enable seamless migration for the most intricate migrations. Our supplementary tools include:
Coexistence manages cross-platform communication with no impact on the end-user. It provides a seamless connection between two different remote systems during the migration. For example, a Google user can check the free/busy time of an MS 365 user. It also creates all users as contacts on both sides and keep the address books up to date.
To discuss any of these supplementary tools further, please get in touch with your existing Cloudiway contact.
2. Security
For more information about security, please Check how Cloudiway is handling security.
3. Performance
4. Google Workspace to Microsoft 365 mail migration : scope
4.1. What can be migrated and what are the limitations?
You will find what can be migrated and the limitations from Google Workspace (G Suite) to Office 365 on this page:
G Suite uses labels rather than folders to organize emails, and users can apply multiple labels to a single email. Office 365 mail doesn’t use labels, emails can be stored in only one folder.
When multiple labels are applied to one email, only one label is converted to a folder, for further information, please refer to this article.
4.2. Considerations
Migration takes place between existing mailboxes. This means that before starting a migration, mailboxes must exist in the target at the time of migration (steps are included in this guide).
4.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 this page. This will ensure a fast, cost-effective, and stress-free implementation.
5. Pre-migration configuration
5.1. Before you start
Before you start, you need the following accounts.
| Name | Description | Location |
| Cloudiway | Account to configure the Cloudiway Platform for your migration. | https://portal.cloudiway.com |
| Google Admin | To configure the Google feeds. | https://admin.google.com |
| Office 365 Admin | Used to configure Azure Active Directory Application and associated permissions. | https://aad.portal.azure.com |
5.2. How it works
The product uses IMAP and Google APIs calls to read the source.
Cloudiway uses Exchange Web Services API (EWS) to migrate emails, contacts, and calendars. It uses PowerShell for mailbox permissions,shared, rooms and resources.
Note: all network operations are performed over TLS 1.2.
5.3. Source Prerequisites
5.3.1. Google IMAP Configuration
2. From the Admin console Home page, go to Apps > Google Workspace > Gmail > End User Access
3. Select the organizational unit you want to configure settings for. If you want to configure settings for everyone, select the top-level unit. Or, select one of the child organizational units.
4. Go to POP and IMAP access.
5. Click the pencil “edit” icon.
6. Check Enable IMAP access for all users. And Select Allow any mail client. You do not need to enable POP for Cloudiway tools to work.
7. Save your settings.5.3.2. Google feeds
To perform the migration, you need to configure the permissions (Google feeds).
This article explains how to add the Google feeds:
5.4. Target Prerequisites
5.4.1. Create Target Office 365 Service Account
We recommend creating another Office 365 account (service account) with impersonation privileges dedicated to the migration, that can be deleted once the migration is completed. This migration account is used to access the target mailboxes and to make PowerShell calls when migrating mailbox permissions, shared mailboxes, rooms and equipments. It must be configured with multi-factored authentication (MFA) and SSO (ADFS) turned off. To deactivate MFA on your Office365 migration account (guide: https://help.cloudiway.com/article/deactivate-mfa-on-your-office365-migration-account/).
An Office 365 account can access up to 100 mailboxes concurrently. Therefore, by default, Cloudiway allows you to migrate 100 concurrent users in an Office connector. If you wish to speed up your migration, you should set up additional source Office 365 connectors on the Cloudiway platform and associate different source accounts with admin access to each one. Each source connector will be assigned to the corresponding source connector pool to automatically allocate connectors to 100 users.
5.4.2. Azure Active Directory Application
Target EWS API calls are performed through an Azure Active Directory Application which is granted specific permissions.
You can either create an Azure Active Directory Application manually or let the platform create one for you (if your migration account is global admin). You need to register one app both in the target Azure Active Directories when creating the Office 365 Connector.
Please consult how to create the Azure Active Directory Application and associated permissions.
5.4.3. Create your user mailboxes
Cloudiway migrates between existing user mailboxes and does not provides a tool to provision user mailboxes. Therefore, the user mailboxes must be created prior to the migration. You can set up user accounts on the target Microsoft 365 tenant in several ways. (The following links are to Microsoft documentation.)
5.4.4. Create a partial archive from a normal inbox
Creating a partial archive of emails provides a number of benefits. From a migration perspective, the biggest benefit is reduced bandwidth. End-users who access mail via Outlook have their mailbox locally cached (in .ost file format). After a mail migration, Outlook will download all migrated mailboxes the first time users access their mailboxes. Therefore, if many users are likely to access Outlook at around the same time after migration (for example, if you’ve completed a cutover migration one weekend before staff arrive at 9am Monday morning), your bandwidth might slow down due to a glut of downloads.
This can be avoided by partially migrating data to the online archive. For example, you could choose to migrate all items older than 1 year to a mail archive, which would be performed prior to the final cutover. The data will remain online and accessible from each user’s inbox as an In-Place Archive
folder. The most recent 1 year of emails will be migrated and downloaded when each user first logs in, reducing overall bandwidth usage due to smaller mailbox sizes.
Note: you must ensure that In-Place archiving is switched on within your Exchange Admin center (you can bulk-activate using the instructions on TechNet as https://technet.microsoft.com/enus/library/jj984357(v=exchg.150).aspx).
In-Place archives at the source are treated differently to standard mail and are not migrated by default. You can buy a mail archive quota package to perform an archive migration (see section 7.5.2).
5.4.5. Create your resource mailboxes
Cloudiway provides a tool to provision and migrates resource mailboxes in a separate menu. In the Mail Migration section of the tools, you will see a Room & Equipment option. This tool can be used to discover your resource mailboxes and provision them to the target tenant so you don’t have to do it manually.
More details on how to use this feature can be found here:
5.5. Mapping Table
During the migration, Cloudiway uses a mapping table to perform the conversion of email addresses in email headers, calendar items and mailbox permissions.
Important: the mapping table must be exhaustive, any missing email address will not be converted, and would end up with loss of mailbox permissions, unreplyable emails and broken calendar items. Cloudiway automatically populates this mapping table when source mailboxes are discovered by Get List functionality explained below. However make sure if the mapping table was populated automatically that you are not missing any email address.
6. Use the Cloudiway platform to migrate your Mailboxes
6.1. Create Your Connectors
For Cloudiway to migrate your Mailboxes, it needs to be able to communicate with both your source (GSuite) and target (Office365) domains. To do this, Cloudiway uses connectors. 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 from the page below to configure your connectors:
For large projects, it’s possible to create multiple connectors that will be used in parallel from connector pools. Please contact Cloudiway consulting services if you need to set up such configuration.
6.2. 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.
From the Mails area of https://portal.cloudiway.com, click on Global Settings
Most of the options are self-explanatory.
The Convert Email Address option needs further explanation. The Convert Email Address option is switched on by default (and is best left on). When activated, this option rewrites email addresses found in the email headers, calendar items and mailbox permissions and replaces source email addresses with their corresponding target email addresses in the mapping table. Therefore, it’s important that all users exist in the mapping table before migration begins.
Archive Mails Older Than is to migrate the emails older than specified date and time in the past to the target archive mailbox and Migrate Everything to Archives is to migrate all the emails to the target archive mailbox. See the 7.5.2. Migration to archives section for further information.
Click on the Save button at the bottom of the screen to update your global settings.
6.3. Import or create your users into Cloudiway platform
There are a number of ways to add users that you wish to migrate. These include:
- CSV file import.
- Cloudiway’s mailbox discover tool (Get List).
- 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).
Note that importing users into Cloudiway won’t create the user mailboxes in the target tenant. See 5.7. Create your user mailboxes
6.3.1. Option 1: CSV file 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;SourceRecipientType;TargetRecipientType;BatchName
2. Click on MANAGE and select Import
6.3.2. Option 2: Get List
Cloudiway’s Get List tool helps you to retrieve mailboxes from your source tenant. There are 5 Get List tools corresponding to the different sections:
- User List: to discover only user mailboxes.
- Shared Mailboxes: to discover only shared mailboxes. In Google does not exist the concept of shared mailbox as in Office 365, so user mailboxes with delegate permissions won’t be discovered but you can import them manually to migrate delegate permissions.
- Room Equipment: to discover only resource mailboxes.
- Distribution list: to discover only distribution lists.
- Archive: to discover only Google Vault accounts.
Go to User List, Room & Equipment or Distribution Lists sections and then click on Migration, select Get List.
The tool requires you to enter the Source and Target Pool of connectors.
Then to specify:
- The Matching Rule:
- Mail Exact Match: the source email = the target email (bob.marley@sourcedomain.com > bob.marley@sourcedomain.com)
- Keep Email Prefix Same as Source: only the domain name changed (bob.marley@sourcedomain.com > bob.marley@targetdomain.com)
- FirstName.LastName (i.e. bob.marley@targetdomain.com)
- F.LastName (i.e. b.marley@targetdomain.com)
- FLastName (i.e. bmarley@targetdomain.com)
- LastNameF (i.e. marleyb@targetdomain.com)
- The Target Domain.
It will then add new users to the User List. You can monitor the progress of this task in the User List: Get List Logs.
6.3.3. Option 3: Create a single user
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.
Click on MANAGE > Create User and enter the following details:
For more information regarding the different fields, check out this article. Repeat the process for any more users you’d like to create.
6.4. Activate and monitor your migration
Cloudiway is an incremental migration platform that supports delta passes. Every time you restart the migration of a mailbox, only items that haven’t already been copied to the target will be migrated and for those already migrated items that have been modified in the source will be updated in the target. The platform, therefore, does not duplicate items in the target, just updates them.
The migration strategy usually consists of at least 2 migration passes, one before the cutover and another pass after the cutover:
- 1st migration pass: which migrates the majority of the mailbox. Select mailboxes, click on MIGRATION, then the Start button. Explained below in more detail.
- Cutover: You have to manually remove the domain from the source tenant, attach it to the target tenant and change the MX record in your DNS server. This is not automated by Cloudiway.
- 2nd migration pass, delta pass: which migrates what hasn’t been migrated and updates modified items. Select mailboxes, click on MIGRATION, then the Start button. Explained below in more detail.
- 3rd migration pass, delta pass: 24 hours after cutover you can submit an additional delta pass to make sure no residual email is left behind due to DNS propagation delays. Select mailboxes, click on MIGRATION, then the Start button. Explained below in more detail.
You can submit as many migration passes as you want for 3 months and until consuming the amount of GBs allowed by the assigned licenses but usually, you only need one before the cutover and another after the cutover. Find out more about the delta migration passes:
What a migration pass takes to complete depends on a lot of factors. Find out more about the migration performance:
You can create user batches from the Batches tab to easily group subset of mailboxes. Click on the + icon and enter a batch name:
After creating the different batch, under Users tab, select the users you want to assign to a specific batch, click on BATCH button and Add to Batch:
To start your migration, select the users or batch you wish to migrate.
- For users, under Users tab, select all the users you want to submit and click on MIGRATION, then the Start button.
- For user batch, under Batches tab, select the user batch you want to submit and click on MIGRATION, then the Start button.
Your migrations will be scheduled and will begin as soon as cloud resources are available.
NOTE: When migrating by user batches during a long period of time you may want to enable email forwarders.
For more information, please see this article:
7. Other migration options
7.1. Mailbox permissions migration
You can migrate mailbox permissions for mailboxes through the Cloudiway platform.
Migration of permission isn’t performed during the migration of the mailboxes but through a dedicated job.
The migration of the permissions will migrate permissions on the mailboxes, on the primary and secondary calendars.
If permissions were applied to mail-enabled security group, the mail enable security group must exist at the destination for the permission to be applied correctly.
Click on User List, select the users, go to MIGRATION, then click on Migrate Permissions
NOTE: Once you start the process of permissions migration, it cannot be stopped.
7.2. Resource mailbox migration
From the Rooms & Equipment section under Mail, you can recreate and migrate resource mailboxes from your source tenant to your target tenant.
For more information, please see this article:
7.3. Shared mailbox migration
From the Shared Mailboxes section under Mail, you can manually import user mailboxes and migrate mailbox permissions of user mailboxes being used as Shared mailboxes from your source tenant to your target tenant.
For more information, please see this article:
7.4. Distribution List migration
From the Distribution Lists section under Mail, you can recreate and migrate distribution lists from your source tenant to your target tenant.
For more information, please see this article:
7.5. Archive Migration
7.5.1. Migrate existing archive mailboxes
The Cloudiway platform migrates Google Vault archives, you can refer to the following admin guide:
https://cloudiway.com/documentation/migrate-google-vault-mail-archives/
7.5.2. Migration to archives
The Google mailboxes can be migrated to the Office 365 mailboxes, to the Office 365 archives, or to a mix of both archives or online mailboxes.
Creating a partial archive of emails provides a number of benefits. From a migration perspective, the biggest benefit is reduced bandwidth. End-users who access mail via Outlook have their mailbox locally cached (in .ost file format). After a mail migration, Outlook will download all migrated mailboxes the first time users access their mailboxes.
For example, you could choose to migrate all items older than 30 days to a mail archive, which would be performed prior to the final cutover. The data will remain online and accessible from each user’s inbox as an In-Place Archive. The most recent 30 days of emails will be migrated and downloaded when each user first logs in, reducing overall bandwidth usage due to smaller mailbox sizes.
Note: you must ensure that In-Place archiving is switched on within your Exchange Admin center (you can bulk-activate using the instructions on TechNet as https://technet.microsoft.com/enus/library/jj984357(v=exchg.150).aspx).
In the Cloudiway platform, you can migrate either only old emails or all the emails to the target archive mailbox. So 2 options:
- From the Global Settings section, Archive Mails Older Than is to migrate the emails older than specified date and time in the past to the target archive mailbox. Keep Migrate Everything to Archives disabled.
In this example emails older than April 7 2020 will be migrated to the archive mailbox:
Click on the Save button, when your migration starts, any emails older than the date you specified will be migrated to an In-Place archive. More recent items will be migrated to the target mailbox.
- From the Global Settings section, Migrate Everything to Archives is to migrate all the emails to the target archive mailbox. In the Mail Global Settings, enable Migrate Everything to Archives and all emails will be migrated to the target archive mailbox:
8. Troubleshooting
Cloudiway provides an extensive Help Center, also known as knowledge base, with many resources, including common error messages, guides, and downloads.
Please visit the Help Center here (where you can search for keywords or read through topics): https://help.cloudiway.com/
The Help Center also contains information on how you can ask for further support.
