Written by Jennifer Walsh. Reviewed for technical accuracy by Shubham Dixit, Independent Expert in Email Forensics and Data File Conversion. Updated 18 September 2026.
Shubham is an independent external reviewer and not an employee of PCDOTS.
Quick answer. Exchange has no MBOX import, it takes PST, so you bridge the file across. The free way is to load the MBOX into Thunderbird, add your Exchange or Microsoft 365 account, then copy the mail into it over IMAP. Admins can convert the MBOX to PST and import that with PowerShell or the Microsoft 365 import service. A converter uploads to Exchange directly.
On this page
Why won’t Exchange import an MBOX directly?
MBOX is the open mailbox format that Thunderbird and Apple Mail use. Exchange is Microsoft’s mail server, either on your own on-premises box or in the cloud as Exchange Online, part of Microsoft 365.
Exchange imports mailboxes from a PST file, not from MBOX. There’s no MBOX option anywhere in it. So to import MBOX to Exchange you bridge the file, three ways, through Thunderbird, through a PST or with a converter that uploads for you.
All three carry the mail, the attachments and the folder structure. The right one depends on how many mailboxes you have and whether you run Exchange yourself or on Microsoft 365.
People move to Exchange for shared mailboxes, calendars and public folders, plus clean Outlook and Microsoft 365 access from anywhere. The routes below work on on-premises Exchange 2010 to 2019 and on Exchange Online.
MBOX has no direct Exchange import, so a bridge carries it in.
“The thing to get straight is that Exchange only ingests PST, so MBOX always needs a bridge. For a single mailbox I load it into Thunderbird, connect the Exchange account and copy the folder up over IMAP. For a server full of users I convert to PST and let New-MailboxImportRequest do the import, though on Microsoft 365 that cmdlet is gone and you use the network upload service instead. One catch on Exchange Online, basic-auth IMAP is switched off, so the connection has to use OAuth. A converter is the quick path when there are a lot of MBOX files to push in at once.” Shubham Dixit, Email Migration reviewer (draft, pending approval)
How do you import MBOX to Exchange for free with Thunderbird?
You import MBOX to Exchange for free by using Thunderbird as the bridge. You load the MBOX into Thunderbird, add your Exchange account there, then copy the mail into it. Thunderbird uploads it to the server over IMAP.
Here are the five steps.
- In Thunderbird, add the free ImportExportTools NG add-on, then right-click Local Folders and Import mbox file.
- Add your Exchange or Microsoft 365 account in Thunderbird as an IMAP account.
- Sign in. Exchange Online uses OAuth, so approve access in the browser rather than a plain password.
- Drag or copy the imported MBOX folder into the Exchange account in the sidebar.
- Thunderbird uploads the mail to Exchange. It syncs to Outlook and the web app.
For a single mailbox I use the Thunderbird bridge, and for a server full of users I hand a PST to the admin route below. On on-premises Exchange, turn on the IMAP4 service first, or the account won’t connect.
Load the MBOX, add the Exchange account and copy the mail up.
How do admins import MBOX to Exchange as a PST?
Admins import MBOX to Exchange by first turning the MBOX into a PST, then importing that PST into the target mailbox. Exchange handles PST natively, so this is the clean route for many users at once.
On on-premises Exchange, put the PST on a shared folder and run New-MailboxImportRequest -Mailbox user -FilePath \\server\share\file.pst. You need the Mailbox Import Export role, and the Exchange Trusted Subsystem group needs Read on the share, which Microsoft documents.
On Exchange Online, that cmdlet is retired. Instead you use the Microsoft 365 import service, uploading the PST to Azure with AzCopy, then running an import job. Convert the MBOX to PST first with a converter, since there’s no free MBOX to PST built into Windows.
If you’re a single user, not an admin, there’s a simpler path. With your Exchange mailbox open in Outlook, click File, Open & Export, Import/Export, then import the PST from another program or file. The mail lands straight in your Exchange mailbox.
How do you import MBOX to Exchange in bulk with a tool?
You import MBOX to Exchange in bulk with a converter that reads the files and uploads to the server for you. It skips Thunderbird and the PowerShell steps, which helps when there are many MBOX files.
PCDOTS MBOX Converter loads a folder of MBOX files and exports them to Exchange over IMAP, or to PST for an admin import. It keeps the folders and attachments, runs on Windows and filters by date or sender. For Exchange Online, sign in with an app password, since basic auth is off. The free trial exports a sample first. Follow these four steps.
- Install and run PCDOTS MBOX Converter, then Open and select your MBOX files.
- Preview the loaded mail in the left pane.
- Open Export and select IMAP for Exchange, or PST for an admin import.
- Enter the Exchange server and account, then start the upload.
The tool route, MBOX files uploaded to Exchange at once.
Here are the first steps with the screens.
Step 1. Install and run PCDOTS MBOX Converter.
Step 2. Open and select your MBOX files or folder.
Step 3. Open Export and select IMAP for Exchange.
Step 4. Enter the Exchange server and account, then start.
Related reading, our guides to export Outlook to MBOX, the other direction, and import EML files to Thunderbird. To read a file first, the free MBOX viewer opens a .mbox without a client.
Match the route to your scenario, one mailbox, one user, a server or a batch.
Which method should you use?
Use Thunderbird for one mailbox, the PST route for a server of users and a converter for many MBOX files at once.
| Method | Best for | Good to know |
|---|---|---|
| Thunderbird bridge | One mailbox, free | IMAP, OAuth on Online |
| MBOX to PST, then import | An admin migration | PowerShell or the 365 service |
| MBOX Converter | Many MBOX files | Windows, direct upload or PST |
Key takeaways
- Exchange imports from PST, not MBOX, so an MBOX always needs a bridge.
- The free way is Thunderbird, add the Exchange account and copy the mail in over IMAP.
- Admins convert to PST, then use New-MailboxImportRequest on-premises or the 365 import service online.
- A converter uploads a batch of MBOX files to Exchange directly, on Windows.
Frequently asked questions
Does Exchange support MBOX files?
No. Exchange imports mailboxes from PST files only. To import MBOX to Exchange you bridge the file through Thunderbird, a PST or a converter.
How do I import MBOX to Exchange for free?
Load the MBOX into Thunderbird with ImportExportTools NG, add your Exchange account as IMAP, then copy the folder into it. Thunderbird uploads the mail to the server.
Why does the Exchange Online sign-in fail with a password?
Because basic-auth IMAP is switched off in Exchange Online. Use OAuth in Thunderbird, or an app password in a converter, to connect.
How do admins import a PST into Exchange?
On-premises, run New-MailboxImportRequest with the PST on a network share. In Exchange Online, use the Microsoft 365 import service, since that cmdlet is retired online.
Can I import MBOX to Exchange on a Mac?
The Thunderbird bridge works on a Mac. The PCDOTS converter is Windows only, so run it on a Windows machine or a virtual one.
Do the folders and attachments stay intact?
Yes. All three routes keep the folder structure and the attachments. A PST import and a converter also hold the read and unread state.
So which bridge fits your migration?
Importing MBOX to Exchange always means a bridge, because Exchange only takes PST. For one mailbox, Thunderbird moves it in over IMAP for free. For a server of users, convert to PST and let PowerShell or the Microsoft 365 service import it. For a stack of MBOX files, a converter uploads them in one run. Every route lands the mail, attachments and folders in Exchange. So which bridge fits your migration, a free Thunderbird copy, a PST import or a bulk upload?
