Data Recovery Case File · Email & Application Data · The Local-Only Archive

Mail that never left the machine: a twenty-year Outlook archive, a migration that broke it, and the extraction that didn't need the repair to work

The scale of this enquiry was measured in decades. Switching from Legacy Outlook to the New Outlook for Mac experience, his default profile corrupted during the automatic migration of the local "On My Computer" folders — the folders holding over twenty years of critical email that had never synced to Exchange Online. His rescue attempts were methodical and each hit a wall: the built-in repair first failed demanding 257.5GB of free space on his 1TB Mac; copying the corrupted profile to another Mac with an 8TB drive — a genuinely smart move — bought the space but not the repair, which now failed with a generic could-not-be-completed. And the fallback the internet recommends was closed too, as he'd already established: no .olm export files existed, so third-party OLM repair tools had nothing to chew on. Twenty years, one broken database, every official door shut.

The anatomy — why the repairs failed and the mail hadn't gone anywhere

Two decodes unlock the case. First, the trap he'd been standing in for twenty years without knowing: "On My Computer" means exactly that. Outlook's local folders live only in the Mac's profile — a private database of message records, attachments and indexes — and never touch the server; an archive filed there for two decades has precisely one copy in the universe, inside one application's proprietary store, and a migration is that store being rebuilt wholesale: the single riskiest day of its life. Second, the repair attempts' anatomy: the 257.5GB demand was the repair confessing its method — it rebuilds a profile beside the original, needing workspace on the store's own scale — and the generic failure once space existed was the more fundamental confession: the rebuild walks the database's internal structure, and a structure broken mid-migration can't be walked. His enquiry's key virtues were preservation and diagnosis both: the copy to the 8TB Mac meant a pristine, untouched instance of the corrupted profile existed regardless of what any tool did next — and his no-OLM observation was exactly right, closing the export-repair route and pointing at the only one left: stop asking the application to fix its database, and read the database directly.

The extraction — twenty years, message by message

The profile's message store was parsed forensically on a working copy: its internal records enumerated beneath the broken walkways — each message's content, headers, dates and attachments recovered from the record level, the corruption's actual casualties bounded to the migration's footprint rather than the archive's breadth — and his original folder hierarchy, the filing of twenty years, reconstructed from the store's own metadata. Delivery was designed around the trap the case exposed: everything extracted to standard, application-independent mail formats — importable into current Outlook, Apple Mail, or anything else, and readable in plain form besides — so the archive left its one-application prison permanently. Verification meant opening mail across the decades, oldest folders to newest, attachments included; the losses — messages caught mid-rewrite by the migration itself — were itemised by folder in the report rather than left to be discovered at some future search. And the last deliverable was the cheapest: the archive, now portable, went straight into a second location before it shipped.

Outcome

Twenty years of correspondence recovered from a database its own application had given up on — and the trap named publicly for everyone whose "it's all in Outlook" has quietly meant it's all in one file on one machine. Check where your mail actually lives: local folders — "On My Computer," "On My Mac," archive folders in desktop clients — are single-copy by design, invisible to the server's protections, and at their most fragile precisely during upgrades and migrations, the moments that feel most routine. Export before you migrate; keep the export somewhere second; and treat a decades-old profile like the archive it is rather than the app data it resembles. His had exactly one copy for twenty years. It has three now, in formats that will outlive the application — which is the only place a twenty-year archive should ever live.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.