FAQs: Google Takeout as a Source
This article addresses frequently asked questions regarding the use of Google Takeout as a source platform in CloudM Migrate.
Metadata Support
Q: What metadata is preserved when migrating from a Google Takeout source?
The level of metadata preserved depends on the specific item type being migrated:
- Mail Items: Labels associated with each mail item are supported and migrated. Key metadata fields (Date/Time, To, From, CC) are also preserved.
- Drive Items: Only the File Title and the File Contents are migrated.
Note: Metadata such as permissions and sharing settings will not be included.
File Path Limitations & Orphaned Files
Q: Why are some files migrated to an "Orphaned Files" folder rather than their original directory?
This behavior is a safeguard against file path length limitations:
- The Cause: Due to the specific structure of Google Takeout output files, CloudM Migrate is unable to calculate the full file path length prior to starting the migration.
- The Behavior: If a file path exceeds the destination or OS character limit during migration, CloudM Migrate will move the item to an Orphaned Items folder.
- The Benefit: This process ensures the content is preserved and migrated successfully, rather than failing the item completely due to path length errors.
Supported File Types
Q: What file types are supported?
- We strictly support .mbox files and items contained within .zip archives.
- Any items located outside of these specific formats will not be detected, exported, or migrated.