Google Vault Mapping File Limitation
Handling archives exceeding 100GB during Vault migration.
Last updated: 2025-01-15 Troubleshooting
Overview
Error Message
"Warning: The PST mapping file contains some missing target address entries. It needs to be adjusted manually."
Size Limitations
1GB
Per PST File
Google export chunk
100
Max PST Files
Office 365 limit
100GB
Max Per Pass
Platform threshold
Root Cause
Platform Limitations
- • Google Vault exports generate one PST file per 1GB of data
- • Cloudiway can handle mapping files up to 100GB
- • Office 365 has a hard limit of 100 PST files per migration
- • Archives exceeding 100GB exceed the platform limit
What Happens
For Archives Above 100GB
1
Upload all PST files to Microsoft blob storage in 1GB chunks
2
Populate 100 mapping file entries
3
Leave additional entries without target addresses
4
Display warning message and block upload to prevent failed imports
Solution
Two-Pass Approach for Large Archives
1
First Pass
The first 100GB of data migrates successfully with an auto-generated file
2
Identify Destinations
Identify destination addresses for the remaining data
3
Update Mapping File
Manually fill in target addresses in the mapping file for additional entries
4
Clean Mapping File
Remove any empty lines from the mapping table to ensure validity
5
Restart Migration
Restart the migration for unmigrated data
Complete Migration
This two-pass approach allows complete migration of vault archives exceeding
the 100GB platform threshold.