Migrate EML to Outlook: Drag and Drop or PST Conversion

EML files heading into Outlook is one of the friendlier file-import scenarios. Outlook on Windows actually accepts EMLs by drag-and-drop, which feels almost too easy after wrestling with MBOX-to-PST conversions and PST imports. The catch: drag-and-drop scales badly. Once the batch hits a few thousand files, Outlook locks up, the UI hangs, and you start questioning the wisdom of doing this manually at 2am. For larger jobs, conversion to PST followed by the Import wizard is faster, more reliable, and produces logs. This walkthrough covers both paths and the points where each one breaks.

Two practical routes#

EML to Outlook has fewer landmines than MBOX or PST conversions because Outlook reads EML natively for individual messages. The two real options:

• Drag-and-drop — Select EML files in Windows Explorer or Finder and drop them onto an Outlook folder. Outlook reads each one and stores it in the folder. No conversion, no third-party tool. Works for tens to low-thousands of messages.
• EML to PST conversion — A converter reads EML directory structures and produces a PST that mirrors the folder hierarchy. Import the PST through Outlook's Open & Export wizard. Faster for large batches and preserves nested folders cleanly.

Drag-and-drop is fine for a few hundred messages, especially when the structure is flat. PST conversion is better when message counts climb or when folder hierarchy matters.

Prerequisites#

Locate and organise EML files#

Find the source. Common scenarios:

• Outlook Express or Windows Mail exports from old workstations.
• Apple Mail drag-exports as .eml or .emlx files.
• Forensic exports with numbered file names.
• Legal discovery exports from ediscovery tools.
• Manually saved messages users dragged to desktop folders.

Copy everything to a local SSD working folder. Don't run import against EMLs on network shares; file locking causes intermittent failures Outlook reports vaguely.

Organise into the intended Outlook folder structure on disk:

EmlImport/
  Clients/
    Acme/
      2024/
        msg-00001.eml
        msg-00002.eml
      2023/
        ...
  Personal/
    ...

The directory tree determines the resulting Outlook folder structure. Both drag-and-drop and PST conversion respect the hierarchy, though drag-and-drop only handles one folder at a time.

Verify file integrity#

Open a sample EML in a text editor. Confirm:

• Standard headers (From:, To:, Subject:, Date:) are present.
• The Content-Type: header looks reasonable (often multipart/mixed, multipart/alternative, or text/plain).
• The file ends cleanly without truncation.

A corrupt EML is rejected silently by Outlook during drag-and-drop, or causes the converter to skip it. Tool logs and import-status messages catch them after the fact.

Convert EMLX if needed#

Apple Mail produces .emlx files, not .eml. EMLX adds a length-prefix line at the start and metadata at the end that strict readers reject. Some tools handle both formats transparently; Outlook on Windows mostly does not.

For EMLX sources:

1. Rename the extension to .eml and try drag-and-drop. Sometimes Outlook ignores the EMLX framing and reads the inner message anyway.
2. If that fails, use a converter that explicitly handles EMLX. Most decent EML-to-PST converters do.
3. Worst case, write a script to strip the EMLX wrapper and produce clean EML files.

Confirm Outlook profile#

Outlook must be running the profile for the target mailbox. Multiple profiles are easy to mix up. Verify in File > Account Settings > Account Settings that the listed account is the intended destination.

Route A: Drag and drop#

1. Create the destination folder

   In Outlook, navigate to the parent location in your folder tree where the imported content should land. Right-click, New Folder, name it (e.g. Imported).

   For nested structure, create the full hierarchy first: Imported, then under it Clients, then under that Acme, and so on. Drag-and-drop drops messages into one folder at a time; you have to repeat the operation per source directory.

2. Open both windows side by side

   Open Windows Explorer to the EML source directory. Position it so you can see both Explorer and the Outlook folder pane simultaneously. Outlook needs to be the visible window receiving the drop, with the target folder selected in the folder pane.

3. Select and drop

   In Explorer, select EML files (Ctrl+A for all in current folder). Drag onto the Outlook target folder in the folder pane.

   Outlook reads each file and stores it. The status bar shows progress. UI feels frozen during processing; this is normal. For 500 EMLs, expect 30 to 60 seconds. For 2,000, expect 2 to 5 minutes with Outlook noticeably unresponsive.

   If Outlook hangs for more than 10 minutes, kill the process and try a smaller batch. Outlook does not handle drops over a few thousand files well.

4. Repeat per directory

   For nested source directories, repeat the operation:

   1. Navigate Outlook to the matching destination folder.
   2. Navigate Explorer to the corresponding source folder.
   3. Select and drop.

   This is the part that makes drag-and-drop painful at scale. A source with 50 subdirectories means 50 separate drag-and-drop operations. PST conversion handles all of this in one pass.

5. Verify after each folder

   Right-click the destination folder in Outlook, Properties, check total items count. Compare to the source EML count in Explorer.

   If counts differ, scroll through the destination folder and look for rejected messages. Outlook silently skips EMLs it can't read.

Route B: EML to PST conversion#

1. Choose a converter

   Several EML-to-PST converters exist. Selection criteria:

   • Handles your source variant (plain EML, EMLX, Outlook Express compatible).
   • Recurses through nested directories preserving structure.
   • Preserves attachments without re-encoding.
   • Handles UTF-8 bodies correctly.
   • Logs skipped files with reasons.

   Free converters typically cap at a few hundred files. Paid converters in the $40 to $120 range handle larger batches and produce one PST per source tree.

2. Run conversion

   Point the converter at the root of the EML directory tree. It should recurse, reading each EML and writing into a PST that mirrors the directory structure.

   For batches over 50,000 files, expect 30 to 90 minutes of conversion time. RAM matters; some converters load files into memory before writing. A workstation with 16 GB RAM handles most batches.

   Output: one PST file (or several if you split by top-level directory).

3. Verify the PST

   Run scanpst.exe against the produced PST:

   "C:\Program Files\Microsoft Office\root\Office16\scanpst.exe"
   

   Repair any errors. Open the PST in Outlook as a standalone data file (File > Open & Export > Open Outlook Data File) and browse the folder structure. Spot-check messages and attachments. If everything looks right, close the file and proceed to import.

4. Import via the wizard

   With the source PST verified:

   File > Open & Export > Import/Export > Import from another program or file > Outlook Data File (.pst)

   Point at the converted PST. Choose Do not import duplicates for safety. Select the destination, either a dedicated folder or "Import items into the same folder in [target account]" to recreate the structure.

   A PST containing 10,000 messages imports in 15 to 30 minutes.

5. Wait for Exchange sync

   If the target is Exchange Online or on-prem Exchange, content lands in the OST cache first then syncs server-side. Sync takes about as long as the import itself.

   OWA does not show imported content until sync completes.

What changes during import#

Folder structure#

Both routes preserve folder structure when handled correctly. Drag-and-drop is folder-by-folder so you control the destination. PST conversion mirrors the source directory tree into the PST and then into Outlook.

Dates#

EML message Date headers are preserved. Outlook uses them for sort order. Messages appear in their original chronological position.

Read state#

EML files don't carry read state. All imported messages arrive as unread. Users have to mark-as-read or filter on a per-folder basis after import.

Flags and categories#

Flags don't exist in EML. Categories are preserved only if the EMLs include X-Outlook-Category or similar headers, which is rare unless the export was specifically structured. Treat both as lost.

Attachments#

Attachments and inline images survive through both routes. Outlook reads the MIME structure and stores attachments as Outlook-native attachments. Inline images with intact Content-ID references display inline.

Common failure modes#

Outlook hangs on drag-and-drop#

Too many files in one drop, or Outlook is low on memory. Kill the Outlook process (Task Manager), restart, try smaller batches.

EMLs land in wrong folder#

The target folder wasn't selected in Outlook when you dropped. Outlook drops onto the currently selected folder. Verify before each drop.

EMLX files appear as garbage in Outlook#

The EMLX wrapper made it through. Outlook displayed the length prefix and metadata as message body content. Use a converter that handles EMLX, or strip the wrapper first.

Converter produces empty PST#

Source directory is empty, or the converter didn't recurse into subdirectories. Verify the input path is correct and the tool's recurse setting is on.

Errors have been detected in the file during PST import#

Run scanpst against the converted PST and repair. If scanpst can't fix it, try a different converter.

Some EMLs missing after drop#

Outlook silently skipped corrupt or unreadable files. Spot-check the source folder for files with unusual extensions or zero byte sizes. Open a sample in a text editor to confirm headers are intact.

Picking a route#

Pick drag-and-drop when:

• You have under 1,000 EML files.
• The structure is flat or has only a few folders.
• It's a one-off and conversion tool cost isn't worth it.
• You want zero third-party software involvement.

Pick PST conversion when:

• You have over 1,000 EML files.
• The structure has multiple nested folder levels.
• You need logs and reconciliation reports.
• You'll use the produced PST as an archival artifact.
• You're doing batch work across multiple users.

For format background, see the EML format glossary entry and the PST, MBOX, and EML migration guide. For the related PST format topic, see the PST file glossary entry. If your destination is Gmail instead of Outlook, EML to Gmail covers the IMAP-append route. For MBOX sources targeting Outlook, see MBOX to Outlook.