Skip to content
MigrationSanity

Your company, moved, and a report of what moved.

A managed migration from Google Workspace to Microsoft 365, run for you from start to finish: no staff to train, no plan to write, no migration tool to learn. One fixed price is approved before work begins, and a report accounts for what moved.

Get your fixed quoteSee how it works

From $2,950 · a proof batch first · a report of what moved

FIG 1.1Your tenant, exploded
GOOGLE WORKSPACEMICROSOFT 365MAILCALENDARSCONTACTSMY DRIVESHARED DRIVESCOPIED · GOOGLE NEVER CHANGED

What arrives, and where

Move all of it, or only what you need: mail only, files only, any mix. Whatever you choose runs as one engagement, with one price and one report, and each thing lands where your people will look for it.

Mail

Gmail → Exchange Online

  • Inbox, Sent and DraftsbecomesThe matching Outlook folders
  • Archived mailbecomesOutlook Archive
  • LabelsbecomesCategories
  • StarsbecomesFlags
  • AttachmentsbecomesCarried with their messages
  • Read and unreadbecomesKept as it was

Calendars

Google Calendar → Outlook

  • Your calendarsbecomesOutlook calendars
  • Recurring meetingsbecomesOn the same dates
  • Invitees and responsesbecomesKept on each event

Contacts

Google Contacts → Outlook

  • Saved contactsbecomesOutlook contacts
  • Contact labels and starsbecomesOutlook categories

My Drive

My Drive → OneDrive

  • Each person's filesbecomesTheir own OneDrive
  • FoldersbecomesThe same structure
  • Docs, Sheets, SlidesbecomesWord, Excel, PowerPoint
  • SharingbecomesRe-created for people in the move

Shared drives

Shared drives → SharePoint

  • Shared drivesbecomesSharePoint sites
  • FoldersbecomesThe same structure
  • Docs, Sheets, SlidesbecomesWord, Excel, PowerPoint
  • File created and modified datesbecomesKept

A few Google features work differently in Microsoft 365, and calendars and files carry a few more known limitations than mail. See how each one is handled.

Each item is read, copied and recorded

Take one message. Each part shown here has a matching place in Outlook, and the same care goes into each event, contact and file. Nothing is changed in Google along the way.

FIG 2.1One message, taken apart · sample values
A GMAIL MESSAGEIN OUTLOOKFOLDERInboxFOLDERInboxLABELSClientsTaxCATEGORIESClientsTaxSTARStarredFLAGFlaggedATTACHMENTbudget.xlsxATTACHMENTbudget.xlsxREAD OR UNREADUnreadREAD OR UNREADUnreadDATEMar 4, 2024DATEMar 4, 2024

  1. Read

    Your Google data is read and never changed.

  2. Copied

    Each item goes to its matching place in Microsoft 365.

  3. Checked

    Files are checked as they land.

  4. Recorded

    Every run is recorded as it goes, and your report is built from that record.

Proof, not “it finished”

That record becomes your report. While your move runs, each copy is counted and each file is checked as it lands. When it is done, you hold a report, not just our word that it went fine.

FIG 3.1The move, as it runs · illustration
WAVE 1 · 40 PEOPLEILLUSTRATION · SYNTHETIC NUMBERS

ITEMS ACCOUNTED FOR

100%

RUN COMPLETE · OUTCOMES RECORDED

Filled cell
COPIED AND ACCOUNTED FOR
Open cell
NOT YET REACHED
Ochre
LISTED FOR YOU
DATASETITEMSLISTED
  • MAIL412,8800
    COUNTED
  • CALENDARS9,6140
    COUNTED
  • CONTACTS3,2070
    COUNTED
  • MY DRIVE96,5020
    CHECKED
  • SHARED DRIVES58,1403
    CHECKED

Listed for you, for example: a Google Form in a shared drive. It has no Microsoft 365 file to become, so instead of leaving a broken placeholder we list each one by name in your report, and you decide whether to rebuild it in Microsoft Forms.

How an engagement runs

Five steps from your first message to the report.

Timeline The engagement, start to finish

  1. 1

    Tell us the shape of it

    Headcount, what's moving, and the date that matters. We confirm fit and scope, then quote.

  2. 2

    Approve the number

    One fixed quote for the whole migration. Nothing begins until you've signed off on it.

  3. 3

    Check the proof batch

    A few of your people move first, and you check them in your own tenant.

  4. 4

    The move runs

    Your data copies ahead of time. On the weekend you pick, your admin switches mail over once the agreed checks pass.

  5. 5

    Open the report

    What moved, in a report you can hand to your board.

See a few of your own people land before the rest move

Every engagement starts with a proof batch. A few of your people move first, and you check them in your own Microsoft 365 tenant: their mail in its folders, their labels, their calendars and contacts, and their My Drive files if you ask for them. The full migration runs after you have looked.

FIG 6.1The proof batch
PROOF BATCH · MOVES FIRSTTHE REST · AFTER YOU HAVE CHECKED
FIG 5.1Cutover: new mail follows your MX record
INTERNETSENDERSDNSLOOKUPGOOGLEMICROSOFT 365MX: MICROSOFT 365AFTER CUTOVERMX: GOOGLEBEFORE CUTOVERMX: MICROSOFT 365AFTER CUTOVER · MX UPDATED

What cutover looks like

Once your mail has moved, your admin points your domain's MX record at Microsoft 365, and new mail shifts there as the change spreads across the internet. We can be on the call if you want us there.

  • Point MX at Microsoft 365, so new mail is delivered there.
  • Add Autodiscover, so Outlook finds each mailbox on its own.
  • Update SPF, DKIM and DMARC, so other mail servers trust mail sent from your domain.

Once routing has settled, we run a final mail pass to pick up anything that arrived during the switch. DNS cutover, explained.

Tell us the shape of it.

Four answers is enough to start. We come back with a number, what it covers, and the two or three things we'd need to confirm.

We never ask for credentials here. Access is arranged securely later, by your admin, and you can revoke it at any time.

Engagements start at $2,950, quoted as one fixed number for the whole migration. What moves the number.

Prefer to talk it through? Call (858) 203-1530 or email hello@migrationsanity.com.

How many people are moving?
Optional