The Most Common Advice on Every Forum
Search for "emails show wrong date after migration" on any IT forum, and the top answer is almost always the same: "Just sort by sent date instead of received date." This advice appears on Microsoft community forums, Google Workspace help threads, Reddit posts, and Spiceworks discussions. It's become the default response to what is actually a server-level data problem.
The advice is well-intentioned. In Outlook, switching the sort column from "Received" to "Sent" does change the visible order of emails. Messages that appeared to all have the same migration date suddenly sort into their original chronological sequence. At first glance, the problem looks solved.
But it isn't.
Why It Seems to Work
The Visual Improvement
When a user changes the Outlook view to sort by "Date Sent," the inbox immediately looks correct. Emails from 2020 appear before emails from 2023. For a user who was staring at 10,000 emails all showing the same date, this is a dramatic improvement.
It Works in One View, on One Device
The sort-by-sent-date workaround works in exactly one place: the specific folder view, on the specific device, where the user made the change. If the user switches to a different folder, the view may revert. If the user opens email on a different device, the setting doesn't carry over.
All the Ways It Fails
Search Results Still Show Wrong Dates
Email search in Outlook, Gmail, Apple Mail, and Thunderbird indexes messages using the received date (INTERNALDATE), not the sent date. When a user searches for "emails received in March 2022," the search engine checks the INTERNALDATE, which still shows the migration date. The search returns zero results for March 2022 and returns every email for the migration date.
For users who frequently search by date range (accountants looking for invoices from a specific quarter, lawyers gathering correspondence from a case period), this makes the mailbox functionally broken. Changing the sort column doesn't touch what the search engine uses.
Compliance and eDiscovery Are Compromised
Tools like Microsoft Purview, Google Vault, and third-party compliance platforms query server-side metadata including INTERNALDATE. Sorting by sent date in Outlook has zero effect on what these tools retrieve. A legal hold request for "all emails received between January and March 2023" will return incorrect results.
For organizations in finance, healthcare, legal, and government sectors, inaccurate eDiscovery results can lead to sanctions, fines, or adverse legal outcomes.
Must Be Set on Every Device and Every Folder
Outlook doesn't apply view settings globally. Changing the sort column in the Inbox doesn't change it in Sent Items, Drafts, Archive, or custom folders. Each folder must be adjusted individually. Settings are stored locally, meaning they must be repeated on every device. For an organization with 100 users, each with 4 devices and 10 folders, that's 4,000 individual view changes. Who's going to do that?
The INTERNALDATE Is Still Wrong
The IMAP INTERNALDATE remains incorrect on the server. This affects backup tools, future migration tools (which carry forward the wrong INTERNALDATE), API integrations, and email archiving systems. The INTERNALDATE problem persists indefinitely until corrected at the server level.
Email Rules and Filters Use the Received Date
Outlook rules, Gmail filters, and Exchange transport rules based on received date will malfunction. A rule that says "move emails received more than 90 days ago to Archive" may archive everything in the mailbox or nothing. Power Automate flows and Google Apps Scripts that process emails based on received date produce incorrect results.
Some Email Clients Don't Even Support It
Not every email client supports sorting by sent date. Apple Mail on iOS doesn't offer a "sort by sent date" option. Thunderbird handles date columns differently than Outlook. Webmail interfaces (Roundcube, Horde) have limited column customization.
Conversation Threading Breaks
Email clients that support conversation view group related messages based on headers and dates. When received dates are wrong, conversation threading can misorder messages within a thread or display the thread's date stamp as the migration date.
The Actual Fix: Correct the Server-Side Data
The reason "sort by sent date" fails is that it addresses the symptom (wrong display order) without fixing the cause (wrong server-side date metadata). The actual fix requires correcting the date metadata on the server for each affected email.
Once the server-side data is corrected, every email client displays the right date. Search results return accurate date ranges. Compliance tools query correct timestamps. Rules and filters operate on the real received date. No per-device, per-folder settings needed. The fix is permanent and universal.
How Redate.io Performs the Server-Level Fix
Redate.io's proprietary correction engine connects to the mailbox (Google Workspace, Microsoft 365, or any IMAP server) and scans every email to identify those with migration "Received" headers. The scan is free.
For each affected email, the multi-stage analysis pipeline identifies migration signatures through pattern matching across hundreds of known migration tool patterns, applies targeted corrections while preserving message integrity (S/MIME signatures, multipart structures, inline attachments, non-ASCII headers, and dozens of other edge cases), and runs integrity verification on every single corrected email. Originals are moved to a visible backup folder for 30 days. The full process is detailed in how email dates can be fixed after migration.
After the fix, there's nothing to configure in Outlook, no setting to change on each device, and no workaround to remember. The dates are simply correct, everywhere, permanantly.
Stop relying on a workaround that only half-works. Start a free scan to see how many emails have wrong dates, and fix 10 for free to verify the results.