HomeCase StudiesGoogle Workspace migration
Nonprofit · 45 people

Google Workspace to Microsoft 365 without losing a grant file.

The organization had Microsoft 365 through nonprofit licensing, but everything that mattered — grants, board docs, program files — lived in Google Drive with tangled sharing and no structure. This is how a 45-person nonprofit moved it all to SharePoint without losing a single grant file, and without spending anything extra on licenses.

380Kfiles moved from Drive
$0extra license spend
2 wksDrive to done
The problem

Microsoft 365 in hand — and everything still in Google Drive.

The organization had done the sensible thing: it secured Microsoft 365 through nonprofit licensing. But licenses don't move files. Day-to-day work never left Google Drive — grant applications and reporting, board documents, program files — all of it living where it had always lived, while the Microsoft tenant sat essentially empty.

Drive itself had grown the way Drive grows when nobody owns the structure. Files were shared person to person, link by link, over years — ownership tied to individual staff accounts, access accumulated one exception at a time. There was no map: whether a document sat in a shared drive or in somebody's My Drive depended on who had created it and when. Finding the right version of the right file meant knowing the folklore.

For a nonprofit, that is more than an inconvenience — grants and board records are exactly the documents the organization can least afford to misplace, and files owned by a personal account are exactly the files that vanish when staff move on. The migration had to carry everything across intact, untangle the sharing on the way through, and do it without adding a single license to the bill.

What we did

Map everything. Move once. Leave nothing stranded.

Nothing moved until everything had a destination. We mapped first, migrated once — with ownership and sharing rebuilt on the way through — and finished with an intranet home and two live training sessions, so the new environment was used, not just populated.

1
Every shared drive mapped

Each shared drive was mapped to an exact SharePoint destination before a single file moved. The map was the migration plan — and nothing moved off-map.

2
A structure designed, not copied

Google Drive's tangle wasn't recreated in new clothes. Grants, board documents and program files each got a proper SharePoint home, organized around how the organization actually works.

3
Ownership brought in-house

Files owned by individual Google accounts became files owned by the organization — so the next staff departure can't strand a grant file in a personal drive.

4
Sharing remapped to groups

Years of person-to-person shares were replaced with Microsoft 365 groups: membership decides access, and every permission finally has an explanation.

5
A simple branded intranet home

The new environment got a front door — a simple, branded intranet home that makes the libraries findable, so day one didn't begin with a blank SharePoint site.

6
Two live training sessions

Staff were trained in two live sessions on the environment they'd actually use: where everything now lives, and how to share a link instead of another copy.

Results

The whole move, in three numbers.

Every file made the trip, the nonprofit licensing they already held covered the tools, and the move ran start to finish in two weeks.

380Kfiles moved from Drive
$0extra license spend
2 wksDrive to done
SharePoint Online ShareGate Microsoft 365 Groups

Working out of Google Drive while Microsoft 365 sits ready?

Book a free 30-minute audit — we'll look at how your files are shared today and show you exactly what a clean move to SharePoint would take.