How to Migrate from Global Relay to Jatheon Cloud

This guide outlines the end-to-end process for migrating archived email data from Global Relay into Jatheon Cloud using the Ultimate Migrator toolset (UM) — including prerequisites, discovery, migration planning, execution, and validation.

Before You Begin

• Access & Authorization
  • Global Relay admin/service account with export rights (SFTP/API as applicable).
  • Jatheon Cloud ingest/journaling address configured and allow-listed.
• Tooling
  • UM Central Application installed (IIS + SQL) and reachable.
  • At least one UM Remote Agent (RA) installed with multi-threading enabled.
  • RA has sufficient local disk for logs/temp and meets CPU/RAM guidelines.
• Connectivity
  • RA can reach Global Relay export endpoints (DNS/ports/firewall/proxy verified).
  • RA can reach Jatheon ingest endpoints; TLS/allow-lists confirmed.
  • Outbound bandwidth window agreed (note: external throttling may cap throughput).
• Data Scope & Policy Mapping
  • Inventory ready (users/journal split, item counts, date ranges).
  • Retention & legal hold mapping defined for the target archive.
  • Timezone and SMTP alias history considerations noted.
• Pilot & Acceptance
  • Pilot slice chosen (e.g., 10–20 users or 30–60 days of journal).
  • Success criteria set (counts, hash/COC checks, random sampling in Jatheon).
  • Reporting cadence and points-of-contact agreed.

Prerequisites

• UM components available — Central Application (IIS + SQL) for scheduling/management and one or more Remote Agents (RAs) to perform extraction/ingest. The console stores settings/logs only; message data does not pass through it. RAs perform the “heavy lifting” and can run multi-threaded. :contentReference[oaicite:0]{index=0} :contentReference[oaicite:1]{index=1}
• Source access — a Global Relay administrator/service account with rights to export/archive data as per your contract, and network access to Global Relay export endpoints (SFTP/API) as applicable. (Confirm with your Global Relay rep.)
• Destination access — journaling/ingest addresses and policies configured in Jatheon Cloud, plus any required allow-listing.
• Connectivity — firewalls/load balancers tuned to allow UM RAs to reach source and destination; note that many sources/destinations impose throttling, so adding threads may not always increase throughput. :contentReference[oaicite:2]{index=2}

About the Tooling

Ultimate Migrator is designed for distributed operation (Central Application + Remote Agents). It automates discovery, extraction, and ingestion with robust logging and error handling. Global Relay is a supported source; data moves directly from source to destination, held only in memory (no intermediary staging), with security and chain-of-custody controls. :contentReference[oaicite:3]{index=3}

Process Overview

1. Preparation — confirm data flows, roles, access, and system prerequisites; schedule installation. :contentReference[oaicite:4]{index=4}
2. Installation & Discovery — deploy UM components, connect to Global Relay, build inventory (message counts/volume), run a controlled test to baseline throughput, and produce the discovery report. :contentReference[oaicite:5]{index=5}
3. Migration — agree batching, pre-/delta runs, scheduling windows, monitoring and reporting cadence; execute and track to completion with acceptance criteria. :contentReference[oaicite:6]{index=6}

Installation & Discovery (What We Do)

• Install/verify UM Management Console, SQL database, and Remote Agents. :contentReference[oaicite:7]{index=7}
• Configure connection to Global Relay and test endpoint access (all connections working and unrestricted). :contentReference[oaicite:8]{index=8}
• Scan the source archive to inventory volume and message counts; run a test migration to measure throughput and identify bottlenecks. :contentReference[oaicite:9]{index=9}
• Deliver a discovery report (data volume, item counts, and recommendations) and an estimated timeline based on measured throughput. :contentReference[oaicite:10]{index=10}

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 messages directly from Global Relay to the target, while monitoring screens and reports provide live status and exception handling. :contentReference[oaicite:11]{index=11} :contentReference[oaicite:12]{index=12}

Data Fidelity & Compliance

• No message content is stored on the Central Application/DB; items are passed unaltered from source to destination with headers, timestamps, senders/recipients, content, and attachments preserved. :contentReference[oaicite:13]{index=13}
• Comprehensive logging at the archive-item level supports audit and chain-of-custody requirements. :contentReference[oaicite:14]{index=14}

Roles & Responsibilities

• Customer — confirm data flows, ensure prerequisites are met, provide required access, attend installation sessions, and review discovery findings. :contentReference[oaicite:15]{index=15}
• UM/Jatheon — install/verify components, run discovery and test extraction, produce reporting, tune for throughput, execute and monitor migration per plan. :contentReference[oaicite:16]{index=16}

Performance Considerations

Throughput depends on source/destination throttling, network, and storage. Adding resources to Remote Agents and threads helps up to the point of external throttles; discovery test runs are used to measure and tune before bulk runs. :contentReference[oaicite:17]{index=17} :contentReference[oaicite:18]{index=18}

Troubleshooting

• Connectivity issues — verify firewall/proxy rules and any load balancers that may shape high-bandwidth flows. :contentReference[oaicite:19]{index=19}
• Slow/variable throughput — check source throttling, storage IOPS, and RA thread counts; re-test and adjust batches/schedule. :contentReference[oaicite:20]{index=20}
• Errors during extraction — use UM logs to distinguish transient vs. permanent errors and rerun failed items. :contentReference[oaicite:21]{index=21}

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. :contentReference[oaicite:22]{index=22}