Home /Platform Considerations

Google Workspace / Gmail Considerations

The following considerations should be understood when migrating to or fromGoogle Workspace or Gmail.

Google Workspace Authentication

To migrate bulk accounts to or from Google Workspace (formerly called G Suite),you will need to set up a Google Service Account. You will grant permissionto a service account to access your Google Workspace data, allowing you toexecute an efficient migration.

Follow these directions to create a Google Service Account:

• Create a Google Service Account

Single-user authentication

To migrate a single mailbox (or only a few mailboxes) without usage of a ServiceAccount, you will need to use end-user credentials (email address and password)for each account you migrate.

• Migrate individual accounts with end-user authentication.

Migrate from Google Vault

If you are migrating data from Google Vault, follow these steps to modify yourGoogle Service Account and enable Advanced Custom Options in Transend MigrationConsole.

• Migrate from Google Vault

Migrate mail into Google Groups/Collaborative Inboxes

If you are migrating email intoGoogle Groups (Collaborative Inboxes){target=”_blank”}, customize your configuration and allowed scopes to supportthe migration.

• Migrate to Google Groups (Collaborative Inboxes)

Multi-party approval required for domain-wide delegation

Google added domain-wide delegation to theMulti-party approval{target=”_blank”} feature, which requires one Super Admin to approve theactions of another. If Multi-party approval is enabled for your organization,editing scopes or deleting domain-wide delegation for a client app requiresapproval from another super admin.

• Set up domain-wide delegation{target=”_blank”}

Snoozed messages

When migrating Snoozed messages between Google Workspace or Gmail accounts, bydefault all Snoozed messages will migrate into a folder named Snoozed Mailin the target mailbox.