Move Data

How to Import PST to Exchange Server (SE, 2019, 2016 & 2013) Safely?

Fact-checked and reviewed in accordance with our Editorial Policy

You can import PST files to Exchange Server SE, 2019, 2016, 2013 or Exchange Online with the help of the built-in import tools offered by Microsoft as well as a specialized tool. The Exchange Server 2019, 2016 and 2013 versions are no longer supported by Microsoft, but the import procedures compatible with the mentioned Exchange Server versions may still work with older versions. You can follow these steps to import PST to Exchange Server:

Prerequisites: First, provide the “Mailbox Import Export” role to your administrator account. In the case of importing to a local Exchange, save the PST files to a shared folder on the network and ensure that the “Exchange Trusted Subsystem” has permission for access. If you are importing PST files into Exchange Online, ensure that the required roles are assigned as per the Microsoft instructions; the permissions will take some time to become operational.

Manual Methods:

  • Local Servers (EAC GUI): Access the Exchange Admin Center, navigate to Mailboxes, and select “Import PST.” All that is required is to type in the network file path, choose a mailbox for the destination, and click on Finish.
  • Local Server (PowerShell): Access the Exchange Management Shell and issue the New-MailboxImportRequest. The command simply requires you to provide the name of the mailbox to which you want to send the PST.
  • Exchange Online (Microsoft Purview): You need to start a new import job via the Microsoft Purview dashboard in order to get your secure link for upload. You should then upload your PST files while keeping their size less than 20 GB using the AzCopy tool, then submit a CSV file indicating to the system which user should receive which file.

Dedicated Tool:

  • Use the BitRecover PST to Exchange Server Migration Tool to easily batch import PST to Exchange Server SE, 2019, 2016, and 2013, without manual scripting or technical challenges.

Managing local Outlook Data Files (.pst) across various computers of employees can be a challenge for IT admins. Such files are kept locally and, therefore, isolated from organizational search, security, and backup systems.

However, to tackle this problem, administrators have to combine their email systems and import the scattered PST files into Exchange Server or Exchange Online.

Note: In case of migrating to an on-premises server, Microsoft only allows the use of the latest Exchange Server Subscription Edition (SE); the earlier versions are no longer in service.

User Query on Reddit: Import PST to Exchange Server

Reddit user query on importing PST to Exchange Server

Expert Answer: A PST file can consist of emails sent or received by numerous individuals, however, a typical import will place the contents into the respective mailboxes. This type of import is not able to deliver different emails according to the sender or the receiver. Consequently, in a multi-user migration setup, use separate PST files or make use of a process with a clear PST to mailbox mapping.

Read Here: To back up server databases, check out our guide to export Exchange Server mailboxes to PST.

Why Do Businesses Need to Import PST Files into Exchange Accounts?

  • Centralized storage: The need to import PST to Exchange Server implies centralizing mailbox storage. As a result, disaster recovery and high availability depend on the configuration of Exchange, database replication, backup strategy, and protective services that are in place.
  • Search and compliance: Imported data can be subject to the policies and processes of Microsoft Purview, depending on licensing, configuration, permission policies, and indexing level. Furthermore, import does not configure retention or legal holds by default.
  • Access anywhere: Imported PST files are available from Exchange mailboxes through Outlook and other means of access. The ability to view contact lists, calendars, and other non-email items depends on how specific items have been transferred and the device used.
  • Archive consolidation: allows for merging orphaned PST files of former employees into places where they are either active or placed in the In-Place Archive mailbox.

Exchange Server Lifecycle Timeline: The current supported on-premises platform is Exchange Server Subscription Edition (SE). Microsoft holds no support for Exchange 2016 and 2019 after 14th October 2025, and for Exchange 2013, there is no support after 11th April 2023 (Exchange 2010 is also retired). Although the older steps are applicable in transferring previous server configurations, one must focus on deploying Exchange Server SE or Exchange Online.

Prerequisites Before You Import PST to Exchange Server

Before you begin to import PST files into Exchange Server SE, 2019, 2016, 2013 or Exchange Online, follow the given instructions:

1. Assign the “Mailbox Import Export” Role

The default implementation of on-premises Exchange does not include Mailbox Import/Export role. PST imports in Exchange Online must also comply with permissions outlined in Microsoft’s PST Import Service Description.

  • On-Premises PowerShell: Run New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "admin_user" in the Exchange Management Shell, and after that, simply verify the assignment with Get-ManagementRoleAssignment -Role "Mailbox Import Export" -RoleAssignee "admin_user". Once you change the role membership, simply sign out and then sign back in; and then reopen the Exchange Management Shell.
  • Exchange Online: Follow the Microsoft PST Import Service permission guidance. The recorded permissions include mailbox import/export as well as mail recipients. The documented processes can also be performed by an eligible Global Administrator. Use the least-privileged approach and keep in mind that it takes some time for the permission change process.

2. Configure UNC Share Permissions (On-Premises Native Imports Only)

Native on-premises imports (EAC and New-MailboxImportRequest) require a UNC network path (not required for Purview network uploads):

  1. Perform a right-click on the PST folder, then go to Properties > Sharing > Advanced Sharing, and tick the checkbox for Share this folder.
  2. Then, hit Permissions and provide Read access (Read/Write access in case of exports) to the Exchange Trusted Subsystem group.
  3. In the Security tab, verify that the required file-system permissions are applied to the Exchange Trusted Subsystem as well. Make sure you grant just the necessary permissions as per your scenario, and trust the SYSTEM Full Control grant is general for every import share.

3. Check PST Health, Size Limits & Mailbox Provisioning

  • PST Size and Health: For Exchange Online network uploads, the optimal PST file size should be less than or equal to (≤20 GB). In the case of an on-premise Exchange, the resources available on the server should be checked, and any corrupt PST file should be repaired by using scanpst.exe.
  • Size Limit on Messages: During the Exchange Online import of a PST file, anything greater than 150 MB will not be imported. Prior to this process, one needs to verify the mailbox and organization message size settings since 150 MB is not the default message size in each mailbox of Exchange.
  • Mailbox Availability and Licensing: Verify that your destination mailbox is available and provisioned correctly. Check the licensing requirements that would allow your mailbox features and archive functions.

How to Import PST to Exchange Server Manually? (5 Native Methods)

To import a PST file into Microsoft Exchange Server SE, 2019, 2016, 2013, or Exchange Online manually, you can use Exchange Admin Center (EAC), Exchange Management Shell (EMS), Microsoft Purview Network Upload, Microsoft Purview Drive Shipping, or Microsoft Outlook PST Import:

Method 1: Exchange Admin Center (On-Premises EAC GUI)

In Exchange Server SE, the EAC wizard is utilized to create PST import requests from a UNC share. Similar methods can be used in previous versions of Exchange, including Exchange Server versions 2019, 2016, and 2013, which are not supported anymore:

  1. Sign in to Exchange Admin Center (EAC) using an account that has the Mailbox Import/Export role.
  2. After that, Go to Recipients > Mailboxes > More options (…) > Import PST.
  3. Provide UNC path and filename (e.g., \\FileServer01\PSTImports\john.smith.pst). Then click Next.
  4. Choose the target mailbox. You must choose Import to this mailbox or Import to the mailbox archive, and then click Next.
  5. Finally, set up the notifications by email, click Finish, and you can check the status from the EAC Notification Viewer.

Considerations for the EAC Method

  • Unique Requests: Generates one import request per wizard run to import PST to Exchange Server.
  • Minimal Filtering: Does not include Purview’s item filters and PowerShell’s folder switches.
  • Use On-Premises: Moreover, it only works with on-premises Exchange Server. For imports within Exchange Online, employ Microsoft Purview (Method 3).

Method 2: PowerShell (On-Premises Exchange Management Shell)

With on-premises Exchange Server, it New-MailboxImportRequest sends a PST import request to the Mailbox Replication Service (MRS). The cmdlet and parameters that were used are written to match your version of Exchange. Using this cmdlet does not support importing PST to Exchange Server.

1. Syntax:

New-MailboxImportRequest -Mailbox <TargetMailboxIdentity> -FilePath <UNCPathToPST> [-Name <UniqueName>] [-IsArchive] [-SourceRootFolder <PSTFolder>] [-TargetRootFolder <MailboxFolder>] [-IncludeFolders <Folder1>...] [-ExcludeFolders <Folder1>...]

Available parameters vary by Exchange version. Check Microsoft’s cmdlet reference for the exact syntax supported by your server before adding options such as -BadItemLimit, -LargeItemLimit, or -Priority.

2. Import a PST to a Primary Mailbox:

New-MailboxImportRequest -Mailbox "[email protected]" -FilePath "\\FileServer01\PSTImports\alex_archive.pst"

3. Import Only the Inbox to an Archive Subfolder:

New-MailboxImportRequest -Name "Alex_Inbox_Restore" -Mailbox "alex.cooper" -FilePath "\\FileServer01\PSTImports\alex_archive.pst" -IsArchive -TargetRootFolder "Legacy_Emails" -IncludeFolders "#Inbox#" -Priority High

4. Bulk Import Multiple PSTs via PowerShell Loop:

Get-ChildItem "\\FileServer01\PSTImports\*.pst" | ForEach-Object { New-MailboxImportRequest -Name "BulkImport_$($_.BaseName)" -Mailbox $_.BaseName -FilePath $_.FullName }

Safeguard: This loop presumes that every PST filename (without the extension) corresponds to the mailbox it is meant for. Therefore, do not apply this to an unverified folder. For larger applications, please ensure a mapping has been created between PST files and mailbox destinations.

5. Monitor, Modify, Suspend, Resume & Remove Requests:

  • Check Progress: Get-MailboxImportRequest | Get-MailboxImportRequestStatistics | Format-Table Name,TargetAlias,StatusDetail,PercentComplete -AutoSize
  • View Report: Get-MailboxImportRequestStatistics -Identity "alex.cooper\MailboxImport" -IncludeReport | Format-List
  • Handle Problematic Items: Begin by checking the import report. Make adjustments to bad-item or large-item thresholds where applicable, but do so only once you know which items should be ignored. Nevertheless, these parameters alone will not fix PST errors. Make sure you know what the correct formatting and acknowledgment rules are for your version of Exchange before changing the request.
  • Suspend / Resume: Suspend-MailboxImportRequest -Identity "alex.cooper\MailboxImport" / Resume-MailboxImportRequest -Identity "alex.cooper\MailboxImport"
  • Remove Completed Requests: Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest -Confirm:$false (Confirm scope before running in production.)

Considerations for PowerShell Method

  • Not Supported in Exchange Online: As Microsoft does not offer assistance New-MailboxImportRequest in Exchange Online, one can make use of Microsoft Purview.
  • Handling Request Names: Exchange configures a maximum of 10 default names for the mailbox (MailboxImport0–MailboxImport9). It is possible to use a personalized -Name or delete any completed requests to create more requests.
  • Encrypted or corrupted PSTs: Native import processes do not by default fix PSTs or get around file passwords. Make sure that the PST can be opened using a given workflow, repair the file if needed, provide access credentials if necessary, load (Exchange Online)

Method 3: Microsoft Purview Network Upload (Exchange Online)

  1. Create a Job: As an administrator, open Microsoft Purview and go to Data lifecycle management, and then to Import. Click on New import job and upload your data. Make a note of the SAS URL that is provided and download the AzCopy application.
  2. Upload PSTs: Open the Command Prompt and use the following command to execute the task (make sure to replace the folder and the SAS URL text):
    azcopy.exe copy "C:\LocalPath\PSTs" "Your_SAS_URL"

    Tip: Keep files under 20 GB for best performance.

  3. Create the CSV: Now create a spreadsheet and include exactly these 10 headers:
    Workload, FilePath, Name, Mailbox, IsArchive, TargetRootFolder, ContentCodePage, SPFileContainer, SPManifestContainer, SPSiteUrl

    Fill in the details like this: Exchange, (blank), alex.pst, [email protected], FALSE (for main mailbox), / (to merge folders), and keep the last 4 columns empty (so your row ends with 4 commas).

  4. Validate and Import: Lastly, go back to Purview, confirm the upload, submit your CSV file, click Validate and begin the import task.
Considerations for Purview Network Upload
  • Recommendation for 20 GB Size: Microsoft recommends using PST files that are no more than or equal to 20 GB for effective performance.
  • CSV Errors: Issues with the rows lead to job failure or individual PST mappings coming up as invalid until they are rectified.
  • No Repairs or Unblocking: Unlock the encrypted files and repair any corrupt PST files before beginning the import process. The logs can be checked later to verify the success of the import.
  • Archive Limits: Make sure you are aware of Microsoft’s latest limits before importing large volumes of archived information. Microsoft has set a limit of 100 GB for a single import event into user’s main archive box and it is not possible to use PST Import Service for huge PST files.
Method 4: Microsoft Purview Drive Shipping (Exchange Online)

For multi-terabyte PST archives where data upload is unreliable over the network, Microsoft Purview allows for physical drive shipping. Follow these steps to import PST to Exchange Server:

  1. Make sure to check the eligibility of both your organization and region for using the drive shipping service. Choose a drive that meets the current hardware specifications of Microsoft; thus, verify the interface and capacity of the drive before acquiring it.
  2. Subsequently, use the WAImportExport.exe application to store the PST files in a BitLocker-encrypted drive.
  3. At Microsoft Purview > Data Lifecycle Management > Microsoft 365 > Import, choose a drive shipping method and follow the instructions given in the portal for submitting the journal file, mapping CSV, and encryption details. Make sure to submit only the materials required in the workflow.
  4. Send the drive to the appropriate Microsoft location. According to Microsoft’s data, uploading the data to Azure takes 7 to 10 business days; however, this time does not account for shipping or PST data evaluation.
Method 5: Microsoft Outlook PST Import (Single Mailbox)

Import PST to Exchange Server via both Classic and New versions of Microsoft Outlook for Windows.

  • Classic Outlook: Click on the File tab and select Open & Export followed by Import/Export option, select the Import from another program or file option, and then locate the PST using Outlook Data File option. After that set options concerning the duplication of the imported items, specify the destination and complete the import process.
  • New Outlook for Windows: Open the Settings tab, select Data files followed by the Import button, and then find the PST file using the Outlook Data File option. After specifying the duplication options, choose the destination file and start the import.
Considerations for the Outlook Method
  • Version Differences & Client Load: Interfaces differ between Classic Outlook and New Outlook, and large PST imports are dependent on client hardware, file condition, and synchronization speed.
  • Best for Individual Imports: Outlook is an effective choice for importing files into a single mailbox. Exchange management tools or Microsoft Purview are more effective for bulk imports across multiple mailboxes.
Import PST to Exchange Server Easily via a Dedicated Tool

If you want to bypass manual PowerShell commands, CSV mapping files, or network-upload limits that are too technical and time-consuming, then use a dedicated PST to Exchange import tool.

BitRecover PST Converter Tool provides the easiest interface to quickly and directly import PST file emails, attachments, contacts, calendars, into Exchange Server SE, 2019, 2016, 2013, and Exchange Online accounts. Additionally, the tool supports automated mailbox mapping, large file handling, and lets you preview PST files, folders, and subfolders.

How to Import PST Files into Exchange Server SE, 2019, 2016, 2013, and Exchange Online?

Follow these simple steps to use the PST to Exchange import tool to upload PST files into an Exchange account:

  1. Firstly, Download and start the PST to Exchange import tool on your Windows or Mac.
    start pst to exchange import tool
  2. Click Select Files or Select Folder to load PST files. Or let the tool automatically detect PST files using “Convert configured Outlook mailbox data” to directly import PST to Exchange Server.
    add pst files or folders
  3. Preview and check the required mailbox folders and click Next.
    select required pst files
  4. Choose Exchange Server from the Saving options list to import PST files into Exchange account directly.
    import pst file to exchange server
  5. Enable Ignore System Folders or I am Admin for multi-user migrations.
    import pst to admin exchange account
  6. After that, enter your Exchange Server credentials, verify the mapping, and click Next.
    uploading pst files to exchange
  7. Lastly, inspect SavingLog.txt after completion to verify imported counts and check for skipped items.
    PST to Exchange Server migration completed with log report
Key Capabilities of PST to Exchange Import Tool
  • Destination Compatibility: Directly import PST to Exchange Server versions, Hosted Exchange configurations, and Exchange Online.
  • Batch and Mailbox Mapping: Easily bulk import multiple PST files to Exchange Server at once without manual effort.
  • Advanced Filter Options: PST to Exchange Server import tool allows users to filter PST file emails. The options are Create PST Year Wise, Date Range, From, To, Subject, Exclude Folders, Organizer, Root Folder.
  • Folder Structure & Formatting: Moreover, the software guarantees to import the original PST data to Exchange Server exactly in the same formatting and structure.
Comparison: Manual Methods vs. Dedicated PST to Exchange Import Tool
Criteria Exchange Admin Center Exchange PowerShell Purview Network Upload Purview Drive Shipping MS Outlook Wizard BitRecover Tool
Environment On-Premises On-Premises Exchange Online Exchange Online Configured Mailbox Import PST to Exchange Server SE, 2019, 2016, 2013 or Exchange Online
Bulk Import Individual requests Via scripts Yes (10-column CSV) Yes (CSV & drive) Single-user Bulk import PST to Exchange mailbox
Setup Needed UNC Share & Role UNC Share & Role Roles, SAS, AzCopy & CSV Eligible drive, encryption & current fees Classic or New Outlook “I am Admin” account
Large / Damaged PSTs Damaged items may fail; review import report Configured limits may allow import to continue with items skipped; no repair ≤20 GB recommended; item limits apply Large total volume May need prior repair No restrictions on File Size/ “Recovery Mode Option”
Folder Filtering Imports selected PST to chosen mailbox, subject to limits -IncludeFolders / -ExcludeFolders Preview filters & TargetRootFolder Preview filters & TargetRootFolder Folder & duplicate options Preview Folders and Advanced Filter Options
Final Thoughts

Overall, to import PST to Exchange Server SE, 2019, 2016, and 2013, use the Exchange Management Shell or Exchange Admin Center with the appropriate mailbox permissions and access to UNC shares. For Exchange Online, use the PST Import Service by means of either network upload or using the eligible drive-shipping option from Microsoft Purview. Therefore, if you want to bypass these complex methods to easily bulk import PST files into Exchange Server, then use BitRecover PST to Exchange import tool recommended by professionals.

FAQs: Import PST to Exchange Mailbox

Q 1: What are the necessary permissions to import PST files into Exchange Server?

To import PST to Exchange Server, you require “Mailbox Import Export” role to your account. Hence, if you use BitRecover PST to Exchange import tool, you can simply select the “I am Admin” option and bypass all manual configurations.

Q 2: What is the maximum file size limit to import PST file to Exchange Server?

Manual methods impose certain limitations to import PST files to Exchange Server. However, BitRecover PST to Exchange import tool does not provide any file size restrictions.

Q 3: How do I bulk import PSTs into an Exchange Server account?

You can use BitRecover PST to Exchange Import tool to easily bulk import multiple PST files into Exchange Server.

Q 4: Can I import specific PST file emails into Exchange Server account?

To import specific PST data into Exchange Server, use the dedicated PST to Exchange import tool that provides advanced filter options sort specific emails according to from, to, subject, etc.

About the Author

Rollins Duke

Rollins Duke

Technical Content Writer at BitRecover · 2129 articles

View all posts by Rollins Duke

Live Chat
Google Preferred Source