Fix CloudM Migration Dates in Gmail
Why CloudM Migrations Show the Wrong Date in Gmail
CloudM Migrate (formerly Cloud Migrator) is widely used for migrating mailboxes into Google Workspace. CloudM uses the Gmail API to upload emails to the destination Gmail account. During this upload, Gmail's infrastructure records the insertion timestamp as the message's INTERNALDATE, overwriting the original delivery date with the date the migration was performed.
CloudM attempts to preserve the original Date header within the email body, and Gmail's web interface typically uses this Date header for display purposes. However, the IMAP INTERNALDATE is permanently set to the migration date. Every IMAP client that connects to the Gmail account (Outlook, Apple Mail, Thunderbird, mobile clients using IMAP) reads this INTERNALDATE and displays the migration date in the received column.
Organizations migrating from Microsoft 365, on-premises Exchange, or other platforms to Google Workspace using CloudM discover this problem when users connect desktop clients to their new Gmail accounts. The Gmail web interface may look fine, but Outlook and Apple Mail show every email as received on the migration date, generating confusion and support tickets across the organization.
How This Affects Gmail
In Gmail, the impact depends on how the user accesses their mailbox. The Gmail web interface typically displays dates correctly because it reads the Date header from the email itself. However, any IMAP-connected client (Outlook, Apple Mail, Thunderbird) shows the migration date because these clients rely on the IMAP INTERNALDATE rather than the Date header.
Gmail's label system and search are also affected in subtle ways. While Gmail's web search uses the Date header for "before:" and "after:" operators, the IMAP SEARCH DATE command uses INTERNALDATE. Third-party backup tools and email archiving solutions that connect via IMAP archive the migration date as the message date, creating permanent inaccuracies in backup records. Google Vault, used for compliance and legal hold, may also reference the INTERNALDATE for certain operations, impacting the accuracy of date-based legal discovery.
Frequently Asked Questions
Does CloudM Migrate always corrupt dates in Gmail?
CloudM uploads emails using the Gmail API, which sets the INTERNALDATE to the upload timestamp. The Date header inside the email is preserved, so Gmail web usually shows the correct date. But IMAP clients display the migration date because they read the INTERNALDATE.
Why do emails look fine in Gmail web but wrong in Outlook?
Gmail web uses the Date header from the email body for display, which CloudM preserves. Outlook and other IMAP clients use the IMAP INTERNALDATE, which is set to the migration date. Redate.io corrects the INTERNALDATE so all clients show the right date.
Can Redate.io fix CloudM migration dates across a whole Google Workspace domain?
Yes. Using Google Workspace domain-wide delegation, Redate.io can scan and fix mailboxes across the entire organization. Administrators can process multiple mailboxes without needing individual user involvement.