Company Data BuyersApply to All
Collaboration · Export guide

How to Export Outlook Email Archives and Metadata

Export Outlook email to PST, understand local synchronization and client differences, and preserve message headers, attachments and thread context for AI datasets.

By Company Data Buyers editorial desk · Reviewed · Editorial methodology

Before you begin: scope and permissions

  • Confirm the Outlook client and operating system and the mailbox/folder scope approved by the organization.
  • Verify that required messages and attachments have synchronized locally; check policy restrictions and separate authority for shared or archived mailboxes.
  • Approve the intended scope and use with the business owner; export access alone does not establish licensing rights.
  • Use an approved encrypted working environment with restricted access and a retention deadline.

Define which mailbox evidence is needed

Outlook email contains correspondence, recipient lists, dates, message headers and attachments. A mailbox archive can support continuity or migration; AI preparation requires a narrower question about the conversations and outcomes to preserve. Choose approved business mail folders and dates, excluding personal, HR or legally privileged material from the candidate scope.

Export using the matching Outlook client

For classic Outlook on Windows, use File → Open & Export → Import/Export → Export to a file → Outlook Data File (.pst). Select the approved folder scope, include subfolders if needed, and choose a secure destination. Microsoft’s PST export procedure distinguishes clients. New Outlook uses its Settings → Files → Export workflow where available; Mac and web interfaces differ. Confirm the current instructions for your actual client before starting.

PST is an archive container, not JSONL. Check synchronization and the export contents. Exporting locally available data does not establish that every server-side folder, online archive or shared mailbox was included.

Plan organization-scale collection separately

A workstation export is not a tenant-wide collection mechanism. For many mailboxes, involve the Microsoft 365 administrator in selecting an authorized service-side or API method. This guide does not prescribe a universal compliance export or Graph permission set. Check the chosen method’s current licensing, retention coverage and content access before using it for commercial preparation.

Keep a mailbox-scope register and extraction log. A summary should distinguish the raw number of copied messages from unique messages and complete threads. The same correspondence may occur in several employees’ mailboxes.

Convert without losing message structure

Use an approved PST reader or conversion tool in a restricted environment. Record tool version, parse failures and output counts. Preserve Message-ID, In-Reply-To, References, source folder, timestamp offset and body representation where present. Keep attachment parts linked to the message rather than merging their text into an unexplained body.

For a synthetic thread, message a asks about an error, b suggests a fix and c confirms a result. Thread reconstruction should use header relationships where available, with a documented fallback for missing headers. Grouping only by “Re: Help” can merge unrelated customer incidents.

Clean repeated quotes and protect identities

Retain a source copy, then separate newly authored text from quoted history in a derived field. Deduplicate across mailboxes using reviewed message identities and content checks while preserving all source provenance. Do not assume Message-ID alone is always present or perfectly reliable.

Review To/Cc/Bcc, signatures, calendar invitations, filenames and document text for personal information. Sender aliases can remain linkable through unique roles and incidents. Removing email addresses alone does not establish anonymization. Company mailbox access also does not establish rights over customer-authored text or licensed attachments.

Troubleshoot and assess readiness

Why are older messages missing? Inspect synchronization windows, online archives, folder selection and the actual export log before rerunning.

Why are conversation counts inflated? Check duplicate mailbox copies and quoted history before treating each exported body as an independent exchange.

Possible tasks include correspondence summarization and domain-specific extraction. Assess complete thread coverage, attachment dependencies, language and confidentiality restrictions. Describe these at a high level for an evaluation; do not send a raw PST file in an initial application.

Release checklist

  • Compare exported folder/date coverage with the source mailbox; a local cache may be incomplete.
  • Preserve reply-reference headers and MIME/attachment structure during conversion from PST.
  • Reconcile source counts and date coverage; record excluded or unavailable records.
  • Validate identifiers, relationships, timestamps and field types after transformation.
  • Document provenance, privacy review, third-party restrictions and the authorized release approver.
  • Scan the release files for personal information, secrets and confidential material; test a reviewed sample before transfer.

Continue preparing your dataset

Explore licensing and buyer fit

All data export and preparation guides

Have a proprietary dataset?

Find out whether it may be suitable for AI licensing. Start with a high-level description of the source, date range, volume, rights status, and preparation work still needed.

Assess dataset readiness

Use the existing buyer application when ready. Share only authorized information. Do not submit raw confidential records, credentials, or personal data in the initial assessment.

Sources & verification

Official documentation reviewed 2026-10-15. Procedures and access rules can change. These are documentation-based instructions, not a live export from your account. Verify your product version, permissions and retention settings before running a job.