Fix CloudM Migration Dates in Outlook

You migrated with CloudM. The migration completed successfully. Then you open Outlook and see 30,000 emails all stamped with yesterday's date. Sound familiar?

CloudM Migrate works by downloading messages from the source system and uploading them to the destination. When that destination is Exchange or Microsoft 365, the receiving mail server processes each uploaded message the way it would process any incoming email: it adds a Received header with the current timestamp. This header becomes the most recent entry in the message's header chain, and Outlook reads exactly that header to populate its "Received" column.

The original Date header is still there, buried inside the message. But Outlook does not use it for display. Outlook prioritizes the Received header - specifically the most recent one - and that is the migration timestamp. So every email, whether it was sent in 2015 or last Tuesday, now appears to have arrived on the same day. Sorting by date? Useless. Searching by date range? Broken. The inbox becomes a wall of identically-dated messages with no chronological order whatsoever.

Outlook's default "Arrange by Date" view groups emails into familiar buckets: Today, Yesterday, Last Week, Last Month, Older. After a CloudM migration, every single email lands in a single bucket. The entire mailbox collapses into one undifferentiated block. Have you ever tried to find a specific email from 2021 when 50,000 messages all say they arrived on March 12th, 2026? It is not a productive exercise.

The damage extends to features users rely on daily. Quick Search and Advanced Find return wrong results when filtering by date. Auto-archive, which is supposed to move old emails to a PST file based on age, thinks every email is brand new (because the migration date is recent). Outlook rules triggered by received date misfire. Conditional Formatting rules that highlight emails by age stop working. And calendar-related messages - meeting invitations, RSVPs, cancellations - all show the migration date instead of the original meeting timeline, creating confusion about past scheduling decisions.