Univik Enterprise Vault Converter

Yes. EV journal archives contain the original journal envelope for each message — a wrapper holding BCC recipients and original SMTP routing data that is not visible in standard email headers. Univik Enterprise Vault Converter detects journal archive PSTs and preserves this envelope data in all output formats. For PDF output the journal envelope fields appear in document properties. For EML output they appear as RFC-compliant headers. This BCC and SMTP data is typically required for regulatory productions under SEC Rule 17a-4, CFTC and MiFID II.

Every EV Administration Console export task generates an ExportTask log file alongside the PST output. This log lists every message exported, any items skipped due to vault partition errors, and a count of successfully resolved shortcuts. Univik Enterprise Vault Converter reads this log and cross-references it with the converted output to identify any gaps in completeness. The final conversion report shows you exactly which items from the log were converted, which were skipped in EV and whether any fell through in conversion. Essential for compliance documentation during EV decommissioning projects.

Yes, completely offline. Once you have copied the PST files and export log from the EV server output folder to your local machine, the converter requires no EV server, no EV client software, no Vault Administrator credentials and no network connection. This is particularly important when EV is being decommissioned — the server may be offline before the migration is complete.

Yes. EV Search (the web-based discovery interface) produces the same PST output format as the Administration Console export. The converter handles PSTs from both export routes. If EV Search produced per-custodian PST files, the converter processes each one independently preserving per-user folder structure and journal envelopes.

Minimal requirements:

• OS: Windows 11, 10, 8.1, 8 or 7
• RAM: 4 GB minimum (8 GB recommended for large EV archive batches)
• Disk: 50 MB installation plus space for output files
• Framework: .NET Framework 4.8 or higher

No Enterprise Vault client, Outlook or EV Administration Console required on the conversion machine.

Yes — this is one of the most common EV migration use cases. Convert each per-user EV PST to MBOX format. The MBOX output imports directly into Google Workspace using Google's migration tools or third-party tools like BitTitan or AvePoint. One MBOX per PST maps cleanly to one Google Workspace mailbox. Journal envelope BCC data is preserved in MBOX X-headers.

Free trial converts the first 25 emails per PST file. All features fully functional: journal envelope handling, EV export log reading, all 10+ output formats, preview and date filtering. No time limit. Verify journal envelope handling and folder structure preservation before purchasing ($29 personal, $99 business).

Admin Console steps: (1) Open the EV Administration Console, (2) Expand the Vault Store and click Mailbox Archives, (3) Right-click the target archive and select Export, (4) In the wizard enable Resolve Shortcuts and Preserve Journal Envelopes, (5) Set the output path to a UNC share accessible by the EV service account, (6) Click Finish and monitor under Tasks, (7) When complete, copy the PST and log from the output folder. See the full guide at How to Export from Veritas Enterprise Vault.

Yes. EV PSTs sometimes have structural anomalies that cause scanpst.exe errors and Outlook import failures. Univik Enterprise Vault Converter reads the PST content directly, bypassing Outlook's import mechanism. Genuinely corrupted messages are flagged in the conversion report while all intact content is extracted successfully.