Export Exchange Mailboxes to PST: How-To

Yes, you can export Exchange mailboxes to PST files, and the method depends on whether you have access to the Exchange admin center (for multiple mailboxes) or only Outlook (for a single mailbox). This article explains both approaches, the permissions required, common pitfalls, and what to do when exports fail.

Why Export Mailboxes to PST?

PST (Personal Storage Table) files are the standard offline archive format for Outlook. Exporting a mailbox to PST is useful for:

• Creating a backup before migrating to a new email system.
• Complying with legal holds or eDiscovery requests.
• Freeing up server storage by archiving old emails.
• Transferring a user’s data to a personal computer or external drive.

Keep in mind that PST files are not encrypted by default and can be opened by anyone with the file, so they should be stored securely.

Method 1: Export from the Exchange Admin Center (EAC)

If you are an Exchange administrator, you can export one or multiple mailboxes to PST using the Exchange Admin Center (EAC) or PowerShell. This is the recommended approach for bulk exports.

1. Open the Exchange Admin Center (EAC) at https:///ecp and sign in with an account that has the Mailbox Import Export role (usually an Organization Management or Compliance Management admin).
2. Navigate to Compliance management > Mailbox export.
3. Click the + icon to create a new export request.
4. Select the mailbox(es) you want to export. You can also filter by date or include specific folders.
5. Choose the PST destination. The PST will be written to a network share or a local path on the Exchange server. You must provide a UNC path (e.g., \\server\share\export.pst) and have write permissions to that location.
6. Click Save. The export job runs in the background. You can check its status in the same section.

After the export completes, the PST file is placed at the specified path. You can then copy it to a local drive or external storage.

Method 2: Export via PowerShell

For more control or to automate the process, use the Exchange Management Shell. The cmdlet is New-MailboxExportRequest.

New-MailboxExportRequest -Mailbox "user@domain.com" -FilePath "\\server\share\user.pst"

To export only a specific folder, add the -ContentFilter parameter with a date range or subject filter. For example:

New-MailboxExportRequest -Mailbox "user@domain.com" -FilePath "\\server\share\user_archive.pst" -ContentFilter {(Received -gt '01/01/2020') -and (Received -lt '01/01/2021')}

The export runs asynchronously. Check its status with Get-MailboxExportRequest. Once completed, you can remove the request with Remove-MailboxExportRequest.

Method 3: Export from Outlook (Single Mailbox)

If you are a regular user (not an admin), you can export your own mailbox to PST using Outlook’s built-in Import/Export wizard. This works for Exchange, Microsoft 365, and IMAP accounts.

1. In Outlook, go to File > Open & Export > Import/Export.
2. Choose Export to a file and click Next.
3. Select Outlook Data File (.pst) and click Next.
4. Choose the folder you want to export (or select the mailbox root to export everything). Check the box Include subfolders if needed.
5. Click Next, choose a location and filename for the PST, and set your preferred options (e.g., replace duplicates, allow duplicate items).
6. Click Finish. Outlook will create the PST file.

This method is simple but only exports what is currently in your mailbox. It does not include items that are on the server but not synced (e.g., if you are using Cached Exchange Mode with a limited sync window).

Common Problems and Solutions

Several issues can arise during PST export. Here are the most frequent ones and how to resolve them:

• Permission denied: The account performing the export must have the Mailbox Import Export role. If you get an access denied error, ask your Exchange admin to assign the role or use an account that already has it.
• Export request stuck at “Queued”: This usually happens when the Exchange server cannot reach the network share or the share has insufficient permissions. Verify the UNC path is correct and that the Exchange server’s computer account has write access to the share.
• PST file is too large: PST files have a size limit (20 GB for Outlook 2007 and earlier, 50 GB for Outlook 2010 and later). If your export exceeds this, split the export by date or folder.
• Export fails with “MapiExceptionShutdown”: This can occur if the mailbox is being accessed by another process. Try again during off-peak hours or close Outlook on the user’s machine.
• Outlook export only exports cached items: If you use Cached Exchange Mode, the export only includes items that are in the local OST file. To export everything, either switch to Online Mode temporarily or use the Exchange admin export method.

Comparing Export Methods

Method	Who Can Use	Scope	Best For
EAC Export	Exchange admins	Multiple mailboxes, full mailbox or filtered	Bulk exports, legal holds, migrations
PowerShell	Exchange admins	Same as EAC, but scriptable	Automation, complex filters
Outlook Export	Any user	Single mailbox, whatever is in the OST	Personal backup, moving to another computer

Choose the EAC or PowerShell method if you need a complete, server-side export that does not depend on the user’s Outlook client. Use Outlook export for quick, user-level backups.

Costs and Licensing Considerations

Exporting mailboxes to PST itself does not incur extra costs in Exchange on-premises or Microsoft 365. However, there are considerations:

• Storage: PST files consume disk space on the destination share. Ensure you have enough free space.
• Microsoft 365: In Microsoft 365, the admin export feature is available only if you have the appropriate compliance admin role. There is no per-export fee, but you must have a licensed admin account.
• Third-party tools: Many commercial tools offer PST export with a GUI and advanced filtering, but they are not free. If you are comfortable with the built-in methods, you can avoid those costs.

Safety and Security Tips

PST files contain sensitive email data. Follow these practices:

• Store PST files on encrypted drives or secure network shares with restricted access.
• After export, verify the PST file opens correctly in Outlook before deleting the original mailbox data.
• If the PST contains regulated data (e.g., health records), apply appropriate access controls and consider password-protecting the PST (Outlook allows this when creating a PST).
• For long-term archival, consider using a format like EML or MSG instead of PST, as PST files can become corrupted over time and are tied to Outlook.

Frequently Asked Questions

Can I export a mailbox without being an admin?

Yes, if you have access to the user’s Outlook client, you can use the Import/Export wizard to create a PST. However, this only exports what is currently in the Outlook data file (OST), which may not include all server-side items if you are using Cached Exchange Mode. For a complete export, you need admin access.

How long does a PST export take?

It depends on the mailbox size and server load. A 10 GB mailbox might take 30 minutes to a few hours. The export runs in the background, so you can monitor its progress via the EAC or PowerShell.

Can I export only emails from a specific date range?

Yes. In the EAC, you can specify a date range in the export request. In PowerShell, use the -ContentFilter parameter with the Received property. In Outlook, you cannot filter by date directly; you would need to create a search folder first and then export that folder.

What is the difference between PST and OST?

PST is a portable archive file that can be opened in Outlook and moved between computers. OST is an offline cache file that is tied to a specific mailbox and is automatically recreated if deleted. You cannot open an OST directly; you must export to PST for portability.

Can I import a PST back into Exchange?

Yes, admins can use New-MailboxImportRequest in Exchange to import a PST into a mailbox. Regular users can also import a PST into Outlook, which will upload the items to the server if the mailbox is connected to Exchange.

What if the export fails halfway?

Check the export request status in the EAC or PowerShell. You can often resume a failed export by re-running the request with the same name. If the PST is partially created, you may need to delete it and start over, or use a third-party tool to repair it.

Related

• Unified Write Filter: What It Is & How It Works
• DDNS Dynamic DNS Service Explained
• How to Uninstall Zoom on Any Platform