How to fix New-MailboxExportRequest is Not Recognized Error in Exchange 2016?

Hi Sandra & Lincoln,
The primary use of New-MailboxExportRequest cmdlet is to start the conversion process. It creates a request to export mailbox which is then followed by various other commands. But, sometimes this command fails to perform and there can be various possible reasons for it such as:

1. The Microsoft Exchange you are using is not the updated version.
2. The account implementing the export request does not have the required permissions.
3. Another factor can be not running the Exchange Management Shell commands with administrator rights.
4. Corrupted or damaged Exchange database can also be a reason.

To fix New-MailboxExportRequest failed error, you can try updating the Exchange version by installing SP1. After updating, restart EMS and try running the command again.

Another solution is to run Exchange Management Shell as an administrator.

If these solutions doesn’t work, then the third option is to check that the account using which you are implementing the command have “Import Export Mailbox” permission. If not, then first assign the permission and then try running the cmdlet again.

Hello Sandra,
If you are unable to export mailbox data after trying all the manual procedures then there are chances that your database is corrupted. You can go for a third party application such as EDB to PST Converter Software. This software will help you to remove corruption from Exchange database and then move it to Microsoft Outlook with ease.
Another major benefit of using this utility is that it processes mailbox data of Exchange 2016, 2013, 2010 and its lower versions. It also enables users to perform batch migration which makes the entire procedure time efficient as well and a user doesn’t have to remove New MailboxExportRequest not working error.

Hi Stephen,
Thanks for the reply. Even I easily switched my email application to Outlook without trying to fix New-MailboxExportRequest is not recognized error.