How to Import MSG Files into Outlook and Other Email Clients

Fast Methods to Import Messages from MSG Format (Windows & Mac)Importing messages from MSG files can be necessary when migrating email from one account or computer to another, recovering archived messages, or consolidating mailboxes. MSG is a Microsoft Outlook message format that stores a single email, including headers, body, and attachments. Below are fast, practical methods for importing MSG files on both Windows and Mac, plus tips for bulk import, troubleshooting, and tools to speed the process.

What is an MSG file?

An MSG file is a proprietary file format used by Microsoft Outlook to save individual email messages, calendar items, contacts, or tasks. It contains the message content, metadata (From, To, Subject, Date), and embedded attachments. Because MSG is Outlook-specific, importing these files into other clients or platforms often requires conversion or an Outlook-based import route.

Preparations — general tips before importing

Back up your MSG files and current mailboxes.
If you have many MSG files, keep them organized in folders reflecting desired mailbox structure.
Confirm which email client or service (Outlook Desktop, Outlook.com, Apple Mail, Thunderbird, Gmail) you’ll import into — methods differ.
If you don’t have Outlook installed (common on Mac), plan to use conversion tools or intermediate formats (EML, PST, MBOX).

Windows: Fast Methods

Method 1 — Drag & Drop into Outlook (quickest for small batches)

If you have Outlook installed on Windows:

Open Outlook and navigate to the folder where you want the messages (Inbox or a custom folder).
In File Explorer, select one or multiple .msg files.
Drag the selected MSG files and drop them into the desired Outlook folder.

This preserves message content and attachments.
For large numbers of files, drag-and-drop can be unstable; use a different method for bulk imports.

Method 2 — Use Outlook’s Import via PST (best for bulk and folder structure)

If your MSG files are already organized into folders and you need to import many messages:

Create a new PST file in Outlook: File → New Items → More Items → Outlook Data File.
Open the PST in Outlook so it appears as a data file with folders.
Use drag-and-drop from File Explorer into the PST’s folders.
Alternatively, third-party tools can convert MSG batches into a single PST for direct import.

Converting to PST preserves folder hierarchy and is ideal for large migrations.

Method 3 — Convert MSG to EML, then import to other clients

EML is a more universal single-message format supported by many clients.

Use free converters or scripts (PowerShell with third-party libraries) to convert MSG → EML.
Once converted, clients like Thunderbird or Apple Mail can import EML files via drag-and-drop or import utilities.

Method 4 — Use specialized bulk-conversion tools

Several commercial and free utilities convert MSG to PST, MBOX, EML, or directly import them into target platforms. Features to look for:

Batch conversion, folder structure preservation, attachment handling, and compatibility with your destination client.
Examples include tools that create PST files from MSG folders or directly upload to cloud services.

Mac: Fast Methods

Notes for Mac users

Microsoft Outlook for Mac does not natively import Windows MSG files. You’ll typically convert MSG files into a format macOS email clients accept (EML or MBOX) or use a Windows VM/PC with Outlook to handle imports.

Method 1 — Convert MSG to EML or MBOX (recommended)

Use a dedicated converter app for macOS or an online conversion service to convert .msg to .eml or .mbox.
For Apple Mail: Import the resulting MBOX via Mail → File → Import Mailboxes. For EML: drag EML files into a Mail mailbox.
For Thunderbird on Mac: use Tools → Import or drag EML files into folders.

Conversion preserves message content if the converter supports attachments and encoding.

Method 2 — Use Outlook for Windows inside a VM or Boot Camp

If you need exact fidelity and have many MSG files:

Run Windows on your Mac using Parallels Desktop, VMware Fusion, or Boot Camp.
Install Outlook for Windows, then use the Windows methods (drag-and-drop or PST creation).
Transfer the resulting PST or mailbox data back to macOS clients (convert PST → MBOX or import into Outlook for Mac).

Method 3 — Use cross-platform tools or cloud-based importers

Some cloud mail services or third-party apps accept MSG uploads and convert/import them into cloud mailboxes (Gmail, Office 365). This can work on Mac via web interfaces or native apps.

Bulk import strategies and automation

Batch convert MSG → PST using a commercial tool when migrating thousands of messages.
Use PowerShell scripts on Windows (for advanced users) to automate conversion or import tasks.
Maintain folder structure by converting entire folder trees rather than individual files.
For cloud migrations, check whether your destination (Exchange Online, Gmail) supports direct ingestion of PST files — this often speeds bulk moves.

Troubleshooting common issues

Corrupt MSG files: try opening one in Outlook first to verify integrity.
Character encoding problems: pick a converter that supports Unicode.
Missing attachments after conversion: use tools that explicitly state attachment preservation.
Outlook version compatibility: older MSGs may have differences; importing via a modern Outlook usually resolves this.

Suggested tools and quick checklist

Outlook for Windows (native import).
PST conversion tools (search for reputable vendors).
MSG → EML/MBOX converters (both Windows and Mac options).
Virtual machine software (Parallels, VMware) for Mac users needing Outlook for Windows.
Checklist:
Backup everything.
Pick destination format (PST, EML, MBOX).
Test with a small sample.
Scale up once satisfied.

Conclusion

For Windows, the fastest routes are direct drag-and-drop into Outlook for small sets and PST-based bulk imports for larger migrations. On Mac, converting MSG to EML/MBOX or running Outlook for Windows in a VM gives the most reliable results. Choose batch-capable converters for large volumes and always test on a sample before committing to a full import.