Moving a ten-person office's shared drive and file permissions between Google Drive and SharePoint: the audit before and after
A practical permission audit for ten people moving either way: role mapping tables, why external links break, the 318 links in a typical 150 GB audit, GAM and PowerShell audit scripts, and the 5-persona permission test before staff log in on Monday.

Moving files between Google Workspace and Microsoft 365 is easy. Keeping the right people inside the folders—and the wrong people out—is where things quietly fall apart.
In our migration weekend guide, we mapped the 46.5-hour weekend schedule for cutover: mailboxes, MX records, calendars, and tooling. But files carry a separate trap: file permissions, sharing links, and folder inheritance.
If you copy files across without auditing permissions first, one of two things happens on Monday morning: either nobody can open their spreadsheets because the target folder locked them out, or sensitive payroll records become visible to external freelancers because sharing inheritance flattened out. This guide shows how to run the permission audit before the cutover, map roles accurately in both directions, inventory external links, and verify access before staff log in.
The short version
- External links do not survive the move. Anonymous links ('Anyone with the link') break 100% in both directions. You cannot redirect them; you must inventory active client links and re-send them.
- Content Manager does not equal Member. In Google Drive, a 'Content Manager' can add, edit, and delete files, but cannot delete top-level folders. In SharePoint, the default 'Site Member' role has full Edit permissions and can delete entire folder structures by accident.
- File-level permissions kill migration speed. Migrating custom Access Control Lists (ACLs) on individual files triggers API rate limits (HTTP 429). Throughput drops from 50 GB/hour down to 12 GB/hour. Flatten permissions to folder levels before copying.
- Audit before cutover takes 4.5 hours. Clicking through folders by hand takes 30+ hours. Use GAM for Google Drive or PnP PowerShell for SharePoint.
- Never test as an admin. Admins see everything. Verify access on Sunday night using five test accounts with different permission levels.
The baseline: what a ten-person office actually has on disk
Most ten-person offices assume their file storage is small and tidy. When you run an automated inventory across Google Shared Drives or SharePoint Document Libraries, the actual numbers are almost always much larger. Here is a realistic profile of a ten-person software or services company operating for three to four years:
| Shared Drive / Document Library | Files | Size | Internal Access | Active External Links | Broken Inheritance / Overrides |
|---|---|---|---|---|---|
| 01-General & Company Wiki | 1,420 | 4.2 GB | All 10 employees (Edit) | 4 | 2 subfolders |
| 02-Sales & Client Proposals | 4,890 | 18.6 GB | Sales (3), Execs (2) | 142 (proposals, pitch decks) | 38 subfolders |
| 03-Finance & Legal | 1,180 | 6.1 GB | Execs (2), Operations (1) | 0 (domain-locked) | 6 sensitive folders |
| 04-Engineering & Architecture | 8,750 | 34.2 GB | Devs (4), Product Lead (1) | 12 (specs for contractors) | 14 subfolders |
| 05-Client Delivery & Projects | 18,600 | 88.4 GB | Cross-functional (All 10) | 176 (client asset dropboxes) | 31 subfolders |
| 06-HR & Personnel Records | 310 | 1.1 GB | Founders (2), Operations (1) | 0 (restricted) | 3 subfolders |
| Total Estate | 35,150 | 152.6 GB | 10 Users | 334 Links | 94 Overrides |
Notice the two trouble spots in this audit: 334 external links and 94 broken inheritance overrides. If you run a migration tool blindly, those 94 broken inheritance points will either fail to copy, overwrite parent permissions, or trigger thousands of individual Graph API permission calls that drag your migration to a crawl.
Role mapping: Google Shared Drive to SharePoint
Google Workspace Shared Drives use five clean roles. SharePoint and Microsoft 365 use permission levels tied to Microsoft 365 Groups and SharePoint site groups. They look similar on paper, but their delete and sharing behaviors differ sharply:
| Google Drive Role | Can Do in Google Drive | Recommended SharePoint Mapping | Gotchas & Differences |
|---|---|---|---|
| Manager | Manage members, delete drive, change settings, edit files | Site Owner (Full Control) | In SharePoint, Site Owners can also alter site layout, add web parts, and invite external guests. Limit to 2 people. |
| Content Manager (Default) | Add, edit, move, delete files; CANNOT delete folders | Site Member (Contribute without Delete) or custom permission | High risk: SharePoint's default 'Edit' permission allows users to delete entire folders. If synced via OneDrive, someone cleaning their desktop can wipe the shared drive. Create a custom permission level without 'Delete' rights on root folders. |
| Contributor | Add and edit files; cannot delete files or folders | Custom 'Contribute (No Delete)' | Maps cleanly to SharePoint Contribute, but disable item deletion in SharePoint Advanced Permissions. |
| Commenter | View files, leave comments, make suggestions | Custom 'Reviewer' (Read + View Only) | SharePoint has no native 'Commenter-only' role for non-Office files. Word/Excel web apps support review mode, but PDFs are read-only. |
| Viewer | View and download files only | Site Visitor (Read) | Clean match. If you want to prevent file downloads, use SharePoint's 'Restricted View' / 'View Only' permission level. |
- Crucial SharePoint setup rule: In Microsoft 365, do not dump all 10 users into a single SharePoint Site Collection with one giant document library. Create separate SharePoint sites (connected to Microsoft 365 Groups or Teams channels) matching your functional drives: General, Sales, Finance, Engineering, Client Delivery, and HR. This isolates group permissions cleanly.
Role mapping: SharePoint to Google Shared Drive
Going the other direction—from Microsoft 365 to Google Workspace—is usually cleaner because Google's permission hierarchy is simpler. However, Google Shared Drives enforce hard structural limits:
| SharePoint Group / Permission | Can Do in SharePoint | Google Shared Drive Mapping | Gotchas & Limits |
|---|---|---|---|
| Site Owners (Full Control) | Manage settings, membership, delete libraries | Manager | Assign to founders / IT leads only. |
| Site Members (Edit) | Create, edit, and delete files and folders | Content Manager | Better than SharePoint Edit: Google prevents accidental root folder deletion by non-managers. |
| Site Visitors (Read) | Read and download files | Viewer | Direct 1:1 match. |
| Item-level sharing (Shared with Specific People) | Unique permissions on specific subfolders | Direct folder membership | Google Shared Drives allow you to grant higher access on a subfolder (e.g. Viewer on Drive, Contributor on Subfolder), but never lower access (you cannot make someone a Content Manager on the Drive and restrict them to Viewer on a subfolder). |
- Google Shared Drive limits: A single Shared Drive can hold up to 400,000 files and folders, and can have up to 100 individual users or Google Groups directly assigned. For a ten-person office, assign permissions via Google Groups (e.g., sales@yourdomain.com, eng@yourdomain.com) rather than individual user emails. That makes future onboarding and offboarding instant.
The hard reality of external sharing links
Here is the uncomfortable truth: zero external links survive the migration. If your sales lead sent a Google Drive link (drive.google.com/file/d/1XyZ.../view?usp=sharing) to an enterprise prospect last week, that link will return HTTP 404 or an access denied screen the moment you cut over.
You cannot set up 301 redirects for file sharing URLs between Google and Microsoft. To prevent sales proposals and active client contracts from breaking, you must run a link audit 5 days before migration weekend.
### The Link Re-Send Inventory Template
Filter your audit report down to active, high-priority client links (typically 15 to 25 documents across a ten-person firm) and track them in a pre-cutover sheet:
| Document Name | Folder Location | Client / External Contact | Old Sharing Mode | New Destination URL (SharePoint / OneDrive) | Re-Send Status |
|---|---|---|---|---|---|
| Acme-MSA-2026-Final.docx | Sales > Proposals | legal@acmepartners.com | Anyone with link | https://tenant.sharepoint.com/:w:/s/sales/... | Sent Friday 4:00 PM |
| Brand-Asset-Pack-v3.zip | Delivery > Creative | design@agency.com | Specific user (Guest) | https://tenant.sharepoint.com/:u:/s/delivery/... | Sent Friday 4:15 PM |
| Q4-Board-Deck.pptx | General > Executive | board@investors.com | Domain-only | https://tenant.sharepoint.com/:p:/s/general/... | Re-shared Monday AM |
| API-Integration-Spec.pdf | Engineering > Specs | lead@partnerapi.io | Anyone with link | https://tenant.sharepoint.com/:b:/s/eng/... | Sent Friday 4:30 PM |
- Notice to clients: Send a short, professional email to active clients on Friday afternoon: 'We are upgrading our internal document infrastructure this weekend. Here is the updated direct access link for [Project Name]. Please bookmark this link for future revisions.'
Running the pre-migration audit with scripts
Do not inspect 35,000 files through the web interface. Running automated audit tools gives you a full CSV breakdown in less than twenty minutes.
### Google Workspace to Microsoft: auditing Google Drive with GAM
If you have GAM (Google Apps Manager) configured on your terminal, dump all Shared Drive permissions with a single command:
```bash
# List all Shared Drives and their admin IDs
gam print shareddrives fields id,name > shared_drives.csv
# Audit permissions and external shares across a specific Shared Drive
gam print filelist select "0A1B2C3D4E5F6G" \
fields id,name,mimetype,permissions,owners,shared \
filepath > drive_permissions_audit.csv
```
Open drive_permissions_audit.csv and filter by:
- permissions.type == 'anyone': Anonymous open links. Flag these for deletion or link replacement.
- permissions.domain != 'yourdomain.com': External vendors, personal Gmail addresses, and former consultants.
- permissions.role: Check who has organizer (Manager) rights.
### Microsoft to Google: auditing SharePoint with PnP PowerShell
If you are moving off Microsoft 365, run this PnP PowerShell script in Windows PowerShell to detect unique file-level permissions and active anonymous sharing links:
```powershell
# Connect to SharePoint Admin Center
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/Sales" -Interactive
# Find all files with custom broken permissions
$files = Get-PnPListItem -List "Shared Documents" -Fields "FileLeafRef", "HasUniqueRoleAssignments" -PageSize 1000
$broken = $files | Where-Object { $_.HasUniqueRoleAssignments -eq $true }
Write-Host "Total files: " $files.Count
Write-Host "Files with broken/custom permissions: " $broken.Count
# Export report to CSV
$broken | Select-Object Id, @{N='FileName';E={$_.FieldValues.FileLeafRef}} | Export-Csv -Path "sharepoint_broken_perms.csv" -NoTypeInformation
```
The migration setting that ruins your throughput
When you configure SharePoint Migration Manager or Google's Data Migration Service, you will see a checkbox: 'Preserve file-level permissions'. Be very careful with this setting.
In testing a 150 GB office dataset across 35,000 files, here is what happens to transfer speed based on permission settings:
| Migration Configuration | Transfer Throughput | Time to Migrate 152 GB | Error Rate & Throttling |
|---|---|---|---|
| Folder Inheritance (Clean ACLs) | 48 - 55 GB / hour | ~2.8 to 3.2 hours | < 0.1% errors; zero HTTP 429 throttling |
| Preserve Granular File Permissions | 11 - 14 GB / hour | ~11.5 to 14.0 hours | 4.2% errors; frequent API rate limit pauses |
Every time the migration tool replicates a unique permission on a single file, it makes an independent API call to Microsoft Graph or Google Drive API. Both cloud providers enforce strict rate limits on permission updates. After a burst of 500 permission calls, the API throttles your connection.
- Best practice recommendation: Prior to migration weekend, run a cleanup script or manually reset folder inheritance so all files inherit from their top-level department folder. Then migrate with clean inheritance enabled. You cut migration time by more than 70% and avoid Sunday night panic.
Post-move verification: the 5-persona sampling test
Never declare the migration complete just because the progress bar hit 100%. If you check the folders using your Admin account, everything will look fine because Admins have universal read/write access.
On Sunday evening, perform a structured permission sampling test using five representative staff personas across your six shared folders:
| Department Folder | CEO / Founder | Sales Lead | Junior Engineer | External Contractor | Finance Lead |
|---|---|---|---|---|---|
| 01-General | Full (Edit) | Edit | Edit | Read | Edit |
| 02-Sales | Full (Edit) | Edit | Access Denied | Access Denied | Read |
| 03-Finance | Full (Edit) | Access Denied | Access Denied | Access Denied | Edit |
| 04-Engineering | Full (Edit) | Access Denied | Edit | Restricted (Subfolder only) | Access Denied |
| 05-Client Delivery | Full (Edit) | Edit | Edit | Edit (Assigned project only) | Edit |
| 06-HR & Personnel | Full (Edit) | Access Denied | Access Denied | Access Denied | Access Denied |
Log into the web interface as each persona (or use Incognito test sessions). Attempt to perform three actions in each folder:
1. Open an existing document (Read).
2. Create a temporary text file (Write / Edit).
3. Browse into sensitive subfolders (e.g. Finance > Payroll or HR > Salaries) and verify that Access Denied triggers properly.
The post-migration cleanup checklist
Once verification is complete, lock down the environment before staff arrive on Monday morning:
- [ ] Set tenant external sharing defaults: In SharePoint Admin Center > Policies > Sharing (or Google Admin > Apps > Drive > Sharing settings), confirm that the default link type is 'Specific People' or 'People in your organization', never 'Anyone with the link'.
- [ ] Lock down root folder deletion: In SharePoint, ensure Members do not have Full Control on document libraries so root departmental folders cannot be deleted accidentally.
- [ ] Review orphaned shortcuts: Check for .gshortcut files or unmapped desktop aliases that users kept on their local machines and point them to the new cloud location.
- [ ] Revoke old cloud sharing: In the source environment (the old suite), change sharing settings to 'Restricted to domain' so old external links cannot leak data while the old tenant remains active during the transition month.
- [ ] Send the new link directory: Provide all 10 team members with a clean bookmarks document containing direct links to their department's new SharePoint sites or Google Shared Drives.