Migrate MBOX to Outlook: Conversion Paths That Actually Work

Classic Outlook on Windows does not read MBOX. Period. You can stare at the File menu for an hour and there's no MBOX option. Microsoft never added it, and there's no add-in that meaningfully changes that. So every MBOX-to-Outlook migration goes through an intermediate: either convert the MBOX to PST first using a desktop converter, or set up Thunderbird as a temporary bridge that lets Outlook copy messages across in real time. Both paths work, both have failure modes. This walkthrough covers the practical choices and the points where users get stuck.

Why no native MBOX in Outlook#

MBOX is the Mozilla and Unix world's storage format: line-delimited, simple, text-based. PST is Microsoft's structured binary format with table-of-contents indexes and proprietary metadata. They serve the same purpose (offline mail storage) but the formats have nothing in common. Microsoft has never seen commercial reason to add MBOX reader code to Outlook. The result: third-party converters exist as a small industry, and the Thunderbird-as-bridge trick has become a standard workaround.

The two practical routes:

• MBOX to PST converter — Desktop tools that read MBOX and write PST. Some are free (limited file size), most are paid. Output: one or more PSTs ready for Outlook import.
• Thunderbird bridge — Install Thunderbird, load the MBOX into a local folder, add the Outlook IMAP target as an account, drag messages across. Free, slower, manual.

For New Outlook on Mac (the rewritten 2024+ version), there's a limited native MBOX import for personal mailboxes, but it doesn't cover enterprise scenarios and skips some folder structures. For serious migration, use the PST or bridge route regardless of platform.

Prerequisites#

Centralise MBOX files#

Find sources. Common locations:

• Thunderbird — <profile>/Mail/<account>/ (Windows) or ~/Library/Thunderbird/Profiles/<profile>/Mail/<account>/ (macOS).
• Apple Mail — ~/Library/Mail/V10/<account>/<folder>.mbox/ containing an mbox file inside.
• Google Takeout — single .mbox per Gmail account.
• Old Unix servers — /var/spool/mail/<user> or /var/mail/<user>.

Copy everything to a local SSD working folder. Avoid running conversion against MBOX files on network shares or in OneDrive folders; locking conflicts corrupt the stream.

Compact Thunderbird folders#

If the source is Thunderbird, compact folders before exporting:

In Thunderbird, File > Compact Folders.

Thunderbird marks deleted messages with X-Mozilla-Status headers but leaves the bytes in the MBOX until compaction. A "5 GB" Inbox often contains 2 GB of soft-deleted content. Compact, confirm folder sizes shrank, then copy the MBOX files. Skipping this guarantees you import deleted content into Outlook.

Verify file integrity#

Open each MBOX in a text editor or hex viewer and confirm:

• The file starts with a From line (capital F, no colon).
• Each new message begins with From at line start.
• The file ends cleanly without truncation.

A truncated MBOX produces a corrupt PST after conversion, which Outlook then refuses to import or imports partially. Better to fix at the source.

Confirm target Outlook profile#

The Outlook profile that will run the import must be configured for the target mailbox. Multiple profiles cause confusion: import into the wrong one and you're cleaning up later.

Verify in Outlook under File > Account Settings > Account Settings. Confirm the listed account is the one you intend to receive the imported content.

Route A: MBOX to PST conversion#

1. Choose a converter

   Several established MBOX-to-PST converters exist. Selection criteria:

   • Handles your source variant (Thunderbird, Apple Mail, Google Takeout, plain Unix).
   • Preserves folder hierarchy including nested folders.
   • Preserves attachments without re-encoding.
   • Handles UTF-8 message bodies without garbling.
   • Logs skipped messages with reasons.

   Free converters typically have file-size limits (often 1 GB). Paid converters in the $50 to $150 range handle larger jobs and include batch processing.

2. Run conversion

   Point the converter at your MBOX source. For Thunderbird sources with nested folders, point at the parent directory containing both the MBOX files and the .sbd subdirectories. The converter should recurse.

   For very large MBOX files (over 10 GB), watch RAM. Some converters load entire files into memory. A 15 GB MBOX with a 16 GB RAM workstation crashes the converter. Split the source or use a tool that streams.

   Output is one or more PST files. For multi-folder Thunderbird sources, decent converters produce one PST per top-level account folder with all subfolders inside.

3. Verify PST integrity

   Run scanpst.exe against each produced PST:

   "C:\Program Files\Microsoft Office\root\Office16\scanpst.exe"
   

   The converter occasionally produces PSTs that Outlook later refuses to import. Scanpst catches and repairs most issues.

   Open each PST in Outlook as a standalone data file (File > Open & Export > Open Outlook Data File) and browse the folder structure. Spot-check a few messages. Confirm attachments open. If everything looks right, close the file and proceed to import.

4. Import the PST

   With the source PST verified, use Outlook's Open & Export wizard:

   File > Open & Export > Import/Export > Import from another program or file > Outlook Data File (.pst)

   Point at the converted PST. Choose Do not import duplicates for safety. Select the destination: typically a dedicated folder like Imported Archive in the target mailbox, or "Import items into the same folder in [target account]" to recreate the structure at the root.

   A 10 GB PST imports in 30 to 90 minutes on a modern laptop.

5. Wait for Exchange sync

   If the target is Exchange Online or on-prem Exchange, imported content lands in the OST cache first then syncs to the server. Sync takes roughly as long as the import itself. Don't close Outlook during sync.

   OWA does not show imported content until sync completes. Set user expectations to avoid the "where are my messages?" tickets.

Route B: Thunderbird as a bridge#

1. Install Thunderbird

   Download and install Thunderbird on the migration workstation. The version doesn't matter much; any release from the last few years works.

   If you already have Thunderbird with the source MBOX content as a working account, you can skip to step 3.

2. Load MBOX into Thunderbird Local Folders

   Open Thunderbird. The Local Folders node sits at the bottom of the folder tree.

   Right-click Local Folders, New Folder, and create one for the import (e.g. Imported Archive).

   Close Thunderbird. Navigate to the Thunderbird profile directory:

   • Windows: %APPDATA%\Thunderbird\Profiles\<profile>\Mail\Local Folders\
   • macOS: ~/Library/Thunderbird/Profiles/<profile>/Mail/Local Folders/

   Copy each source MBOX file into this Local Folders directory. Name them after the folders you want (e.g. Inbox-2024 for an MBOX containing 2024 inbox content). No extension.

   Re-open Thunderbird. The new folders appear under Local Folders. Click each to verify messages are visible.

3. Add the Outlook target as an IMAP account

   Configure the target mailbox in Thunderbird as a regular IMAP account. For Exchange Online, this requires OAuth2; Thunderbird supports it natively for Microsoft accounts.

   File > New > Existing Mail Account. Enter the credentials. Thunderbird auto-detects Exchange Online IMAP settings.

   After setup, the target mailbox appears in the folder tree alongside Local Folders.

4. Copy messages across

   Drag folders from Local Folders into the target IMAP account folder tree, or select all messages in a folder (Ctrl+A) and right-click, Copy To > [Target account] > Folder.

   Thunderbird uses IMAP APPEND to push messages to the destination. Speed: 60 to 100 messages per minute, slower than dedicated tools but stable.

   A 5 GB Local Folder takes 4 to 8 hours through this method. Leave Thunderbird running.

5. Verify in Outlook

   Open Outlook. The copied content appears as new folders in the target mailbox. Folder counts should match Thunderbird. Spot-check messages and attachments.

   If the target is Exchange Online, the messages are already server-side because Thunderbird wrote them via IMAP. Outlook only needs to sync to show them.

What changes during conversion#

Folder names#

System folder names like Inbox and Sent need attention. A Thunderbird Inbox MBOX should map to Outlook's Inbox, not a new folder called Inbox next to the real one. Most converters offer a mapping option. The Thunderbird bridge route relies on you targeting the right destination folder when dragging.

Read state#

Thunderbird's X-Mozilla-Status header encodes read state. Decent converters honour it; Outlook sees correct read/unread. Plain Unix MBOX files without this header arrive as all-unread.

Flags, tags, categories#

Thunderbird tags do not map to Outlook categories cleanly. Some converters offer a tag-to-category translation; results are inconsistent. Plan for tag loss.

Outlook flags do not exist in MBOX, so all imported messages are flag-free. Users who relied on flagged-for-follow-up in Thunderbird will need to re-mark.

Attachments#

MIME attachments transfer intact through both routes. Inline images sometimes break if the converter re-encodes the message body; pick a converter that preserves MIME structure rather than parsing and rebuilding.

Common failure modes#

Converter produces empty PST#

Source MBOX is corrupt or unreadable. Open it in a text viewer and confirm From boundaries are intact. Apple Mail directory structure also commonly produces empty PSTs because the converter looked in the wrong place.

Errors have been detected in the file during Outlook import#

Run scanpst against the converted PST and repair. If scanpst can't fix it, the converter produced something broken; try a different converter or reduce the source size.

Outlook hangs during large PST import#

PST over 25 GB or OST cache running out of disk. Move the OST to a larger drive in account settings, or split the source PST.

Thunderbird bridge: messages drop during drag-and-drop#

Network connection dropped mid-IMAP-append. Thunderbird usually shows an error in the activity log (View > Activity Manager). Re-select the failed messages and re-copy.

Folder names with slashes break#

Some converters interpret slashes in folder names as path separators. A Thunderbird folder called Sales/Q3 becomes nested folders Sales > Q3 after conversion. Usually fine, but if you wanted Sales/Q3 as a single name, rename in source first.

Picking a route#

Pick the PST conversion route when:

• You have batch jobs across many users.
• You need to produce PSTs as deliverables (e.g. legal hold copies).
• Conversion speed matters (faster than the Thunderbird drag-and-drop bridge).
• You're comfortable with the converter cost.

Pick the Thunderbird bridge route when:

• It's a one-off migration.
• The source is already a Thunderbird profile (skip the MBOX export step entirely).
• You want to avoid converter cost and licensing.
• Speed isn't critical.

For format background, see the MBOX format glossary entry and the PST, MBOX, and EML migration guide. For a Thunderbird-specific walkthrough, see Thunderbird to Outlook. If your destination is Google instead, see MBOX to Gmail, and for Exchange Online cloud-side, MBOX to Office 365.