> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuco.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Export All Data (CSV)

> Download your Unibox conversations and activity log as CSV files — sent messages, replies, reactions, voice notes, calls, and system events.

## What You Can Export

Tuco lets you download your workspace data as CSV files directly from the app — no API keys or scripts required.

Two exports are available:

* **Unibox conversations** — every sent and received message, grouped by contact so each conversation reads top to bottom like your Unibox thread.
* **Activity log events** — system events such as sends, deliveries, failures, fallbacks, campaign changes, CRM syncs, and webhooks.

Both open cleanly in Excel, Google Sheets, or any BI tool.

***

## How to Export

1. Open **Activity Log** in your Tuco workspace.
2. Click the **Export All Data** button (bottom-right corner — it stays visible while you scroll).
3. Choose what to include:
   * **Unibox conversations**, **Activity log events**, or both.
   * For activity events, pick the categories you want (Messages, Campaigns, Replies, Webhooks, CRM syncs, Telegram, System, Voice calls).
4. Pick a date range — last 24 hours, 7 days, 30 days, or all time.
5. Click **Export CSV**. One CSV file downloads per selected dataset.

<Note>
  Exports are scoped to your current workspace and respect your role's access. Very large workspaces are capped at 50,000 rows per file — narrow the date range to segment bigger histories.
</Note>

***

## What's Inside the Conversations CSV

Each row is one item in a conversation, in thread order:

| Column                           | Meaning                                                    |
| -------------------------------- | ---------------------------------------------------------- |
| Conversation                     | The contact the thread belongs to                          |
| Date / Direction                 | When it happened and whether you sent or received it       |
| Kind                             | `message`, `reaction`, `voice note`, or `call`             |
| Channel                          | iMessage, SMS, email, or call                              |
| Status                           | sent, delivered, failed, fallback, etc.                    |
| Message                          | The full text body                                         |
| Reactions                        | Tapbacks the contact left on your messages (e.g. ❤️ Loved) |
| Attachments                      | File names of photos, videos, and voice notes              |
| Call Duration / Answered         | For call entries, how long and whether it connected        |
| Sent At / Delivered At / Read At | Delivery timeline timestamps                               |

Inbound reactions (Loved, Liked, Laughed at…), inbound voice notes, and placed calls all appear as their own rows with the `Kind` column set accordingly, so reply-rate math in your spreadsheet can include or exclude them explicitly.

***

## What's Inside the Activity Log CSV

Each row is one system event: the event type (for example `message_sent`, `reply_received`, `message_fallback`), its status, description, the contact and line involved, the source that triggered it (dashboard, API, campaign, CRM), and error details when something failed.

This is the same data you see on the Activity Log page, so anything you can filter there you can also take with you.

***

## Related

* [Replies & Inbox](/features/replies) — how replies are captured and matched.
* [Reactions](/features/reactions) — how tapbacks behave.
* [Export & Data Integration](/analytics/export-strategies) — moving Tuco data into BI and reporting tools on an ongoing basis.