How to Connect and Migrate from Lotus / Domino (Lotus Notes) to Jatheon

This guide explains how to connect Lotus Domino to Jatheon for both live journaling and legacy migration. It covers prerequisites, configuring Domino journaling via SMTP, setting up the Jatheon journaling connector, preparing legacy data (NSF/PST/EML/MBOX), user identity mapping, and planning delta/cutover.

Prerequisites

• Admin access to Lotus Domino (Domino Directory).
• Ability to configure Mail Journaling and SMTP forwarding.
• External SMTP journaling address provided by Jatheon (journaling connector endpoint).
• For legacy migration: access to NSF files or tools to export to EML/PST/MBOX.
• Plan for user identity mapping (Lotus IDs → Jatheon users).

Step 1: Enable and Configure Mail Journaling in Domino

In Domino Directory go to Configuration → Messaging → Configurations and set up Mail Journaling so that all inbound, outbound, and internal messages are journaled.

• Choose journaling to a database or to a third-party SMTP address.
• If using SMTP journaling (recommended for Jatheon), define the external recipient as the Jatheon journaling address.

Step 2: Configure SMTP Forwarding to Jatheon

Configure Domino to send journaled messages via SMTP to the Jatheon journaling connector (external address provided by Jatheon).

• Allow outbound SMTP to Jatheon (network/firewall).
• Set up TLS if required and make sure Jatheon is allow-listed (no spam filtering).
• Verify the connector accepts messages from your Domino servers.

Step 3: Prepare Legacy Data (NSF or Export)

For historical mailboxes (legacy migration), prepare content for ingestion into Jatheon:

• Provide original NSF files or
• Export mail to EML/PST/MBOX using third-party tools .

Step 4: Map User Identities (Lotus IDs → Jatheon Users)

Create or verify user accounts in Jatheon so that each historical mailbox maps to the correct user identity. Use consistent primary addresses or aliases to maintain legal chain-of-custody and accurate ownership.

Step 5: Plan Delta / Cutover

Perform a bulk legacy import first (NSF or exported files), then schedule the journaling cutover so that all new messages flow to Jatheon in real time via SMTP journaling.

Step 6: Test and Validate

Send test messages (internal, inbound, outbound) and confirm they appear in Jatheon with correct headers, recipients and timestamps. Resolve any SMTP/TLS/allow-listing issues before cutover.

Step 7: Monitor Jobs and Status

During legacy import and after cutover, monitor tasks/status in Jatheon (job completion, counts, failures). Re-run or remediate any failed batches as needed.

Summary

• Live journaling: Domino journaling rule + SMTP connector to Jatheon.
• Legacy migration: Provide NSF files or export to EML/PST/MBOX via migration tools.
• Users: Map Lotus IDs to Jatheon user accounts to preserve ownership.