Google Workspaces Gmail

Learn how to connect to a Google Workspace Gmail Account

Introduction

Connecting to Google Workspaces for Mailbox migrations is fast to set up and fully supported in Movebot. Movebot uses the Google API with Delegate API Access.

Currently, we do not support native API connections for personal Gmail. To connect to personal Gmail accounts, use the IMAP connector.

Connecting to Google Workspaces by Delegate access provides access to User Data and Shared Drives in the Google Workspace Domain and full support for migrating Drive content.

Requirements

To connect Movebot to Google Workspace Gmail, you will need:

• To have a Google Workspaces Administrator Account

• To be familiar with the Google Admin Center

Configuration Steps

1. Login to Movebot and create a new project or task

2. When configuring the source or destination, choose to Create new Connection

3. Select Google Workspaces Gmail from the list of available connections and set the connection name

4. Provide an email address for an administrator account.

5. Provide the primary domain for your Google Workspace tenant

6. Click "Create Service Account"

7. Copy the identifier for the service account (created as part of the process above)

8. Login to Google Admin - admin.google.com

9. Search for "API Controls" in Google Admin

10. Click "Manage Domain Wide Delegation"

11. Click Add New

12. Provide the "client id" copied from Movebot as the client id

13. Provide the session scopes, (copy-paste from below)

https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/gmail.insert, https://www.googleapis.com/auth/gmail.labels, https://www.googleapis.com/auth/gmail.modify, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.directory.user.security, https://www.googleapis.com/auth/contacts, https://www.googleapis.com/auth/calendar

1. Save the new client connection in Google and return to Movebot

2. Click Save and Test connection in Movebot

3. If the connection has succeeded, you can continue

Common Errors

Movebot supports Google Workspace Mail migrations, including user mailboxes and calendar events. Below are common errors and frequently asked questions related to GWS Mail.

Error: Calendar Event Failure (attendees-mapping-required-error)

Cause: Event attendee mapping is missing for calendar migration.

Resolution: You must configure mapping rules for event attendees in Step 4 of your project settings. Without this, calendar events will not be migrated.

Error: Authentication Failed (invalid-credentials)

Cause: The required scopes for Google Domain Delegation are missing or misconfigured.

Resolution: Review your domain delegation setup and ensure all necessary scopes are assigned correctly.Review the documentation.

Frequently Asked Questions

How do I handle the cutover?

Movebot simplifies cutover using delta migrations. You can migrate while users are active, then run a final delta to capture any changes after they stop using the source—minimizing downtime.

If your domain changes during cutover, use "Remap Domains for Cutover" from the Run Action menu. This allows you to specify the old and new domains for source/destination mailboxes, ensuring mappings remain accurate. After remapping, you can continue running delta migrations post-cutover.

Is it possible to migrate between two existing Google Workspace tenants using Movebot?

Answer: Yes. Movebot supports bi-directional, tenant-to-tenant migrations between Google Workspace environments.

How do I transfer one specific folder within a mailbox?

Answer: Use the CSV Import feature to migrate the specific folder. Example:

source,destination /mailbox:[e-mail]/@MAIL/Important Mail,/mailbox:[e-mail]/@MAIL Learn more.

How does Movebot handle messages tagged with multiple labels when migrating into Microsoft?

Answer: Movebot creates a separate folder in Microsoft for each label from Google. If a message has multiple labels, a separate copy will appear in each corresponding folder.

How can I migrate a mailbox larger than 100GB into Microsoft using the Online Archive feature?

Answer:

1. Add a content exclusion rule in Step 6 of your project settings to ignore mail received within the last year.

2. Run a full migration.

3. Allow Microsoft’s automatic archiving to move older content into the Online Archive.

4. Adjust your exclusion rule to ignore mail older than one year.

How can I migrate only mail that was received before a specific date?

Answer: In your project settings, add a content exclusion rule using "Files/Objects modified after UTC time" to filter messages received after the specified date.

Once I've migrated historical mail, can I migrate only mail received after a certain date?

Answer: Yes. Select "Start Delta Migration" from the launch menu and choose the desired timeframe for the delta to include only newer mail.

Migrated calendar events are missing Google Meet links. Why?

Answer: This is expected behaviour. Google Meet links are tenant-specific and cannot be transferred between environments. Events will be migrated without their original meeting links.

Does Movebot support merging multiple mail accounts into a single mailbox?

Answer: Yes. You can use a CSV import to map multiple source mailboxes into a single destination mailbox, organizing each into its own sub-folder.

Make sure to check "Migrate folder contents" when importing the CSV.

Example: source,destination /mailbox:[e-mail]/@MAIL,/mailbox:[e-mail]/@MAIL/source-one/mailbox:[e-mail]/@MAIL,/mailbox:[e-mail]/@MAIL/source-two/mailbox:[e-mail]/@MAIL,/mailbox:[e-mail]/@MAIL/source-three

Learn more.

Supported Features

Movebot has comprehensive support for Google Workspaces and is well-maintained.

Feature	Supported in Movebot
Email Messages and Folders	Fully Supported
Private Calendars	Fully Supported
Shared Calendars	Fully Supported
Contacts	Fully Supported

Tags: googleworkspaces_gmail