How can we ingest data from mobile devices and chat apps like WhatsApp? What solution parses these conversational threads into a readable format for attorneys?

Ingesting and parsing mobile data and encrypted chat apps like WhatsApp for legal review requires a specialized workflow. Because WhatsApp messages are end-to-end encrypted and stored within local device databases (SQLite) or cloud backups, standard eDiscovery email collections cannot process them natively.prudentialassociates.com+1

A defensible, standard industry workflow bridges forensic mobile acquisition with modern eDiscovery review platforms.

Phase 1: Ingestion & Extraction (The Forensic Collection)

Attorneys or digital forensic examiners cannot simply "download" WhatsApp threads from Meta directly, as Meta does not retain message content. Instead, acquisition must happen at the device or backup endpoint:elitedigitalforensics.com

• Mobile Acquisition Tools: Specialized hardware and software tools physically or logically extract the file system from iOS or Android devices. Industry-standard tools include Cellebrite UFED and Magnet AXIOM.prudentialassociates.com+1
• Cloud & Backup Extraction: If the physical device is unavailable, tools can ingest data via authorized cloud backups (iCloud or Google Drive) provided the necessary credentials and decryption keys or passphrases are accessible.elitedigitalforensics.com
• Chain of Custody: Proper forensic procedures must be maintained during extraction to avoid altering metadata or triggering spoliation claims.prudentialassociates.com

Phase 2: Parsing & Formatting (Making Chats Readable for Attorneys)

Raw database files (like an SQLite .sqlite or Cellebrite .ufdr export) are unreadable to legal review teams. They must be parsed into conversational thread views that resemble how the messages actually appeared on the phone (bubbles, timestamps, sender/receiver details, embedded media, and reactions).jatheon.com

The gold-standard ecosystem for this translation relies on a specialized format:

• Relativity Short Message Format (RSMF): RSMF is the legal industry's open file standard (developed by Relativity) specifically designed to package chat data—including WhatsApp, WeChat, Slack, and SMS—into a single, reviewable file.help.relativity.com
• The Parsing Solution Pipeline:
  1. Forensic Decoding: Tools like Cellebrite Physical Analyzer or Magnet AXIOM parse the raw device artifacts and decode WhatsApp databases.

If you'd like to dive deeper, let me know:

• Are you dealing with iOS or Android devices?
• Do you already have a preferred eDiscovery review platform (like Relativity ) in place?

Yes. The workflow you’re describing is essentially mobile forensics → conversational parsing/threading → legal review.

A practical architecture

1. Collect/extract from the device

• For iOS and Android, a forensic collection tool such as Cellebrite can extract WhatsApp and other messaging artifacts, subject to what can actually be accessed from the device, OS, app version, credentials, and collection method.
• Cellebrite's UFDR output can contain WhatsApp, SMS/MMS, Facebook Messenger, WeChat, Telegram and other chat data.Relativity Help+1

2. Normalize the messages

• The key is converting records such as: timestamp | sender | recipient | message | attachment into a conversation-level representation.
• This needs to preserve participants, timestamps, message IDs, attachments, emojis, reactions/edits where available, and provenance.

3. Thread the conversation

• Instead of giving an attorney thousands of individual database rows, the system groups messages into logical conversational segments.
• This is where products such as Relativity Short Message Format (RSMF) are useful. RSMF is specifically designed to represent conversational data for processing and review.Relativity Help

4. Present it like a chat

• The resulting review interface can look approximately like:

WhatsApp — John Smith / Jane Doe March 14, 2026

John Smith — 9:02 AM Are you still meeting with the client tomorrow?

Jane Doe — 9:03 AM Yes, 10am.

John Smith — 9:05 AM Did you send the revised agreement?

Jane Doe — 9:07 AM Just sent it. [Revised Agreement.pdf] That format retains the context and chronology attorneys need rather than forcing them to reconstruct a conversation from spreadsheets.

The solutions I'd look at

Cellebrite + RelativityOne is probably the clearest end-to-end example of this architecture. Cellebrite's Legalview integration connects mobile forensic extraction with RelativityOne, while Relativity converts Cellebrite UFDR chat data into RSMF for legal review.Cellebrite+1

There are also specialized parsing/review products within the Relativity ecosystem:

• Communication Intelligence by TCDI — takes mobile/chat data and groups messages into conversational segments, renders them in chat-bubble format, handles attachments and emojis, and performs cross-device threading and deduplication. It supports WhatsApp among other messaging formats.Relativity
• CDS Convert — converts mobile/forensic collections and numerous chat applications, including WhatsApp, into RSMF, with conversation threading, metadata extraction, attachments, filtering and review functionality.Relativity
• A&M ChatView — renders WhatsApp and other chat data in a near-native conversational format, including media, voice messages, emojis and other content.Relativity
• MobileRev — specifically brings mobile text messages, WhatsApp and other mobile communications into Relativity for attorney review alongside conventional discovery.

One important distinction

If you're building this capability, I would separate extraction from parsing/review.

Extraction layer → Cellebrite / Magnet AXIOM / Oxygen Forensics → obtains the forensic artifacts

Parsing/normalization layer → WhatsApp databases + JSON/XML/UFDR/etc. → normalize sender, recipient, timestamp, message, attachment, reaction, edit, deletion status, conversation ID, provenance

Conversation engine → thread messages → resolve participants → handle group chats → deduplicate across devices → associate media → preserve source IDs and forensic metadata

Attorney UI → chat-bubble/timeline presentation → search/highlighting → message-level coding → redaction → export/production → audit trail

eDiscovery system → RelativityOne, Everlaw, etc.

One especially important caveat: a normal WhatsApp chat export isn't necessarily interchangeable with a forensic extraction. For example, Relativity currently says standalone WhatsApp exports aren't directly supported for its RSMF conversion, whereas WhatsApp data contained in a Cellebrite UFDR extraction is supported.Relativity Help

So if your question is really “what product should we use to turn Cellebrite/mobile WhatsApp evidence into attorney-readable conversational threads?”, the most directly relevant category is mobile-to-RSMF/conversational parsing, with TCDI Communication Intelligence, CDS Convert, MobileRev, and Cellebrite Legalview + RelativityOne being particularly relevant examples.

If you're evaluating this for a new legal-tech product, I can also map out the actual ingestion/data model—including how I'd parse WhatsApp SQLite/UFDR artifacts into a reviewable conversation format and maintain forensic chain-of-custody.

Yes. The legal-tech workflow you’re describing is generally mobile forensic collection → chat/conversation parsing/threading → eDiscovery review.

A practical architecture

1. Collect from the mobile device

• Forensically collect iOS/Android data using a tool such as Cellebrite Physical Analyzer/UFED.
• Depending on the device and permissions, the collection can include SMS/MMS, WhatsApp, Messenger, Telegram, photos, videos, call logs, contacts, etc.
• Cellebrite's UFDR export is particularly useful because downstream legal-review platforms can consume the structured extraction.Relativity Help+1

2. Parse and normalize the conversations

• The important step isn't merely extracting individual WhatsApp messages. You want to reconstruct conversation threads: participants, timestamps, sender/recipient, message text, edits, reactions where available, attachments, and application metadata.
• The normalized representation can then be converted into an eDiscovery format such as RSMF (Relativity Short Message Format). Relativity specifically supports converting Cellebrite UFDR chat extracts into RSMF, including WhatsApp and other chat applications.Relativity Help+1

3. Render it for attorneys

• Instead of giving a lawyer thousands of rows in Excel, the system presents something resembling the original conversation: chat bubbles, participants, dates/times, images and attachments, while retaining searchable metadata.
• Everlaw, for example, can ingest Cellebrite UFDR exports and render WhatsApp conversations in a user-friendly conversational format, including participant/application/date metadata and inline images.Everlaw Support

The solution I'd look at first

Cellebrite + RelativityOne is probably the most direct end-to-end answer if you're building around a mainstream legal eDiscovery workflow.

Cellebrite's Legalview integration connects its mobile forensic extraction/analysis capabilities with RelativityOne, allowing mobile data to be collected, decoded, converted and transferred into the eDiscovery environment.Cellebrite+1

The resulting workflow is roughly:

iPhone/Android → Cellebrite extraction → UFDR → WhatsApp/chat parsing → RSMF → RelativityOne → attorney review/search/production

Relativity explicitly supports WhatsApp data from Cellebrite UFDR and converts the chat data to RSMF.Relativity Help

There's another interesting option

If your real question is "what software specializes in turning messy mobile/chat evidence into attorney-friendly conversational threads?", take a look at Communication Intelligence by TCDI.

It is designed specifically to group individual messages into meaningful periods of conversation and render them in a chat-bubble interface. It also claims to work across device types, chat applications and forensic sources, including Cellebrite reports and Slack/social-media exports, with cross-device threading and deduplication.Relativity

That's conceptually closer to a "conversation intelligence layer" than simply an extraction tool.

Important distinction

There are really three different products/capabilities here:

Layer	What it does	Examples
Collection / forensics	Gets data off the phone	Cellebrite, MSAB, Oxygen
Parsing / threading	Turns raw databases/extractions into conversations	Cellebrite/Relativity processing, TCDI Communication Intelligence
Legal review	Search, redact, code, produce, privilege review

This distinction matters because WhatsApp's own "Export Chat" isn't necessarily the ideal litigation source. For example, Relativity says standalone WhatsApp exports aren't directly supported for its RSMF conversion, whereas WhatsApp data contained in a Cellebrite UFDR extraction is.Relativity Help

If you're evaluating this as a product/technical architecture rather than simply looking for an existing vendor, I can also map out how to build the ingestion + WhatsApp parser + conversation-threading layer yourself, including the data model I'd use for messages, participants, attachments, timestamps, edits, and chain-of-custody.

Ingesting and parsing mobile data and chat logs like WhatsApp for legal review requires a specialized workflow. Because WhatsApp uses end-to-end encryption and stores data in complex local databases (SQLite format with specific encryption keys), standard copy-pasting or basic screenshots are neither legally defensible nor practical.prudentialassociates.com+2

The standard pipeline moves from collection to processing/parsing to attorney review.

Phase 1: Ingestion & Collection (Mobile Devices & WhatsApp)

To ensure admissibility and maintain a strict chain of custody, collection is typically performed by professional digital forensics examiners or via specialized software.ijert.org+1

• Physical and File System Extraction: Tools acquire a bit-by-bit or logical image of the iOS or Android device. This pulls the active WhatsApp database (msgstore.db ), media files (images, voice notes), and importantly, unallocated space/WAL files where deleted messages may still reside.elitedigitalforensics.com+2
• Cloud & Backup Extraction: If physical access to the device is impossible, extraction can target encrypted iCloud or Google Drive backups, provided the credentials, 64-digit encryption key, or two-factor authentication tokens are lawfully obtained.oxygenforensics.com+1
• Targeted/Self-Collection Warning: Relying on users to export individual chats via the built-in WhatsApp "Export Chat" feature is heavily discouraged in formal litigation. It produces plain text/ZIP files lacking comprehensive metadata, alters timestamps during export, and exposes parties to spoliation or data integrity challenges.prudentialassociates.com

Phase 2: Solutions That Parse Conversations for Attorneys

Once data is extracted, raw database files (.db, .sqlite , or proprietary forensic container files like .ufdr ) are unreadable to attorneys. They must be parsed into conversational thread views—resembling the actual chat interface (bubbles, timestamps, sender/receiver avatars, and embedded media).

Industry-standard solutions handle this parsing and review stage:

1. Cellebrite UFED / Cellebrite Pathfinder : The gold standard in mobile device extraction. Cellebrite parses raw device dumps—including deep WhatsApp chat histories, deleted items, contact cards, and GPS data—into a structured, searchable timeline view that investigators and legal teams can export into readable formats.ijert.org
2. Oxygen Forensic Detective : A direct competitor to Cellebrite, Oxygen excels at decrypting WhatsApp databases, pulling cloud tokens, and parsing complex multi-device messaging artifacts into clean, readable timelines and visual relationship graphs.ijert.org+1

Would you like to explore how to handle deleted WhatsApp messages during parsing, or do you need assistance determining whether a forensic vs. non-forensic collection fits your specific case?

The problem is usually solved with a mobile forensics collection layer + conversational eDiscovery parsing layer. Attorneys generally do not want raw WhatsApp databases, SQLite files, or CSV exports; they need reconstructed conversations with timestamps, participants, attachments, and searchable context.Consilio

A typical architecture looks like this:

Mobile device / WhatsApp export / cloud source
              ↓
Forensic collection & extraction
              ↓
Chat artifact parsing + normalization
              ↓
Conversation threading
              ↓
Attorney review platform
              ↓
Search, privilege review, redaction, production

1. Data ingestion from phones and messaging apps

Common collection sources:

• iPhone / Android device extractions
• WhatsApp exports (ZIP/text/media exports)
• Mobile backups
• Enterprise messaging archives (where available)
• Other apps: iMessage, SMS/MMS, Signal, Telegram, Teams, Slack, Messenger, etc.

For forensic-grade collections, tools such as Cellebrite, Magnet Forensics, and Oxygen Forensics are commonly used to acquire and decode mobile artifacts. The exact data available depends on device type, OS version, app version, encryption, credentials, and collection method.Parse

2. Solutions that turn chats into attorney-readable threads

The key capability is conversation reconstruction. A parser converts records like:

message_id
timestamp
sender_id
recipient_id
text
attachment_id

into something like:

WhatsApp Conversation
John Smith ↔ Jane Doe
March 14, 2026

9:02 AM — John Smith
Did you send the agreement?

9:03 AM — Jane Doe
Yes, attaching it now.

[Attachment: Agreement.pdf]

Important features include:

• Thread reconstruction
• Sender attribution
• Chronological ordering
• Group chat handling
• Media linking
• Emoji/reaction handling
• Reply relationships
• Time-zone normalization
• Evidence provenance

Examples of platforms and products used for this include:

• Relativity — uses formats such as Relativity Short Message Format (RSMF) to display chat data as conversations rather than isolated messages.Morgan Lewis
• Everlaw — supports review workflows for mobile/chat evidence and conversational rendering.Parse
• CDS Legal — CDS Convert focuses on converting chat and mobile data into review-ready eDiscovery formats.Complete Discovery Source

For more narrowly focused WhatsApp-to-evidence conversion, tools such as ChatFormats and ChatParse-style converters can transform exports into formatted PDFs, HTML review views, and legal production formats.ChatFormats+1

If you are building a product

The higher-value component is usually not the extraction engine; it is the normalization and attorney experience layer.

A strong architecture would include:

Ingestion connectors

• Cellebrite UFDR
• Magnet AXIOM exports
• Oxygen exports
• WhatsApp ZIP exports
• iOS/Android backups
• Enterprise chat APIs

Unified evidence schema

Example:

{
  "conversation_id": "abc123",
  "source_app": "WhatsApp",
  "participants": [
    "Jane Smith",
    "John Doe"
  ],
  "messages": [
    {
      "sender": "Jane Smith",
      "timestamp": "2026-03-14T09:03:00",
      "text": "Attaching it now",
      "attachments": [
        "agreement.pdf"
      ]
    }
  ]
}

Attorney-facing features

• Chat-bubble timeline view
• Keyword search
• AI-assisted summaries with message citations
• Timeline generation
• Participant mapping
• Privilege tagging
• Redaction tools
• Bates numbering/export
• Audit trail and chain-of-custody records

The differentiating feature is making a reviewer feel like they are reading the original conversation while preserving the defensibility required for litigation.Consilio

If you are evaluating vendors versus building this internally, the main architectural decision is whether you want to license extraction/forensic capabilities and build the review layer, or buy an end-to-end eDiscovery workflow.

Yes. The standard legal-tech architecture is essentially:

mobile device → forensic collection → chat parsing/normalization → eDiscovery review platform → attorney-friendly conversation view

Best-known solution: Cellebrite + RelativityOne

For a litigation/eDiscovery workflow, I would look closely at Cellebrite + Relativity.

• Cellebrite collects and decodes data from iOS/Android devices, including SMS/MMS and supported messaging applications such as WhatsApp, Facebook Messenger, WeChat and Telegram.Relativity Help+1
• Cellebrite's UFDR output can then be automatically converted by Relativity into RSMF (Relativity Short Message Format). RSMF is specifically designed to represent conversational data for eDiscovery.Relativity Help
• In RelativityOne, attorneys can review those messages as conversations rather than digging through forensic spreadsheets. The viewer preserves participants, timestamps, message counts, attachments and other conversational metadata.Relativity Help+1
• Relativity's Cellebrite integration/Legalview can move mobile-device data into the eDiscovery environment, reducing the manual conversion work between forensic extraction and legal review.Relativity Help+1

So, if by "what solution parses these conversational threads into a readable format for attorneys?" you mean the specific normalization/rendering layer, the answer is RSMF + Relativity's Short Message Viewer, with Cellebrite providing the underlying mobile extraction.

What the attorney actually sees

Instead of something like:

2026-08-14 14:03:22  +15551234567  "Hey"
2026-08-14 14:03:48  +15557654321  "Did you talk to John?"
2026-08-14 14:04:01  +15551234567  "Yes"
...

the review system turns it into a conversation-style document:

WhatsApp — John / Jane
August 14, 2026

Jane       2:03 PM
Hey

John       2:03 PM
Did you talk to John?

Jane       2:04 PM
Yes

[Photo attachment]

The important part is that the system maintains the relationship between messages, participants, timestamps and attachments rather than treating every text as an isolated document. Relativity specifically describes its short-message workflow as importing, searching and reviewing messages at both the conversation and message level.Relativity Help

There are alternatives

Everlaw is another interesting option if your goal is specifically an attorney-friendly review experience. Its mobile-data guidance describes rendering SMS/chats in an intelligible, phone-like format, including chat bubbles and WhatsApp-specific formatting, while keeping conversations together for contextual searching.Everlaw

There are also specialized Relativity applications such as MobileRev, which takes output from forensic tools such as Cellebrite and turns WhatsApp, iMessage and text data into something attorneys can review alongside email and documents.Relativity

If you're designing this as a product

I'd separate the problem into four layers:

1. Collection — Cellebrite/other mobile forensic tools acquire the data while preserving evidentiary integrity.
2. Parsing/normalization — Decode WhatsApp's underlying records and normalize messages, participants, timestamps, reactions, edits, deletions and attachments into a common schema.
3. Conversation reconstruction — Reassemble individual events into coherent threads, including group chats and temporal/contextual boundaries.
4. Legal review rendering — Present the resulting conversation as a searchable, citeable document with Bates numbers, metadata, redactions and links to native attachments.

The key industry format to investigate is RSMF. It is increasingly becoming the interchange format between raw short-message/chat evidence and eDiscovery review. Relativity also allows other chat sources to be converted into RSMF, and provides developer tooling/third-party integrations for sources that don't have native conversion.Relativity Help

If you're asking because you're building a system that ingests WhatsApp/mobile data and produces attorney-readable threads, I can also map out the technical architecture—including WhatsApp extraction formats → canonical message schema → thread reconstruction → RSMF/PDF/HTML rendering → eDiscovery integration—and identify the main commercial competitors.

Ingesting and parsing mobile data—especially secure chat apps like WhatsApp—for legal review requires a specialized workflow. Because WhatsApp messages are end-to-end encrypted and stored in localized SQLite databases, standard corporate IT collection tools cannot simply "copy-paste" the data.oxygenforensics.com+2

Phase 1: How We Ingest Data from Mobile Devices & WhatsApp

The ingestion process depends on whether you need a strict forensic acquisition (preserving deleted messages, metadata, and maintaining a rigid chain of custody) or a targeted/non-forensic collection (exporting active visible chats).relativity.com+2

1. Forensic Device Acquisition (Recommended for Litigation)
   • Tools used: Industry-standard mobile forensics software like Cellebrite Physical Analyzer or Oxygen Forensics.
   • The Process: Qualified examiners connect the physical device (iOS or Android) to extract the physical or logical file system. For WhatsApp, this extracts the underlying encrypted SQLite database files and associated journaling files (WAL ), which often hold recoverable deleted chat histories.
   • Decryption: The forensic software leverages device backups, authorized credentials, or specific keys to decrypt the WhatsApp database so the messages become legible.cellebrite.com+4
2. Cloud Extraction
   • The Process: If physical device access isn't feasible or the device is lost, forensic tools can pull WhatsApp backups directly from cloud storage (iCloud or Google Drive ) provided the legal custodian provides the credentials, 2FA access, and the 64-digit encryption key if applicable.elitedigitalforensics.com+2
3. Targeted / Non-Forensic Export (For Consent/Speed)
   • Tools used: Desktop companion apps or direct app exports (e.g., Decipher Chat for individual thread saving).
   • The Process: Useful for minor civil matters or preliminary reviews where deleted messages are irrelevant, though it lacks the rigorous chain-of-custody defensibility of a true forensic extraction.csdisco.com+2

Phase 2: Solutions That Parse Conversations into Readable Formats for Attorneys

Raw database files (.sqlite ) or forensic extractions are unreadable to attorneys. They need to be converted into conversational, modern layouts (resembling chat bubbles with timestamps, sender/receiver alignments, and embedded media) rather than dense, traditional email-style spreadsheets.

1. The Gold Standard: Relativity (with Cellebrite Integration / RSMF)

• How it works: RelativityOne utilizes the RSMF (Relativity Short Message Format).
• The parsing result: It directly ingests forensic exports (like Cellebrite's .UFDR files) and automatically parses WhatsApp, SMS, WeChat, and Signal threads into a native, Slack- or WhatsApp-style viewer. Attorneys can view continuous chat streams, see read receipts, filter by specific participants or timeframes, and review multimedia context just as it appeared on the mobile screen.help.relativity.com+1

2. Specialized Mobile Forensic Viewers

• Cellebrite Reader / PA Viewer: Cellebrite offers free or review-license reader software where attorneys can scroll through a cleanly rendered, chronological recreation of WhatsApp chats complete with contact icons and attachments.
• Oxygen Forensic Detective Viewer: Exports data into hyperlinked, highly readable standalone reports (PDF, HTML, or Excel formats optimized for legal review) that segment conversations neatly by contact threads.

3. E-Discovery Platforms with Native Chat Parsing

• Platforms like DISCO, Nuix , and Everlaw feature built-in short-message-parsers. They transform raw chat app payloads into unified timelines where a threaded conversation isn't split across a thousand disjointed single-line document records, preserving the context of the back-and-forth dialogue.

Are you looking to handle a collection internally/forensically with hardware tools, or do you need recommendations for an e-discovery review hosting provider to process files you already extracted?

Ingesting and parsing mobile data and chat applications (like WhatsApp, Signal, and iMessage) for legal review requires a specialized workflow. Because chat logs include non-linear threading, multimedia, emojis, and strict encryption, standard email-processing tools fall short.

The standard workflow and the software solutions used to turn chaotic chat data into a readable, legally defensible format for attorneys involve distinct phases:

Phase 1: Ingestion & Collection Methods

How data is pulled from mobile devices depends on access, consent, and whether a forensic-level preservation is required.

1. Logical and Physical Forensic Extractions : For high-stakes litigation or internal investigations, forensic examiners use specialized hardware/software to pull data directly from physical devices or cloud backups (iCloud/Google Drive).oxygenforensics.com+1
2. Targeted Application Export (Self-Collection) : For lower-tier or consensual collections (e.g., family law or employment disputes), users or custodians can export native chat files (like a .txt export of a WhatsApp chat) or use direct-extraction web tools.
3. Enterprise Archiving/Capturing : For corporate-issued devices or BYOD policies, tools intercept or archive business communications in real-time via APIs or carrier-level archiving.

Phase 2: Solutions that Parse Chat Threads for Attorneys

Once ingested, raw database files (like SQLite files from iOS/Android) or extraction reports must be normalized into readable timelines, native-feeling chat bubbles, or standard eDiscovery load files.

• • Copy

      - **Cellebrite (Physical Analyzer / UFED)** : The gold standard for mobile device forensics. It ingests physical/logical extractions and parses WhatsApp, Signal, WeChat, and SMS threads into chronological, readable chat-bubble formats complete with metadata, deleted message recovery, and embedded media.[](https://www.streemview.com/solutions/mobile-data) [[1]](https://www.streemview.com/solutions/mobile-data)

• • Copy

      - **Oxygen Forensics (Detective)** : Another heavy-duty forensic suite that excels at parsing cloud extractions, device backups, and encrypted chat databases into structured, searchable timelines for legal teams.[](https://www.oxygenforensics.com/technical-resources/whatsapp-forensics/) [[1]](https://www.oxygenforensics.com/technical-resources/whatsapp-forensics/)

• • Copy

      - **Hearsay** : A specialized, compliance-focused legal discovery tool geared toward pulling and reviewing text messages and chat apps (WhatsApp, iMessage) alongside emails and social media, exporting them into standard formats like PDF or [RSMF (Reference Stored Message Format)](https://usehearsay.com/).[[1]](https://usehearsay.com/)

• • Copy

      - **StreemView** : A dedicated eDiscovery mobile data platform designed to process raw forensic extraction outputs (from Cellebrite or GrayKey) and normalize iOS/Android messaging apps into clear, deduplicated, and review-ready conversation threads.[](https://www.streemview.com/solutions/mobile-data) [[1]](https://www.streemview.com/solutions/mobile-data)

• • Copy

      - **Relativity (with specialized chat connectors)** : The industry-standard eDiscovery review platform. Through integrations and extensions (or native processing of RSMF files), Relativity allows attorneys to view WhatsApp and text data structured like a chat window rather than flat, unwieldy spreadsheet rows.

To help narrow down the right approach, could you let me know:

• Is this for a formal forensic investigation/litigation or a consensual self-collection?
• Roughly how many devices or custodians are involved?

To ingest mobile-device and chat-app data (WhatsApp, iMessage, SMS, Signal, Telegram, Teams, Slack, etc.) for legal review, the typical architecture is:

Mobile device/app data → forensic extraction → chat normalization/parser → eDiscovery review platform → attorney production/review

The key challenge is not just extracting messages; it is reconstructing fragmented message records into defensible, readable conversations with context. Raw exports often look like rows of timestamps and message IDs, while attorneys need something closer to the original chat experience: participants, chronology, attachments, reactions, and searchable threads.Everlaw+1

1. Data ingestion / collection layer

Common collection tools include:

• Cellebrite — widely used for forensic mobile extraction and decoding of app artifacts.
• Magnet Forensics — provides mobile artifact extraction and analysis capabilities.
• Oxygen Forensics — another mobile forensic collection and analysis platform.

The output is usually a forensic export containing messages, contacts, media, timestamps, app metadata, and device information. For example, Cellebrite exports such as UFDR packages are commonly ingested by review systems.Everlaw

2. Conversational parsing / normalization layer

This is the piece that turns:

message_id | sender | timestamp | text | attachment
483920     | John   | 10:31     | "Where is the file?"
483921     | Jane   | 10:32     | "Attached."

into:

WhatsApp Conversation
John Smith ↔ Jane Doe
March 10, 2026

10:31 AM — John Smith
Where is the file?

10:32 AM — Jane Doe
Attached.

[contract.pdf]

The parser should preserve:

• Sender and recipient identity
• Date/time and time zone
• Group-chat membership
• Attachments and inline media
• Message IDs
• Replies/quoted messages
• Edits/deletions where available
• Source device and provenance metadata
• Hashes and chain-of-custody information

3. Attorney review platforms and solutions

Relativity ecosystem

A common enterprise workflow is:

Cellebrite → RelativityOne → attorney review

Relativity uses formats such as Relativity Short Message Format (RSMF) to represent short-message communications as coherent conversations instead of isolated records.Parse

Everlaw

Everlaw supports mobile chat review workflows and focuses on rendering messages in a readable conversational format, including WhatsApp/iMessage-style views and associated metadata.Everlaw

CDS Legal — CDS Convert

CDS Convert is specifically aimed at converting short-message data from sources including WhatsApp and collaboration platforms into eDiscovery-ready formats, including RSMF-compatible outputs.Complete Discovery Source

ChatFormats

For narrower WhatsApp workflows, ChatFormats converts WhatsApp exports into attorney/court-oriented outputs such as PDF, HTML review files, CSV, and load files.ChatFormats

A practical enterprise workflow

iPhone / Android / WhatsApp export
              ↓
Cellebrite / Magnet / Oxygen extraction
              ↓
Chat parser + normalization engine
              ↓
Conversation objects
              ↓
Relativity / Everlaw / other review platform
              ↓
Search, privilege review, redaction, production

If building a product in this space

The strongest opportunity is usually not another WhatsApp extractor. The valuable layer is a conversation intelligence and normalization engine:

Inputs

• Cellebrite UFDR
• Magnet AXIOM exports
• Oxygen exports
• WhatsApp ZIP exports
• iMessage/SMS databases
• Slack/Teams/Telegram exports

Processing

• Normalize into a common schema
• Thread conversations
• Identify participants
• Link attachments
• Detect gaps in communication
• Preserve evidence lineage

Outputs

• Attorney-friendly chat timeline
• Searchable conversation view
• PDF/HTML exhibits
• RSMF/load-file exports
• AI-assisted summaries and timelines tied back to source messages

For a law firm or litigation-support operation today, the most established route is generally forensic extraction (Cellebrite/Magnet/Oxygen) combined with a legal review layer such as Relativity, Everlaw, or a specialized converter like CDS Convert.Everlaw+1

The typical legal workflow is to treat mobile/chat data as short message data (SMD) and move it through a forensic extraction → parsing/normalization → eDiscovery review pipeline. Attorneys generally do not want raw phone databases, CSV dumps, or app exports; they need threaded, searchable conversations that preserve context, timestamps, participants, attachments, emojis, and metadata.LegalClarity+1

Common ingestion workflow

1. Collect data from the device

• Use mobile forensic collection tools such as Cellebrite or similar forensic platforms.
• Collection may include: - SMS/MMS
• iMessage
• WhatsApp
• Signal/Telegram (where technically available)
• Photos/videos
• Voice notes
• Call logs
• Device metadata

What can be collected depends on the phone model, operating system, app version, encryption, credentials, and extraction method. Parse Everlaw 2. Parse and normalize the conversations A parsing layer converts raw records such as:

message_id
timestamp
sender
recipient
text
attachment_path

into an attorney-readable thread:

WhatsApp Group: Project Discussion

John Smith
Mar 14, 2026 9:02 AM
Are you still meeting the client tomorrow?

Jane Doe
Mar 14, 2026 9:03 AM
Yes, 10 AM.

[Attachment: Contract_Draft.pdf]

The important capabilities are:

• Conversation reconstruction
• Thread grouping
• Participant mapping
• Date/time normalization
• Attachment linking
• Emoji/reaction preservation
• Search indexing
• Redaction and production support

3. Load into an eDiscovery review platform

Common destinations include:

• Relativity
• Everlaw
• Reveal

These platforms let attorneys review chats alongside emails, documents, and other evidence.Everlaw

Solutions that specifically parse WhatsApp/mobile conversations for attorneys

Relativity ecosystem

Relativity uses Relativity Short Message Format (RSMF) for conversational data. RSMF is designed to keep messages grouped as conversations rather than flattening every message into unrelated documents.Parse+1

A common stack is:

Cellebrite extraction → RSMF conversion → RelativityOne review

Contact Discovery Services MobileRev

MobileRev is designed for reviewing mobile content inside Relativity, including text messages and supported chat formats such as WhatsApp, with a phone-like conversation view rather than spreadsheet review.Relativity

CDS Legal CDS Convert

CDS Convert focuses on converting chat and mobile data from multiple sources into review-ready formats for eDiscovery platforms. It supports sources including WhatsApp and mobile forensic outputs.Complete Discovery Source

Everlaw mobile/chat review

Everlaw supports ingestion of mobile forensic exports and renders chats in a conversational format, including WhatsApp-style views, with metadata and attachments preserved for review.Everlaw

If you are building this capability yourself

The architecture usually looks like:

Mobile Extraction Layer
        ↓
Parser / Normalizer
        ↓
Conversation Reconstruction Engine
        ↓
Metadata + Attachment Index
        ↓
Attorney Review UI
        ↓
Production (PDF, load files, RSMF, etc.)

The hardest engineering pieces are usually:

• reconstructing threads correctly
• preserving evidentiary metadata
• handling deleted/edited messages
• maintaining chain of custody
• converting chats into defensible production formats

For a law firm or litigation support team, the most established approach is usually Cellebrite + Relativity (RSMF/MobileRev) or Cellebrite + Everlaw, rather than building a custom parser from scratch.Relativity+1