To convert EDB to PST, mount the database on a working Exchange server and run a mailbox export request. If Exchange is unavailable, load the offline file into a dedicated EDB to PST converter such as MailPro+, which extracts mailboxes and exports them to Outlook PST without a running server. The manual route is free but needs a healthy database. The tool route works on offline, dirty-shutdown, or orphaned files.
What Are EDB and PST Files?
An EDB file is the Exchange database. It holds every mailbox on that database: emails, contacts, calendars, tasks, notes, and sometimes archive mailboxes and public folders. It is tied to transaction logs and a specific server.
A PST file is a portable Outlook data file. It opens in Outlook on any computer, which makes it the standard format for backups, archiving, e-discovery, and migration. This is why people search for “exchange database to outlook pst” and “extract mailboxes from edb file.”
Why Convert an EDB File to PST?
Disaster recovery: The server is dead but the database file survived.
Migration: You are moving to a new platform and need mailbox-level data.
Compliance and e-discovery: You need one custodian’s mail, not the whole database.
Decommissioning: Archive old mailboxes before retiring a server.
Orphaned mailboxes: Users were deleted, but their data is still in the database.
Before You Start: The Checklist Most Blogs Skip
Skipping these checks causes most failed conversions.
Work on a copy. Never convert or repair your only original EDB.
Check the database state. Run eseutil /mh against the file. “Clean Shutdown” is what you want. “Dirty Shutdown” means logs must be replayed or the file needs repair first.
Keep the transaction logs. A dirty database cannot be fully recovered without the matching log files.
Plan disk space. Keep at least as much free space as the database size, since PST output can be large.
Know the PST limits. Modern Unicode PST files default to a 50 GB limit, and Outlook slows noticeably as they grow. Split large mailboxes.
Confirm permissions. Manual exports need the Mailbox Import Export role.
Match versions. The database version must be compatible with the Exchange server you mount it on.
Method 1: Manual Steps for Exchange Admins
If the database is healthy and you have a working server, native PowerShell can handle it.
Step 1: Assign the Mailbox Import Export role to your admin account.
Step 2: Create a network share and grant Exchange permission to write to it. PowerShell exports need a UNC path, not a local drive path.
Step 3: Run an export request:
New-MailboxExportRequest -Mailbox user@domain.com -FilePath \server\share\user.pst
Step 4: Track progress with Get-MailboxExportRequest, and remove completed requests when finished.
For an offline EDB: You cannot export directly from a loose file. Create a recovery database, mount the EDB there, restore the mailbox into a live mailbox, and then export that mailbox to PST. This is slow, and it requires a working Exchange environment.
Limitations of the manual method:
It needs a running Exchange server and the right roles.
Dirty or corrupt databases usually fail.
There is no preview, so you cannot check content before exporting.
It is hard to filter by date, folder, or item type.
Recovery-database restores are time-consuming for a single mailbox.
Method 2: Convert Offline EDB Mailbox to PST with a Professional Tool
When Exchange is not running, the database is damaged, or you need selective exports, a dedicated tool is the practical answer. MailPro+ email conversion lets you export Exchange mailbox to PST without Exchange running and without creating a recovery database.
Follow these steps to convert EDB to PST:
Download and install the tool on a Windows machine. It does not need to be the Exchange server.
Launch the software and choose the EDB option for Exchange database files.
Add your EDB file with the browse option. Select the file copy you made earlier.
Scan the database. A quick scan suits healthy files. Use the advanced or deep scan if the file is corrupt or from a dirty shutdown.
Preview the mailboxes. Expand the folder tree to check emails, contacts, calendars, and attachments before exporting.
Select what to export: all mailboxes, specific users, or specific folders.
Choose PST as the output format and set options such as PST splitting, date filters, or item filters if available.
Pick a destination folder with enough free space.
Click Export and wait for completion.
Verify the result by opening the PST in Outlook through File > Open & Export > Open Outlook Data File. Check folder counts and spot-check recent mail.
Menu labels can vary slightly between versions, so follow the on-screen options of your installed build.
Manual vs. Tool: Which Should You Choose?
Choose the manual method if you have a healthy database, a working Exchange server, a few mailboxes, and time to spare.
Choose the tool method if the server is gone, the database is corrupt, you need to convert offline EDB mailbox to PST, or you want to preview and filter before exporting. It is also the faster option for bulk exports.
What Gets Converted and What Doesn’t
Most guides never say what you actually get. A good EDB converter should carry over:
Emails with attachments and original timestamps
Contacts and distribution lists
Calendar items and meeting requests
Tasks, notes, and journal entries
Folder hierarchy
Archive mailboxes (verify support in your tool)
Public folders (often exported separately)
Always test a sample mailbox first, then check item counts against the source preview.
Common Errors and Fixes
Dirty shutdown state: Replay logs with eseutil /r using the correct log prefix. Use eseutil /p only as a last resort, because it discards unrecoverable data. Use a deep-scan tool instead when logs are missing.
Export request stuck or failed: Check share permissions, available disk space, and whether the mailbox is in a recovery or mismatched database.
PST too large or Outlook slow: Split the output by size, date range, or folder.
Missing mailboxes in the output: The mailbox may be disconnected or soft-deleted. Scan for orphaned mailboxes in the tool, or check retention settings.
Version mismatch: An EDB from a newer server cannot be mounted on an older one. Offline tools avoid this problem.
Pro Tips for a Clean Conversion
Convert in batches of mailboxes rather than all at once, so one failure does not block the project.
Keep a record of source item counts per mailbox so you can compare after export.
Store the original EDB and logs until the PST files are verified by their owners.
Export legal-hold mailboxes with timestamps preserved, and document your process for chain of custody.
Scan finished PST files with Outlook’s built-in inbox repair tool if anything looks off.
Frequently Asked Questions
Can I convert EDB to PST without Exchange Server?
Yes. Offline EDB converters read the database file directly, so you can export Exchange mailbox to PST on any Windows computer without Exchange installed.
Is there a free way to convert EDB to PST?
The native PowerShell export is free, but it requires a licensed, working Exchange environment and a healthy database. Free third-party options are usually limited in size or items.
How do I extract mailboxes from an EDB file?
Mount it in a recovery database and restore mailboxes manually, or load it into an EDB converter, preview the mailboxes, and export the ones you need.
How long does the conversion take?
It depends on database size, disk speed, and scan type. Multi-hundred-gigabyte databases can take hours, so plan a maintenance window.
Can I export only one mailbox or date range?
With PowerShell, you can target a single mailbox. Date and folder filtering is easier in a tool that supports selective export.
Will the folder structure and attachments stay intact?
A reliable converter keeps the folder hierarchy, attachments, and metadata. Verify with a test mailbox first.
Does the PST work in all Outlook versions?
Unicode PST files open in modern Outlook versions. Older ANSI format Outlook releases have a 2 GB limit, so use Unicode output.
Final Thoughts
Whether you run PowerShell on a live server or work from a lone database file, the best way to approach how to convert Exchange EDB to PST is to check the database state first, work on a copy, and verify the output before deleting anything. For offline, damaged, or bulk jobs, a dedicated tool saves hours compared with the recovery-database route.
Top comments (0)