Fix CloudM Migration Dates in Microsoft 365
Why CloudM Migrations Show the Wrong Date in Microsoft 365
CloudM Migrate is commonly used to migrate mailboxes from Google Workspace, on-premises Exchange, and other platforms into Microsoft 365. When CloudM uploads emails to Microsoft 365, the Exchange Online transport pipeline processes each message and adds a Received header with the current upload timestamp. This becomes the most recent Received header in the message's header chain.
Microsoft 365 uses this delivery timestamp across its entire ecosystem. Outlook desktop, Outlook on the web, Outlook mobile, and even Microsoft's AI-powered features all reference the same PR_MESSAGE_DELIVERY_TIME property, which is set from the migration Received header. Unlike Google Workspace (where the web client can mask the issue), Microsoft 365 displays the migration date consistently across all its client applications.
The consistency of the wrong date across all Microsoft 365 clients makes the problem immediately visible to every user. After a CloudM migration to Microsoft 365, the entire organization sees the same symptom: every email in every mailbox appears to have been received on the migration date. There is no client-specific workaround; the date corruption is embedded in the message metadata at the server level.
How This Affects Microsoft 365
Microsoft 365's unified date handling means the migration date appears everywhere simultaneously. Outlook desktop, OWA, Outlook mobile, Teams email integration, and Microsoft Search all show the wrong received date. Users cannot escape the incorrect dates by switching to a different Microsoft 365 application.
For Microsoft 365 administrators, the impact extends to management and compliance tools. The Exchange Admin Center, Microsoft Purview (formerly Compliance Center), and eDiscovery Premium all index messages by the corrupted delivery date. Content searches for emails within a specific date range return incorrect results. Retention labels applied automatically based on message age operate on the wrong timeline, potentially causing premature deletion or indefinite retention of messages that should have been handled differently.
Frequently Asked Questions
Does CloudM offer any option to prevent date corruption during M365 migration?
CloudM preserves the original Date header, but the destination server (Exchange Online) adds its own Received header during message upload. This is a server-side behavior that migration tools cannot prevent. The only solution is to correct the dates after migration.
Can Microsoft 365 admin tools fix the dates?
No. Microsoft 365 does not provide built-in tools to modify the Received headers or delivery time of existing messages. Redate.io is designed specifically for this problem: it strips the migration header and re-inserts the email with the correct INTERNALDATE.
Is the fix permanent in Microsoft 365?
Yes. Once Redate.io corrects the email, the original message (with the wrong date) is moved to a backup label. The corrected message has the proper Received headers and INTERNALDATE, and Microsoft 365 indexes the correct date going forward.