An EDB file is the database behind an Exchange server, and a PST file is what Outlook opens on a desktop. Converting one into the other is mostly a question of getting the mailbox out of the database in a state Exchange can export. The Microsoft route works well when the mailbox is healthy and the server is running. When the database is damaged or only the .edb file survives, the job becomes a recovery task first.
Quick Answer: On a running Exchange 2016, 2019 or Subscription Edition server, export a mailbox to PST with the New-MailboxExportRequest cmdlet. If you only have an offline .edb file, mount it in a recovery database on an Exchange server, then export from there. Whatever method you use, check the PST in Outlook before you delete anything from the source.
Command syntax checked against Microsoft's New-MailboxExportRequest reference and Exchange mailbox export procedures, October 2026.
Why people export Exchange mail to PST
The usual reasons are practical. An employee leaves and their mail needs to be kept, a legal or compliance request asks for a copy, or a migration needs a portable archive. A PST file can be copied, backed up or opened in Outlook without a live Exchange server, which makes it useful as a long-term copy of a mailbox.
What you need before you start
The export cmdlets are for on-premises Exchange. They will not run against Exchange Online or Microsoft 365 mailboxes, which have their own tools.
You need an account in the Mailbox Import Export role. Microsoft notes that the role is not assigned to any role group by default, so an administrator has to add it, for example to the Organization Management group, before the cmdlet will run. You also need a network share with enough free space for the PST, and the Exchange Trusted Subsystem group needs Read/Write permission on that share. Without that permission, the export fails with a connection error to the PST path.
Method 1: Export a mailbox with New-MailboxExportRequest
Open the Exchange Management Shell as an administrator, then run a command in this form:
New-MailboxExportRequest -Mailbox "jane.doe" -FilePath "\\FILESERVER\PSTExports\jane-doe.pst"
Replace the mailbox name and the UNC path with your own. The request runs in the background, so check on it with Get-MailboxExportRequest. For detail on how far along the export has got, use Get-MailboxExportRequestStatistics.
A few switches cover most real jobs. Add -IsArchive to export the archive mailbox instead of the primary one. Use -IncludeFolders or -ExcludeFolders to limit the folders you copy. If the export stops because of unreadable items, -BadItemLimit sets how many bad items the process tolerates before it fails. Only use -AcceptLargeDataLoss if you understand that it lets the export continue past items it could not copy.
If you later need to get the PST into Outlook Web Access, manual methods to import PST files into OWA cover that step. Once the request reports Completed, open the PST in Outlook and check a few folders and recent messages before you remove the request or make any other change.
Method 2: Recover mail from an offline EDB file
The export cmdlet works only on a mailbox that is mounted in a database on a running server. If all you have is a copy of the .edb file, you first need to bring the database back to a state Exchange can read.
The usual route is to add a recovery database on an Exchange server, point it at the copied files, and mount it. Once the mailbox appears there, run the same New-MailboxExportRequest command against it. If the database is damaged, Microsoft's Eseutil tool can attempt repair, but it changes the files it works on, so always run it against a copy and keep the original untouched.
For a more detailed walk through the EDB side, see how to extract data from an EDB file to Outlook PST. Expect this to take longer than the export itself. It is a recovery job, and the result depends on how damaged the database is.
Old methods you will see in search results
Older guides mention ExMerge, a free Microsoft utility from the Exchange 2003 era. It is not a sound choice for current Exchange versions, and most of those guides also describe Exchange Server versions that are no longer supported. If you find a step that tells you to use ExMerge on Exchange 2016 or later, treat that guide as out of date.
The same applies to any tool that promises to convert an EDB file on a PC with no Exchange server present. Some commercial converters do work from the file alone, and they can be useful when the server is gone. Read the vendor's own documentation, test the trial on a copy, and check that it supports your Exchange version and the Outlook version you plan to use.
Limits and things that go wrong
Export requests run slowly on large mailboxes, and a request can stall or fail partway through. Permissions are the most common cause of trouble, because the Mailbox Import Export role and the share permissions must both be in place. Items that Exchange cannot read will stop the job unless you allow a bad-item limit.
Filters are limited with the standard cmdlet. If you need to export only messages from a given date range, check the cmdlet's content filter options in Microsoft's reference before you start, because the syntax is easy to get wrong.
A safe order of work
Make a copy of the source database or the .edb file before you touch anything. Run the export to a new PST, not over an existing one. Open the result in Outlook and check the folder structure, a recent message, and an attachment. Keep the PST and the original backup until you have confirmed the mail is complete. If the PST then shows errors when Outlook opens it, how to repair an Outlook PST file covers the repair options.
Have you had to recover mailboxes from a damaged Exchange database? Tell us in the comments what worked, and what you would do differently.
