This guide provides basic configuration steps for migrating from PST Archives. Review the full application documentation for your specific source and destination platforms to understand all available migration options.
Prerequisites
- CloudM Migrate Self Hosted: This migration path is supported on self-hosted installations only.
- File Access: The workstation or server running CloudM Migrate must have read/write access to the file paths where the PST files are located.
-
Mapped Network Drives: If PST files are stored on network shares, you must ensure the CloudM Migrate service account has permissions to access these locations. Refer to Configuring Mapped Network Drives for setup instructions.
- Multi-server environments: Mapped network drives must be configured and accessible across the entire infrastructure (primary and all secondary machines).
Configuration
Specify the path to the PST archive for each user in the Archive Path field of the Items to migrate list.
To migrate multiple PST files to a single user account, enter multiple paths separated by a semi-colon.
C:\PST\User1a.pst;C:\PST\User1b.pst
Troubleshooting: Migration or Scan fails to start
If an Environment Scan or Migration task results in no progress or "0 items processed," the source PST files may be corrupted or locked. CloudM Migrate requires the PST structure to be valid to initialize the session.
To resolve this, repair the PST files using the Microsoft Inbox Repair tool (ScanPST.exe):
- Locate ScanPST.exe on the migration machine (typically found in the Microsoft Office installation directory).
- Run the application and select the source PST file.
- Select Start to begin the analysis.
- Whether errors are found or not (recommended), select Repair.
- Once the repair is complete, restart the migration or environment scan in CloudM Migrate.