Enterprise Vault.cloud™ Legacy Import Guide
Legacy email message assignment FAQ
Question: Which email formats can be imported into Enterprise Vault.cloud?
Answer: Enterprise Vault.cloud supports PST and EML message formats. While NSF and MSG files are also supported, importing of these file types requires conversion, which increases the import time.
Question: What is the preferred email format?
Answer: Veritas prefers that your organization sends your legacy email messages in PST format. PST or NSF format is required for the replication of legacy folder structures.
Question: How does the Veritas data management team ensure that PST files are assigned to the correct Enterprise Vault.cloud account?
Answer: Veritas uses the CSV mapping file that your organization provides to map the PST files to the correct user accounts. The mapping process ensures that all the legacy email messages belonging to a user are assigned to that user account.
Question: How can our organization ensure that interoffice email messages are assigned to the correct Enterprise Vault.cloud account?
Answer: In addition to the CSV mapping file for PST files, Veritas requests that your organization provides us with the common names for all user accounts. With this information Veritas can ensure that all the legacy email messages belonging to a user are assigned to that user account.
Question: What if my legacy PST files are not linked to individual users?
Answer: If import is performed without a CSV mapping file, note the following consequences:
Email messages rely on a sender or a recipient email address or a common name to map correctly to a Enterprise Vault.cloud account.
Email messages where the sender or the recipient email address does not contain the domain name for your organization or a common name are not imported into Enterprise Vault.cloud.
Email messages that cannot be mapped are assigned to the Unassigned Legacy account for the life of the account. Reassignment of messages to a user account cannot be performed.