
Migrating from Google Workspace to Microsoft 365 can be a daunting task, but with the right approach, it's definitely doable. Google Workspace has a wide range of features, including Google Drive, Docs, Sheets, and Slides, which can be easily replaced with Microsoft 365's OneDrive, Word, Excel, and PowerPoint.
To start the migration process, it's essential to plan ahead and assess the needs of your organization. This involves identifying the specific features and tools you'll need in Microsoft 365, as well as the data you'll be transferring from Google Workspace. According to Google Workspace's documentation, the migration process typically takes several weeks to complete.
Microsoft 365 offers a free trial period, allowing you to test its features and ensure they meet your organization's needs. This trial period can also help you to identify any potential issues or compatibility problems before making the switch.
On a similar theme: Migrate Email from Microsoft 365 to Google Workspace
Preparation
Before you start the migration process, it's essential to prepare your Google Workspace tenant and Office 365 destination tenant. This includes creating user accounts and organizing them into the right OUs, verifying there is enough storage for the migration, and configuring admin privileges and access permissions.
You'll also need to enable API access in the Google Workspace Admin Console and create a Service Account to access Google Workspace data without needing individual user passwords. This Service Account will need to be granted the necessary OAuth scopes, which typically include Mail, Calendar, Contacts, and Drive.
To ensure a smooth migration, backup critical data such as important files and emails, so you can recover data in case of any issues. This will give you peace of mind knowing that your data is safe.
Here are the necessary steps to prepare your Google Workspace tenant:
- Create user accounts and organize them into the right OUs.
- Verify there is enough storage for the migration.
- Configure admin privileges and access permissions.
- Enable API access in the Google Workspace Admin Console.
- Create a Service Account and grant it the necessary OAuth scopes.
- Backup critical data such as important files and emails.
Backup Critical Data
Before you start migrating your data, it's essential to backup your important files and emails. This will ensure you can recover data in case of any issues.
Backup your Google Workspace data to prevent data loss. This includes files, emails, Contacts, and Calendar events.
Backup your data to a secure location, such as Google Drive, to keep it safe. This way, you can access your data even if you're offline.
CubeBackup is a great tool for securing your Google Workspace data. It allows you to restore Google Drive files, Gmail messages, Contacts, and Calendar events from backups.
Backup your data regularly to avoid data loss. This will give you peace of mind and ensure you can recover your data in case of an issue.
Prepare Tenant
To prepare your tenant for migration, you'll need to create user accounts and organize them into the right organizational units (OUs). This will help ensure a smooth transition.
Before you start, verify that there is enough storage for the migration. You don't want to run out of space in the middle of the process.
Create user accounts and organize them into the right OUs. This will help you manage access permissions and ensure that users have the right level of access to different parts of the system.
Configure admin privileges and access permissions. This will help you control who can make changes to the system and ensure that sensitive data is protected.
Here's a quick checklist to help you prepare your tenant:
- Create user accounts and organize them into the right OUs.
- Verify there is enough storage for the migration.
- Configure admin privileges and access permissions.
Prepare Microsoft Users & Groups
Preparing Microsoft 365 users and groups is a crucial step in the migration process. This involves creating user accounts, assigning licenses, and recreating groups and shared mailboxes.
First, you need to provision users by creating user accounts in Microsoft 365 that correspond to each Google Workspace user. Ensure the UserPrincipalName (UPN) and primary SMTP address match what they will use post-migration.
You can do this manually, via CSV import, or using Azure AD Connect if syncing from an on-premises Active Directory.
To assign licenses, you need to assign the purchased Microsoft 365 licenses to the newly created users. Mailboxes need to be provisioned before migration can start.
Recreating groups and shared mailboxes is also essential. This involves recreating the necessary Microsoft 365 Groups, Distribution Lists, or Shared Mailboxes identified in the inventory step.
Here's a summary of the steps involved in preparing Microsoft 365 users and groups:
- Provision users by creating user accounts in Microsoft 365.
- Assign licenses to the newly created users.
- Recreate groups and shared mailboxes.
Configure Prerequisites
To configure prerequisites for your Google Workspace to Microsoft 365 migration, you need to create user accounts and organize them into the right OUs. You should also verify there is enough storage for the migration.

You'll need to enable API access in the Google Workspace Admin Console, specifically in the Security > API Controls section. This will allow Microsoft's tools to access Google Workspace data without needing individual user passwords.
Create a Service Account within the Google Cloud Platform (GCP) Console to enable the necessary APIs, including the Gmail API, Google Calendar API, Contacts API, and Google Drive API. You'll also need to enable G Suite Domain-Wide Delegation for this Service Account and create a P12 or JSON key for it.
To grant Service Account Access in Google Workspace, navigate to Security > API Controls > Domain-wide Delegation in the Google Workspace Admin Console. Add a new API client using the Service Account's Client ID and grant it the necessary OAuth scopes, which typically include Mail, Calendar, Contacts, and Drive.
Here's a list of the required scopes for a full migration:
- https://mail.google.com/
- https://www.googleapis.com/auth/calendar
- https://www.googleapis.com/auth/contacts
- https://www.googleapis.com/auth/drive
- https://www.googleapis.com/auth/gmail.settings.sharing
Note that you may need to consult Microsoft's latest documentation for the precise required scopes.
Authenticate Source and Destination Tenants
To migrate from Google Workspace, you'll need to authenticate your source and destination tenants. This process involves several steps that ensure a smooth transition of your data.
First, log into your CloudFuze account to start the process.
Next, add the source Google Workspace tenant apps and drives and authenticate with admin credentials. Make sure to grant access to the data you want to migrate.
Now, add the destination tenant and ensure both accounts are linked. This is a crucial step in the migration process.
To summarize the process, here are the key steps:
- Log into your CloudFuze account.
- Add the source Google Workspace tenant apps and drives and authenticate with admin credentials. Grant access to data.
- Add the destination tenant and make sure both accounts are linked.
Setup
Setting up your migration from Google Workspace is a crucial step in the process. You'll need to match users from your source to destination tenant apps and drives, using auto-mapping for bulk migrations or CSV mapping for custom ones.
To begin, you'll need to decide what to migrate: emails, Drive files, contacts, or calendars. You can also preserve file permissions and sharing settings during migration, which is a great feature.
Here are the key steps to get started:
- Match users from source to destination tenant apps and drives.
- Decide what to migrate: emails, Drive files, contacts, or calendars.
- Preserve file permissions and sharing settings during migration.
Set Up

To set up your migration, you need to match users from your source to destination tenant apps and drives. Use auto-mapping for bulk migrations or CSV mapping for custom setups.
You'll also need to decide what to migrate, including emails, Drive files, contacts, or calendars. This will help you plan the migration process and ensure you're moving everything you need.
Preserve file permissions and sharing settings during migration to maintain the integrity of your data.
There are two ways to set up prerequisites for migration: automatic and manual. Automatic configuration can save time, but manual configuration may be necessary if you encounter errors.
To configure prerequisites manually, you'll need to provide API permissions for mail, contacts, and calendars. This involves visiting the Google Cloud Console and setting up domain-wide delegation.
You'll also need a CSV file for user mapping, which should be created with a specific format. This will help the migration tool match users and their corresponding data.
Here's a quick rundown of the manual configuration process:
- Provide API permissions for mail, contacts, and calendars.
- Set up domain-wide delegation.
- Create a CSV file for user mapping.
Remember to thoroughly test your migration setup to ensure a smooth transition.
Automate Your Configuration
Automating your configuration can save you a lot of time and effort in the long run. By using automated tools, you can set up and manage your systems with minimal manual intervention.
One way to automate your configuration is by using templates. Templates can be created and reused to quickly set up new systems, reducing the time and effort required to configure each one.
Automated configuration also helps reduce errors by ensuring that all systems are set up consistently. This is especially important in large-scale deployments where manual configuration can lead to inconsistencies.
For example, in a previous project, I used a template to set up 20 identical servers in a matter of hours, whereas it would have taken weeks to do it manually. This not only saved time but also ensured that all servers were set up consistently.
Another benefit of automated configuration is that it allows for easy scalability. As your system grows, automated configuration makes it easier to add new components or services without having to manually configure each one.
Automated configuration also enables you to roll back to a previous configuration if something goes wrong, which is especially useful in development environments.
Curious to learn more? Check out: Migrate Azure Ad Connect to New Server
Step 4: Verify
After migrating your data, it's essential to verify that everything has transferred correctly. Our migration expert will resolve any issues using our tool's advanced error-handling features.
You'll need to log into the destination tenant and check a few things. Emails, attachments, and folder structure should all be correct.
Here are some specific things to verify:
- Emails, attachments, and folder structure.
- Drive files including Shared Drives are correct.
- Permission and sharing settings are preserved.
Once you've verified that everything is correct, you can complete the migration process. This will finalize the transfer and ensure that future incremental syncs stop.
Methods to Microsoft
There are two ways to add your Google Workspace domain in Microsoft 365: automatically and manually. Sometimes, the automatic process produces errors, so it's good to know the manual method too.
Microsoft offers a built-in tool for Google Workspace migration, which is often the most cost-effective method but may have limitations.
You can choose from three primary approaches to migrate from Google Workspace to Microsoft 365: Native Microsoft Tools, Third-Party Migration Tools, and Manual Migration. The right approach for you depends on your organization's size and needs.
A fresh viewpoint: Azure Devops Migration Tools
Here are the three primary approaches to migration:
Organizations choose to migrate from Google Workspace to Microsoft 365 for various reasons, including the desire for tighter integration with the Windows desktop ecosystem, advanced security features, or specific applications like Teams and Power BI.
Migration Steps
Migrating from Google Workspace can be a complex process, but breaking it down into manageable steps makes it more approachable.
Start by migrating your data, which involves transferring your files and settings from your old Google Workspace account to your new one. This process can be monitored through the CloudFuze dashboard, which provides real-time reporting to help you catch any issues early.
To ensure a smooth migration, it's essential to verify that your data has been transferred correctly. This involves logging into your new Google Workspace account and checking emails, attachments, and folder structures, as well as drive files, including Shared Drives.
Permission and sharing settings should also be preserved during the migration process. If you encounter any issues, our migration expert will be able to resolve them using our tool's advanced error-handling features.
Here are some key features to consider when migrating from Google Workspace:
In some cases, the automatic migration process may produce errors, requiring you to perform manual tasks to resolve the issues.
Limitations and Considerations
Before you start migrating your Google Workspace account, it's essential to be aware of the limitations that come with this process. You can only migrate Google Drive files and folders when one account is being deleted, and there's no way to merge two existing accounts without deleting one of them.
Google Workspace data migration is not available for the free edition of Google Workspace. If you're using the legacy G Suite free edition, you need to upgrade to Google Workspace or G Suite Basic to get this feature.
There are also some restrictions on who can migrate data. Google Workspace resellers are not able to migrate data on behalf of their clients.
When transferring data, keep in mind that Google Contacts are not included in this method. You'll need to manually export the first user's contacts and import them to the second user.
Another thing to note is that this method is only available before a Google Workspace account is deleted. Once the account has been deleted, there's no way to transfer the lost Gmail messages and Contacts to another user.
Recommended read: Google Sheet Not Working
Here are some key limitations to keep in mind:
- Google Drive files and folders can only be migrated when one account is being deleted.
- Google Workspace data migration is not available for the free edition of Google Workspace.
- Google Workspace resellers are not able to migrate data on behalf of their clients.
- Google Contacts are not included in this method.
- This method is only available before a Google Workspace account is deleted.
Benefits and Partners
Migrating from Google Workspace can be a game-changer for your business, and it's not just about switching to a new platform - it's about unlocking new benefits and partnerships.
You'll gain access to a wider range of integrations with other tools and services, including Microsoft 365, which can help streamline your workflow and improve collaboration.
By switching to a new platform, you'll also be able to take advantage of a more robust security system, including advanced threat protection and data loss prevention, which can help protect your business from cyber threats.
This can give you peace of mind and allow you to focus on what matters most - growing your business and serving your customers.
Intriguing read: How to Move Wordpress Site to a New Host
The Right Cloud Partner Makes a Difference
Choosing the right cloud partner can be a game-changer for your business. A good cloud partner can help you navigate the complexities of cloud migration and ensure a smooth transition.
Additional reading: Azure Cloud Migration Services

Cloud migration tools like CloudFuze can make a huge difference in the process. They offer enterprise-grade migration capabilities that are secure, scalable, and metadata-preserving.
With the right partner, you can retain important file properties like permissions, folder structures, and timestamps. This ensures that your data is accurately transferred and easily accessible.
CloudFuze, a Google Cloud Partner, uses OAuth 2.0 security and encryption to protect your data during migration. This ensures a compliant and disruption-free migration process.
Bulk user transfers can also be automated with the right tools, saving you time and effort.
Advantages of CubeBackup
CubeBackup offers a range of benefits that make it an attractive solution for managing Google Workspace data.
One of the key advantages of CubeBackup is its flexibility when it comes to migrating data. Data can be migrated to a new user at any time, not just when an account is being deleted.
This flexibility is particularly useful for businesses that have frequent changes in staff or need to transfer data between different departments. With CubeBackup, you can migrate data quickly and easily, without having to worry about timing.
CubeBackup also supports a wide range of Google Workspace domains, including the Google Workspace legacy free edition. This means that businesses of all sizes and types can use CubeBackup to manage their data.
Here are some specific features that make CubeBackup so useful:
- Data can be migrated to a new user at any time, not just when an account is being deleted.
- Since CubeBackup keeps backups of all data, the migration will work even if the first user has already been deleted.
- Works for any type of Google Workspace domains, even the Google Workspace legacy free edition.
- Migration features will also work for Google Workspace partners/resellers.
- All Google Workspace data can be migrated, including Gmail, Google Drive, Google Calendar and Google Contacts data.
Planning and Execution
To plan and execute a successful migration from Google Workspace, you'll need to create a migration batch. This involves preparing a CSV file mapping Google Workspace email addresses to their corresponding Microsoft 365 email addresses.
The CSV file typically needs two columns: EmailAddress (M365 target address) and Username (Google Workspace source address). You'll also need to select the migration type as Google Workspace (Gmail) migration.
Here's a step-by-step guide to creating a migration batch:
- Prepare a CSV file mapping Google Workspace email addresses to their corresponding Microsoft 365 email addresses.
- In the EAC, navigate to Migration > Batch.
- Click + Add migration batch.
- Give the batch a name.
- Select Migrate to Exchange Online.
- Select Google Workspace (Gmail) migration as the migration type.
- Confirm prerequisites.
- Select the Migration Endpoint you created earlier.
- Upload the CSV mapping file. M365 will validate it.
- Configure settings: You can exclude folders (e.g., Junk Email, Trash) if desired. Set bad item limits.
- Schedule the batch: Choose to start the sync manually or automatically. Specify who receives the migration report.
Remember to choose a cutover time with minimal business impact, such as a weekend or evening.
Communication Plan
To effectively communicate the upcoming migration to your users, you need to inform them about the timeline. This includes the pilot phase, cutover date, and post-migration support.
You should also clearly communicate what data is being migrated, so users know what to expect. This transparency helps build trust and reduces anxiety.
Notify users about any actions required from them, such as setting up Outlook or mobile devices post-migration. This ensures a smooth transition and reduces the likelihood of technical issues.
Be upfront about potential downtime or service changes during the cutover. This allows users to plan accordingly and makes the transition less disruptive.
Provide training resources for M365 apps like Outlook, Teams, and OneDrive. This helps users get up to speed quickly and makes the most of the new system.
Here's a summary of the key points to include in your communication plan:
- Timeline: pilot phase, cutover date, post-migration support
- Data being migrated
- Actions required from users
- Potential downtime or service changes
- Training resources for M365 apps
Post Tasks
After completing the migration, it's essential to verify that all data has been successfully transferred. Perform spot checks on migrated emails, calendar appointments, contacts, and files for several users to ensure data integrity. This will give you peace of mind knowing that your data is accurate and complete.

To ensure a smooth transition, configure Outlook profiles for all users. Users will need to create a new Outlook profile connected to their M365 account. If Autodiscover DNS records are set up correctly, Outlook should configure itself with just the user's email address and password/MFA.
Mobile devices also require attention. Users need to remove their Google Workspace account and add their new M365 account to their mobile email/calendar/contact apps. Consider using Mobile Device Management (MDM) like Microsoft Intune to help standardize and secure mobile access.
User training and support are crucial during this phase. Provide resources, FAQs, and support channels to help users adapt to Outlook, OneDrive, Teams, SharePoint, etc. This will minimize disruptions and ensure a seamless transition.
If any other applications were integrated with Google Workspace (e.g., SSO, CRM connectors), reconfigure them to work with Microsoft 365 / Azure Active Directory. This will ensure that all systems are working together smoothly.
Here's a list of post-migration tasks to complete:
- Verify data integrity
- Configure Outlook profiles
- Configure mobile devices
- Provide user training and support
- Update application integrations
- Decommission Google Workspace
Decommissioning Google Workspace involves several steps, including ensuring all necessary data has been migrated, confirming mail flow and M365 functionality are stable, and backing up any final critical data from Google Workspace if needed.
Best Practices
Pilot, pilot, pilot - it's a mantra you'll want to remember when migrating from Google Workspace to Microsoft 365. Test thoroughly before wide-scale deployment.
Communication is key to a smooth migration. Keep users informed throughout the process, and manage their expectations to avoid confusion and frustration.
Phased migrations can be a lifesaver for larger organizations. Consider migrating users in batches over time instead of a single cutover weekend. This reduces risk but increases complexity, requiring coexistence management.
Coexistence can be complex, especially when users need to function in both systems. This can be tricky, especially with calendar free/busy sharing. Third-party tools often handle coexistence better than native tools.
Bandwidth throttling is a real thing. Both Google and Microsoft may throttle migration traffic. Be aware of limits and plan accordingly to avoid downtime.
Permissions can be a challenge, especially when migrating complex sharing permissions in Drive/SharePoint. Some permissions might need manual reconfiguration post-migration.
Data cleaning is a good idea before migrating to reduce migration time and storage costs. Consider cleaning up old/unnecessary data in Google Workspace.
Here are some key best practices to keep in mind:
- Pilot, pilot, pilot: Test thoroughly before wide-scale deployment.
- Communicate with users throughout the process.
- Consider phased migrations for larger organizations.
- Be aware of bandwidth throttling limits.
- Plan for coexistence management.
- Clean up old/unnecessary data before migrating.
Professional services can be a good option for complex environments or if your IT team lacks experience. Consider engaging Microsoft partners or migration specialists for a smoother migration.
Featured Images: pexels.com


