How to Export Public Folder to PST: A Technical Guide

Written By Khushboo Maurya
Updated on October 13th, 2026

ⓘ Fact-checked and reviewed in accordance with our Editorial Policy

5/5 - (1 vote)

Exchange Public Folders store shared content across departments & teams. Administrators often need to export this content into PST files for backup. The correct export method depends on whether the source’s Exchange Server, on-premises, Exchange Online or a hybrid environment. This guide walks through supported methods & common issues administrators encounter during export Public Folder to PST.

Table of Contents

What Is an Exchange Public Folder?

A Public Folder is a shared place inside Exchange that many people use. It keeps emails, calendar events, contacts, tasks, & messages all in one spot. Unlike a persons mailbox a Public Folder is not owned by just one person. Instead different groups or teams can use it depending on the permissions they have. The information in Public Folders is stored in Public Folder mailboxes on the Exchange Server or, in Exchange Online.

Why Export Exchange Public Folders to PST?

Organizations export Public Folder content to PST for several practical reasons:

Creating a local backup copy of shared organizational data.
Migrating Public Folder content to another environment or platform.
Archiving older content that is no longer actively used.
Preserving data before decommissioning an Exchange Server.
Accessing Public Folder content offline without server connectivity.
Maintaining a portable copy for administrators and compliance teams.
Supporting legal discovery or regulatory compliance requirements.

Prerequisities

Export options differ across Exchange Server 2010, 2013, 2016, and 2019. Exchange Online & hybrid environments introduce additional considerations. Confirming the source version first helps determine which export method applies.
Exporting a Public Folder requires appropriate permission levels on that folder. Common permission roles include Owner, Publishing Editor, Editor, & Reviewer. Administrators may also need elevated rights within the Exchange Admin Center.
Review the total size of the Public Folder before starting the export. Count the number of items, large attachments, and nested subfolders. Larger folders require more planning around time and storage capacity.
Confirm that the destination disk has sufficient free space available. The expected PST size should include room for temporary working files. Insufficient storage is a frequent cause of failed export attempts.
PST file size limits vary depending on the Outlook version in use. Modern Outlook versions using Unicode format support significantly larger PST files. Administrators should still avoid extremely large single PST files where possible.
Avoid modifying source Public Folder data while an export is running. Record the existing folder structure for later comparison and verification. Document folder permissions separately if they need to be reapplied later.

How to Export Office 365 Public Folders to PST

Several approaches exist for exporting Public Folder content, and each fits different environments and administrative access levels.

Method 01: Export Public Folder Via Outlook

Microsoft provides the Import & Export Wizard within Outlook for this task. This method works for Outlook 2013 and later versions with appropriate permissions.

This method suits smaller Public Folders & one-time export tasks. Microsoft documentation notes this approach is not recommended for very large Public Folders, generally above thirty gigabytes, due to performance limitations within Outlook.

Method 02: Export Public Folder Mailbox to PST Using Exchange Admin Tools

The Exchange Admin Center and Exchange Management Shell serve different administrative purposes. The Admin Center supports managing Public Folder permissions and mailbox assignments through a graphical interface. The Management Shell supports scripted export requests and detailed monitoring through cmdlets. Role-based access control determines which administrators can create or manage export requests. Review request status regularly and address any reported errors promptly. Capabilities available through each tool can differ across Exchange Server versions.

Method 03: Professional Way to Export Public Folder to PST

The Cigati Exchange Server to PST Backup Tool is one such solution built for this purpose:

It supports Public Folder mailboxes alongside Primary, Shared, and Archive mailbox types.
The software preserves folder hierarchy throughout the export process, keeping the PST structure consistent with the source.
Administrators can apply date range filters to narrow the scope of an export.
A duplicate detection feature identifies repeated items based on sender, subject, & body content.
Batch processing allows multiple Public Folder mailboxes to be exported within a single session.
With this software, you can migrate Public Folder to Shared Mailbox.
It supports Exchange Server 2019, 2016, 2013, 2010, & earlier versions.

Download Now Purchase Now

Look at the guide on how the Cigati Exchange Server to PST Backup Tool Works.

How to Export Exchange Online Public Folder to PST

Exchange Online Public Folders require a different administrative approach than on-premises servers. Native PowerShell export requests to PST are not available in Exchange Online. Microsoft Purview eDiscovery tools can export Public Folder content for compliance purposes in supported scenarios. Outlook remains available as a method when Public Folders are added to a Microsoft 365 profile. Large Public Folder environments in Exchange Online may require exporting folders individually. Administrators should evaluate whether they need the entire hierarchy or selected folders only.

Public Folder Permissions vs PST Data

A PST file stores mailbox items rather than server configuration settings. Public Folder permissions exist as configuration data within Exchange itself. Exporting a Public Folder to PST does not restore its original permissions automatically. Organizations planning migration or disaster recovery should document permissions separately in advance.

Common Problems When Export Public Folder to PST

Public Folder Is Not Visible in Outlook This issue often relates to permissions, Outlook profile settings, / cached data. Confirm folder permissions & refresh the Outlook profile before trying again.	Export Option Is Missing Outlook version limitations or insufficient permissions can hide the export option. Confirm the Outlook version supports Public Folder export before proceeding further.
Export Stops or Gets Stuck Large folders, network interruptions, or Exchange throttling can pause an export. Corrupt items within the folder may also interrupt the export process.	Some Items Are Missing Applied filters, unsupported item types, or permission restrictions can exclude items. Review export logs to identify which items were skipped & why.
PST File Is Too Large Split the export into smaller PST files or separate folder batches. Adjust PST size settings appropriately before starting a new export attempt.	Attachments Are Missing Check item-level export results and verify attachment size against known limits. Review detailed export logs to confirm attachment handling during the process.

How to Verify the Exported PST

Open Outlook on a machine with access to the file.
Add or open the exported PST file within Outlook.
Check that the Public Folder hierarchy appears as expected.
Compare folder counts against the original source structure.
Compare item counts between the source and exported PST.
Open sample emails to confirm content displays correctly.
Test several attachments to confirm they open properly.
Check calendar and contact items where they were included.
Verify dates and metadata match the original source items.
Review export logs or generated reports for any errors.

Public Folder to PST Validation Checklist

PST file opens successfully in Outlook.
Folder hierarchy remains intact and accurate.
Expected folders are all present in the PST.
Item counts appear reasonable compared with the source.
Attachments open correctly without errors.
Sample emails display readable, accurate content.
Calendar and contact items appear where expected.
No unresolved export errors remain in the log.
The PST file has been copied to secure storage.

Public Folder Export vs Public Folder Migration

Public Folder Export	Public Folder Migration
Creates a PST copy of the data	Moves data to another Exchange environment
Useful for backup or archiving	Useful when changing platforms entirely
PST file is the final destination	Another Exchange environment is the destination
Permissions often need separate handling	Permissions may need migration mapping
Generally a simpler process	Generally a more complex process

Best Practices for Public Folder to PST Export

Schedule exports during periods of lower server usage.
Confirm source folder permissions before starting any export.
Maintain sufficient free disk space throughout the process.
Export larger folders in smaller, manageable batches.
Preserve the original folder hierarchy during every export.
Record source folder and item counts before starting.
Validate the resulting PST file after export completes.
Retain export logs for future reference and audits.
Store exported PST files in a secure location.
Avoid deleting source data until validation is fully complete.

Conclusion

Exporting Public Folder data to PST requires attention to permissions, size, & environment. Available methods include Outlook, Exchange, and third-party software. Requirements differ across Exchange Server versions, Exchange Online, and hybrid environments. Permissions and PST size limits deserve careful attention throughout the export process. Validating the resulting PST file remains an essential final step. Administrators should select an export method that fits their environment, folder size, and available administrative access.

Frequently Asked Questions

Q1: Why doesn’t PowerShell export work for Exchange Online Public Folders?

Ans. Exchange Online does not provide native PST export-request cmdlets for Public Folders like on‑premises Exchange. Instead administrators must use Purview eDiscovery to export or export manually from Outlook after adding the folder to a profile.

Q2: What permission roles affect export capability. How do they differ?

Ans. Owner, Publishing Editor, Editor and Reviewer roles control read, write and create access at the folder level. In addition administrators may need Exchange Admin Center or RBAC rights to create or manage export requests across the organization.

Q3: What’s the technical difference between Exchange 2010 and 2013+ Public Folder architecture?

Ans. Exchange 2010 stored Public Folders in a Public Folder database. Exchange 2013. Later replaced that database with Public Folder mailboxes—regular mailboxes that host the folder hierarchy and content. That is why PowerShell export requests became possible from Exchange 2013 onward.

Q4: What causes Exchange throttling during export. How does it affect large folders?

Ans. Exchange applies throttling policies to limit resource use per request or user. For Public Folders throttling can slow or pause export jobs. You can mitigate this by batching exports running them during off‑peak hours or splitting the export by subfolder.

Q5: What’s the technical reason large PSTs cause problems?

Ans. ANSI‑format PSTs had a limit of 2 GB. Unicode‑format PSTs introduced with Outlook 2003 support larger sizes but very large single PST files can still corrupt, run slowly and take long to load in Outlook. That is why it is recommended to split PST files.

Q6: How do I monitor an export request via Shell?

Ans. Use status‑checking cmdlets to query the export request. These cmdlets return the progress percentage, status (Queued, InProgress, Completed, Failed) and any error messages. Monitoring this way lets you intervene before a failure becomes critical.

Q7: What technical factors cause ” items” during export?

Ans. Filters that limit the date range or item type may exclude content. Corrupted items that fail mid‑export can also be missing. Insufficient permissions on subfolders can cause items to be skipped. Export logs usually flag skipped items with a reason code.

Q8: Whats required to include subfolders, in an export request?

Ans. The export request, whether you use Shell parameters or a tool’s user interface must explicitly enable an “include subfolders” or recursive scope option. Without this option the top‑level folder’s items are exported, not the nested hierarchy.

About The Author:

Khushboo Maurya

Khushboo Maurya is a digital content and SEO professional focused on creating useful, search-friendly content that connects with the right audience. She specializes in content optimization, website growth, and practical SEO strategies that improve visibility, engagement, and organic reach.