Skip to main content
  1. CloudM
  2. Archive
  3. Overview

CloudM Archive: Supported Features and Exclusions

Updated

CloudM Archive is designed to support the archiving of specific data types to ensure efficient and relevant data retention. This article details the supported features, licensing requirements, and known exclusions.

Google Workspace Data Support

CloudM Archive supports the archiving and restoring of Mail, Google Drive, and Google Chat data. Note that Google Chat (via Google Chat API) is supported for standard Archive, but is currently not supported for Archive Vault.

Entity Supported Features Unsupported / Exclusions
Mail
  • All active user emails and associated data.
  • Google Vault: Archives deleted data retained in Vault.
  
Drive
  • All active files and folders owned by the user.
  • Google Vault: Archives deleted data retained in Vault.
  • Shortcuts and Non-owned items (including Shared Drive files).
  • Google Sites, My Maps, Jamboard, and Photos.
Chat
  • Google Chat: Direct Messages (1-on-1 and Multi-member).
  • Text, Links, Emojis, Reactions, and Attached Drive files.
  • Images, GIFs, and Voice/Video recordings.
  • Metadata (Member names, Date/Time stamps).
  • Legacy Hangouts: Restoration of previously archived data remains supported (restored as Mail items).
  • Archive Vault: Google Chat is not supported in Vault archiving.
  • Google Hangouts: Archiving of new/legacy Hangouts data is removed (deprecated by Google).
  • Spaces and Apps.
  • Edit history (final state only) and Text styling.
  • Calendar invites and Google Meet links.

User Status & Licensing

CloudM Archive supports specific licensing workflows and user states to facilitate offboarding:

  • Archive users with an AU License
    The Archive workflow successfully processes users who already hold an Archive User (AU) license. You do not need to temporarily assign a full Google Workspace license to these users; previously, this scenario would result in a skipped step and failure.
  • Archive Suspended Users (Available on Request)
    It is possible to archive suspended users as part of an offboarding workflow or on an ad-hoc basis.
    Note: This feature requires backend configuration. Please submit a request to support.cloudm.io to enable this for your environment.

Related Articles

Was this article helpful?
0 out of 0 found this helpful