How to Import MBOX to Office 365: 3 Secure & Reliable Methods
A step-by-step reference for IT administrators migrating email archives from MBOX-based clients to Microsoft 365 — without losing a single message.
Written from real migration scenarios, not just documentation. Our team handles MBOX-to-M365 migrations regularly — from single-user archives to enterprise-wide cutovers. Every method below has been tested in production. Last verified: March 2026.
Can Microsoft 365 import MBOX files directly?
No — Microsoft 365 has no native MBOX reader. You'll always need an intermediate step. For 1–2 mailboxes, Thunderbird's IMAP bridge works fine. For teams or large archives, purpose-built migration software is far more reliable and faster. The three methods below cover the full range of use cases.
Why Organisations Make the Switch
Keeping email in local MBOX storage means it's tied to a single machine. One hard drive failure, one stolen laptop, one ransomware incident — that's all it takes to lose data permanently. Microsoft 365 mailboxes replicate across multiple data centres automatically, which removes that whole category of risk.
The operational case is equally strong. Running eDiscovery across MBOX files scattered on individual devices isn't realistic. Retention policies, audit logging, DLP rules — none of that works on data that's outside the tenant.
Platform Switch
Historical email needs to follow users into the new system, not stay stranded on old machines.
Tenant Consolidation
Multiple legacy setups being merged into a single Microsoft 365 tenant.
Compliance Mandates
Centralised archiving requirements that local MBOX storage simply cannot satisfy.
Client Retirement
Retiring Thunderbird or Apple Mail in favour of Outlook and OWA across the organisation.
Plenty of administrators have started reaching for AI tools to generate migration scripts — the pitch is hard to argue with. Describe what you need, get working code back in seconds. The track record in production environments, though, is pretty poor.
Email migration isn't just moving files from A to B. MIME structure, folder hierarchy, attachment encoding, timestamps, sender/recipient metadata, read/unread flags — all of it needs to come through intact. Scripts generated by AI routinely drop one or more of these, often silently. Use AI to understand how migration works. For live business data, use software actually built for this.
Method 1: Thunderbird as a Migration Bridge
Thunderbird has native MBOX support built in, making it a reasonable intermediate layer between MBOX files and any server that accepts IMAP connections — Microsoft 365 included. The idea: load your MBOX data into Thunderbird, then sync it to the cloud mailbox over IMAP.
Thunderbird IMAP Bridge
Free · 1–2 mailboxes · Beginner-friendly · A few hours
What You Need
Step-by-Step Process
-
1
Download and install Thunderbird if not already on the machine.
-
2
Add the Microsoft 365 account via IMAP. Incoming server:
outlook.office365.com, port993. Use the full email address and M365 password — or an app password if MFA is in place. -
3
Install ImportExportTools NG through the Add-ons Manager. It adds import/export options to the right-click menu on any folder.
-
4
Create a local folder under Local Folders. Right-click → ImportExportTools NG → Import mbox file to bring the MBOX data in.
-
5
Once messages appear in the local folder, drag and drop the folder across to the Microsoft 365 account in the left panel. Thunderbird handles the upload via IMAP.
-
6
Monitor progress. Larger mailboxes can run for several hours, and IMAP timeouts may require retrying certain folders.
Works fine for one or two mailboxes. Speed is the main pain point — IMAP uploads are slow compared to API-based methods, and Thunderbird gives you almost no visibility into whether individual messages actually landed. Folder hierarchy can also come out wrong depending on how the source MBOX was structured. Good for testing a workflow or migrating a personal archive; beyond that, it becomes more effort than the task warrants.
Method 2: Convert to PST and Use Network Upload
Microsoft never added MBOX import to Outlook, so this approach requires a conversion step first. You'll end up with a PST file that goes into Microsoft 365 via the Network Upload feature in the Admin Center. More moving parts than the Thunderbird method, but every tool you're touching along the way is from Microsoft.
PST Conversion + Network Upload
Free · Small teams · Intermediate · 1–3 days
The Conversion Path
MBOX can't go straight into Outlook. The conversion runs in two stages: MBOX → EML, then EML → Outlook, exported as PST.
-
1
Locate or export the source MBOX file.
-
2
Run a conversion utility to extract messages as individual EML files. Aid4Mail has a free tier that handles this; online converters work for smaller jobs.
-
3
In Outlook: File → Open & Export → Import/Export. Pick Import from another program or file, select EML, point it at the folder.
-
4
Export from Outlook as PST: File → Open & Export → Import/Export → Export to a File.
-
5
Log into the Microsoft 365 Admin Center → Compliance → Content Import → Import Email Messages. Use the Network Upload wizard to upload the PST and assign it to the right mailbox.
The number of steps is the main drawback — every conversion is another place where something can break, and storage footprint stacks up fast (MBOX + EML exports + PST all on disk at once). That said, no third-party software touches your email data, which matters for organisations with strict data controls. Holds up well at a few gigabytes; at enterprise scale, it gets unwieldy fast.
Method 3: Dedicated Migration Software
For production migrations — multiple users, large archives, a firm deadline — purpose-built software is the most dependable path. MIME parsing, metadata handling, folder mapping, error recovery — all built in rather than bolted on.
Purpose-Built Migration Tool
Paid · Teams & large archives · Beginner-friendly · Minutes to hours
What Good Migration Software Does Differently
- Talks directly to Microsoft 365 via the Graph API, cutting out IMAP speed constraints entirely
- DRS Softech MBOX Converter Tool preserves folder structure, timestamps, sender/recipient fields, read/unread flags, and attachment integrity
- Runs multiple mailboxes in parallel — practical for department or company-wide migrations
- Generates a full migration log so you can confirm what moved and flag anything that needs attention
- Catches duplicates before they land in the destination mailbox
- Supports date-range and folder-level filtering when you only need part of an archive
Typical Workflow
-
1
Install the migration tool on a Windows 10+ machine with access to the MBOX files and a stable internet connection.
-
2
Add the MBOX source files. Most tools let you load multiple files at once and show a folder structure preview before anything transfers.
-
3
Connect to Microsoft 365 with admin credentials. Grant admin consent through Azure AD or set up temporary impersonation rights on target mailboxes.
-
4
Set filters — date range, specific folders, size limits — to keep the migration scoped correctly.
-
5
Map source folders to destinations in the Microsoft 365 mailbox if naming conventions don't match.
-
6
Run a test migration on a small batch first. Check results in Outlook Web App before proceeding.
-
7
Kick off the full migration. Most tools support scheduling so you can run overnight and minimise working-hours network impact.
-
8
Review the migration report and resolve anything flagged.
Cost is the obvious sticking point — licensing is typically per mailbox or per gigabyte. On larger migrations, the time saved and risk reduction make it easy to justify. For one person moving a personal archive, a free method makes more sense. When data integrity is non-negotiable and mailbox counts are high, this is what professional IT consultants reach for.
Method Comparison at a Glance
| Method | Best For | Time Required | Data Safety | Skill Level | Cost |
|---|---|---|---|---|---|
| Thunderbird Bridge | 1–2 mailboxes | A few hours | Moderate | Beginner | Free |
| Outlook PST Workflow | Small teams | 1–3 days | Moderate | Intermediate | Free |
| Migration Software | Teams & large archives | Minutes–hours | High | Beginner | Paid |
Run a Pilot Before the Full Migration
Whichever method you choose, test it on a small sample before touching the full archive. It rarely takes more than an hour and can save you from discovering a structural problem after you've already shifted hundreds of gigabytes.
- Choose 5–10 representative mailboxes — a mix of folder depths, large attachments, and older messages gives the most useful read.
- Run the migration for those accounts only.
- Log into each migrated mailbox and verify: folders present, attachments opening, timestamps correct, read/unread status intact.
- If everything looks right, move on to the full migration. If not, sort out the problem now — not after it has affected everything.
Frequently Asked Questions
Final Thoughts
No single method fits every situation. Volume of data, number of mailboxes, and how much risk you're willing to carry all feed into the decision. One person migrating a personal archive is working with very different constraints than a team running a company-wide cutover.
Thunderbird is a fair starting point when scope is small. The PST workflow fits when staying inside Microsoft tooling is a hard requirement. Dedicated migration software makes sense when accuracy, speed, and auditability all need to be in place simultaneously.
Whichever route you take, run a pilot first. It takes very little time and prevents the kind of data loss you can't walk back.
This guide was prepared for IT administrators managing Microsoft 365 email migrations in 2026. Method availability and software features may change over time; always verify steps against current vendor documentation before running a production migration.