Use this guide to prepare your environment for a successful deployment of Transvault Migrator 10.3. This includes server specs, account permissions, and network configuration details.
📅 Updated: February 2025
📦 Version: 1.8
✅ Server Requirements
🖥️ 1. Migration Server (per instance)
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| CPU | 4 cores | 8 cores | |
| RAM | 8 GB | 16 GB | More may be needed for large volumes |
| OS | Windows Server 2016 | Windows Server 2019+ | Server Core not supported |
| Outlook | 2016 (x86 or x64) | 2016 or later | x86 required for Notes and SourceOne (API-based) |
| .NET Framework | 4.8 | 4.8+ | Download |
| Visual C++ Runtime | 2015 | 2015+ | Download |
| Lotus Notes (if needed) | 8.5 x86 | 9 x86 | For NSF migrations; install in single-user mode |
Additional Storage:
- 100 GB for install/logs (e.g. D:)
- Temp working folder (e.g. E:)
- Output storage (if PSTs used)
- 1x Gigabit NIC minimum
🗃️ 2. SQL Server
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| CPU | 4 cores | 8 cores | |
| RAM | 8 GB | 16 GB | |
| OS | Windows Server 2016 | Windows Server 2019+ | |
| SQL Version | SQL Server 2016 | SQL Server 2019+ | Standard/Enterprise only, CI collation required |
Disk Space: ~4 GB per 1M messages (larger for CTM feature)
Other: 1x Gigabit NIC, dedicated drives for SQL data/logs
👤 Account Requirements
🔐 1. Migrator Service Account
- Domain account with Local Admin rights on Migrator servers
- SQL access:
- Initially:
sysadmin - Then:
db_owner,db_datareader,db_datawriter - Source/Target Access as per archive platform (see below)
- Can also be used as Admin account and for AD/LDAP access
🎯 2. Target Platform Account
- Must have 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\MigratorC:\Users\<ServiceUser>\AppData\Local\Temp\TransvaultWorkingFolderC:\Program Files\Transvault Software
Exclude this process:
Server.Core.exe
👉 Disable Windows Defender for best performance.
🔥 Firewall & Port Requirements
| Purpose | Port(s) | Notes |
|---|---|---|
| SQL access | 1433, 1434 | SQL communication |
| LDAP | 389 (or 636 SSL) | AD/LDAP access |
| Exchange EWS | 80/443 | Required for Exchange Online |
| Transvault Remoting API | 1829 | Client-to-server communication |
| Config Service | 10101 | Inter-server coordination |
| Licensing | 8301, 8222 | Licensing operations |
| Toolbox | 443, 8125, 8301, 8840 | Used for Insight and Toolbox |
| Retrieval Agent | 8300 | Only for Azure deployments |
🔗 For configuring DCOM & dynamic RPC ports:
Microsoft Guide
📦 Archive-Specific Access Requirements
Microsoft Exchange / Microsoft 365
- ApplicationImpersonation role required
- Throttling config recommended (set limits to Unlimited)
- OAuth + EWS App must be registered in Azure
EWS App Setup KB
Enterprise Vault
- Direct: Read access to Vault Store partitions
- API: Install EV Runtime (version-specific) + .NET 4.8
- Write access needed when migrating into EV
NSF / Lotus Notes Archives
- Notes client (x86) and valid user account with:
- 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
Whitelist outbound access to:
*.transvault.com- Microsoft 365
- Google (if target platform)
Comments