This article describes the item and user level metadata stored in Archive Shuttle databases.


Knowing the metadata stored by Archive Shuttle can help with security/legal audits, particularly in regions where identifiable, personal data cannot leave that region.
Data stored by Archive Shuttle relates to these aspects of a migration:

  • Users
  • Archives/Containers
  • Items

Each of these objects has a number of attributes, as shown below:


  • First name, last name, display name, and title of each user (from Active Directory)
  • The user SID
  • The email and SMTP address of the user
  • The domain and AD container where the user object is located
  • User GUID, samAcctName, DN, and UPN
  • Geographical information, including street address, state, office name, company name, department, and country
  • Whether the user is enabled
  • The dates the user was created, updated, and deleted

Note: Archive Shuttle collects and stores metadata from Active Directory. If you have concerns about this data, enable the Do not transmit non-essential Active Directory information option in the system configuration. With the option enabled, bold items above are not collected.


  • Archive Name (from the Enterprise Vault Directory Database)
  • Archive Description (from the Enterprise Vault Directory Database)
  • The Vault Store that a source or target Archive is stored on
  • The owning user SID
  • The Archive ID (from the Enterprise Vault Directory Database)
  • The number of items in the archive, and the overall size
  • Mailbox name and Exchange Server name


  • Source transaction ID
  • Original Size
  • Compressed Size
  • Target Transaction ID (in the case of a migration to Enterprise Vault)
  • Target SaveSet ID (in the case of a migration to Enterprise Vault)
  • Target Entry ID (in the case of a migration to Microsoft Exchange)

Note: No identifiable data, such as subject lines, or content of emails / archived items are stored in any of the Archive Shuttle databases.
As an additional note for Archive Shuttle Cloud customers, no migration content will pass through from the modules/staging-area to the cloud. No data leaves the customer network perimeter.
A non-disclosure agreement is available upon request.

Print Friendly, PDF & Email