Real User Query (From Microsoft Dynamics Community, 2025)“I exported a large collection of old emails from my previous email client and saved them in MBOX format. I recently switched to Microsoft Office 365 and want all my previous messages accessible in my new mailbox. I tried uploading the MBOX file directly, but Office 365 doesn’t support the format. I then searched Outlook for a manual import option — it only supports PST files, not MBOX. Has anyone managed to import MBOX files into Office 365 successfully? I don’t want to lose access to these emails.” — Microsoft Dynamics Community Forum, 2025 |
Switching to Microsoft 365 and realizing your old MBOX archive is just sitting there, unreadable — that’s a genuinely annoying situation. You’d expect some kind of import option. There isn’t one. Microsoft 365 doesn’t read MBOX at all.
But you’re not out of options. There’s a free manual route using Thunderbird that works fine for smaller mailboxes, and a direct tool-based approach for anyone dealing with large archives where attachments and folder structure actually matter. This guide covers both, plus a few things worth checking before you touch anything.
Microsoft 365 and MBOX Don’t Speak the Same Language
Here’s the short version of why this is even a problem.
MBOX is what email clients like Mozilla Thunderbird, Apple Mail, Eudora, and The Bat! use to store mail. It’s been around since the 1970s and it’s essentially a giant text file with all your emails stacked end to end. Simple format, widely supported — just not by Microsoft.
Outlook and Microsoft 365 use PST (Personal Storage Table). That’s Microsoft’s own format, and it’s what the entire ecosystem is built around. There’s no MBOX importer in Outlook, no upload option in the Microsoft 365 admin center, nothing. So you either convert MBOX to PST first and then import the PST, or you use a tool that skips that middle step entirely.
Method 1: The Free Way — Thunderbird as a Bridge
This works. It’s just slow if your mailbox is large, and it has some real failure points you should know about going in.
Step 1: Get your MBOX into Thunderbird
If you already use Thunderbird, your emails may already be sitting there. If not, install the ImportExportTools NG add-on — find it under Tools > Add-ons. Once installed, right-click any local folder, select ImportExportTools NG > Import MBOX file, and point it at your file.
Step 2: Add your Microsoft 365 account
Go to Account Settings > Add Mail Account and log in with your Microsoft 365 credentials. Thunderbird picks up the IMAP settings automatically.
Step 3: Move emails across
With both accounts showing in the left panel, drag emails from the local Thunderbird folder into your Microsoft 365 inbox. Thunderbird pushes them to the server as you go.
What goes wrong at scale: Past a few thousand emails, the drag-and-drop sync slows to a crawl. Large attachments fail without any error message — they just don’t show up on the other side. Folder structure tends to collapse too; what was a tidy hierarchy in Thunderbird often ends up as a pile in one folder. If Thunderbird crashes halfway through, you start over.
For 200 emails and no nested folders, this is fine. For anything more complicated, it’s a gamble.
Method 2: Upload MBOX to Microsoft 365 Using a Dedicated Tool
When attachment integrity matters — or you’re moving thousands of emails and can’t spend a weekend babysitting a sync — a purpose-built converter is worth it.
SysInfoTools MBOX Converter reads your MBOX file directly, preserves everything — attachments, folder structure, timestamps, CC/BCC fields — and pushes it into your Microsoft 365 mailbox without converting to PST first.
Here’s how to use it:
Step 1: Install and open the software
Runs on Windows. Download, install, open.
Step 2: Load your MBOX file
Click Add File for a single file, or Add Folder if you have several MBOX files to process at once. It handles files from Thunderbird, Apple Mail, Eudora, Entourage, SeaMonkey, and others.
Step 3: Check the preview
Before anything gets sent anywhere, browse through the loaded emails — subjects, senders, attachments — to confirm the data came in clean. Worth doing before a large transfer.
Step 4: Export MBOX files to Microsoft 365
Choose Export > Office 365, enter your account credentials, and let it run. The tool maps your folders to Microsoft 365 and transfers everything folder by folder.
What comes through intact: all attachment types, original folder names, email timestamps, CC and BCC fields, and non-English characters. Emails land in Microsoft 365 exactly as they were stored in the MBOX file.
Which Approach Makes Sense for You?
| Manual (Thunderbird) | SysInfoTools MBOX Converter | |
|---|---|---|
| Cost | Free | Paid (free trial available) |
| Speed | Slow on large files | Handles bulk transfers fast |
| Attachments | Can drop silently at scale | Preserved |
| Folder structure | Often breaks | Kept intact |
| Batch MBOX files | One at a time | Multiple files at once |
| Setup difficulty | Moderate | Minimal |
Under 500 emails with a simple folder setup? The Thunderbird method is probably fine. Larger than that — or if you’re doing this for a client or a team migration — the dedicated tool takes the guesswork out.
Before You Start — A Few Things Worth Checking
Most import problems aren’t caused by the method you pick. They come from skipping a few basic checks beforehand.
Open the MBOX File and Spot-Check It First
An MBOX file can look perfectly normal in your file explorer and still have broken headers or corrupted email boundaries inside. Load the file into Thunderbird and click through a handful of emails — different senders, different sizes, at least one with an attachment. If some emails show blank or folders appear empty, the file itself is damaged. No tool fixes that automatically.
Check How Much Space Your Microsoft 365 Mailbox Has Left
Microsoft 365 mailboxes have storage caps — 50 GB on basic plans, 100 GB on Business and Enterprise. If your mailbox is already close to full and your MBOX file is a few gigabytes, you could hit the ceiling mid-import and end up with a partial transfer. Check Settings > Storage in Outlook on the web before anything else.
Know Which Email Client Created the File
Thunderbird, Apple Mail, Eudora, and SeaMonkey all write MBOX files slightly differently. Header structures vary. Most tools handle this automatically, but confirm your source client is on the supported list before you commit — especially if the file came from a less common client.
Sort Out Your Folder Mapping Before the Transfer
If you’re moving a Thunderbird archive with 15 custom folders, decide where each one lands in Microsoft 365 before the import runs. Figuring this out after 8,000 emails have been dumped into one folder is painful. Most dedicated tools let you control this mapping upfront; the Thunderbird method doesn’t.
Do a Small Test Run First
Pick one folder — 50 to 100 emails, a mix of plain text and attachments — and run the import on just that before touching the full archive. Confirm the emails land in the right place, attachments open, and dates look right. Catching a misconfiguration with 80 emails is far less painful than catching it with 80,000.
Wrapping Up
Microsoft 365 won’t open MBOX files natively, and that’s not going to change. The Thunderbird workaround is free and works for small, simple mailboxes. For anything larger — or when you need every email, every attachment, and every folder to arrive cleanly — SysInfoTools MBOX Converter handles the full process without the variables.
Your old emails aren’t gone. They just need a one-time conversion to get into Microsoft 365.
FAQs:
Q1. Does Microsoft 365 have a built-in MBOX importer?
Ans. No. It only accepts PST files natively. MBOX needs to be converted first — either via Thunderbird or a dedicated migration tool.
Q2. Can I import MBOX to Microsoft 365 on a Mac?
Ans. SysInfoTools is Windows-only. The Thunderbird method works on Mac but takes a bit more setup. You can also run the Windows converter on a virtual machine if needed.
Q3. Will the import affect emails already in my Microsoft 365 mailbox?
Ans. No. The process only adds incoming emails. Nothing already in your mailbox gets touched.
Q4. How long does a large import take?
Ans. Depends on file size and connection speed. A 5 GB MBOX file usually takes 30 minutes to a couple of hours with a dedicated tool. The manual Thunderbird method takes longer, especially past 1 GB.
Q5. Which email clients does SysInfoTools support?
Ans. Mozilla Thunderbird, Apple Mail, Eudora, The Bat!, Entourage, SeaMonkey, Postfix, and other clients that export in standard MBOX format.
Q6. Do I need admin access to import into Microsoft 365?
Ans. For your own mailbox, standard credentials are enough. Importing into someone else’s mailbox — as part of an IT migration, for example — requires admin or delegated access.
