How to Export Exchange 2016 Mailboxes to PST – PowerShell

The practice of exporting mailboxes data to PST using PowerShell commands are now getting popular day-by-day, as the number of users are migrating to newer Exchange Server version 2016. With the release of Exchange Server 2016, Microsoft has added lot of new features in Exchange latest version along with the newer cmdlet for exporting mailboxes data to PST file that is available only in on-premises Exchange Server 2016.

So today we’ve decided to share a post on Exchange 2016 cmdlet New-MailboxExportRequest, and will show you how easily you can export Exchange 2016 mailboxes data to PST format by simply using this PowerShell in Exchange Management Shell. But New-MailboxExportRequest command is only available in Mailbox Import Export role, not to a role group. To use the command, we have to add the Mailbox Import Export role to a role group. Check here how to add a role to a role group.

Once you’ve assigned a role to a role group, you can perform the below PowerShell to Export Exchange Server mailboxes data.

PowerShell to Export Exchange 2016 Mailbox to PST

  1. Let’s consider a scenario where you’ve to export a user’s primary mailbox data to PST file on the network shared folder on an Exchange Server, where Thomson is a primary mailbox user, MyNetworkPST is a network shared folder, and SERVER22 is the server.

Just run below command to export PST file-

New-MailboxExportRequest -Mailbox Thomson -FilePath “\\SERVER22\MyNetworkPST\Thomson_Recovered.pst”

  1. Considering another case where you need to export Thomson’s archive to a PST file on MyNetworkPST network shared folder on Exchange Server SERVER22.

New-MailboxExportRequest -Mailbox Thomson -FilePath “\\SERVER22\MyNetworkPST\Thomson_Archive.pst” –IsArchive

  1. In the next example we’re exporting mailboxes messages on the basis on content filtering or word matches ‘target‘ and ‘sales‘ in the body of the message for the Thomson user mailbox received before May 2, 2015. Execute the below command-

New-MailboxExportRequest -Mailbox Thomson -ContentFilter {(body -like “*target*”) -and (body -like “*sales*”) -and (Received -lt “02/05/2015”)} -FilePath \\SERVER22\MyNetworkPST\Thomson_MyCompanyReports.pst

And in case if you want to export all the Thomson mailbox messages to the PST file ThomsonData, run the below PowerShell-

New-MailboxExportRequest -Mailbox Thomson -IncludeFolders “#Inbox#” -FilePath \\SERVER22\MyNetworkPST\Thomson\ThomsonData.pst

We can also create multiple mailbox export request per mailbox where each request must have a unique name. However, Exchange server automatically generates up to 10 unique names for a request but if you want to export more than 10 mailboxes, you will have to specify a unique name. You can also remove current mailbox export request by executing Remove-MailboxExportRequest cmdlet before starting a new mailbox export request with the default request name. Also check the mentioned Import Export permission over here , as it is required to check what permissions are needed to run these cmdlets.

So this is the suggested way to export mailboxes into .pst file from Exchange 2016 if you could manage and run shell commands in Exchange Management Shell. But if you find any difficulty in the above process, we suggest you try Stellar mailbox to PST export tool, as it is an efficient way for exporting EDB/Mailboxes items to PST file. Whether you’re using Exchange Sever 2016, 2013, 2010, or any other previous version; this software supports all MS Exchange versions. You can download the demo version from here:

You cannot only export live mailboxes to PST but also can convert an offline EDB file to PST format. Additionally, the inbuilt functionality of this software allows you to export offline mailboxes to any other live exchange server and Office 365.

Let us know if you’ve faced any difficulty in above solution or in the suggested software.

3 Comments

  1. Brandon June 10, 2016
  2. Paco August 22, 2017
    • Admin August 25, 2017

Leave a Reply

Your email address will not be published. Required fields are marked *