Fix GSMMO Migration Dates in Outlook

GSMMO (Google Workspace Migration for Microsoft Outlook) is Google's official tool for migrating PST files and Outlook profiles into Google Workspace. It reads emails from your local Outlook data and uploads them to your Google Workspace account via the Gmail API. During this upload, Gmail stamps each message with the current upload timestamp as the INTERNALDATE and adds a Received header reflecting the migration date.

Then comes the irony. You migrated away from Outlook to Google Workspace using GSMMO, but you still need Outlook (maybe your company requires it, or you just prefer it). So you connect Outlook back to your Google Workspace account via IMAP or Google Workspace Sync. Outlook reads the IMAP INTERNALDATE and the topmost Received header - both now contain the migration date. Every email that displayed perfectly in your old PST file now shows the GSMMO migration date in Outlook's received column.

What makes GSMMO migrations particularly painful is the expectation gap. Users follow Google's own step-by-step migration guide. They expect the process to be transparent, preserving their email history exactly as it was. Nobody warns them that the date metadata will be overwritten. The problem is discovered days later when they open Outlook and find 8 years of email history all stamped with last Tuesday's date. And because GSMMO is a self-service tool, the affected users are often individuals without IT support to diagnose the issue.

Think about how you use Outlook. You sort by date. You scan the received column to find that email from three months ago. You use date ranges in search. All of that breaks after a GSMMO migration. Every email - client proposals from 2018, invoices from 2021, team discussions from last quarter - shows the identical migration date. Outlook's date-sorted view becomes a wall of identical timestamps.

Outlook's conversation view still groups related messages by subject and message-ID, so threading technically works. But the date displayed next to each message in the conversation is wrong, making it impossible to understand when each reply was actually sent. Calendar invitations and meeting responses in the migrated mailbox show the migration date, which creates confusion when reviewing past scheduling decisions. Outlook's search filters that rely on received date (like "received: last month") return either everything or nothing, depending on when the migration happened. For professionals who depend on Outlook's date-based organization to manage hundreds of emails daily, a GSMMO migration effectively destroys their workflow.

Redate.io fixes this through pattern matching across GSMMO migration tool signatures combined with safe low-level message handling. The correction targets only the date metadata - message content, attachments, and folder structure remain untouched. Every corrected message is verified individually against its original Date header.