How to Migrate from Veritas Enterprise Vault for Notes to Jatheon Cloud

This guide outlines the end-to-end process for migrating archived e-mail and chat data from Veritas Enterprise Vault for Notes (Domino) to Jatheon Cloud using the Ultimate Migrator (UM) toolset — including prerequisites, discovery, migration planning, execution, and validation.

Before You Begin

• Access & Authorization
  • EV Administrator/Service account with access to Vault Store DB and indexes.
  • Domino/Notes access (ACL) to referenced mail/Journal NSF where applicable.
  • Jatheon Cloud ingest/journaling address allow-listed (TLS endpoints).
• Scope & Inventory
  • Inventory of Vault Stores (users, journal, date ranges, item counts, total volume).
  • Retention policies / legal hold mapping for the target archive.
  • SMTP alias history and timezone considerations documented.
• Environment & Windows Hosts
  • UM Central (IIS + SQL) host available; at least one UM Remote Agent (RA).
  • RA has CPU/RAM per guidelines and local disk for logs/temp.
  • Firewall/Proxy rules for EV endpoints, Domino, SQL and Jatheon ingest verified.

Prerequisites

• UM Central Application (IIS + SQL) installed and reachable.
• UM Remote Agent(s) installed with multi-threading enabled.
• Source access — EV admin/service credentials; Domino ACL where needed.
• Destination access — Jatheon ingest/journaling address configured & allow-listed.
• Connectivity — RAs can reach EV databases/indexes and Jatheon ingest over TLS.

About the Tooling

Ultimate Migrator uses a distributed architecture: the Central Application orchestrates schedules and logging, while Remote Agents perform extraction from EV for Notes and direct ingest to Jatheon Cloud. Message content and metadata (headers, timestamps, folders, attachments, legal hold flags) are preserved end-to-end. Items are streamed directly (in-memory) from source to destination with chain-of-custody logging.

Process Overview

1. Preparation — confirm data flows, roles, access, and system prerequisites.
2. Installation & Discovery — deploy UM components, connect to EV for Notes, build inventory, run a controlled pilot to baseline throughput, and produce the discovery report.
3. Migration — agree batching, pre/delta runs, scheduling windows, monitoring/reporting cadence; execute and track to completion with acceptance criteria.

Installation & Discovery (What We Do)

• Install/verify UM Management Console, SQL database, and Remote Agents.
• Configure connections to EV Vault Stores/Indexes and test endpoint access.
• Scan the source archive to inventory volume & item counts; run a pilot migration to measure throughput and identify bottlenecks.
• Deliver a discovery report (data volume, counts, and recommendations) and an estimated timeline based on measured throughput.

Migration Plan & Execution

After discovery sign-off, we agree the migration plan (scope, batching, pre/delta runs, scheduling, milestones, reporting, and comms) and initiate the production runs. UM Remote Agents move items directly from EV for Notes to Jatheon Cloud while live dashboards and logs provide status and exception handling.

Data Fidelity & Compliance

• No content is stored on the Central/DB; items are passed unaltered with headers, timestamps, senders/recipients, content and attachments preserved.
• Comprehensive item-level logging supports audit and chain-of-custody requirements.
• Original Notes/EV foldering and metadata are retained where applicable.

Roles & Responsibilities

• Customer — confirm data flows, ensure prerequisites are met, provide required access, attend installation sessions, and review discovery findings.
• UM/Jatheon — install/verify components, run discovery and pilot extraction, produce reporting, tune for throughput, execute and monitor migration per plan.

Performance Considerations

Throughput depends on source/destination throttling, network and storage. Adding RA threads/agents helps up to external throttling limits. Discovery pilot runs are used to baseline and tune before bulk runs.

Troubleshooting

• Connectivity issues — verify EV SQL, Domino ports, and firewall/proxy rules (including TLS to Jatheon ingest).
• Slow/variable throughput — check source throttling, storage IOPS, and RA thread counts; adjust batches/schedule.
• Permission denied — confirm EV service account rights and Domino ACL access.

Completion & Handover

The migration phase is complete when all in-scope data is processed, validated against plan, and accepted by the customer. Final summary reporting is delivered; software/services are removed from customer assets after sign-off.