Exporting WhatsApp Chats: Formats, Limits and Keeping History When Staff Leave

WhatsApp exports one chat at a time. There is no account-wide export, and no admin console to retrieve conversations from someone else's device. That single fact drives everything else here.

Exporting a single chat#

Android: open the chat → menu (⋮) → More → Export chat → With media or Without media → choose where to send it.

iPhone: open the chat → tap the contact or group name → scroll down → Export Chat → With or Without Media → share sheet.

Desktop / Web: export is not available in the browser client. Do it on the phone.

The result is _chat.txt — one line per message with a timestamp and sender — plus attachment files if you chose media.

[21/08/2026, 14:32:07] Priya Sharma: Do you have the 500ml in stock?
[21/08/2026, 14:33:19] Store: Yes, ready to dispatch today.

What the export contains, and what it drops#

Included: message text, timestamps, sender names, system events (joins, leaves, security-code changes), and attachments when you export with media.

Not included, or unreliable:

• Deleted messages — gone.
• Disappearing messages already expired.
• View-once media — never exportable.
• Reactions and edit history — inconsistent across versions.
• Full media on long chats — the with-media export is size-capped and truncates the oldest messages first.

The practical rule: with media for a short, important thread; without media when you need the fullest possible text record.

Making an export searchable#

The text file is simple to parse — one timestamp-prefixed line per message. A short script converts it to CSV for a spreadsheet:

import re, csv
pattern = re.compile(r"^\[(.*?)\] (.*?): (.*)$")
with open("_chat.txt", encoding="utf-8") as f, open("chat.csv", "w", newline="", encoding="utf-8") as out:
    w = csv.writer(out); w.writerow(["timestamp", "sender", "message"])
    for line in f:
        m = pattern.match(line.strip())
        if m: w.writerow(m.groups())
        elif line.strip(): w.writerow(["", "", line.strip()])  # continuation line

Multi-line messages continue on following lines without a timestamp — the elif branch above keeps them rather than discarding them, which naive parsers usually do.

Note the date format follows the exporting phone's locale, so parse defensively when combining exports from several devices.

The problem exports do not solve#

If your customer conversations happen on a staff member's phone, exporting is damage control, not a system.

What you lose when someone leaves: every thread, every commitment made, every price quoted, and the relationship itself. The customer messages the same number and reaches whoever now holds it, with no context.

What you cannot do: show who said what during a dispute, review quality, hand over an account cleanly, or answer "what did we promise this customer in March".

What you may be obliged to do: retain records of commercial communications for a defined period, and produce them on request. A text file on a former employee's phone does not meet that in any jurisdiction.

Keeping history on the company side from the start#

Conversations belong in a system the business controls:

• The number is registered to the business, not to a personal device — see one number, several agents.
• Every message is stored centrally as it happens, not exported afterwards.
• Access is by role, so leaving staff lose access without taking data.
• History attaches to the contact record, alongside stage, tags and consent — labels versus tags.
• Search works across everything, not one file at a time.

Once conversations arrive over the Business Platform, retention becomes a configuration decision rather than an act of hope.

Before any migration#

If you are moving a number onto the Business Platform, export first:

1. Your top customer threads, without media, for the text record.
2. Any thread containing a commercial commitment, with media, for the attachments.
3. Anything under active dispute.

Store them somewhere the business controls, with the export date in the filename. Chat history does not carry across the migration, and that is the one irreversible step in the process.

Keep conversation history in a shared workspace where it stays with the business, searchable, and attached to the customer record.

Related: when backups fail · running one number across a team.