Symphony Migration to Jatheon Cloud
This guide explains how to migrate Symphony messages (1:1 chats, rooms, events) to Jatheon Cloud. It covers prerequisites, native Symphony Content Export (SFTP) setup, connector-based options (e.g., 17a-4 DataParser), packaging/manifesting, ingestion, and validation to ensure full integrity and compliance.
Prerequisites
- Symphony admin access (Admin Portal) with rights to configure Content Export.
- SFTP destination (domain, port, username, RSA key pair) for export delivery.
- List of users/rooms, date ranges, and retention/hold requirements.
Overview
Symphony provides a Content Export capability to regularly export messaging, events and chat room data, either on a schedule or ad-hoc. Exports can be delivered to SFTP and consumed by archiving platforms or connectors. Alternatively, partner connectors (e.g., 17a-4 DataParser) can collect Symphony content and convert it into an email-like format suitable for ingestion pipelines.
Export Paths
- Native Symphony Content Export (SFTP) — Configure in Admin Portal → Company Settings → Export Content; set SFTP domain/port/username, choose key, and schedule ad-hoc or recurring exports.
- Connector-based — Use a partner connector (e.g., 17a-4 DataParser) that leverages Symphony’s compliance export and outputs items in a message format for downstream ingestion.
Tip: Start with a pilot window (e.g., last 30–60 days, 2–3 rooms) to validate counts, attachments and search parity before bulk export.
Set up Native Content Export (SFTP)
- Sign in to Symphony and open Admin Portal.
- Go to Company Settings → Export Content.
- Open the SFTP tab and note SFTP Domain, Port, and Username.
- Under Authentication, choose your key (Symphony-provided or customer-managed), then Save & Close.
- Schedule a recurring export or trigger an ad-hoc export for the pilot range.
Packaging & Manifest
Maintain a manifest (CSV) with file paths, sizes, timestamps, and hashes to preserve chain-of-custody.
Sample CSV header:
ArchivePath,FileName,SizeBytes,LastWriteUTC,SHA256,ExportWindowStart,ExportWindowEnd
Example PowerShell to compute SHA-256 and build a manifest:
$Root="D:\Symphony\Exports"
$Out="D:\Symphony\manifests\symphony_manifest.csv"
$files=Get-ChildItem -Path $Root -Recurse -File
$rows=foreach($f in $files){$h=Get-FileHash -Algorithm SHA256 -Path $f.FullName;[pscustomobject]@{ArchivePath=$f.DirectoryName;FileName=$f.Name;SizeBytes=$f.Length;LastWriteUTC=$f.LastWriteTimeUtc;SHA256=$h.Hash;ExportWindowStart=$null;ExportWindowEnd=$null}}
$rows|Export-Csv -NoTypeInformation -Path $Out -Encoding UTF8
Ingestion to Jatheon Cloud
- Native exports — Deliver packages from SFTP to the agreed ingestion location (e.g., S3 or secure share). Jatheon will map exported items and metadata to the archive schema.
- Connector exports — If using a connector (e.g., DataParser), route the converted items (email-like format) to the Jatheon ingestion pipeline.
- Run ingestion in phased batches; monitor exceptions and remediate.
Validation & Cutover
- Reconcile item/file counts and sizes vs. the manifest.
- Spot-check conversations: participants, timestamps, message text, attachments.
- Verify search parity (keywords, participants, date range) in Jatheon Cloud.
- Schedule a delta export and finalize cutover; retain the export logs and checksums.
Troubleshooting
- SFTP auth fails — Re-check domain/port/username and the configured RSA keys; ensure allow-list/firewall rules.
- Missing rooms/users — Confirm export filters and scope; rerun for the correct date range and entitlements.
- Large exports — Split by date/user; increase export frequency; stage locally before upload to ingestion.
- Encoding issues — Validate UTF-8 output and special characters; verify after ingestion.
Comments
0 comments
Please sign in to leave a comment.