This article explains what the requirements are for migrating from PST files to a target environment, and then covers the basic steps that should be followed to start such a migration.


The following is a list of requirements.

Modules installed on source

The PST Export module should be installed on an appropriate server.

Modules installed on target

The appropriate modules should be installed on each appropriate target server involved in the migration.

AD Collector module installed

An AD Collector module should be installed so that it can collect user-level information for the migration project.

Staging Area created

One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.

PSTs made available

Ensure that the PST files that are the source for the migration are available in a high speed manner. In other words if they’re on network locations ensure that they are close to the server which is running the PST Export module. If they’re on multiple USB drives ensure as many of those are accessible, or at least the first is accessible ready to start the migration process.

Workflows reviewed

The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project.

Apply appropriate failed item threshold

It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value.

Basic Steps

The following are the basic steps to start this type of migration.

Enable Modules

Screen: Modules
All Archive Shuttle modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (indicating that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected.

Enable Domains

Screen: Active Directory
Select and enable one or more domains for synchronization.

Create PST Link

Screen: Links
Create a PST link, and ensure that ‘Source’ modules are associated with it. The PST Output Path in this case is not used, so any UNC Path can be given.

Create Link Database

Screen: Links
Create a link database for the newly created PST Link.

Add PST Source Folders

Screen: Links
Add one or more source folder locations where the PST files that are to be migrated can be found. It is not necessary to execute the ‘scan’ command. Newly added paths are automatically scanned.

Add Target Links

Screen: Links
Ensure that the link for the migration target is added, and modules associated with it.

Add Staging Area

Screen: Links
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of vault stores being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.

Configure Folder-Less Item Handling

Screen: System Configuration
Many versions of Enterprise Vault allow archiving of items in a folder-less area called the Top Of Information Store. On the System Configuration screen, enter a folder name to be used for placing the items into the target archive.

Associate owner to PST

It is recommended to associate an owner to each discovered PST. If this is not actioned, then the Bulk Mapping page can not be used to migrate the PST, instead the Manual Mapping screen must be used.
Screen: Bulk Mapping
It is easiest to use a filter on the bulk mapping screen to show only PST as a source archive type. If the PST file names match a users samAccountName, then the ownership of that PST will be shown, otherwise many PST files may show as ownerless.

Map one or more Containers

Screen: Map Containers
One or more containers can now be mapped and migration can begin.

General Considerations

The following general considerations should be taken into account for this type of migration:

  • Scanning PST files themselves for items can take considerable time .Exports will not begin for that PST until the scanning is complete.
Print Friendly, PDF & Email