# Google Drive to SharePoint Migration: Step-by-Step Technical Guide

A Google Drive to SharePoint migration requires mapping user identities, converting proprietary Google MIME types into OpenXML formats, and resolving orphaned files and shortcuts that native tools skip. This step-by-step guide details how to plan the audit, execute transfers with Microsoft Migration Manager, and maintain file intelligence across cloud workspaces.

Source: https://fast.io/resources/google-drive-to-sharepoint-migration/
Author: [Derek Labian](https://fast.io/authors/derek-labian/)
Last reviewed: 2026-10-10

## Pre-Migration Audit: Inventorying Formats Before a Google Drive to SharePoint Migration

Automated cloud migrations often report complete success while quietly omitting files that teams rely on every day. In a Google Drive to SharePoint migration, automated tooling converts standard documents but routinely bypasses Google shortcuts and leaves unorganized files abandoned in source accounts without triggering a fatal error. Understanding how files exist inside Google Workspace is the first requirement for preventing silent data loss.

Google Drive to SharePoint migration transfers documents, spreadsheets, and folder hierarchies from Google Workspace Shared Drives to SharePoint Online, requiring conversion of proprietary Google formats into OpenXML files. As outlined in [Microsoft Learn migration guidance](https://learn.microsoft.com/en-us/sharepointmigration/mm-google-overview), Migration Manager natively supports Google Workspace migrations as of recent Microsoft 365 releases. While third-party tools and native utilities advertise automated transitions, the underlying differences between Google's object model and Microsoft's document libraries introduce structural friction that requires manual intervention.

### The Anatomy of Proprietary Google MIME Types

Google Docs, Sheets, and Slides do not exist as standard binary files within Google storage clusters. They are structured database records represented by proprietary Google MIME types. When an administrator initiates a transfer, the migration engine cannot copy raw bytes across platforms. The source environment must generate OpenXML representations on the fly through the Google Export API:

- `application/vnd.google-apps.document` converts into a Microsoft Word file (`.docx`)
- `application/vnd.google-apps.spreadsheet` converts into a Microsoft Excel file (`.xlsx`)
- `application/vnd.google-apps.presentation` converts into a Microsoft PowerPoint file (`.pptx`)
- `application/vnd.google-apps.drawing` converts into a static PNG graphic (`.png`)
- `application/vnd.google-apps.form` converts into Microsoft Forms metadata if a target destination is designated
- `application/vnd.google-apps.site` cannot be converted and must be rebuilt as modern SharePoint communication pages
- `application/vnd.google-apps.map` cannot be exported and must be replaced with alternative geographic tools
- `application/vnd.google-apps.shortcut` represents a pointer to another file or folder and is skipped by automated engines

Standard binary formats, including PDF documents, JPEG images, and MPEG videos, transfer without modification. The risk during migration centers almost entirely on proprietary Google records where conversion alters file layout, breaks calculation engines, or disconnects references.

### The Google Shortcuts Hazard

In Google Drive, users frequently create shortcuts (`application/vnd.google-apps.shortcut`) rather than copying or moving items. Shortcuts allow a document located in a personal My Drive or an external department's Shared Drive to appear in multiple locations across an organization's directory tree.

Microsoft Migration Manager skips shortcut files when processing Google Workspace accounts. Because SharePoint Online document libraries do not support Google's multi-parent shortcut architecture, skipping these files means secondary project directories arrive in SharePoint missing key references. If an operations team accesses financial records through shortcuts placed in their operational folder, those files will not exist in the migrated operations library. The team will encounter empty directories unless the primary source files are independently mapped and transferred.

### The Orphaned Files Blind Spot

An orphaned or unorganized file occurs when an individual creates an asset inside a shared folder, and the folder owner subsequently deletes or unshares that parent container. In Google Drive, files remain active as long as the file owner's account exists. However, the file loses its parent folder association and vanishes from the standard hierarchical directory tree.

These unorganized items can only be located by executing the search operator `is:unorganized owner:me` directly in the Google Drive search bar. Because Microsoft Migration Manager only crawls structured folder hierarchies, orphaned files are never discovered during pre-migration scans. They are not transferred, and they do not appear on error reports. Unless administrators instruct users to run search queries and re-home unorganized assets into visible folders before migration, these files remain abandoned in Google Workspace.

### Pre-Migration Audit Checklist

To ensure comprehensive coverage before initiating file transfers, administrators should execute a systematic audit across all target accounts:

1. **Catalog proprietary Google file counts:** Audit total volumes of Google Docs, Sheets, Slides, Drawings, and Forms to anticipate conversion workloads and potential formatting reviews.
2. **Discover and re-parent orphaned files:** Instruct team members to run `is:unorganized owner:me` across their personal accounts and place active documents into structured directories.
3. **Resolve multi-parent shortcuts:** Identify critical shortcuts within departmental folders and replace them with true file copies or document target URLs before migration.
4. **Inventory custom scripts and formulas:** Flag spreadsheets containing Google Apps Script, `QUERY`, or `IMPORTRANGE` functions that require manual rewriting in Excel.
5. **Check destination path character limits:** Verify that nested folder hierarchies will comply with the SharePoint Online limit of 400 characters for destination URL paths.
6. **Record external sharing permissions:** Document existing external sharing configurations to re-establish secure access links for outside partners after cutover.

## How to Configure Microsoft Migration Manager for Google Workspace

Microsoft 365 provides native tooling to migrate content from Google Workspace into SharePoint Online and OneDrive for Business. Known as Migration Manager, this cloud-hosted administrative service manages authentication, directory discovery, format conversion, and scheduled file transfers directly through the Microsoft 365 admin center. Administrators can review [Google Workspace documentation](https://knowledge.workspace.google.com/admin/migrate/migrate-files-from-a-sharepoint-online-account) alongside Microsoft deployment plans before initiating tenant-wide jobs.

### Administrative Prerequisites and Setup

Executing a tenant-level migration requires elevated permissions across both cloud ecosystems. On the Microsoft 365 side, the administrator must hold the Global Administrator, SharePoint Administrator, or Microsoft 365 Migration Administrator role. On the Google Workspace side, a Super Admin account is required to install and authorize marketplace integrations.

To connect the two platforms:

1. Open the Microsoft 365 admin center and navigate to **Setup** > **Migration resources**.
2. Under **Self-service migration and import tools**, select **Explore migration & imports tools**, then choose **Google Workspace**.
3. Install the Microsoft 365 Migration app from the Google Workspace Marketplace.
4. Authorize the required OAuth scopes, which permit the Microsoft migration service to read Drive files, inspect Shared Drive structures, and retrieve user directory profiles.

Once authentication is confirmed, Migration Manager establishes a persistent connection to the Google Workspace tenant and prepares for content assessment.

### Scanning and Pre-Migration Assessment

Before executing data transfers, administrators must add target Google Drives to the Migration Manager scan queue. The engine supports adding individual user drives, selecting Shared Drives, or uploading bulk CSV files listing source drives.

During the scan phase, Migration Manager assesses file counts, identifies unsupported file formats, flags path lengths exceeding limits, and checks for potential data transfer bottlenecks. Once scanning concludes, administrators can download detailed scan reports:

- **Summary Reports:** Provide high-level statistics covering total item counts, overall data volume, and estimated transfer duration.
- **Item Failure Reports:** Detail specific files that cannot be migrated, including Google Sites, standalone Google Maps, or path strings exceeding 400 characters.

Addressing these warnings before proceeding prevents avoidable job failures during active transfer phases.

### Sizing Tiers: Standard Migration Manager vs. Migration Manager Lite

Microsoft provides two operational interfaces based on organization size. Migration Manager Lite is enabled by default for tenants with fewer than 300 Microsoft 365 licenses when the migration project is created.

The following comparison details the operational differences between the standard workflow and Migration Manager Lite:

| Migration Stage | Standard Migration Manager | Migration Manager Lite |
| --- | --- | --- |
| Connect to Google Workspace | Supported | Supported |
| Separate Scan and Assess Phase | Supported | Consolidated into guided setup |
| Manual Copy to Migrations List | Supported | Automated queue assignment |
| Individual Destination Path Review | Granular library mapping | Automated root mapping |
| Dedicated Identity Mapping Tab | Granular Entra ID mapping | Automated identity pairing |
| Execute and Monitor Progress | Detailed job monitoring | Streamlined task monitoring |

In larger deployments utilizing Standard Migration Manager, administrators retain explicit control over each phase, enabling phased migrations across separate business units.

### Mapping Destinations and Scheduling Execution

After scanning validates source accounts, administrators copy ready items into the active migrations queue and establish target destination paths:

- **Shared Drives to SharePoint:** Each Google Shared Drive maps directly to a dedicated SharePoint Online site collection and document library.
- **Personal My Drive to OneDrive:** Individual Google My Drive accounts map to the corresponding employee's OneDrive for Business storage.
- **Forms Redirection:** If Google Forms are included, administrators must designate an explicit Forms destination in Microsoft 365.

Migrations should follow an incremental strategy. Run an initial baseline pass during off-peak hours to transfer the bulk of documents, images, and archives. While users continue working in Google Drive, the migration engine copies historical content. When the cutover window arrives, administrators initiate a delta pass, which transfers only files that have been created or modified since the baseline pass.

## Mapping Permissions and User Identities from Google Workspace to SharePoint

Transferring files without accurately mapping access rights creates operational chaos. Either sensitive documents become accessible to unauthorized staff, or employees lose access to the assets they need for daily work. Moving from Google Workspace to Microsoft 365 requires reconciling two fundamentally different permission models.

### Identity Mapping via Microsoft Entra ID

Migration Manager relies on an identity mapping file to pair Google Workspace user accounts and groups with their corresponding Microsoft Entra ID (formerly Azure Active Directory) identities. If identity mapping is omitted or misconfigured, migrated files will default to inheriting top-level library permissions, severing user ownership.

Administrators can auto-map identities if email prefixes and domain names match identically between Google Workspace and Microsoft 365. When domain naming conventions diverge, administrators must generate a CSV mapping file pairing Google account emails directly with Microsoft Entra ID User Principal Names (UPNs):

```csv
SourceUser,DestinationUser
marcus.vance@example-workspace.com,mvance@example.com
sarah.chen@example-workspace.com,schen@example.com
marketing-team@example-workspace.com,Marketing-M365-Group@example.com
```

Groups must also be mapped deliberately. A Google Group used for Shared Drive access must be paired with an existing Microsoft 365 Security Group or mail-enabled security group prior to initiating migration.

### Role Translation Across Cloud Platforms

Google Workspace applies distinct permission models across personal My Drive accounts and organization-owned Shared Drives. SharePoint Online evaluates access through Microsoft 365 groups, SharePoint permission levels, and inherited security scopes.

The following comparison table details how Google Workspace roles map to SharePoint Online permission levels during an automated transfer:

| Source Account Type | Google Workspace Role | SharePoint Online Permission | Applied Access Scope |
| --- | --- | --- | --- |
| Google Shared Drive | Manager | Full Control (Owner) | Manage library settings, modify permissions, add and delete content |
| Google Shared Drive | Content Manager | Edit | Add, modify, and delete document library items |
| Google Shared Drive | Contributor | Edit | Add and modify documents; restricted from deleting existing items |
| Google Shared Drive | Commenter | Read (Can view) | Read and download content; comments convert to static annotations |
| Google Shared Drive | Viewer | Read (Can view) | Read and download document library content |
| Google Personal Drive | Owner | Owner (Full Control) | Primary administrator of personal OneDrive for Business library |
| Google Personal Drive | Editor | Edit | Modify document contents and participate in collaborative authoring |
| Google Personal Drive | Commenter / Viewer | Read (Can view) | Read and download file representations |

### Folder Inheritance vs. Explicit File Permissions

In Google Drive, users can share an individual document located deep inside a folder structure with an outside colleague without granting access to the parent folder. This practice creates complex, fragmented permission trees.

By default, Microsoft Migration Manager preserves folder permissions while instructing child files to inherit settings from their parent folder. Under this default behavior, explicit individual file shares are dropped, and child items adopt whatever permissions govern the destination folder.

Administrators can override this behavior by enabling explicit file-level permission migration in Migration Manager project settings. While enabling file-level permissions preserves granular sharing, it creates unique permission scopes on individual items within SharePoint Online. Applying unique scopes across thousands of files can impact library search performance and complicate long-term governance. The recommended practice is to organize files into role-specific folders prior to migration, allowing clean inheritance at the folder boundary.

### External Sharing and Guest Access

Public sharing links created in Google Drive, such as "Anyone with the link can view", do not survive the migration process. SharePoint Online handles anonymous access through distinct tenant sharing policies and expiring link tokens. Following migration, links previously shared with outside clients or contractors will fail. Administrators must audit external collaboration requirements and reissue authenticated guest sharing links from SharePoint Online or OneDrive.

## How File Conversions Impact Documents, Spreadsheets, and Automation

The physical transfer of bytes across networks is rarely where migrations fail. The primary source of post-migration disruption stems from subtle translation discrepancies when proprietary Google files convert into Microsoft Office formats.

### Google Docs to Microsoft Word Layout Variations

During migration, the Google Export API renders Google Docs as OpenXML `.docx` files. While narrative text, basic headings, and simple bulleted lists translate predictably, complex layout elements frequently shift:

- **Header and Footer Table Alignments:** Google Docs allows loose tabular formatting in headers. Word enforces rigid cell boundaries, often pushing logo images or metadata off the printable page.
- **Font Substitutions:** Google Workspace defaults to open-source web fonts such as Roboto, Lexend, and Open Sans. If destination endpoints running desktop Word do not have these typography packages installed locally, Word falls back to default system fonts, causing line breaks and paragraph overflows.
- **Drawing Canvases and Callout Shapes:** Shapes, arrows, and overlaid text boxes created using Google Drawings inside a Doc convert to flattened bitmap graphics or misaligned shapes in Word.
- **Tracked Suggestions and Inline Comments:** Active suggestion history is often converted into accepted revisions or flattened into static reviewer notes, obscuring historical editorial context.

Organizations handling formal proposals or legal documentation should export sample templates manually before migration to verify that visual styling conforms to corporate standards.

### Formula Incompatibilities Between Sheets and Excel

Google Sheets and Microsoft Excel share core mathematical and financial syntax, but Google Sheets includes specialized functions designed for web-native data aggregation. When a `.gsheet` converts to an `.xlsx` file, these specialized functions break, returning formula errors:

- `QUERY`: Executes database queries using the Google Visualization API Query Language. Excel has no native `QUERY` function. Migrated workbooks containing `QUERY` formulas will return `#NAME?` errors. These calculations must be reconstructed using Excel Power Query or nested lookup functions.
- `IMPORTRANGE`: Dynamically pulls continuous data arrays from external Google Sheets workbooks. Excel does not recognize `IMPORTRANGE`. Cross-workbook connections must be re-established through Excel external workbook links or Power Query data connections.
- `ARRAYFORMULA`: Instructs formulas to output arrays across surrounding empty cells. While modern Excel supports native dynamic arrays and automatic formula spilling, syntax differences in multi-condition arrays often cause calculation failures after export.
- `FILTER` and `UNIQUE`: While newer versions of Microsoft Excel support these dynamic array formulas, older desktop versions do not, causing cross-version calculation issues for distributed teams.
- Web Data Functions (`IMPORTXML`, `IMPORTHTML`, `IMPORTFEED`): These formulas fetch live web tables and RSS feeds into Google Sheets. Excel disables or corrupts these calls upon conversion, requiring teams to rebuild them as automated web queries.

### Automation Disruption: Google Apps Script vs. Office Scripts

The most severe operational break occurs in automated business logic. Google Workspace automations rely on Google Apps Script, a cloud runtime built on modern JavaScript. Microsoft 365 automations rely on Microsoft Office Scripts (TypeScript) or desktop Visual Basic for Applications (VBA).

Migration Manager does not convert code. Scripts attached to Google Sheets, Docs, or Forms are completely discarded during the OpenXML export process. This impacts:

- Automated data validation routines
- Custom interface buttons and dialog menus
- Event triggers (`onEdit`, `onOpen`, `onChange`)
- Webhook integrations dispatching notifications to external tools
- Custom reporting scripts assembling daily operational logs

Every business-critical Google Apps Script must be inventoried prior to migration and re-architected within Microsoft 365 using Power Automate, Office Scripts, or custom web services.

### Google Forms and Drawings Handling

Google Forms can be migrated to Microsoft Forms if administrators configure an explicit Forms destination in Migration Manager. The basic question structures, radio buttons, and text fields transfer into the Microsoft Forms environment. However, advanced logic branching and connections that write responses directly into linked spreadsheets must be manually re-established.

Google Drawings convert into static PNG image files (`.png`). They cease to exist as editable vector assets. If graphic designers or process engineers need to edit diagram shapes, flowcharts, or system diagrams after migration, those assets must be recreated inside Microsoft Visio, PowerPoint, or an alternative vector diagramming tool.

## Maintaining Unified File Access Across Multi-Cloud Workspaces

Completing a Google Drive to SharePoint migration rarely results in clean, monolithic cloud storage. In production environments, departments often retain legacy archives in Google Drive, ongoing partner collaboration continues in Box or Dropbox, and internal corporate operations run on SharePoint Online. This distribution creates fragmented knowledge silos that hinder daily work and break automated AI workflows.

### Challenges with Native Cloud Storage Connectors

When organizations deploy autonomous AI agents or automated indexers across native cloud storage, they encounter significant architectural constraints. Connecting agents directly to SharePoint Online through Microsoft Graph API or to Google Drive through the Google Drive API introduces substantial operational overhead:

- **Complex Permission Scopes:** Granting an agent access to SharePoint often requires tenant-wide application permissions or elaborate Entra ID application registrations, exposing entire document libraries when the agent only needs specific project files.
- **API Throttling and Latency:** Microsoft Graph API enforces aggressive request rate limits on document libraries. When an agent attempts to crawl or index directory trees, requests are throttled, introducing network latency.
- **Context Window Bloat:** Native cloud connectors require agents to download whole files or traverse complete folder hierarchies across HTTP endpoints. Pulling large PDF archives or spreadsheet sets into an agent's memory consumes context tokens and drives up inference costs.

### The Fast.io Intelligent Workspace Approach

Rather than forcing rigid platform consolidation or wrestling with brittle API connectors, organizations can bridge distributed storage using Fast.io [intelligent workspaces](/product/workspaces/). Fast.io provides org-owned workspaces that serve as a secure, neutral collaboration layer for people and AI agents.

Fast.io supports direct [cloud import](/product/cloud-import/) from Google Drive, Dropbox, Box, OneDrive, and external URLs via OAuth without consuming local bandwidth. For synchronized collaboration, Fast.io Cloud Sync supports Google Drive, Dropbox, Box, and OneDrive on a schedule or on demand. SharePoint document libraries connect directly through the OneDrive connector, allowing teams to keep their primary files in enterprise storage while mirroring active working folders into Fast.io workspaces.

Inside a Fast.io workspace, every file benefits from foundational management capabilities:

- **Per-File Version History:** Every write and edit preserves complete version history, allowing teams to audit changes and restore earlier versions if an agent or collaborator introduces errors.
- **Granular Access Permissions:** Access is granted per organization, workspace and share through member roles, so agents only reach the workspaces and shares assigned to them.
- **Detailed Activity Log:** A detailed activity log records every creation, modification, and permission update, providing full visibility across human and agent actions.
- **Collaborative Notes:** Shared markdown notes kept inside a workspace, indexed for AI grounding, allow teams and autonomous agents to maintain project documentation alongside stored assets.

### Remote Model Context Protocol (MCP) Integration

Fast.io integrates directly with the modern AI agent ecosystem through a consolidated remote MCP server hosted at `mcp.fast.io`. Connecting over the Streamable HTTP transport, the server eliminates the need for local bridge scripts or background daemon processes.

AI clients connect to designated remote endpoints based on their operational environment, enabling dedicated [storage for agents](/storage-for-agents/) without local infrastructure overhead:

- **Claude and General Agent Runtimes:** Claude Desktop, Claude web, mobile clients, Manus, and general agent frameworks connect directly to `https://mcp.fast.io/mcp/tools`.
- **Coding Agents and IDE Environments:** Coding agents including Cursor, Claude Code, Cline, and Devin connect to `https://mcp.fast.io/mcp/code`. Setup instructions are documented at `https://mcp.fast.io/docs`.

When Intelligence Mode is enabled on a workspace, files are automatically indexed for hybrid search, combining full-text search, semantic search, and metadata queries. Instead of pulling whole document libraries across an API, agents query the Fast.io MCP server using natural language. The server retrieves only the precise text passages and citations needed, minimizing token consumption.

In independent evaluations published at https://fast.io/benchmarks/, Fastio was measured the fastest and lowest cost of the providers tested for agent storage connectors.

### Structured Data Extraction with Metadata Views

For teams migrating large volumes of unstructured documentation, Fast.io provides [Metadata Views](/product/document-data-extraction/). Rather than relying on rigid OCR templates, users describe the information they need in natural language. The system designs a typed schema (supporting Text, Integer, Decimal, Boolean, URL, JSON, and Date & Time formats), extracts structured fields from PDFs, scanned documents, Word files, and spreadsheets, and populates a dynamic, queryable table. AI agents can create views and query structured records directly through MCP actions, turning static migrated archives into active operational databases.

Fast.io operates on transparent subscription tiers. Monthly plans start with a 14-day free trial, which requires a credit card. Organizations can scale across Starter, Business, and Enterprise plans depending on team seat count and workspace storage requirements, providing a reliable foundation for multi-cloud collaboration and autonomous agent operations.

## Frequently asked questions

### How do I transfer Google Drive files to SharePoint without losing formatting?

Preserving formatting during a Google Drive to SharePoint migration requires auditing proprietary Google Docs and Sheets before transfer. Standard documents with straightforward margins and basic tables convert to Word (.docx) and Excel (.xlsx) cleanly through Microsoft Migration Manager. For documents with complex multi-column layouts, embedded drawing canvases, or non-standard fonts, export a test batch manually to inspect visual alignment. In spreadsheets, replace proprietary Google functions like QUERY and IMPORTRANGE with standard Excel formulas or Power Query connections prior to migration.

### Does Google Drive migrate directly to SharePoint using Microsoft tools?

Yes, Microsoft 365 includes Migration Manager, an administrative tool that connects directly to Google Workspace through marketplace app authorization. Migration Manager scans Google Shared Drives and personal My Drive accounts, maps user identities to Microsoft Entra ID, converts proprietary Google formats to OpenXML files, and transfers content directly into SharePoint Online document libraries and OneDrive for Business.

### What happens to Google Forms and Sheets during migration?

Google Sheets convert into Microsoft Excel (.xlsx) workbooks during migration, but custom Google Apps Script macros and proprietary formulas do not translate to VBA or Office Scripts. Google Forms can be transferred to Microsoft Forms if administrators designate a Forms destination within Migration Manager project settings. Once migrated, question branching logic and automated response sheet connections must be reconfigured manually in Microsoft 365.

### How does Microsoft Migration Manager handle Google Drive shortcuts?

Migration Manager skips Google Drive shortcuts during migration. Because shortcuts in Google Workspace allow a single file to display across multiple folders, skipping them means secondary folder views will lose access to those files in SharePoint. Administrators should identify shortcuts during the pre-migration audit and either copy the underlying source file into the destination folder or create SharePoint document links after cutover.

### What happens to orphaned files during a Google Drive migration?

Orphaned files in Google Drive occur when a parent folder is deleted or unshared while individual files owned by other users remain active. These unorganized files lack a parent directory and do not appear in normal folder navigation. Microsoft Migration Manager traverses folder trees and does not scan or migrate orphaned files. Users must locate orphaned files using the is:unorganized owner:me search operator in Google Drive and move them into an active folder before migration begins.

### Can Fast.io import from Google Drive?

Yes, Fast.io provides cloud import capabilities that connect directly to Google Drive, Dropbox, Box, OneDrive, and web URLs via OAuth without requiring local file downloads. Cloud Sync is supported for Google Drive, Dropbox, Box, and OneDrive on a schedule or on demand.

## Sources

- [Microsoft Learn: Migrate Google Workspace to Microsoft 365 with Migration Manager](https://learn.microsoft.com/en-us/sharepointmigration/mm-google-overview): Migration Manager Lite is enabled by default for tenants with fewer than 300 Microsoft 365 licenses when the migration project is created.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli. MCP setup is at https://mcp.fast.io/docs: Claude and most MCP clients connect to https://mcp.fast.io/mcp/tools, ChatGPT to https://mcp.fast.io/mcp/operations, and coding agents to https://mcp.fast.io/mcp/code.