'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Migrate from Google Workspace to Microsoft 365 with an Existing Tenant
Question details
The user wants to migrate Google Workspace mailboxes and SharePoint data to an existing Microsoft 365 tenant where users have already created Microsoft accounts associated with the primary domain.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Performing a batch migration from Google Workspace to Microsoft 365 without disrupting existing tenant structures or losing associated volume licensing information.
- Observed behavior
- The target Microsoft 365 tenant already exists and is tied to the organization's volume licensing. Replacing or deleting the tenant to facilitate migration risks losing critical licensing data.
Ensure you have global administrator privileges in both your Google Workspace and Microsoft 365 admin centers. It is highly recommended to document your current volume licensing details before making any structural changes to your tenant.
Perform a Batch Migration via the Exchange Admin Center
Safely migrate your organization's data by provisioning users as mail-enabled accounts and utilizing migration batches, preserving your existing tenant and volume licensing.
To protect your volume licensing, you must not delete or replace your existing Microsoft 365 tenant. Instead, you can migrate Google Workspace data into the existing accounts by grouping users into migration batches.
This process leverages the automated migration tools built into the Exchange admin center and SharePoint admin center to ensure a seamless transition.
Before starting the migration, contact Microsoft licensing support to confirm the status of your volume licensing. Ensure that mapping new data to the existing tenant will not disrupt your current licensing agreements.
Log in to the Microsoft 365 admin center and provision your existing users as mail-enabled users. This step is necessary to properly route emails during the transition phase before the migration is finalized.
Navigate to the Exchange admin center. Go to the Migration section, click 'Add migration batch', and select Google Workspace as the source. Assign your provisioned mail-enabled users to specific migration batches.
Start the migration batches for the mailboxes. For your SharePoint data, open the SharePoint admin center and use the Migration Manager tool to map and transfer your Google Workspace files directly into Microsoft 365.
Looking for a cost-effective alternative to Microsoft 365?
If managing Microsoft 365 tenants and complex migrations is becoming overwhelming or expensive, consider WPS Office. It provides a lightweight, highly compatible alternative for your document productivity needs without the hassle of complex cloud tenant management.
- 1. Download the software: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen instructions to complete the installation in minutes.
- 3. Open existing Office files: Launch WPS Office and directly open your existing Microsoft documents with full formatting preserved.
Frequently Asked Questions
Will migrating to an existing tenant affect my Microsoft volume licensing?
As long as you do not delete or replace the existing tenant, your volume licensing will remain intact. Always consult Microsoft support before modifying existing tenant structures to ensure full compliance.
What is a mail-enabled user in the context of this migration?
A mail-enabled user is an account created in Microsoft 365 that has an external email address associated with it. Provisioning users this way allows you to safely route mail properly before the mailbox migration is fully completed.
Can I use the Exchange admin center to migrate SharePoint data?
No, the Exchange admin center is used specifically for mailbox migration. To migrate SharePoint and Google Drive data, you should use the Migration Manager located within the SharePoint admin center.
Do I need to abandon my secondary domain to migrate?
No, you do not need to abandon your secondary domain. You can migrate your data directly to the Microsoft accounts that already exist on your primary domain by grouping the migration into managed batches.
