Fix CloudM Migration Dates in Microsoft 365

CloudM Migrate is a go-to tool for organizations moving mailboxes from Google Workspace, on-premises Exchange, or other platforms into Microsoft 365. The migration itself usually goes smoothly. Then someone opens Outlook and notices something alarming: every single email - thousands of them - shows the same received date.

What happened? During upload, Exchange Online's transport pipeline treats each migrated message as a fresh delivery. It stamps a new Received header with the current processing timestamp and sets the PR_MESSAGE_DELIVERY_TIME property accordingly. This property is what Outlook desktop, Outlook on the web, Outlook mobile, and even Microsoft's Copilot features all reference when displaying dates. Unlike Google Workspace (where the web client can mask the problem), Microsoft 365 shows the wrong date consistently everywhere.

That consistency is actually what makes the M365 version of this problem so visible. There is no "it works fine in the browser" escape hatch. Every user, on every device, in every Microsoft 365 application sees the migration date. IT teams typically discover the issue within hours of completing the CloudM migration, but by then the damage is already embedded in the message metadata at the server level.

The impact ripples through the entire M365 ecosystem. Outlook desktop, OWA, Outlook mobile, Teams email integration, Microsoft Search - all show the migration timestamp. Users cannot escape the incorrect dates by switching applications. Imagine an attorney searching for "emails received between January and March 2023" in preparation for litigation. The search returns nothing, or returns everything, depending on when the migration happened. That is not a minor inconvenience; it is a potential discovery failure.

Microsoft Purview (formerly Compliance Center) and eDiscovery Premium index messages by the corrupted delivery date. Content searches based on date ranges produce unreliable results. Retention labels applied automatically based on message age operate on the wrong timeline, which means some messages get deleted too early while others are retained indefinitely. Auto-archive policies in Outlook miscalculate message age across the board. For any organization subject to regulatory email retention requirements, this creates a compliance gap that persists until the dates are corrected.