How to Resolve “PST file corruption” during Import

A “PST file corruption” error during a Google Workspace migration means the Google Workspace Migration for Microsoft Outlook (GWMMO) tool or GWMME server has hit unreadable data sectors inside your local Outlook data file. This happens when the internal index system of the .pst file breaks down, stopping the Google migration engine from parsing emails, calendar events, or contacts. To fix this immediately, stop the migration tool and run the Microsoft Inbox Repair tool (scanpst.exe) against the target file to rebuild its internal folder architecture before restarting the import.

Fast-Fix: The 45-Second Solution

Run Microsoft’s built-in Inbox Repair tool (scanpst.exe) to rebuild the damaged data file’s internal index tables. If the file size exceeds 50GB, split the archive into smaller segments before running the Google Workspace migration utility again.

Quick Risk Snapshot

• Severity: High (Completely halts data ingestion for the affected user mailbox).
• Safe to Proceed?: No (Forcing a broken file through the tool results in massive data omission or immediate tool crashes).
• Primary Cause: Broken database index tables within the PST file, usually caused by sudden power cuts, network drops during file transfers, or file size inflation.
• Rare Cause: Local hardware failures, such as failing storage drive sectors or memory bit flips during a large compression export.

Low Risk vs. High Risk Paths

• Low Risk Path (Minor Index Errors): If the data file opens natively inside Microsoft Outlook but throws errors only during the Google migration pass, the corruption is localized to unread message indices. Running a single pass of scanpst.exe will generally repair the alignment.
• High Risk Path (File Size Blowouts & Total Lockouts): If the PST file approaches or exceeds the 50GB size threshold, or if it sits on a network share during the migration, the risk of unrecoverable data loss drops sharply. For file size threshold errors, refer to “0x800411c” PST File Size Limit Errors.

How PST Internal Storage Works

Think of a PST file as a massive warehouse filled with thousands of numbered storage boxes. The file has an index at the very front, like a master clipboard log, that tells Outlook exactly which shelf holds which box. When you run a migration, the Google utility reads this clipboard log to copy items sequentially.

If a network connection drops while writing to the archive, or if Outlook closes unexpectedly, the log gets out of sync with the actual boxes on the shelves. The Google tool arrives at a designated shelf location, finds unexpected data or a blank spot, and halts the entire migration run to prevent corrupted records from uploading to the cloud.

Probability Breakdown

• Damaged or Desynchronized Internal Index (60% probability): The file structure is mostly intact, but the pointer references are broken.
• Oversized Data Payload (25% probability): The file has grown past Outlook’s natural stability limits, causing the lower database blocks to overlap or degrade.
• Network Interruption Corruptions (10% probability): The PST was copied or moved over a weak Wi-Fi connection, leaving the trailing bytes of the file incomplete.
• Bad Hardware Sectors (5% probability): Physical storage drive degradation has corrupted the localized system blocks where the file resides.

What Increases the Risk

• Storing PST Files on Network Shares: Running a migration against a PST file hosted on a network drive or a live sync folder (like OneDrive or Dropbox) causes constant file-locking conflicts that break database integrity.
• Antivirus Scanning: Aggressive local security software that locks files during active read/write passes can disrupt the migration tool’s access mid-stream.
• Legacy Tool Chain Execution: Running the migration engine on a machine using outdated Windows updates or older, unpatched Office installations can trigger profile instabilities. For modern authentication handshake hangs, see “GWMMO stuck at 0%” (Modern Auth Handshake).

Consequence Timeline

• 24 Hours: Individual user migration schedules fail. The user remains stuck without access to historical records inside their new Google account.
• 1 Week: Local archive backlogs build up. Manual recovery efforts drag down IT personnel, delaying tenant-wide implementation goals.
• 1 Month: Risk of data permanence failure. Uncorrected files left sitting on degraded storage risk total structural collapse, rendering historical corporate data completely unrecoverable.

What This Is Confused With

This issue is frequently mistaken for other migration blockages. It is distinct from a profile mismatch where the tool cannot hook into the mail application layout, which is covered in “0x8004011c” Profile Mismatch in Migration Tool. It is also separate from systemic infrastructure blocks like registry throttling or connection interruptions, which can be reviewed at “Network timeout” (GWMMO Registry Throttling).

What To Do Right Now

Locate the damaged PST file on the local disk. Do not make any repairs directly to this file. Make a copy of the .pst file, paste it into a separate, isolated backup directory on your local solid-state drive, and label it Backup_Migration_Date.pst. All diagnostic and recovery passes must be performed exclusively on this copy to preserve the original raw data.

Hard-Stop Triggers

• Stop immediately if scanpst.exe crashes continuously or if it alerts you that the file structure is unreadable by the underlying application.
• Cease troubleshooting if the local drive throws S.M.A.R.T. hardware failure notices or clicking sounds. This points to immediate physical disk failure.

What an Admin Will Check

To completely resolve the file corruption, follow these step-by-step diagnostic actions:

1. Execute the Inbox Repair Tool

Locate the scanpst.exe utility on the machine. Its location depends on your version of Office:

• Click-to-Run (64-bit Office): C:\Program Files\Microsoft Office\root\Office16\
• Click-to-Run (32-bit Office): C:\Program Files (x86)\Microsoft Office\root\Office16\

Launch the utility, browse to your copied PST file, and click Start. The tool will analyze the structural blocks and folder structures. If errors are found, click Repair.

2. Monitor Log Reports

Open the generated log file located in the same directory as the PST file to see which items were dropped or repaired.

3. Check Data Integrity within Outlook

Mount the newly repaired file inside a local Outlook profile to confirm that the folder hierarchy expands smoothly and that older items open without throwing data errors.

Typical Effort Range

• Complexity: Low to Moderate.
• Time Required: 30 minutes to 3 hours, depending entirely on the total file size and the performance speed of the local drive storage.
• Tools Needed: Local administrative access, Microsoft Office’s native scanpst.exe engine, and sufficient free storage space to hold the duplicated backup file.

Related System Escalators

If your migration tool errors out due to access privileges rather than structural corruption inside the file, read the access validation steps found at “0x80070005” Access Denied during GWMMO.

Workspace Assessment

Always run repairs on an independent copy of your archive files rather than the live primary source. Running scanpst.exe resolves the vast majority of indexing and pointer issues, allowing the Google Workspace migration utility to smoothly process and upload your historical mail archives without data loss.