Use Apple Mail for local mailbox backup

Use Apple Mail when the goal is a local mailbox backup on a Mac. Its built-in export saves selected mailboxes as .mbox packages. That gives a clear local copy of messages and folders without digging through hidden system files.

The useful part is simple. Open Mail, select a mailbox, then choose Mailbox > Export Mailbox. Pick a folder for the export. Mail creates an .mbox package in that location.

An MBOX file is a mailbox file. It stores email messages in a form that many mail programs can read. Apple Mail uses an .mbox package, which may look like one item in Finder. Inside it, macOS stores the mailbox data.

I prefer this method for a first backup because it uses the mail program itself. The export starts with mailboxes that Mail can open. That avoids copying a database while it is still changing. Email software is rarely improved by being copied mid-sneeze.

Local mailboxes need a little care. In Apple Mail, items under On My Mac exist only on that Mac. They are not held on the mail server. They are also separate from messages shown under an account, such as an IMAP account.

That difference matters. A message visible in Mail may still live on the server. A message under On My Mac may exist only on the computer. The backup plan has to include both kinds when both contain useful mail.

Export the mailbox

The export process is short.

1. Open Apple Mail.
2. Select one or more mailboxes in the sidebar.
3. Choose Mailbox > Export Mailbox.
4. Select a backup folder.
5. Click Choose.

Apple Mail exports the selection as .mbox packages. If a mailbox with the same name already exists, Mail does not replace it. It creates another package with a changed name, such as My Mailbox 3.mbox.

That behavior is safe, but it can cause clutter. A folder with dated backup copies is easier to check than a pile of files with unclear names. The date can be part of the folder name, such as Mail Backup 2026-03-24.

Exporting one mailbox at a time can also make checking easier. A large account may contain many folders. A single export can be harder to inspect when a problem appears later. Smaller groups give a clearer record of what was saved.

The export itself is not proof of a complete backup. Mail may show folders that contain messages still stored on a server. Some account settings may also affect what has been downloaded to the Mac. A local export can only save what Apple Mail can access at that time.

This is where a quiet check helps. Open the exported mailbox on the Mac, if possible, and look through several folders. Check old messages, recent messages, attachments, and nested folders. The point is not to admire the .mbox file. The point is to see whether the useful content is there.

Contacts need separate attention. Mailbox export concerns mailboxes and messages. It is not a full export of every contact, calendar item, account setting, or password. Those items need their own backup path.

The same applies to message rules and signatures. They are part of the Mail setup, not simply another message inside an MBOX mailbox. A mailbox backup is useful, but it is not a complete copy of the whole Mac.

The file format sets the next limit

MBOX is a common format, but it is not one single standard with one behavior everywhere. Different mail programs can store MBOX data in slightly different ways. Folder structure, flags, attachments, and special message data may not appear the same after import.

Apple Mail can import MBOX mailboxes exported by other mail programs. It can also import mailboxes that Apple Mail exported. That makes MBOX a practical bridge for moving mail between systems.

Still, a bridge is not the same as a perfect copy. A message may transfer while a label, flag, rule, or folder detail does not. Some mail clients use labels instead of folders. Others store account data in a different way.

That is why a migration is finished only after the imported mailbox is checked. The export screen can report success while a needed folder is missing. The file can open while one damaged message causes trouble later. A clean export is a good sign, not a guarantee.

For a move into another client, the .mbox package may need to be imported there. The exact steps and support can change with the client version. The target program may also place imported mail in a new folder instead of restoring the old layout.

When the final destination is Outlook, MBOX is usually an intermediate format rather than the final Outlook mailbox file. Outlook commonly uses PST files for stored mail on Windows. A PST is a different mailbox format. Moving from Apple Mail to Outlook may therefore require a conversion step from MBOX to PST.

That is where a 2PST conversion tool can fit. Its job is separate from Apple Mail’s export. Apple Mail creates the local .mbox copy. A suitable 2PST tool may then convert that source into the format needed for the next mail system, subject to the tool’s supported versions and the condition of the source file.

The two tasks should stay separate in the records. First, confirm that Apple Mail exported the right mailboxes. Then confirm that the converted file contains the needed messages and folders. Mixing those checks makes it hard to tell where a problem began.

A local copy still needs protection

A backup saved beside the original Mac is not a strong safety net. If the Mac fails, both copies may be lost. A local mailbox export works best when the exported folder is also copied to another storage location.

Time Machine can back up mail content that Apple Mail downloaded, depending on the settings used on the Mac. It can also help restore lost mailboxes. That is different from making a separate .mbox export for inspection or conversion.

Both methods have a place. The MBOX export gives a clear mailbox file. Time Machine protects the Mac’s stored data as part of a wider backup. Neither method proves that every account message, contact, rule, and attachment has been captured.

The honest limit is account state. Apple Mail may not have every server message stored locally. Sync settings, account type, available disk space, and software version can affect what appears in the export. Apple changes Mail over time, and other mail programs change too.

So the practical answer stays narrow. Use Apple Mail for local mailbox backup when the mail is available there and an MBOX copy meets the next step. Export the needed mailboxes, open the result, and check content before deleting or changing the source.

A mailbox backup is complete only when the messages, folders, and needed details survive the move. The export button starts that work. It does not finish it.

That is the useful lesson for The Migration Brief: one practical fix, one file format explained, and one safer way to move your mail.