Why Outlook Shows the Wrong Date
After an email migration, Outlook users frequently discover that every email in their mailbox displays the same date - the migration date. This problem affects Outlook Desktop, Outlook for Mac, the new Outlook for Windows, and Outlook Mobile. The root cause is the same across all versions: Outlook determines the "Received" date by reading the most recent "Received" header in the email, and migration tools add a new "Received" header with the migration timestamp.
How Outlook Determines the "Received" Date
When Outlook displays the date of an email, it reads the IMAP INTERNALDATE and the "Received" headers in the message. For the "Received" column (which is the default sort column in most Outlook views), Outlook uses the timestamp from the topmost "Received" header. During a normal email delivery, this header reflects when the message arrived at the recipient's mail server - the actual received date. After migration, the topmost "Received" header reflects when the migration tool inserted the message into the new server.
The Difference Between "Sent" and "Received" in Outlook
Outlook distinguishes between two date columns: "Sent" (from the "Date" header in the email) and "Received" (from the "Received" headers or INTERNALDATE). After migration, the "Sent" date may still be correct because the original "Date" header is preserved. However, the "Received" date shows the migration timestamp. Since Outlook's default view sorts by "Received" date, and most users never change this, the migration date is what everyone sees.
Quick Check - Is This a Migration Date Issue?
Before attempting a fix, confirm that the problem is caused by migration headers rather than another issue.
How to View Raw Email Headers in Outlook
In Outlook Desktop, open the affected email, click "File" then "Properties." The "Internet headers" box at the bottom shows the raw headers. Look for "Received" headers near the top. In Outlook on the web (OWA), open the email, click the three dots menu, then "View" and "View message details." The raw headers appear in a popup window.
Identifying the Migration "Received" Header
Look for a "Received" header that contains references to the migration tool. Common patterns include "mx.migrationwiz.com" for BitTitan, "cloudm.io" for CloudM, or a generic "localhost" entry with a timestamp matching the migration date. If the topmost "Received" header has a date that matches the migration date (and differs from the original message date), the problem is confirmed. This is the header that Redate.io identifies and removes. For tool-specific guides, see fixing Outlook dates after BitTitan, CloudM, imapsync, GSMMO, Exchange IMAP, or manual IMAP copy migrations.
Solutions That Don't Work
Outlook users and IT administrators typically try several approaches before realizing that the fix must happen at the server level, not in the Outlook client.
Changing Column to "Sent" Date
Switching the Outlook view from "Received" to "Sent" date is the most common workaround. While this changes the sort order, it does not fix the underlying data. Search results still reference the wrong received date. Rules and filters based on received date malfunction. Compliance and eDiscovery tools that rely on received timestamps produce incorrect results. And users must change this setting on every device and in every folder - a support burden that scales poorly across an organization.
Rebuilding OST/PST Files
Some administrators attempt to fix the problem by deleting the local Outlook cache (OST file) and letting Outlook re-sync from the server. This does not help because the problem exists on the server side, not in the local cache. The re-synced data contains the same migration "Received" headers, so the dates remain wrong. Similarly, exporting to PST and re-importing does not remove the migration headers.
Outlook View Settings
Adjusting Outlook view settings, conditional formatting, or group-by options cannot change the date that Outlook reads from the email headers. These settings control how data is displayed and organized, but the underlying date value comes from the server. No combination of view settings can make Outlook ignore the migration "Received" header.
The Fix - Restore Correct Dates at the Server Level
The only way to fix wrong dates in Outlook after migration is to correct the emails on the server. Once the server-side data is corrected, Outlook automatically displays the right dates on the next sync. No client-side changes needed.
Why can't you just do it yourself with a script? Because this is far more complex than a find-and-replace operation. Each email has a unique header structure. Some messages carry S/MIME digital signatures that become invalid if a single byte changes. Others have PGP encryption, nested MIME parts, non-ASCII encoded headers (RFC 2047), or Content-Transfer-Encoding quirks that trip up naive parsing. Corrupted MIME boundaries can silently destroy attachments. Broken threading can scatter conversations across the mailbox. And without proper verification, you won't even know something went wrong until a user reports a missing attachment three weeks later.
How Redate.io Fixes Outlook Dates
Redate.io connects directly to the email server (Google Workspace, Microsoft 365, or any IMAP server) and processes each email through its proprietary correction engine. The engine runs a multi-stage analysis pipeline that handles pattern matching across hundreds of known migration tool signatures, preserves message integrity across complex MIME structures, and verifies every correction before finalizing it. Original messages are moved to a visible "Redate.io - Originals" folder for 30 days.
After Redate.io completes the fix, Outlook picks up the corrected dates on its next sync. No changes are needed in Outlook settings. The fix works across all Outlook versions because the correction happens at the server level.
Before and After
Before the fix, an Outlook inbox after migration shows every email with the same received date - for example, "April 11, 2019" on messages originally sent between 2015 and 2019. After Redate.io processes the mailbox, the same inbox displays the correct original dates. Emails from 2015 show 2015 dates, emails from 2018 show 2018 dates. Sorting by date works correctly again, and search results return accurate timestamps.
Step-by-Step Guide
Fixing wrong Outlook dates with Redate.io takes three steps, regardless of the email platform.
Google Workspace Users
For organizations using Google Workspace, the administrator creates a Service Account with domain-wide delegation. This allows Redate.io to access mailboxes without requiring individual user passwords. The admin enters the Service Account credentials in Redate.io, selects the mailboxes to fix, and runs the free scan. The scan identifies how many emails have wrong dates in each mailbox. After reviewing the results, the admin selects a pricing plan and starts the fix. Redate.io processes all selected mailboxes automatically. Users see corrected dates in Outlook (and any other client) after the next sync.
Microsoft 365 Users
For Microsoft 365 organizations, the administrator registers an Azure AD application with the appropriate mail permissions. Redate.io uses this application to access Exchange Online mailboxes via the Microsoft Graph API or IMAP. The process is the same: connect, scan for free, review results, then fix. Admin consent is required once and covers all mailboxes in the tenant.
Other IMAP Servers
For mailboxes hosted on other IMAP servers (Zimbra, Zoho, cPanel, Dovecot, Courier), users connect with their standard email credentials (server address, username, password). Redate.io connects via IMAP, scans the mailbox, and applies the same fix. This option works for individual mailboxes and does not require administrator access to the server.
Regardless of the platform, the result is the same: Outlook displays the correct original dates, sorting works properly, and the mailbox's chronological order is fully restored.
Outlook showing wrong dates after migration? Start a free scan with Redate.io to see how many emails are affected and restore correct dates automatically.