Exchange Migrator per Import and per Session Import options and CSVHeaders options

The Exchange Migrator has two types of Import options that can be set through the Import GUI.

  • Per Import options are the options that can be set different on every PST or Mailbox your importing
  • Per Session option are options that affect all the PST’s or Mailboxes your importing in the session

Considerations for CSV imports

If you are using a CSV file to populate the import queue and you want to configure any of the per Import options that you need to configure these setting using the appropriate CSV header. Per session options aren’t affected by CSVHeaders.

Per Import Options

Folder Destination options


This setting controls the destination location of the Import, The CSV header for this option is “Usepstrootname” If true a subfolder will be created to import into otherwise false mailbox root will be used.


This setting controls whether address rewriting is used. Address rewriting will rewrite the Native Exchange email address format (for example EX: /o=First Organization/ou=first administrative group/cn=Recipients/cn=UserName’) which are only valid in the source Exchange organization to the SMTP address for the address entry if it can found within other message properties or resolved by looking at the Global Address List based on the Display Name of the recipient. Note because this is an automated processes exact address matching can never be 100% assured if GAL resolution is used and more than 1 contact has the same display name. The CSV header for this option is “Useaddressrewrite” if true Address rewriting will be used (enabled by default).


This setting controls whether the Deleted Items are included in the Import, The CSV header for this option is “Dontimportdeleteditems” if true deleted Items will not be imported.


Folder filtering allows you to specify the folders you want included in the Import, The CSV header for this option is “includefolders” it contains the folders to Include in the import separated with a semicolon “;” eg \Inbox;\SendItems;\Contacts. The other CSV header for this option is “includesubfolders” if true the subfolders of the include folder will be included as well.


Exclude Folders contains the folders to exclude from the Import.  The CSV header for this is “excludefolders” contains folders to exclude for the export separated with a semicolon “;” eg \Inbox;\SendItems;\Contacts. The other CSV header for this option is “excludesubfolders”  if true the subfolders of the exclude folder will be excluded as well.

Per Session


This setting controls the handling of the duplicates in the Import session, the default option uses the PSTEntryid which is unique to the PST being imported. The PSTid option should be used if you are importing a static set of PST files using the Exchange Migrator. This will prevent duplicates if the exact same PST file is imported multiple times into the same mailbox. Note, exporting a mailbox more than 1 time to different PSTs will result in duplicates if this option is selected.

The SourceKey option uses 3 different keys for duplicate detection. It first tries the PSTid, then it uses the SourceKey and then the SearchKey. The SourceKey and SearchKey should be same on multiple copies of an the Item, so if this is used it shouldn’t import a message if it finds a match for either of these three keys. This should prevent duplicates in the instance where an aborted Outlook import has been performed and you want to use the Migrator.


This option will enable the use of MAPI as well as EWS when uploading, using MAPI can be helpful if you’re having problems with Throttling. However this will not strictly increase the performance of the Import and depending on the structure of Items being import using EWS only can yield better performance.


This option will mean that during MAPI profile creation the Autodiscover will run directly against the Office365 endpoint rather than using the convention DNS lookup. This option should be used when having problems with the MAPI profile creation.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section