Transvault Migrator 10.3 — Deployment Requirements

Use this guide to prepare your environment for a successful deployment of Transvault Migrator 10.3, including server specs, account permissions, and network configuration.

Updated: February 2025  •  Version: 1.8

Server Requirements

1) Migration Server (per instance)

Additional storage & network:

• ~100 GB for install/logs (e.g., D:\)
• Temporary working folder (e.g., E:\)
• Output storage (if PSTs are used)
• 1× Gigabit NIC minimum

2) SQL Server

Disk space: ~4 GB per 1M messages (larger if using CTM).   Other: 1× Gigabit NIC; dedicate separate drives for SQL data/logs.

Account Requirements

1) Migrator Service Account

• Domain account with Local Admin on Migrator servers.
• SQL access:
  • Initial: sysadmin
  • Then: db_owner, db_datareader, db_datawriter
• Source/Target access as required by the archive platform.
• May also be used as Admin account and for AD/LDAP access.

2) Target Platform Account

• Write access to the target archive (e.g., Microsoft 365, Enterprise Vault).

3) Active Directory Account

• Read access to LDAP/AD (usually the same as the Migrator Service Account).

4) Admin/Client Account

• Optional if not using the Migrator Service Account.
• Requires Local Admin + Remote Login on the server.

Network & Security

External Bandwidth

• Minimum 200 Mbps outbound to ensure smooth migration to Microsoft 365.

Antivirus Exclusions

Exclude these folders:

• C:\ProgramData\Transvault Software\Migrator
• C:\Users\<ServiceUser>\AppData\Local\Temp\TransvaultWorkingFolder
• C:\Program Files\Transvault Software

Exclude this process:

• Server.Core.exe

Firewall & Port Requirements

For configuring DCOM & dynamic RPC ports, see the Microsoft guide.

Archive-Specific Access Requirements

Microsoft Exchange / Microsoft 365

• ApplicationImpersonation role required.
• Throttling configuration recommended (raise limits to Unlimited where appropriate).
• Register OAuth + EWS App in Azure — see: EWS App Setup KB.

Enterprise Vault

• Direct: Read access to Vault Store partitions.
• API: Install EV Runtime (version-specific) + .NET 4.8.
• Write access required when migrating into EV.

NSF / Lotus Notes Archives

• x86 Notes client and a valid Notes user account.
• Access to Domino Directory via LDAP; Internet password set.
• Access to NSF files (ACL reader rights).

EmailXtender

• Close volumes before migration.
• Service account needs read access to volume shares.

CommVault

• Install ContentStore Mailbox Agent.
• Same domain as Migrator; access to REST API port (default 1430).

Cloud Whitelisting

Allow outbound access to:

• *.transvault.com
• Microsoft 365
• Google (if target platform)