Fix BitTitan Migration Dates in Outlook

BitTitan MigrationWiz downloads each email from the source server and uploads it to the destination. Standard migration procedure. But during that upload, the destination mail server stamps a new Received header on every message. That header carries the migration timestamp - not the original delivery date.

Why does Outlook care? Because Outlook determines the date in the "Received" column by reading the topmost Received header in each email's header chain. MigrationWiz's header sits right at the top. So Outlook shows the migration date for every single message in the mailbox. Inbox, sent items, archive folders - all stamped with the same date.

This is broken.

You just migrated 4,237 emails for a sales director who relies on chronological email history to track client communications. She opens Outlook on Monday, and every email from the past six years shows Saturday's date. Sort by date? One giant block. Search for emails from last October? Nothing comes back (actually, everything comes back, dated to the migration day). Her Outlook rules that trigger based on received date misfire or fail entirely.

In corporate environments where MigrationWiz moves hundreds of mailboxes simultaneously, this is not one person's problem. It is an organization-wide crisis on the first business day after migration. Calendar-linked email threads lose their temporal context. Conversation view becomes unreliable when all messages share an identical received timestamp.

Outlook desktop and Outlook for Windows both populate the "Received" column from the IMAP INTERNALDATE and the topmost Received header. After a BitTitan migration, sorting by date groups the entire mailbox into a single day. Finding an email from three months ago means scrolling through thousands of messages with identical dates.

Search is broken too. Date-range filters return incorrect results because the indexed date reflects the migration, not the original delivery. And here is a detail that surprises most admins: Outlook's cached mode (the local .ost file) stores the corrupted date, so even switching to offline mode does not help.

Redate.io uses a proprietary correction engine with pattern matching across migration tool signatures to identify and correct BitTitan-injected metadata at the server level. Each message undergoes targeted metadata correction without altering message content, attachments, or folder structure. Once processed, the original date appears automatically in Outlook desktop, OWA, Outlook mobile, and every other connected client.