Metalogix Archive Manager for Exchange Migration to Jatheon Cloud

This guide explains how to migrate archived data from Metalogix Archive Manager for Exchange to Jatheon Cloud. It includes prerequisites, connection setup, technical notes, export commands, migration scope, and post-migration verification to ensure full data integrity and compliance.

Prerequisites

• Determine the SQL Server name/instance where the Metalogix database resides.
• Ensure the account you are using has permission to read all Metalogix databases.
• Ensure the account has access to the Metalogix file shares (HSM content storage).
• Determine if the archives are user-only, journal-only, or a combination of both.
• Check whether there is a defined journal cut-off date or retention that affects export.
• Access to your Jatheon Cloud tenant for ingestion and verification.

Overview

Metalogix Archive Manager for Exchange centralizes and retains organizational email. With lifecycle management, PST control, and Single Instance Storage (SIS), organizations can achieve up to 80% reduction in email storage and 50% faster backups. Jatheon Cloud migration preserves messages, metadata, retention rules, and chain of custody with verified integrity.

Supported Source Systems

• Microsoft Exchange 2010 / 2013 / 2016
• Microsoft Office 365 (Exchange Online)
• PST file imports and legacy archives

Migration Scope

1. Data Extraction — Export archived emails and metadata (headers, timestamps, custodians, folder paths).
2. Structure Preservation — Map retention categories, folder hierarchy, and legal holds to Jatheon Cloud equivalents.
3. PST Handling — Consolidate and convert PSTs into import-ready format.
4. Integrity Verification — Checksum validation and audited transfers with detailed logs.
5. Phased Ingestion — Controlled batches with throughput throttling for compliance windows.
6. Monitoring & Reporting — Progress dashboards, exception handling, and status reviews.

What We Preserve

• Message bodies and attachments (original formats)
• Headers and delivery metadata
• Custodian/mailbox relationships
• Folder hierarchy and labels
• Retention markers and legal hold flags

Technical Notes

Metalogix stores metadata in SQL Server and message content within HSM file shares. Both must be accessible for a complete export.

• Identify the SQL Server instance and connected database (commonly PAMExchange or HSMDB).
• Ensure read access to Metalogix SQL databases and archive file shares.
• Confirm archive types: user, journal, or hybrid archives.
• Check journal cut-off dates and retention restrictions before extraction.
• Run PowerShell or API-based discovery and exports to plan and validate the migration.

Performing a Migration from the Archive Manager Exchange Edition

As this is a database-backed source, first load the SQL connection string, HSM database name, and the Metalogix schema used.

Create a job to migrate Metalogix mailbox “123” to PST (example target shown):

Generate a list of all mailboxes (adjust the output path for your environment):

Simply Migrate Metalogix PowerShell Commands

Analyze and test before bulk runs. Some examples use Export-CSV to visualize data at scale. Update the configuration with: Metalogix Connection String, HSM Database Name (e.g., HSMDB), and Schema Name (e.g., dbo or svarchiving).

These commands retrieve mailbox lists, folder structures, and message-level stats for planning, prioritization, and test exports. After extraction, data is normalized and ingested into Jatheon Cloud while preserving metadata, folder hierarchy, and retention markers.