How To: Migrate An Exchange Mailbox to PST

Detailed Description

This How To will provide steps how a Microsoft Exchange Mailbox can be migrated to a PST file using the Simply Migrate Management Shell.
To ensure permissions have been correctly set, please follow the steps outlined in the following article;
Microsoft Office 365 and Microsoft Exchange Permissions

Create Job

To migrate a Microsoft Exchange mailbox to a PST file, the following command syntax can be used.  There are additional options that can be set within a job depending on the version and type of Exchange environment we are accessing.

New-SMJob -Source Exchange -SourceInput user@domain.com -SourceCredential (Get-Credential) -SourceOptions Ex2016 -SourceEwsUrl (Get-SmDefaultO365EwsUrl) -Target PSTFile -TargetOutput "F:\Some_Path\Personal Folders.pst" -MaxPSTSize 5120 -BatchId 1 -Tags "PST Extract"

Lets go through what we just did and break it down.

Source – You can tab through this list to see all supported Technologies that you can export data FROM, we chose Exchange
SourceInput – This is the UPN of the mailbox you wish to migrate the data from.
SourceCredential – These are a set of credentials that has permissions to fetch the data from the source technology.
SourceOptions – Here we have specified the version of Exchange we are coming from.
SourceEwsUrl – Optionally we can specify an EWS URL to connect to Exchange.  In the example above, we have used the Simply Migrate Helper cmdlet for the Office 365 EWS endpoints, but you can manually specify your EWS endpoint.  e.g. ‘https://mail.domain.com/EWS/Exchange.amsx’
Target – You can tab through the supported technologies that you want to migrate data TO, in the above, we have chosen PSTFile.
TargetOutput – This is going to be the path to a PST file you would like to migrate data to.
MaxPSTSize – This sets a maximum PST file size for the target files. It is specified in MB. When a file reaches this size it will be closed off and a new one started with an incrementing number appended to the name.
BatchId – This tells the job to which batch it belongs.
Tags – You can give your jobs nice tags so they are easier to group in the Management User Interface.