-

Written By Harshita Sachdeva
-
Approved By
Shivam Rathore -
Updated on October 6th, 2026
Rachel, IT Admin From Ohio, Asked
We’re retiring a batch of employee accounts, and compliance wants a local copy of each primary mailbox before the accounts get disabled. I ran the eDiscovery export first. It split one 14 GB mailbox into two PST files the moment it crossed 10 GB, and now the records team has two files to track instead of one. I also can’t afford to lose folder structure or calendar entries in the process. What’s actually the most reliable way to export Primary Mailbox to PST file without hitting size errors or losing data along the way?
Introduction: In today’s era of digitalisation, every organisation or enterprise relies on Outlook for its day-to-day business communications. As a result, the entire communication associated with a particular employee/working professional resides in Outlook’s mailboxes, including the primary mailbox. Once these employees leave the organisation, it creates a need to create a backup of these conversations and keep them preserved for work-related needs. This is when users turn to Microsoft Outlook/eDiscovery to backup Primary Mailbox to PST. However, a few of them opt for the Aryson Exchange Server Backup Tool due to certain Microsoft 365 size limits and permission requirements.
A user’s live Exchange or Microsoft 365 mailbox consists of multiple folders, including inbox, sent items, calendar, contacts, and subfolders. When professionals consolidate this data into a single portable Outlook data file (.pst), the export process is termed “Primary to PST export”.
Working professionals export this Outlook data to a PST file at the time of offboarding employees, when they create backups, and for auditing purposes. The resultant PST file consists of a folder structure and timestamps as it is. On the other hand, the server-side permissions, retention labels, or litigation holds might not be automatically included
There are certain limitations that are associated with the Primary mailbox to PST export. The below-given tabulated structure lists all the required size limits one needs to know.
| Item | Export Details |
| Emails, folders | Migrated with structure intact in Outlook and PowerShell export |
| Calendar, contacts | Included when exporting via Outlook or PowerShell; not always via eDiscovery |
| PST size (Outlook 2016+) | Capped at 50 GB per Microsoft’s documented data-file limit. |
| eDiscovery PST export | Capped at 10 GB per mailbox; larger results auto-split into multiple PSTs. |
| Content search export rate | Limited to roughly 2 GB per hour per mailbox by Microsoft |
| PowerShell export | Requires the Mailbox Import Export RBAC role, unassigned by default. |
| Archive mailbox | Needs a separate export request using the -IsArchive parameter. |
| Server permissions | Not carried into the PST; must be reconfigured post-export |
There is no single native method that would fit for each export scenario. The right choice of method might vary from user to user depending upon the mailbox size, bulk-export needs, and permissions already assigned. This section covers the top manual and professional methods to download Primary Mailbox to PST format in a secure way.
You can use the classic version of Microsoft Outlook to export the primary mailbox to a local PST file. There is no need for admin-level PowerShell access to perform this export. This method is generally used where there is a need to export one mailbox at a time. Also, it depends on whether the required mailbox data is available and synchronised in the Outlook profile.
This Exchange PowerShell method is particularly for admins to help them migrate data, and it is designed for on-premises Exchange Server. It would create a mailbox export request that will eventually save the mailbox data as a PST file on a YNC network share. Thus, there is no need for Outlook to perform the export.
| New-MailboxExportRequest -Mailbox <User> -FilePath “\\Server\PSTShare\User.pst” |
| Get-MailboxExportRequest |
Manual export methods lag behind enterprise needs in several ways:
Large organisations have a large number of mailboxes to migrate, so they prefer to opt for the Aryson Exchange Server Backup tool instead of migrating each individual file. The CSV import feature makes bulk migration of all sub-users way easier and much more convenient for the end user. At the same time, the tool exports primary and shared mailboxes, along with the Online Archive, without compromising data integrity or credential security. With the help of the same software, one can export Exchange mailbox to PST within a few minutes. Even the folder hierarchy and data are kept intact at the end of the export process.
An IT admin reported that as a member of a legal firm, he needed to export 40 employees’ mailboxes to PST format before the platform retired. Each mailbox contained approximately 15 GB of data. Initially, he tried to use the eDiscovery export method, but it kept splitting files after a limit of 10GB. This was when he switched to the Aryson Exchange Server Backup tool to export entire Primary Mailbox to Outlook PST file. This saved him days and even delivered satisfactory results.
The right method to export Primary Mailbox to PST file might vary from user to user, depending on the mailbox count and size. Even the concern of folder structure maintenance plays an important role in method selection. To export a lightweight mailbox to PST format, the manual methods like Outlook and PowerShell might help you. Whereas, to export a bulky mailbox, it is highly recommended to opt for the Aryson Exchange Server Backup tool. Even if you don’t possess any technical expertise, it is easy to operate this intuitive and GUI-based utility. Also, in case of any export-related queries, the tech support team is 24/7 available for personalised assistance.
Ans: Microsoft says that Outlook 2016 and subsequent versions will support PST files of up to 50GB. However, older versions such as Outlook 2007 have an upper limit of just 20GB. You really need to think about your file size whenever you’re planning an export.
Ans: With the help of the Date Range Filter of the software, you can pick the emails from a certain project duration if you require. Just specify the start and end dates of the duration and begin the export process. This will help you export only the relevant data to PST format.
Ans: Even if your primary mailbox contains data in large amounts, the software doesn’t limit the export. You can use the PST Splitting option in order to divide the resultant file into multiple PSTs based on a particular specified size. This eventually helps users to manage large exports and manage files in a much better manner.
Ans: When you export the primary mailbox to PST format, it is necessary to consider whether there is any duplication. To avoid any kind of duplicate data, you can use the Duplicate Removal filter of the software, which identifies repeated emails on the basis of Subject, From, and To. Once you toggle on this feature, the repeated emails will not be included in the resulting file.
Ans: No. Exporting to PST makes a copy of your mailbox data itself. Your actual mailbox on Exchange or Microsoft 365 will stay exactly the same – unless you perform a different delete or archive operation afterwards.
Ans: Yes, archive mailbox data can be included by using the -IsArchive parameter in PowerShell or by selecting the Online archive option in the Aryson Exchange Server Backup tool.
Ans: If you feel stuck at any step of the export process, reach out to the technical support team. The team is available 24/7 to help you out and assist with any export-related doubts.
About The Author:
Harshita Sachdeva, a professional technical writer at Aryson Technologies, specialize in delivering clear, hands-on documentation for data management, migration, and recovery solutions. With a meticulous, reader-first approach, I break down complex technical processes into simple, actionable content - helping IT professionals and decision-makers tackle challenges efficiently.
Related Post
Useful Links
© Copyrights 2014-2026 by Aryson Technologies Private Limited - All Rights Reserved