How to Merge Multiple Google Workspace Tenants: A Complete Guide

Published 2025-12-15 by TechNet New England

If you're reading this, chances are you've found yourself managing multiple Google Workspace tenants and wondering how to consolidate them into one. You're not alone. This scenario is increasingly common, whether you've acquired another company, merged with a business partner, or simply accumulated multiple Workspace accounts over the years through departmental growth or shadow IT.

This guide will walk you through everything you need to know about merging Google Workspace tenants, from initial planning to post-migration cleanup.

Table of Contents

• Why Do Businesses End Up with Multiple Tenants?
• The Challenges of Merging Workspace Tenants
• Planning Phase: Setting Yourself Up for Success
• Migration Options
• Step-by-Step Migration Process
• Post-Migration Cleanup
• Common Pitfalls to Avoid
• When to Get Professional Help

Why Do Businesses End Up with Multiple Tenants?

Before diving into the how, it helps to understand how organizations end up in this situation. Understanding the root cause can help you plan better and avoid similar issues in the future.

Mergers and Acquisitions

This is the most common reason. When Company A acquires Company B, each typically has their own Google Workspace (or one has Workspace while the other has Microsoft 365). Post-acquisition, consolidating to a single platform streamlines operations and reduces costs.

Organic Growth and Departmental Silos

Sometimes different departments or divisions set up their own Workspace accounts independently. Marketing might have their own domain, the sales team another, and suddenly you're paying for three separate subscriptions with no centralized management.

Shadow IT

Employees or teams sometimes create Google Workspace accounts to solve immediate needs without going through IT. These accounts grow over time, accumulating critical data and becoming entrenched in business processes.

Regional Expansion

Companies expanding internationally sometimes create separate tenants for different regions or countries, especially when there were concerns about data residency or local compliance requirements.

Legacy from Business Transitions

A company might have started with G Suite Basic years ago, then created a new "fresh" Workspace account when upgrading or rebranding, never fully decommissioning the old one.

The Challenges of Merging Workspace Tenants

Merging Google Workspace tenants isn't as simple as copying files from one account to another. There are significant technical and organizational challenges to navigate.

Data Migration Complexity

Google Workspace contains multiple types of data that need to be migrated:

• Gmail: Emails, labels, filters, and signatures
• Google Drive: Files, folder structures, and sharing permissions
• Google Calendar: Events, recurring meetings, and shared calendars
• Google Contacts: Contact lists and contact groups
• Google Sites: Intranet sites and internal wikis
• Chat/Spaces: Message history and shared files
• Keep: Notes and checklists
• Google Forms: Form definitions and response data
• Shared Drives: Team file repositories

Each of these requires different handling, and some data (like Chat history) can be particularly difficult to migrate cleanly.

User Confusion and Change Management

Users will need to:

• Learn new email addresses (potentially)
• Update their calendars and contacts
• Find their files in new locations
• Re-establish sharing permissions
• Update bookmarks and saved links

Without proper communication and training, productivity can plummet during and after the migration.

Domain and DNS Conflicts

Both tenants may have verified domains, and you'll need to decide:

• Which domains to keep
• How to handle domain aliases
• What to do with users whose primary email domain is being deprecated

Third-Party Integration Breakage

Apps, services, and automations connected to the old tenant will break:

• OAuth connections to third-party apps
• API integrations
• SSO configurations
• Mobile device management (MDM) profiles
• Chromebook enrollments

Compliance and Data Retention

If you're in a regulated industry, you need to consider:

• Legal hold requirements
• eDiscovery implications
• Audit trail preservation
• Data retention policy consistency

Planning Phase: Setting Yourself Up for Success

A successful migration starts with thorough planning. Rushing this phase is the #1 cause of migration failures.

Step 1: Complete Inventory

Document everything in both (or all) tenants:

Step 2: Choose Your Primary Tenant

One tenant will become the "primary" or surviving tenant. Consider:

• Size: Usually easier to migrate smaller tenant into larger
• Licensing: Which has better license tiers?
• Domain authority: Which domain has better email reputation and SEO value?
• Integrations: Which has more critical third-party integrations?
• Compliance: Which has better-established compliance controls?
• Cost: Consider any contract lock-ins or volume discounts

Step 3: Create a Communication Plan

Users need to know:

• Why the migration is happening
• Timeline and key dates
• What will change for them
• What they need to do (if anything)
• How to get help

Create a communication timeline with announcements at:

• 4 weeks before: Initial announcement
• 2 weeks before: Detailed instructions
• 1 week before: Final reminders
• Migration day: Go-live communication
• 1 week after: Follow-up and feedback collection

Step 4: Document Current State

Before changing anything, document:

• DNS records for all domains
• MX records configuration
• SPF, DKIM, and DMARC settings
• Google Workspace Admin Console settings
• Security settings and 2FA policies
• User provisioning workflows

Migration Options

There are several approaches to migrating data between Workspace tenants, each with pros and cons.

Option 1: Google's Native Data Export (Google Takeout)

Best for: Small organizations (under 25 users) with limited data

How it works:

1. Users export their data using Google Takeout
2. Data is downloaded as files (MBOX for email, etc.)
3. Data is imported into the new tenant manually

Pros:

• Free (no additional tools needed)
• Users can verify their own data
• No third-party access required

Cons:

• Very time-consuming
• Manual process prone to errors
• Doesn't preserve sharing permissions
• Email import can be problematic
• No folder structure preservation in Drive
• Not practical for more than a handful of users

Option 2: Third-Party Migration Tools

Best for: Medium to large organizations, or any organization wanting a clean migration

Popular tools include:

• BitTitan MigrationWiz: Industry standard, supports most migration scenarios
• CloudM (formerly Cloudiway): Google-focused, excellent Drive migration
• AvePoint: Enterprise-grade with strong compliance features
• Mover (Microsoft): Free for Drive-to-Drive, limited features
• MultCloud: Cloud-to-cloud transfer, simpler interface

Pros:

• Automated, less manual work
• Better preservation of metadata
• Can migrate sharing permissions
• Detailed migration reports
• Can handle large data volumes
• Support for incremental/delta migrations

Cons:

• Cost (typically per-user or per-GB pricing)
• Requires admin access to both tenants
• Learning curve for tool configuration
• Some limitations with specific data types

Option 3: Google Workspace Migrate (For Enterprise)

Best for: Large enterprises with Google Workspace Enterprise licenses

Google offers Workspace Migrate as part of Enterprise licensing. It provides:

• Server-based migration architecture
• Support for large-scale migrations
• Direct Google-to-Google migration paths
• Integration with Admin Console

However, it requires significant technical expertise to set up and manage.

Option 4: Hybrid Approach

Best for: Complex environments with mixed requirements

Many successful migrations use a combination:

• Third-party tool for email and Drive
• Manual migration for Shared Drives (to restructure)
• Fresh start for Chat/Spaces (no migration)
• Recreation of Groups in the new tenant

Step-by-Step Migration Process

Here's a generalized process that works for most migrations. Adjust based on your chosen tools and specific requirements.

Phase 1: Pre-Migration (2-4 weeks before)

1. Verify domain ownership in target tenant

   Add and verify any domains you'll be moving. Don't remove them from the source tenant yet.

2. Create user accounts in target tenant

   Create all user accounts that will be migrated. Match email addresses where possible.

3. Configure licensing

   Ensure adequate licenses are available in the target tenant.

4. Set up migration tool

   Configure your chosen migration tool with admin access to both tenants.

5. Run test migration

   Migrate a few test users to identify issues before the full migration.

6. Document third-party integrations

   List all OAuth apps and API integrations that will need reconfiguration.

Phase 2: Migration Execution

1. Final user communication

   Send go-live notification with specific instructions.

2. Start data migration

   Begin with historical data (email older than 30 days, archived files).

3. Migrate current data

   Move recent emails, active Drive files, and calendars.

4. Update MX records

   Point email delivery to the new tenant. This is the critical cutover moment.

5. Run delta sync

   Catch any data created during the migration window.

6. Migrate Shared Drives

   Transfer Shared Drives with their permission structures.

7. Migrate Groups

   Recreate or migrate Google Groups and mailing lists.

Phase 3: User Transition

1. Users log into new tenant

   Provide clear login instructions and new credentials if needed.

2. Reconfigure email clients

   Update Outlook, Apple Mail, and mobile email apps.

3. Reconnect mobile devices

   Re-enroll devices with new tenant credentials.

4. Verify data integrity

   Users confirm their emails, files, and calendars are present.

Post-Migration Cleanup

The migration isn't complete until you've properly cleaned up and verified everything.

Immediate Tasks (First Week)

• Monitor email flow: Verify emails are being delivered to the new tenant
• Check for bounces: Monitor for delivery failures
• Support user issues: Have help desk ready for increased ticket volume
• Verify calendar syncing: Ensure recurring meetings are working
• Test sharing: Verify internal and external sharing works

Short-Term Tasks (First Month)

• Reconfigure third-party apps: Re-establish OAuth connections and API integrations
• Update SSO configurations: Reconfigure identity provider settings
• Migrate remaining data: Address any data that couldn't be migrated initially
• Update documentation: Revise IT documentation and user guides
• Set up email forwarding: Configure forwarding from old addresses to new (if domains changed)

Long-Term Tasks (1-3 Months)

• Decommission old tenant: After confirming all data is migrated and accessible
• Cancel old licenses: Don't pay for both tenants longer than necessary
• Remove old domain verification: Release domains from the old tenant
• Archive old tenant data: Export final backup before deletion
• Update external services: Notify vendors, partners, and customers of any email changes

Common Pitfalls to Avoid

Learn from others' mistakes. These are the most common issues we see in Workspace migrations:

1. Underestimating Data Volume

Users accumulate more data than you expect. A "quick" migration can take days if you haven't properly assessed storage usage. Always run storage audits before estimating timelines.

2. Forgetting About Shared Drives

Shared Drives are often overlooked in planning. They require special handling because:

• Ownership works differently than My Drive
• Permissions are more complex
• Some migration tools handle them poorly

3. Ignoring Email Signatures and Rules

Users spend years building email filters, labels, and signatures. These often don't migrate automatically and users get frustrated when they "lose" their customizations.

4. Poor Communication

Surprising users with a migration causes panic, resistance, and support overload. Communicate early, often, and clearly.

5. Not Testing Thoroughly

Skipping the pilot migration phase to save time usually costs more time in the long run. Always test with real users and real data before the full migration.

6. Migrating During Peak Business Hours

Email cutover should happen during low-activity periods (evening/weekend). Never change MX records on a Monday morning.

7. Forgetting Calendar Resources

Meeting rooms, equipment, and other calendar resources need to be recreated in the new tenant. Don't forget to update room booking systems.

8. Not Accounting for External Sharing

Files shared with external users will break when the sharing user moves. Plan for re-establishing external sharing relationships.

9. Overlooking Mobile Devices

If you use Google's MDM, devices need to be re-enrolled. Users on personal devices will need to reconfigure their email apps.

10. Losing Google Sites

Google Sites don't migrate well. If you have important internal sites, plan to recreate them or use a third-party backup/migration tool.

When to Get Professional Help

While small organizations with tech-savvy staff can handle simple migrations, consider professional help if:

You Should Definitely Get Help If:

• You have more than 100 users
• You're in a regulated industry (healthcare, finance, legal)
• You have complex compliance requirements (HIPAA, SOX, GDPR)
• You're also migrating from Microsoft 365
• You have critical third-party integrations
• You have limited IT staff
• You have tight timelines with no room for error

Types of Professional Help:

• Google Partners: Certified Google Cloud Partners specialize in Workspace migrations
• Migration Specialists: Companies that focus exclusively on cloud migrations
• MSPs/IT Consultants: Managed Service Providers often offer migration services

What to Expect Cost-Wise:

Professional migration services typically cost:

• Small org (25-50 users): $3,000-8,000
• Medium org (50-200 users): $8,000-25,000
• Large org (200+ users): $25,000+ depending on complexity

This includes planning, execution, and post-migration support. DIY migrations save money upfront but can cost more in lost productivity and troubleshooting if issues arise.

Conclusion

Merging Google Workspace tenants is a significant undertaking, but with proper planning and execution, it can be done smoothly. The key takeaways are:

1. Plan thoroughly: Inventory everything, choose your primary tenant wisely
2. Communicate clearly: Users should never be surprised by changes
3. Test before going live: Pilot migrations catch issues early
4. Use the right tools: Third-party migration tools are worth the investment
5. Don't rush: A patient, methodical approach prevents disasters
6. Keep the old tenant active: Give yourself a fallback for at least 60 days

Whether you're consolidating after an acquisition or cleaning up years of organic growth, following these guidelines will help ensure a successful migration.