4 September 2026, 01:54 PM
I’m preparing to move some old Outlook PST archives into Google Workspace, but a few of the files may be corrupted or partially unreadable. I’m trying to figure out what should be checked before starting the actual migration because I’d rather identify problems at the beginning than discover missing emails or attachments after everything has been transferred.
One thing I think is important is validating the PST files before migration. A file that cannot be read properly could potentially cause incomplete results, so having a tool that detects corrupted or unreadable files during the loading stage would be useful. I’ve been looking at DRS Softech’s PST migration solution for this reason. It reportedly checks PST files while they are being loaded and displays an error when a file has corruption or cannot be read.
Another thing I would check is the actual mailbox content before exporting. DRS Softech provides a preview panel where you can browse the folder hierarchy, search emails, and open individual messages. The preview can show details such as email content, attachments, contacts, calendars, tasks, headers, and raw HTML. That seems helpful for comparing what is actually present in the PST before migration.
I’d also want to avoid blindly transferring years of unnecessary data. The software has a Date Range Filter, so specific start and end dates can be selected. It also includes duplicate detection, with criteria such as To, From, Subject, CC, and Body, which could be useful when several backup PSTs contain overlapping emails.
For the actual transfer, I came across the DRS PST to Gmail migration tool as an option for moving Outlook data into Google Workspace. It supports individual PST files, complete folders, or drag-and-drop loading. For organizations, authentication can be performed using a Google Workspace Admin account and Service Account JSON key, followed by selecting the required Workspace users.
I’m interested in hearing from admins who have dealt with damaged PST archives. What do you normally check first—PST readability, folder structure, attachments, duplicate messages, or date ranges? And if you’ve had to import PST to Google Workspace from older archives, did you test the files individually before starting the full migration?
I’d especially appreciate practical advice on preventing incomplete migrations when the source PST files are old or potentially corrupted.
One thing I think is important is validating the PST files before migration. A file that cannot be read properly could potentially cause incomplete results, so having a tool that detects corrupted or unreadable files during the loading stage would be useful. I’ve been looking at DRS Softech’s PST migration solution for this reason. It reportedly checks PST files while they are being loaded and displays an error when a file has corruption or cannot be read.
Another thing I would check is the actual mailbox content before exporting. DRS Softech provides a preview panel where you can browse the folder hierarchy, search emails, and open individual messages. The preview can show details such as email content, attachments, contacts, calendars, tasks, headers, and raw HTML. That seems helpful for comparing what is actually present in the PST before migration.
I’d also want to avoid blindly transferring years of unnecessary data. The software has a Date Range Filter, so specific start and end dates can be selected. It also includes duplicate detection, with criteria such as To, From, Subject, CC, and Body, which could be useful when several backup PSTs contain overlapping emails.
For the actual transfer, I came across the DRS PST to Gmail migration tool as an option for moving Outlook data into Google Workspace. It supports individual PST files, complete folders, or drag-and-drop loading. For organizations, authentication can be performed using a Google Workspace Admin account and Service Account JSON key, followed by selecting the required Workspace users.
I’m interested in hearing from admins who have dealt with damaged PST archives. What do you normally check first—PST readability, folder structure, attachments, duplicate messages, or date ranges? And if you’ve had to import PST to Google Workspace from older archives, did you test the files individually before starting the full migration?
I’d especially appreciate practical advice on preventing incomplete migrations when the source PST files are old or potentially corrupted.