Google Workspace Connector Configuration Guide
Complete guide to configuring Google Workspace (G Suite) connectors in Cloudiway. Learn about service accounts, domain-wide delegation, OAuth scopes, and migration setup.
Overview
The Google Workspace connector enables Cloudiway to access your Google environment for migration operations. Whether you're migrating emails, files, sites, or chat data, proper connector configuration is essential for a successful migration.
This guide covers creating the connector, choosing between Cloudiway's predefined service account or your own custom service account, and configuring domain-wide delegation in Google Admin Console.
Creating the Connector
Navigate to Connectors
Go to Connectors → New in the Cloudiway platform.
Select Google Workspace
Choose "Google Workspace" (or "G Suite") as the connector type.
Configure Direction
Specify whether this connector is a source or target for your migration.
Select Products
Choose which migration products to enable (Mail, Drive, Sites, Chat, Groups).
Service Account Options
Cloudiway uses a service account to authenticate with Google APIs. You have two options:
Cloudiway's Predefined Account
Use Cloudiway's standard service account for quick setup with no additional configuration.
114818336788408865729 - Fastest setup
- No service account creation needed
Custom Service Account
Create your own service account in Google Cloud Console for complete control.
- Full control over permissions
- Organization-specific requirements
Which Should I Choose?
Configuration Fields
Superadmin Recommended
Domain-Wide Delegation Setup
After creating the connector, you must authorize API access in Google Admin Console:
Access Google Admin Console
Go to admin.google.com and sign in with a superadmin account.
Navigate to API Controls
Go to Security → Access and Data Control → API Controls.
Manage Domain-Wide Delegation
Select "Manage Domain Wide Delegation" at the bottom of the page.
Add New Client
Click "Add new" and enter the Client ID (Cloudiway's or your custom one).
Add OAuth Scopes
Paste the required OAuth scopes for your migration type (see below).
OAuth Scopes
Different migration types require different OAuth scopes. Each scope must be separated by a comma.
Gmail / Mail Migration Scopes
https://mail.google.com/,
https://www.googleapis.com/auth/calendar,
https://www.googleapis.com/auth/contacts,
https://www.googleapis.com/auth/tasks,
https://www.googleapis.com/auth/admin.directory.user.readonly
Google Drive Migration Scopes
https://www.googleapis.com/auth/drive,
https://www.googleapis.com/auth/admin.directory.user.readonly,
https://www.googleapis.com/auth/admin.directory.group.readonly
Google Sites Migration Scopes
https://www.googleapis.com/auth/drive,
https://www.googleapis.com/auth/sites,
https://www.googleapis.com/auth/admin.directory.user.readonly
Google Chat Migration Scopes
https://www.googleapis.com/auth/chat.spaces.readonly,
https://www.googleapis.com/auth/chat.messages.readonly,
https://www.googleapis.com/auth/chat.memberships.readonly,
https://www.googleapis.com/auth/admin.directory.user.readonly
Google Groups Migration Scopes
https://www.googleapis.com/auth/admin.directory.group.readonly,
https://www.googleapis.com/auth/admin.directory.group.member.readonly,
https://www.googleapis.com/auth/apps.groups.migration
Scope Formatting
Related Articles
Was this article helpful?
Let us know if you found what you were looking for.