Getting an .olm into Outlook for Windows (and a .pst out)
Almost nobody wants a .pst for its own sake. What you want is the mail from a Mac colleague's archive sitting in Outlook for Windows, and .pst is the file Outlook writes when it exports. So the route is: convert the archive to a format Outlook accepts, put the messages into Outlook, then use Outlook's own export to produce the .pst. No converter purchase, and the .pst is written by Outlook, which is the only thing that writes one properly.
We do not generate PST files here, and we will not pretend to. A .pst is a binary database of B-tree nodes rather than a container of messages, so making one means rebuilding the database, not work a browser tab can do reliably. A .pst that Outlook refuses to open is worse than no file at all.
The file you get
From this site, a .zip of .eml files, one per message. From Outlook, after the import, a .pst containing the same mail, produced by Outlook's own Import/Export wizard.
Steps
- Get the .olm out of Outlook for Mac first: Tools tab → Export, tick what you want, Continue, save the file. If Export is greyed out you are in the new Outlook; switch the New Outlook toggle off, top right, and it comes back.
- Drop the
.olmon this page. It is read by JavaScript in your browser tab; the file never leaves your machine. - Export to EML and unzip the result. One
.emlper message, in folders matching the Outlook tree. - In classic Outlook for Windows, create a new folder (right-click your mailbox → New Folder) and name it for the archive.
- Drag the
.emlfiles into that new folder, in batches of about 20 to 30. Dropping them onto the Inbox can make Outlook treat them as attachments instead of messages, so always drop into a folder you made. Widely reported to work; Microsoft does not document.emlimport, so check that the first batch arrived as real messages before doing the rest. - Export the folder: File → Open & Export → Import/Export → Export to a file → Next → Outlook Data File (.pst) → Next. Pick the folder, tick Include subfolders, click Browse, name the file, then Finish. Set a password or leave it blank.
- The
.pstis now on disk, made by Outlook, openable by any Outlook.
What carries over
- Every message with its headers, body and attachments, through EML and into Outlook
- Folder structure, if you recreate the folders in Outlook and drop each folder's files into its own
- Original dates on the messages
- Everything Outlook itself then writes into the
.pston export
Good to know
- The reliable alternative to drag-and-drop, and the better route for thousands of messages: convert to MBOX, import that into Thunderbird (Local Folders), add the destination mailbox to Thunderbird as IMAP, and drag the folders onto it. The mail goes up to the server; open the same account in Outlook for Windows and export to
.pstfrom there. Slower, but it does not depend on undocumented drag behaviour. - New Outlook for Windows cannot import a
.pstand does not handle calendar or contact items stored in one. Use classic Outlook for both the import and the export. - Contacts and calendar do not travel as EML. Export them separately as
.vcfand.icsand import those into Outlook. - Outlook writes times in UTC but leaves the time zone off the timestamp. Every date here is read as UTC, so nothing shifts by your offset, a common fault in other converters.
- Microsoft has never published the
.olmformat. Mail, attachments, contacts and calendar entries are read from the XML Outlook writes; unusual items (notes, tasks, journal entries) are skipped in this version.