migrating toBrowse playbooks
← All playbooks
Office suites migration

Microsoft 365 → Google Workspace

Move users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions, documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings from Microsoft 365 to Google Workspace with a reversible cutover, explicit exception ledger, and evidence-backed verification.

Typical timeline15–45 business days70–180 hours active work
Statusneeds review
Source profileMicrosoft 365 documentation reviewed 2026-07-20
Destination profileGoogle Workspace documentation reviewed 2026-07-20
Documentation date
Review window
Evidence2 sources
This route needs review.Use it as a planning baseline, then verify the dated sources and test with representative data before production.
Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Microsoft 365

Reasons to stay
  • Office applications, Exchange, Teams, SharePoint, identity, endpoint management, and compliance form a deep enterprise suite
  • Mail, documents, calendars, storage, and collaboration share one managed productivity environment
Reasons to leave
  • Licensing, tenant architecture, native formats, retention, and interconnected workloads make migrations extensive
  • Native file formats, permissions, identity, retention, and adjacent apps create a very broad migration surface
New platform

Google Workspace

What gets better
  • Browser-native collaboration makes mail, documents, calendars, meetings, and storage easy to administer
  • Mail, documents, calendars, storage, and collaboration share one managed productivity environment
What gets worse
  • Google-native file formats, labels, shared drives, Vault, and identity semantics complicate migration
  • Native file formats, permissions, identity, retention, and adjacent apps create a very broad migration surface
Best of the move

Google Workspace: Browser-native collaboration makes mail, documents, calendars, meetings, and storage easy to administer. This removes a major source-side concern: Licensing, tenant architecture, native formats, retention, and interconnected workloads make migrations extensive.

Worst of the move

What you lose: Office applications, Exchange, Teams, SharePoint, identity, endpoint management, and compliance form a deep enterprise suite. What you inherit: Google-native file formats, labels, shared drives, Vault, and identity semantics complicate migration.

Connected catalog

2 destinations are documented from Microsoft 365. Compare nearby routes before committing.

Also from Microsoft 365
Also moving to Google Workspace
Jump to a section
01At a glance

Know the shape of the move.

Transfer outcome10 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 7, Manual rebuild: 3, Not transferred: 0.
Clean0
Partial7
Manual3
Lost0
Mapping route9 of 9 fields have a destination path

This timeline assumes

  • Up to 10,000 users, 500 TB of files and mail, 50 million calendar events, and 10 years of retained evidence
  • Administrators control both Microsoft 365 and Google Workspace, including billing, identity, APIs, integrations, and export permissions.
  • Microsoft 365 remains intact and recoverable until Google Workspace completes one representative operating cycle.
  • A production-shaped pilot includes every object type, access class, edge case, and failure path.
  • The migration team preserves stable source identifiers and records durable evidence for every blocking check.
02What transfers

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

ItemOutcomeImpactWhat happensMitigation
Users, groups, domains, aliases, and identitypartialcriticalAccount IDs, aliases, groups, licenses, federated identity, MFA, and recovery require coordinated provisioning. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map users, groups, domains, aliases, and identity explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Mailboxes, folders, labels, rules, and archivespartialcriticalFolders versus labels, message IDs, flags, delegated mailboxes, rules, archives, and retention differ. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map mailboxes, folders, labels, rules, and archives explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Calendars, events, rooms, and delegationpartialcriticalRecurring series, organizers, responses, resources, permissions, time zones, and conferencing need mapping. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map calendars, events, rooms, and delegation explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Files, folders, shared drives, and permissionspartialcriticalOwnership, shared spaces, links, inheritance, external access, versions, and paths transform differently. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map files, folders, shared drives, and permissions explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Documents, spreadsheets, and presentationspartialcriticalNative formats, formulas, macros, fonts, charts, comments, and collaborative history can lose fidelity. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map documents, spreadsheets, and presentations explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Chat, meetings, recordings, and team spacespartialcriticalConversation history, channels, direct messages, meeting links, recordings, and apps have separate coverage. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map chat, meetings, recordings, and team spaces explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Sites, forms, notes, tasks, and adjacent appspartialhighSuite-specific applications and embedded workflows often lack direct destination equivalents. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Map sites, forms, notes, tasks, and adjacent apps explicitly, pilot every feature class, and reconcile accepted, changed, rejected, and excluded items.
Devices, endpoint policy, and application settingsmanualcriticalEnrollment, device trust, compliance, configuration profiles, desktop apps, and mobile controls require rollout. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Inventory and rebuild devices, endpoint policy, and application settings, then test normal, edge, failure, and rollback behavior.
Retention, eDiscovery, audit, and legal holdsmanualcriticalVaults, holds, labels, retention, cases, audit evidence, and regulatory boundaries need legal validation. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Inventory and rebuild retention, ediscovery, audit, and legal holds, then test normal, edge, failure, and rollback behavior.
DNS, integrations, automation, and cutovermanualcriticalMX, autodiscover, SPF, DKIM, SSO, APIs, third-party apps, and mail routing must switch in controlled phases. A successful bulk job therefore does not prove semantic parity between Microsoft 365 and Google Workspace.Inventory and rebuild dns, integrations, automation, and cutover, then test normal, edge, failure, and rollback behavior.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
Microsoft 365: Users, groups, domains, aliases, and identityGoogle Workspace: approved users, groups, domains, aliases, and identity representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for users, groups, domains, aliases, and identity.
Microsoft 365: Mailboxes, folders, labels, rules, and archivesGoogle Workspace: approved mailboxes, folders, labels, rules, and archives representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for mailboxes, folders, labels, rules, and archives.
Microsoft 365: Calendars, events, rooms, and delegationGoogle Workspace: approved calendars, events, rooms, and delegation representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for calendars, events, rooms, and delegation.
Microsoft 365: Files, folders, shared drives, and permissionsGoogle Workspace: approved files, folders, shared drives, and permissions representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for files, folders, shared drives, and permissions.
Microsoft 365: Documents, spreadsheets, and presentationsGoogle Workspace: approved documents, spreadsheets, and presentations representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for documents, spreadsheets, and presentations.
Microsoft 365: Chat, meetings, recordings, and team spacesGoogle Workspace: approved chat, meetings, recordings, and team spaces representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for chat, meetings, recordings, and team spaces.
Microsoft 365: Sites, forms, notes, tasks, and adjacent appsGoogle Workspace: approved sites, forms, notes, tasks, and adjacent apps representationtransformPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for sites, forms, notes, tasks, and adjacent apps.
Microsoft 365: Devices, endpoint policy, and application settingsGoogle Workspace: approved devices, endpoint policy, and application settings representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for devices, endpoint policy, and application settings.
Microsoft 365: Retention, eDiscovery, audit, and legal holdsGoogle Workspace: approved retention, ediscovery, audit, and legal holds representationmanualPreserve source IDs, ownership, timestamps, access intent, and an explicit exception status for retention, ediscovery, audit, and legal holds.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Microsoft 365 data, configuration, access, and operating evidence before any destination write.

  1. Export every available Microsoft 365 object and binary in scope, including users, groups, domains, aliases, and identity, mailboxes, folders, labels, rules, and archives, calendars, events, rooms, and delegation, files, folders, shared drives, and permissions.
  2. Capture configuration and runtime dependencies for documents, spreadsheets, and presentations, chat, meetings, recordings, and team spaces, sites, forms, notes, tasks, and adjacent apps, devices, endpoint policy, and application settings.
  3. Record counts, sizes, owners, timestamps, access classes, financial totals where applicable, and known exceptions.
  4. Hash immutable exports, record tool versions and commands, and transform working copies only.

Proof to capture: A signed manifest accounts for every scoped record class, configuration object, binary, count, total, exception, and hash.

Transformation · Version-controlled migration workbook, SQL, or typed transformation code

Identity, schema, and disposition registry

Preserve stable identity and make every mapping or exclusion reviewable.

  1. Inventory source types, identifiers, owners, states, and access.
  2. Define one approved destination representation or explicit archive decision.
  3. Reject unmapped critical items and produce an exception ledger.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Official APIs, provider importers, checksums, and reconciliation scripts

Dependency-ordered migration package

Load prerequisite identities and configuration before dependent records and runtime actions.

  1. Normalize encoding, timestamps, identifiers, nulls, and destination limits.
  2. Run a representative pilot and retain request, response, and rejection evidence.
  3. Reconcile the final delta before enabling destination production writers.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Import

A completed migration hides missing or altered users, groups, domains, aliases, and identity

criticalpossible likelihood

Headline counts look plausible while semantic, access, or relationship checks fail.

Consequence
The destination becomes authoritative with incomplete or misleading business data.
Mitigation
Reconcile by type, state, owner, access class, and representative record rather than total count alone.

Stop if: Any critical item lacks a verified destination, approved transformation, explicit exclusion, or recoverable archive.

Cutover

Microsoft 365 and Google Workspace both perform production actions

criticalpossible likelihood

Users, schedules, webhooks, integrations, or traffic continue changing both systems.

Consequence
State diverges or customers receive duplicate, contradictory, or unsafe actions.
Mitigation
Freeze source writers and transfer one production owner at a time with an approved rollback.

Stop if: An unapproved source writer or destination duplicate action appears after the freeze.

Verification

Destination access or security is broader than approved

criticalpossible likelihood

A representative restricted user can read, change, export, or trigger an unauthorized item.

Consequence
Confidential, regulated, financial, or security-sensitive data is exposed or changed.
Mitigation
Apply least privilege before bulk loading and test every access class using ordinary identities.

Stop if: Any unauthorized read, write, export, administrative action, or secret access succeeds.

06Precise timeline

Do the work in this order.

Estimate forUp to 10,000 users, 500 TB of files and mail, 50 million calendar events, and 10 years of retained evidence
Total elapsed15–45 business days
Active work70–180 hours
BufferAdd time for large Microsoft 365 exports, destination rate limits, unsupported features, identity exceptions, regulated data, or a strict downtime objective.
01
Days 1–4Inventory and decisions2–4 days
02
Days 3–8Backup and reconcile2–5 days
03
Days 6–20Map, transform, and pilot5–12 days
04
Days 18–35Bulk load, final delta, and switch2–8 days
05
Days 25–45Observe and close7–14 days
  1. Days 1–4 · inventory

    Inventory and decisions

    8–16 hours active2–4 days elapsedOwner, legal, security, and finance review waiting
    • Inventory Microsoft 365 data, configuration, identities, integrations, limits, and billing.
    • Approve scope, owners, mappings, exclusions, acceptance thresholds, and rollback authority.

    Depends on: Microsoft 365 and Google Workspace administrator access

    Stop / go checkpoint

    Export?

    Go when: Every critical item and production action has an owner and disposition.

    Stop when: Authority, retention, billing, access, or system ownership is unclear.

  2. Days 3–8 · backup

    Backup and reconcile

    8–20 hours active2–5 days elapsedProvider export processing waiting
    • Create immutable data, configuration, binary, and audit exports.
    • Reconcile source counts, totals, sizes, access classes, and hashes.

    Depends on: Approved inventory and retention location

    Stop / go checkpoint

    Transform?

    Go when: The signed source manifest and exports agree.

    Stop when: Any critical dataset, binary, configuration, or recovery path is absent.

  3. Days 6–20 · pilot

    Map, transform, and pilot

    25–70 hours active5–12 days elapsedDestination processing and owner review waiting
    • Configure Google Workspace and transform a production-shaped pilot.
    • Test normal records, every feature class, edge cases, permissions, failures, and rollback.

    Depends on: Verified source backup and approved mapping registry

    Stop / go checkpoint

    Scale?

    Go when: Every pilot mapping and blocking verification check passes.

    Stop when: Any critical invariant, access boundary, or production action lacks a safe destination.

  4. Days 18–35 · cutover

    Bulk load, final delta, and switch

    20–55 hours active2–8 days elapsedImports, propagation, indexing, or synchronization waiting
    • Freeze production writes and automated actions in Microsoft 365.
    • Apply and reconcile the final delta, switch ownership to Google Workspace, and run all blocking checks.

    Depends on: Passed pilot, stakeholder go decision, and rehearsed rollback

    Stop / go checkpoint

    Open production?

    Go when: Google Workspace is the sole production owner and every critical exception is resolved.

    Stop when: A source writer remains active, a blocking check fails, or rollback is unavailable.

  5. Days 25–45 · observe

    Observe and close

    9–19 hours active7–14 days elapsedRepresentative operating-cycle evidence waiting
    • Monitor correctness, access, failures, latency, delivery, cost, and user outcomes.
    • Sign the verification report and close rollback only after stable evidence.

    Depends on: Verified cutover

    Stop / go checkpoint

    Close rollback?

    Go when: No trigger occurs during the approved observation period.

    Stop when: Data, access, delivery, routing, cost, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Google Workspace the only production system without losing the final Microsoft 365 delta.

Recommended window: A low-volume weekday morning with platform, data, security, networking, finance, and business owners available.

  1. Freeze user, integration, schedule, and API writes in Microsoft 365.
  2. Capture and reconcile the final source delta against the last verified checkpoint.
  3. Apply the approved delta and configuration changes to Google Workspace.
  4. Switch traffic, domains, integrations, credentials, automation, and user entry points in dependency order.
  5. Run every blocking verification check and keep the source intact.

Proof to capture: Google Workspace alone owns production, totals reconcile, exceptions are signed, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Microsoft 365 without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, keys, or retention settings are changed.

  1. Stop new user, integration, schedule, and API writes in Google Workspace.
  2. Restore prior Microsoft 365 traffic, domains, credentials, automation, and integration ownership.
  3. Export and classify the Google Workspace post-cutover delta.
  4. Apply safe destination-era changes back to Microsoft 365 without duplicating actions.
  5. Run the same blocking checks against the restored source.

Proof to capture: Microsoft 365 again owns production with current data and no duplicate destination action.

Rollback immediately when
  • Unexplained critical count, value, relationship, or checksum variance
  • Missing, corrupted, or exposed critical data
  • Duplicate production action or unresolved split-brain state
  • Failed access, security, delivery, routing, performance, or integration check
  • A critical feature has no safe destination replacement or rollback path
08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingUsers, groups, domains, aliases, and identity reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for users, groups, domains, aliases, and identity.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Users, groups, domains, aliases, and identity ledger with counts, exceptions, sample IDs, and owner sign-off.
V-02BlockingMailboxes, folders, labels, rules, and archives reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for mailboxes, folders, labels, rules, and archives.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Mailboxes, folders, labels, rules, and archives ledger with counts, exceptions, sample IDs, and owner sign-off.
V-03BlockingCalendars, events, rooms, and delegation reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for calendars, events, rooms, and delegation.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Calendars, events, rooms, and delegation ledger with counts, exceptions, sample IDs, and owner sign-off.
V-04BlockingFiles, folders, shared drives, and permissions reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for files, folders, shared drives, and permissions.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Files, folders, shared drives, and permissions ledger with counts, exceptions, sample IDs, and owner sign-off.
V-05BlockingDocuments, spreadsheets, and presentations reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for documents, spreadsheets, and presentations.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Documents, spreadsheets, and presentations ledger with counts, exceptions, sample IDs, and owner sign-off.
V-06BlockingChat, meetings, recordings, and team spaces reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for chat, meetings, recordings, and team spaces.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Chat, meetings, recordings, and team spaces ledger with counts, exceptions, sample IDs, and owner sign-off.
V-07Sites, forms, notes, tasks, and adjacent apps reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for sites, forms, notes, tasks, and adjacent apps.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Sites, forms, notes, tasks, and adjacent apps ledger with counts, exceptions, sample IDs, and owner sign-off.
V-08BlockingDevices, endpoint policy, and application settings reconciliationCompare source inventory, transformed output, destination results, and a stratified sample for devices, endpoint policy, and application settings.Every in-scope item is present, intentionally transformed, explicitly excluded, or retained in the signed source archive.Devices, endpoint policy, and application settings ledger with counts, exceptions, sample IDs, and owner sign-off.
09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check and exception.

  1. Create final Microsoft 365 exports and archive verification, access, financial, and rollback evidence.
  2. Revoke temporary credentials, API keys, webhooks, elevated roles, and migration network access.
  3. Remove obsolete jobs, embeds, domains, integrations, collectors, routes, and DNS records.
  4. Keep the source intact and read-only through the approved legal and operational retention window.
  5. Cancel paid plans only after billing, legal, security, evidence, and recovery review.
  6. Schedule the next Google Workspace backup, restore test, access review, and migration-playbook review.
10Experiences from the field

When the plan met reality.

First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.

Devoteam's Vitaly case study covers moving more than 2,500 people from Microsoft 365 to Google Workspace during a merger. The project paired the technical transfer with a formal change-management plan and synchronized calendars before the main migration to reduce overlapping or missing meetings. The account is useful for its emphasis on user adoption and calendar continuity at organization scale.

What they recommend
  • Treat communications, training, and local champions as migration workstreams with owners and deadlines, not post-launch extras.
  • Synchronize and validate calendars before the main cutover so existing meetings remain usable across the transition.
Worth noticing
  • The 2,500-user move was framed as an organizational adoption project as much as a mail and file transfer.
  • Calendar synchronization reduced an immediate source of disruption while the two collaboration environments converged.
Sources and evidence

Verify against the primary material.

Platform behavior changes. Check these sources and the review dates above before executing a production migration.

  1. Microsoft 365: official portability and migration documentationAccessed 2026-07-20
  2. Google Workspace: official portability and migration documentationAccessed 2026-07-20