Chat now with support
Chat with Support

Migration Manager for PSTs Enterprise Edition 7.2 - Administrator Guide


Pre-ingestion modules are those that are configured to run prior to the ingestion module. Sometimes referred to as the “pre-flight checks,” pre-ingestion modules are designed to prepare and safeguard PST data for ingestion into a desired target. The following table discusses the pre-ingestion modules available for enablement.

Local Upload

Checks if the PST file is present in the BITS upload location


Moves ownerless files to an alternate storage location until ownership is defined


Copies a PST file to a designated location until operator deletion


Executes the Outlook SCANPST repair utility against files identified as corrupted


Filters and extracts PST files to disk to enable streamlined processing and delivery to the target


Reviews the PST file content to identify duplicated messages and removes them

In most configurations, Extraction and Repair modules should be local to the Uploads directory frequently configured on the Core server.


Ingestion modules are typically chosen at the point of installation. These are the modules responsible for the Migration Manager for PSTs actions taken to ingest a PST file’s contents into the desired target. As the first item ingesting successfully completes, the migrated content should be immediately available in the target system. Once a PST file has been successfully ingested or ingestion of the file is not required, Migration Manager for PSTs considers the file as “completed.”

Rate of ingestion is frequently a point of bottleneck in a migration and can be monitored in the Management Console, Admin Console, or via the Migration Manager for PSTs Portal. Tuning an ingestion for performance requires the Migration Manager for PSTs Admin Console and an account with sufficient rights. The net ingestion rate may be constrained by limitations of the environment and increasing its work capabilities may result in a decrease of performance. In general, ingestion tuning is performed while closely monitoring the entire environment and until a suitable rate has been achieved or a resource is excessively constrained. If resource constraint occurs, the last known good configuration should be evaluated for resource constraint and selected as the "best tuned" configuration at that point in time.


Migration Manager for PSTs still has some wrapping up to do after the ingestion has completed for a file. Post-ingestion modules are those modules that are responsible for the tasks necessary to clean up after a file has been migrated. The following table discusses the post-ingestion modules available for enablement.

Legacy Viewer

Provides a web-based view into the original PST file contents and structure


Removes processed content from the BITS upload directory

Source File Remover

Queues request for Agents to delete the original file in its original location


Permits the execution of PowerShell scripts as part of the workflow of a PST file. PowerShell scripts can be also be used in the pre-ingestion workflow.

Migration Agents

Migration Manager for PSTs leverages a component installed on end-user Windows workstations called the Migration Agent. This agent is critical for discovering PST files, providing meta-data to help determine PST file ownership, managing the user interaction with the migration process, and uploading PST files to a centralized location throughout a migration project. The Migration Agent has a lightweight footprint and is supported on many client operating systems. The Windows version of the Migration Agent has 64 and 32-bit versions. The version of agent that will be installed will coincide with the architecture of Outlook that is installed.

Related Documents