Fix BitTitan Migration Dates in Exchange Online

Exchange Online is the mail engine behind every Microsoft 365 mailbox. BitTitan MigrationWiz is one of the go-to tools for moving mailboxes from on-premises Exchange, Lotus Notes, GroupWise, or other legacy platforms into Exchange Online. The migration itself usually goes fine. The dates? Not so much.

Here is what happens. MigrationWiz uploads each message using EWS or IMAP, and Exchange Online's transport pipeline stamps a fresh Received header on every single message. That header carries the upload timestamp - the date of migration, not the date the email was originally sent or received. Exchange Online then uses this Received header and the associated PR_MESSAGE_DELIVERY_TIME property to determine what date gets displayed to users.

The problem? Unlike some mail systems, Exchange Online does not let migration tools override the delivery timestamp. It applies the actual upload time, period. So every migrated email - whether it is from 2018, 2021, or last Tuesday - ends up stamped with the same migration date.

You just migrated 1,200 mailboxes over a weekend using MigrationWiz. Monday morning, your helpdesk gets 400 tickets. Every user's inbox looks like all their emails arrived on Saturday. Date sorting is broken. Search by date returns garbage. And the corrupted timestamp propagates everywhere: Outlook desktop, OWA, mobile clients, even PowerShell queries like Get-MessageTrace and Search-Mailbox. Compliance tools (In-Place Hold, Retention Tags) apply policies based on the wrong date, potentially retaining or deleting messages at incorrect intervals.

The damage is total. Every layer of the Exchange Online stack reads the corrupted delivery time. Outlook desktop shows the migration date. OWA shows it. Mobile apps show it. The built-in search indexes the migration timestamp, so date-range queries return wrong results across every client.

For administrators, it gets worse. Exchange Online Management Shell commands reference the delivery time property, which now reflects the migration date. Mailbox auditing, journaling rules, and transport rules that filter by message date all operate on corrupted timestamps. Can you run a reliable compliance audit when every email appears to have arrived on the same day? No.

Redate.io fixes this through a proprietary correction engine that performs header chain analysis and date metadata reconstruction at the server level. Each message is processed with per-message verification to ensure the original date is accurately restored across all Exchange Online services - without altering message content or attachments. The corrected timestamps propagate automatically to Outlook, OWA, mobile apps, and compliance tools.