Google Workspace and Microsoft 365 migration, planned and secured.
Sorami moves mail, files, scripts and identity between Google Workspace and Microsoft 365. The old tenant stays live until the new one passes your checks.
- Both directions, one method
- Cutover rehearsed on a pilot group first
- Security review before and after the move
- No reseller margin on licences
Mail · Calendar · Drive and SharePoint · Shared Drives · Sites · Apps Script · Sheets and Excel · Chat and Teams · Identity · Devices
Sorami plans, runs and secures workplace migrations between Google Workspace and Microsoft 365 in either direction. We inventory what you have and map it to the target. We pre-stage the data and rehearse the cutover with a pilot group. Then mail routing switches in an agreed window. A security review closes the project.
What does a workplace migration cover?
Infrastructure moves to AWS, Azure or Google Cloud are a different service. This is the office suite.
A workplace migration moves the systems your staff touch every day. Mail, calendars and contacts move first because they carry the deadline. Files follow: My Drive to OneDrive, Shared Drives to SharePoint, or the reverse. Google Sites and SharePoint sites need rebuilding rather than copying. Apps Script and Power Automate flows need a developer rather than a copy tool. So do Sheets formulas and Forms. Chat and Teams history moves where the vendor tool supports it. Identity, single sign-on, device management and mail routing change underneath all of it.
Servers, databases and Kubernetes are not part of this service. Those moves are covered by cloud migration and use a different rollback method.
Which migration page do you need?
Google Workspace to Microsoft 365 migration
Mail, calendars, contacts and Drive move with first-party Microsoft tooling.
Explore the service 02Microsoft 365 to Google Workspace migration
Google retired its Exchange Online path in Workspace Migrate from October 2026.
Explore the service 03SharePoint, OneDrive and Google Drive migration
Copying files is the easy part.
Explore the service 04Apps Script, Power Automate, Sheets and Excel migration
No migration tool converts a script or a QUERY formula.
Explore the service 05Migration security review
A migration copies every open link, stale token and forgotten OAuth app into the new tenant.
Explore the serviceHow does Sorami run a migration?
The same five steps in either direction. Tooling changes, the method does not.
- 01
Inventory
Users and mailbox sizes. Drive and SharePoint volumes. Shared Drives and Sites. Scripts, Forms and integrations. Devices and DNS. Nothing is scoped from memory.
- 02
Design
Target tenant layout and identity source. Licence mix and retention settings. The mail routing plan and the written list of items the tools will not move.
- 03
Pre-stage
Mail, calendar, contacts and files copied while the old tenant keeps serving. Permissions mapped and checked on a sample before the bulk run.
- 04
Pilot and cutover
A pilot group moves first and reports. Then MX records switch in a quiet window, a delta pass catches late mail and devices re-enrol.
- 05
Hypercare and close
A week of fast fixes, then the source tenant is reduced to read-only, retention is confirmed and the security review signs the project off.
Which tools does Sorami use?
First-party tools come first because they are included with your licences. Google Workspace to Microsoft 365 uses the Exchange Online automated batch migration for mail, calendar and contacts, and Migration Manager for Drive and Shared Drives. Microsoft 365 to Google Workspace uses the Google Admin console data import tool for Exchange Online, OneDrive, SharePoint Online and Teams channels.
Where first-party tools stop, for example Google Sites to SharePoint or Google Groups to shared mailboxes, we quote a third-party tool such as BitTitan MigrationWiz or Movebot at the vendor's list price. We name the tool in the plan and you buy the licence. We do not resell it.
What changes for Privacy Act, data residency and Essential Eight?
Microsoft stores core customer data for Australian tenants in the Australia geography. Google Workspace data regions cover the United States and Europe only, so an Australian organisation moving to Google cannot pin data to Australia. The plan states this before the decision, not after.
Privacy Act APP 11 asks for reasonable steps to protect personal information and to destroy it when no longer needed. A migration that leaves an unmanaged copy in the old tenant fails that test. Retention rules in Google Vault or Microsoft Purview do not migrate and are rebuilt by hand. Audit log retention differs too: six months in the Google Admin console, 180 days in Purview Standard.
ASD published Essentials for cloud on 15 October 2026 for organisations that run entirely on SaaS. The Essential Eight is maintained alongside it during the transition. A migration is the natural point to reset MFA, admin roles and application control against both, which the migration security review covers.
How is a workplace migration priced?
Pricing is quoted per user after a 20 minute scoping call. Sorami holds no partner tier with Microsoft or Google and takes no reseller margin, so licences are bought on your account at list price.
The scoping call collects the user count and the mailbox and file volumes. It also records Shared Drives and Sites, the scripts and integrations in use, the identity source and the deadline. The written quote then separates four parts: planning, running the migration, script and formula work and the security review. You can buy one part or all four.
Practical answers.
How long does a Google Workspace to Microsoft 365 migration take?
Elapsed time depends on data volume and the vendor throughput limits, not on effort. Google allows roughly 2 GB of mail per mailbox per day into Exchange Online, so a 20 GB mailbox pre-stages over about ten days while staff keep working. Most small tenants complete in two to four weeks including a pilot and a hypercare week.
Can staff keep working during the migration?
Yes. Data is pre-staged while the old tenant stays live. The only interruption is the cutover window, usually a Friday evening MX change and a weekend delta pass. Devices re-enrol on Monday with a written guide and a help channel.
Do you migrate in both directions?
Yes. Google Workspace to Microsoft 365 and Microsoft 365 to Google Workspace use different first-party tools but the same method: inventory and pre-stage first, then pilot, cutover and review. Each direction has its own page with its own list of items the tools will not move.
Does Sorami resell Microsoft 365 or Google Workspace licences?
No. Sorami holds no partner tier with Microsoft or Google and takes no reseller margin. Licences are bought on your own account. The recommendation on which suite to move to is based on fit, residency and running cost.
Is this the same as cloud migration?
No. Cloud migration moves servers, databases and Kubernetes to AWS, Azure or Google Cloud. Workplace migration moves mail, files, scripts and identity between office suites. Sorami offers both as separate services with separate scoping.
Planning a move between Google Workspace and Microsoft 365?
Send the user count, what runs where and any deadline. We reply within one business day with a time for a 20 minute scoping call.
Last reviewed: