Last date modified: 2026-Jun-15

Supported short message sources for RSMF conversion

This page answers common questions about which data sources can be converted to Relativity Short Message Format (RSMF).

RSMF overview

RSMF is the file format Relativity Processing uses to represent conversational data. Supported data types include chat messages, SMS, and instant messages. Relativity converts the source data to RSMF during Processing.

Sources that can be converted to RSMF

There are two paths to RSMF in Relativity:

  • File-based Processing workflows, where you export data from the source and upload it to Relativity for conversion.
  • Relativity Collect integrations, where data flows directly into Relativity in RSMF format without a separate export step.

Sources supported through file-based Processing

Source types supported by Relativity through the file-upload processing workflow include the following (each has a dedicated documentation page covering required input formats, processing profile settings, and known limitations).

Relativity Collect sources

Relativity converts some sources to RSMF as part of a Relativity Collect integration. In this workflow, Relativity Collect connects directly to the source platform, retrieves the data, and produces RSMF output without requiring a separate export-and-upload step.

Sources not supported

The following sources cannot currently be converted directly to RSMF.

Microsoft Teams — HTML exports (including Microsoft Purview)

Relativity does not support Teams data exported as HTML for RSMF conversion. Microsoft Purview's default Teams export format changed to HTML in May 2025. If you are collecting Teams data through Microsoft Purview, configure the export to produce PST output instead of HTML. Then submit the data to Relativity.

Microsoft Teams — MSG files

Relativity does not support Individual MSG files as a Teams input format. Export Teams data as a complete PST.

Slack data embedded in a PST container

Slack data wrapped inside a PST or other email-container format is not supported. Provide Slack data as the direct JSON export from Slack's standard export workflow.

WhatsApp standalone exports

WhatsApp data exported directly from the application—such as a chat archive or device backup—is not supported for direct RSMF conversion.

WhatsApp data collected through a Cellebrite UFDR extraction is processed through the standard UFDR workflow. It may produce RSMF output as part of the chat apps category. See Short message conversion for Cellebrite for more details.

Facebook account downloads

Relativity does not support data downloaded from Facebook accounts (the "Download Your Information" export) for RSMF conversion.

Non-Cellebrite mobile forensic tools

Extractions produced by forensic tools other than Cellebrite Physical Analyzer — including Oxygen Forensic Detective and other vendor-specific formats — are not natively supported. The following alternative paths are available:

  • Export to RSMF directly from your tool. If your forensic tool offers an RSMF export option, export the data as RSMF and import the file directly into Relativity. No short message conversion job is required.
  • Re-extract using Cellebrite Physical Analyzer. If you have access to the original device or forensic image, re-extract the data to produce a supported UFDR file.
  • Submit a feature request. This helps the product team in tracking demand for native support of your tool.

AI conversation tool exports

Conversation exports from AI tools — including ChatGPT, Claude AI, Fathom AI, and Perplexity — are not supported for direct RSMF conversion.

If AI conversation content appears inside a Cellebrite UFDR extraction (for example, captured during mobile forensic extraction of a browser session), the data is processed as part of the UFDR workflow but will not render as structured short messages in the output.

Unlisted sources

If your source is not listed in the preceding sections, the following options may apply.

  • If your source can export to RSMF directly, import the RSMF file into Relativity. No short message conversion job is required.
  • If your data is collected through a Cellebrite UFDR, follow the standard UFDR workflow regardless of the original chat application. RSMF support depends on the UFDR's content, not on the original app.
  • If neither applies, submit a feature request so the product team can track demand for the source format.
Return to top of the page
Feedback