In September I started working with a community-run kindergarten that had been running two domains in two different systems for more than a decade. One domain was on Google Workspace, the other on Microsoft 365. And one staff member held every admin password for both. Here's how we planned to migrate Google Workspace to Microsoft 365.
That's a really common way for things to end up when an organisation has grown bit by bit over the years. The plan is to bring everything into Microsoft 365, and to make sure more than one person can get into it.
Start with the list of people
Before we moved a single email, we sat down and went through every account. There were just over 20 in Google and a few fewer in Microsoft, and they didn't line up neatly.
For each one we decided to keep it, merge it with its match in the other system, or retire it. Several went. Some belonged to people who'd left, some had never really been used, and one looked like a typo from when someone set up an account years ago.
One account belonged to a staff member who's away for an extended stretch. We kept that one, because she's coming back and she'll need her email when she does.
It's the dull part, but that session is what stops you paying for, and migrating, accounts nobody needs.
Moving the data from Google Workspace to Microsoft 365
There's well over 100 GB to move, most of it email. So the order matters:
- Copy one account across first as a pilot, and check everything arrived.
- Move the rest once the pilot looks right.
- Leave all the data in Google until we've confirmed it's been copied.
Nothing gets deleted from the old system just because a progress bar says it's done.
Licences and room addresses
The kindergarten qualifies for Microsoft's not-for-profit licensing. They decided to start on the basic plan and leave the security upgrade decision until after their next security audit. That's a sensible call, and it's theirs to make.
Each room's address goes into a shared mailbox, which is one inbox a few people can get into. A shared mailbox doesn't need its own licence, so the room addresses don't add to the count. Our guide to choosing a Microsoft 365 plan covers the difference between the plans and when a shared mailbox is the right fit.
What other organisations can take from it
If your organisation has drifted into two systems, what I'd do first is write down every account, who uses it and whether they still need it. Do that before you touch anything else. And make sure more than one person can get into the admin side.
We handle this kind of move as part of our Microsoft 365 setup for small businesses and community groups. But that list of accounts is something you can start on today with a pen and paper.