Moving Between Google Workspace and Microsoft 365
Email, files and calendars moved over a weekend. Your team logs in Monday morning and everything is where it should be, including the mail from 2015 that nobody wants to admit they still need.
We've run migrations for banks and global firms shifting hundreds of terabytes. Same care, priced for a business with fifteen people. And we run Microsoft 365 in our own business, so we're not recommending something we've only read about.
Which way are you going?
Google Workspace → Microsoft 365
The most common move we do. Usually because the business has grown into Excel, needs Teams, or wants proper Windows device management.
- Gmail to Outlook, with folder structure preserved
- Google Drive and shared drives to OneDrive and SharePoint
- Meet and Chat to Teams
- Licensing sized to what you actually use
Microsoft 365 → Google Workspace
Less common, but we do it just as often for businesses who live in Docs and Sheets and find Microsoft heavier than they need.
- Outlook to Gmail, with rules and filters rebuilt
- OneDrive and SharePoint to Drive and shared drives
- Teams to Meet and Chat
- Straight answer on whether the move is worth it
Tenant to tenant
Two businesses merging, or one splitting in half. Same platform, different tenant, and far more fiddly than it sounds.
- Mailboxes moved between tenants
- Domains transferred without a mail outage
- Duplicate accounts reconciled
- Staged over several weekends if needed
What comes across
The question everyone asks first.
- Every email, including the ones from 2015
- Calendars, with recurring meetings intact
- Contacts and distribution groups
- Files from Google Drive to OneDrive and SharePoint
- Shared drives, with permissions rebuilt
- Your existing email addresses, so nothing changes for your customers
Your data stays in Australia
If you handle personal information, the Australian Privacy Principles apply during a migration just as much as they do day to day. That means knowing where your data physically sits.
We provision tenants in Australian data centre regions and can tell you exactly where everything lives when a client or an auditor asks. Overseas providers can't answer that, and most local ones never think to raise it.
How a migration runs
1. We look at what you have
How many mailboxes, how much mail, what is in Drive, who needs what. Usually an hour on a call.
2. We plan the cutover
Which weekend, what happens to mail sent during the move, and what your team needs to know on Monday.
3. Trial run
We move a few mailboxes first and check everything landed. Nobody finds out their calendar is broken in production.
4. The weekend
The last ninety days of mail and files come across, then mail flow moves. Everything older was already copied during the week.
5. Monday morning
We're around when your team logs in, because that's when the questions turn up.
6. The week after
Old system stays read-only for a while, so nothing is a one-way door.
Bigger, older, or stranger jobs
Legacy archives, Enterprise Vault, cross-platform database moves and compliance-driven retention work are all things we've done at considerable scale. If your migration is more complicated than moving everyone to a new mailbox, it's probably still something we've seen before. Ask.
Tell us which way you're heading
Tell us how many people you have and where you're going. We'll say what it involves and whether it's worth doing.