Directly Migrate Google Drive to Microsoft 365

["This wiki is currently locked by <b>shovivsoftware</b>."]

Organizations switching from Google Workspace to Microsoft 365 often need to migrate documents, spreadsheets, presentations, PDFs, images, and other files stored in Google Drive. A successful migration requires proper planning, user mapping, permission preservation, and post-migration validation.
This guide explains how to directly migrate Google Drive to Microsoft 365, including migration methods, prerequisites, best practices, and common challenges.

Why Migrate Google Drive to Microsoft 365?

Businesses migrate from Google Workspace to Microsoft 365 for several reasons:

  • Centralize collaboration in Microsoft 365.
  • Use Microsoft Office desktop applications.
  • Integrate with Microsoft Teams.
  • Improve document management through SharePoint.
  • Consolidate security and compliance policies.
  • Leverage OneDrive for Business storage.
    After migration, Google Drive files are typically stored in:
  • OneDrive for personal user files.
  • SharePoint Online for team and departmental data.
  • Microsoft Teams connected SharePoint document libraries.

Understanding the Migration Options

There are two primary ways to migrate Google Drive to Microsoft 365:

  1. Microsoft Migration Manager- for Small to medium organizations
  2. Third-Party Migration Tool- for Large enterprises and complex projects

Method 1: Migrate Google Drive Using Microsoft Migration Manager

Microsoft provides a native migration platform through the SharePoint Admin Center.
This method supports:

  • My Drive (user drives)
  • Shared Drives
  • Folder structures
  • Documents and files
  • User-to-user mapping

Prerequisites

Before starting the migration, ensure:
Microsoft 365 Requirements
You need:

  • Global Administrator account
  • SharePoint Administrator permissions
  • Active Microsoft 365 licenses for users
  • Sufficient OneDrive and SharePoint storage

Google Workspace Requirements
You need:

  • Google Workspace Super Admin account
  • Access to Google Cloud Console
  • Required API permissions
  • Access to all Google Drive accounts being migrated

Step 1: Prepare the Microsoft 365 Environment

Before migration:

Verify User Accounts

Ensure every Google Workspace user has a corresponding Microsoft 365 account.
Example:

Google User

john@company.com
john@company.com

Microsoft 365 User

sarah@company.com
sarah@company.com

This mapping is critical for successful migration.

Provision OneDrive Accounts

Users should sign in to OneDrive at least once.
This automatically creates their OneDrive sites.

Step 2: Create a Google Cloud Project

Microsoft requires access through Google APIs.

Sign In

Open Google Cloud Console and create a new project.

Enable Required APIs

Enable:

  • Google Drive API
  • Admin SDK API

Configure OAuth

Create OAuth credentials and consent settings.

Generate Credentials

Download the required JSON credential file.
You will upload this file to Microsoft 365 later.

Step 3: Configure Migration Manager

Open SharePoint Admin Center

Navigate to:
Migration → Google Workspace

Create Migration Connection

Provide:

  • Google Workspace admin credentials
  • API credentials
  • Authentication details

Microsoft validates the connection.

Step 4: Scan Google Drive Accounts

Run a scan to discover:

  • Users
  • Shared Drives
  • File counts
  • Folder structures
  • Storage consumption

The scan helps identify potential issues before migration begins.

Step 5: Map Source Users to Destination Users

User mapping tells Microsoft where migrated files should be placed.
Example:

Source Google Account

employee1@gmail.com
employee2@gmail.com

Destination Microsoft 365 Account

employee1@company.com
employee2@company.com

Incorrect mapping is one of the most common causes of migration failures.

Step 6: Configure Migration Settings

Choose destination locations.

Option A: Migrate to OneDrive

Best for:

  • Personal files
  • Individual user data

Destination:

User’s OneDrive account.

Option B: Migrate to SharePoint Online

Best for:

  • Department files
  • Team collaboration
  • Shared content

Destination:

SharePoint document libraries.

Option C: Migrate to Teams

Since Teams stores files in SharePoint, migrated content can be placed into Team-associated SharePoint sites.

Best for:

  • Project teams
  • Collaboration workspaces

Step 7: Start the Migration

Launch migration jobs.

Migration Manager begins transferring:

  • Documents
  • PDFs
  • Images
  • Videos
  • Presentations
  • Spreadsheets
  • Shared content

Progress can be monitored from the dashboard.

Step 8: Monitor Migration Reports

Review reports for:

  • Successful items
  • Failed items
  • Permission issues
  • Unsupported file types
  • Duplicate content

Address any reported errors before decommissioning Google Drive.

Step 9: Validate the Migration

Verify:

✅ Folder structure
✅ File counts
✅ File accessibility
✅ Permissions
✅ Shared folders
✅ User access

Conduct validation with selected end users before announcing completion.

Common File Types Supported

Typical file types include:

  • DOCX
  • XLSX
  • PPTX
  • PDF
  • TXT
  • CSV
  • JPG
  • PNG
  • ZIP
  • MP4

Google-native files such as:

  • Google Docs
  • Google Sheets
  • Google Slides

may be converted into Microsoft Office formats during migration.

Common Migration Challenges

Permission Mismatches

Google and Microsoft use different permission models.
Some sharing settings may require manual review.

Large File Volumes

Organizations with terabytes of data may experience:

  • Longer migration windows
  • Bandwidth limitations
  • Throttling

Unsupported Characters

Certain file names may contain characters unsupported by SharePoint.

Examples include:

  • •
  • :
  • "
  • <
  • |

These files may require renaming.

Duplicate Content

Users often store duplicate files in multiple locations.
Pre-migration cleanup can significantly reduce migration time.

Method 2: Using a Professional Migration Tool

Many organizations choose specialized migration software when:

  • Migrating hundreds or thousands of users
  • Handling multiple domains
  • Preserving permissions
  • Migrating Shared Drives
  • Running incremental migrations
  • Scheduling migration jobs

What Shoviv for Enterprise Migrations

For organizations planning a Google Drive to OneDrive migration, the Shoviv Google Drive to OneDrive Migration Tool provides a secure and efficient way to transfer data from Google Workspace to Microsoft 365. Designed to handle business-scale migration projects, the software supports bulk user migration, automated job processing, and incremental synchronization to reduce manual effort and minimize disruption.

The tool helps preserve folder structures, file organization, sharing permissions, and other important data attributes throughout the migration process. Administrators can apply filters based on file type, date range, and size to migrate only the required data, helping optimize storage usage and simplify project management.

With support for modern authentication methods, automated scheduling, and detailed migration controls, the solution enables organizations to perform large-scale migrations with greater accuracy and reliability. Whether migrating a few users or an entire organization, Shoviv provides a scalable approach to moving data from Google Drive to OneDrive while maintaining business continuity and operational efficiency.

Advanced migration features provide by Shoviv Software

  • Bulk user migration
  • Automatic user mapping
  • Delta migration support
  • Detailed reporting
  • Job scheduling
  • Permission preservation
  • Selective migration filters
  • Retry mechanisms

These capabilities can significantly reduce administrative effort in large-scale migration projects.

Best Practices for a Successful Migration

1. Perform a Migration Assessment

Analyze:

  • Number of users
  • Total data size
  • Shared Drives
  • Permission complexity

2. Clean Up Data

Remove:

  • Obsolete files
  • Duplicate documents
  • Temporary folders
  • Unused accounts

This reduces migration time and storage consumption.

3. Run a Pilot Migration

Start with:

  • 5–10 users
  • One department
  • Limited data

Validate results before full deployment.

4. Schedule During Off-Hours

Large migrations can consume bandwidth and impact productivity.
Schedule major migration activities during evenings or weekends.

5. Use Incremental Migration

Incremental migration transfers only newly created or modified files after the initial migration.
Benefits include:

  • Reduced downtime
  • Faster cutover
  • Improved accuracy

6. Validate Permissions Carefully

After migration:

  • Check folder permissions
  • Review shared content
  • Confirm user access rights

Permission-related issues are among the most common post-migration complaints.

7. Keep Google Drive Active Temporarily

Do not immediately delete the source environment.
Maintain Google Drive access until:

  • Migration verification is complete
  • Users confirm access
  • Compliance requirements are satisfied

Post-Migration Checklist

Use this checklist before declaring the project complete:

  • User accounts verified
  • OneDrive provisioned
  • SharePoint sites configured
  • User mapping validated
  • Data migrated successfully
  • Permissions reviewed
  • Shared content verified
  • Reports analyzed
  • Incremental migration completed
  • User acceptance testing performed
  • Final cutover completed

Conclusion

Directly migrating Google Drive to Microsoft 365 is achievable using Microsoft’s Migration Manager or a dedicated migration solution. While Microsoft’s native approach works well for many organizations, larger environments often benefit from advanced migration tools that provide automation, scheduling, permission preservation, detailed reporting, and incremental synchronization. By planning carefully, validating data thoroughly, and following migration best practices, organizations can ensure a smooth transition from Google Drive to Microsoft 365 with minimal disruption to users and business operations.

Helpful Resources: