All Workloads in One Tool
Email, Drive, Calendar, Contacts, SharePoint, and OneDrive — migrate every workload from the same app. No separate tools, no separate credential sets, no separate progress views to juggle mid-project.
Migrate your entire Google Workspace tenant —
one tool, full control
From
Google Workspace
To
Google Workspace
TenantBridge handles full GWS-to-GWS and M365-to-GWS cross-tenant moves — email, Drive, Calendar, Contacts, and SharePoint — all managed from one unified Migrate view, running entirely on your own machine.
Runs locally, never internet-exposed
All workloads in one tool
Credentials stored encrypted on your machine
Single download, no install dependencies
TenantBridge · Migrate
● Live
Marketing SP → Shared Drive
SharePoint · contoso.sharepoint.com
Running
Email batch · 240 mailboxes
Microsoft 365 → Google Workspace
Running
Eng Shared Drive → Drive
Google Drive · copy
Queued
Calendar sync · 240 users
Microsoft 365 → Google Calendar
Done
Four steps to a full Google Workspace migration
A consistent, predictable path from tenant connection to all jobs running — whether you're moving GWS-to-GWS or M365-to-GWS.
Connect Source and Destination Tenants
Set up connectors for both your source tenant (Microsoft 365 or Google Workspace) and the destination Google Workspace. Credentials are stored encrypted and reused across every project — enter them once, use them everywhere.
Discover Users, Drives, and Sites
Run Discovery to pull the real list of users, Shared Drives, SharePoint sites, and mailboxes from the source tenant. Every item is saved as a snapshot so you're building your migration plan against actual data — not a guess from a spreadsheet.
Map Workloads and Configure Options
Map each user, drive, and site to its destination. Configure domain pairs so cross-tenant email addresses translate correctly. Set per-workload options — date filters for email, permissions apply for files, concurrency limits. Nothing runs until you're ready.
Run All Jobs from a Single Migrate View
Switch to Migrate and see every job — email, Drive, Calendar, Contacts, SharePoint — in one unified table. Start All or start workloads individually. Live progress, current file or message, and error counts update in real time. Job state is saved continuously so restarts are always safe.
Everything needed for a full Google Workspace tenant migration
All workloads, one tool, one Migrate view — email, Drive, Calendar, Contacts, and SharePoint managed from your own machine.
Cross-Tenant Domain Pair Configuration
Configure domain pairs in the Edit Project screen to map user addresses between source and destination tenants. TenantBridge applies these mappings automatically when setting permissions and mapping mailboxes across both sides of a cutover.
GWS-to-GWS Drive Migration
Move Google Shared Drive content between Workspace tenants directly — folder structure preserved, permissions discovery included. The same job engine handles both GWS-to-GWS and M365-to-GWS Drive transfers.
Single Unified Migrate Table
All job types — email batches, SharePoint sites, Drive jobs, Calendar, and Contacts — appear together in the Migrate view. Start, stop, and monitor everything from one place without switching screens.
Discovery Before Mapping — Real Data, Not Guesswork
Run Discovery to pull the actual list of users, drives, sites, and mailboxes before you configure a single mapping. Build your migration plan against what's really there — not a stale export or a manual count.
No Hosted Cloud Service — Runs Locally
TenantBridge is a single executable that runs on the machine you choose — workstation, VM, or server. The web interface is only accessible locally. Files move directly between tenants. No TenantBridge cloud relay, ever.
Google Workspace migration questions
Can TenantBridge handle a full GWS-to-GWS tenant migration?
Yes. TenantBridge supports Google Workspace to Google Workspace migrations, including Drive, email (via IMAP or Google connector), Calendar, and Contacts. All workloads run from the same app and are managed from the same Migrate table.
Does it migrate Google Calendar and Contacts as well as Drive?
Yes. TenantBridge migrates Google Calendar events (including secondary calendars) and Google Contacts alongside Drive and email. Calendar and Contacts jobs are configured per-batch and appear in the same Migrate view as mail and file jobs.
How does domain mapping work for cross-tenant moves?
You configure domain pairs in the Edit Project screen. TenantBridge uses these pairs to translate user email addresses between the source and destination tenants — so a user at [email protected] maps correctly to [email protected] when permissions and mailbox ownership are applied.
Is there a limit to how many users or drives I can migrate?
There is no hard limit imposed by TenantBridge. You can organize large user sets into multiple batches within the same project and run them sequentially or in parallel. Worker concurrency is configurable to match your API rate limits and infrastructure.
Does TenantBridge require a cloud service or hosted infrastructure?
No. TenantBridge is a single executable that runs on your own machine — workstation, VM, or server. The web interface is only accessible locally, credentials are encrypted on disk, and files move directly between tenants without passing through any TenantBridge server.
Ready to migrate your Google Workspace tenant?
Request a demo or reach out — we'll walk you through it.