Fix BitTitan Migration Dates in Exchange Online
Why BitTitan Migrations Show the Wrong Date in Exchange Online
Exchange Online is the mail backend powering Microsoft 365 mailboxes, and BitTitan MigrationWiz is frequently used to migrate mailboxes from on-premises Exchange, Lotus Notes, GroupWise, or other platforms into Exchange Online. During the migration, MigrationWiz uploads each message using EWS or IMAP APPEND, and Exchange Online's transport pipeline stamps each message with a Received header containing the upload timestamp.
Exchange Online uses this Received header and the associated PR_MESSAGE_DELIVERY_TIME property to determine the displayed received date. Unlike some mail systems that allow migration tools to set a custom delivery time, Exchange Online's processing consistently applies the actual upload timestamp. This means every migrated email carries the migration date in its delivery time metadata, regardless of the original send date.
The problem is amplified in Exchange Online because the corrupted date propagates through all connected services: Outlook desktop reads it, OWA displays it, mobile clients show it, and Exchange Online's built-in search indexes it. PowerShell scripts that administrators use to query mailbox content by date also return results based on the migration timestamp rather than the original date, complicating post-migration verification and troubleshooting.
How This Affects Exchange Online
In Exchange Online, the corrupted delivery time affects every layer of the mail stack. The Outlook desktop client, Outlook on the web, and mobile apps all display the migration date in the received column. Exchange Online's search service indexes the migration timestamp, so date-range queries in Outlook and OWA return incorrect results.
For administrators, Exchange Online Management Shell commands like Get-MessageTrace and Search-Mailbox use the delivery time property, which now reflects the migration date. Mailbox auditing, journaling rules, and transport rules that reference message dates all operate on the corrupted timestamps. Organizations that rely on Exchange Online's native compliance features (In-Place Hold, Retention Tags) find that these policies apply based on the wrong date, potentially retaining or deleting messages at incorrect intervals.
Frequently Asked Questions
Is this different from the Microsoft 365 date issue?
Exchange Online is the backend service that powers Microsoft 365 mailboxes. The root cause is the same: BitTitan adds a Received header during migration that overrides the displayed date. Fixing it in Exchange Online corrects the date across all Microsoft 365 applications.
Can Exchange Online administrators fix this with PowerShell?
PowerShell cannot modify the Received headers or INTERNALDATE of existing messages in Exchange Online. The only way to fix the dates is to re-insert the corrected messages, which is exactly what Redate.io automates at scale.
Does Redate.io support Exchange Online hybrid environments?
Yes. Redate.io connects to Exchange Online mailboxes directly. Whether the organization runs a hybrid Exchange setup or is fully in the cloud, Redate.io can fix the date corruption on any mailbox accessible via IMAP or Exchange protocols.