# Exporting your data

Download your catalog, customers, conversations, messages, bookings and agent configuration as CSV or Excel. What arrives immediately, what arrives by email, and how long a download link lasts.

Source: https://docs.omazy.ai/workspace/exporting-data/

import Figure from '../../../components/Figure.astro'
import { Aside } from '@astrojs/starlight/components'

Everything your workspace holds can be downloaded as CSV or Excel. You start an export
under **Workspace, Data and privacy**.

It is your data, and the export is designed so you never have to ask anyone for
it: no ticket, no waiting on support, no format nobody can open.

## What you can export

| Dataset | One row per | Contains |
|---|---|---|
| **Catalog** | Product or service | Titles, prices, availability, images, descriptions |
| **Customers** | Contact | Names, email, phone, tags, custom fields |
| **Conversations** | Conversation | Channel, status, topic, timings, the customer |
| **Messages** | Message | Who said what, when, on which channel |
| **Bookings** | Booking | Reference, date, party, amounts, status |
| **Agents** | Agent | Name, model, capabilities, the agent's brief |

Pick one dataset or take everything.

## CSV or Excel

| You ask for | You get |
|---|---|
| One dataset, CSV | A single `.csv` file |
| Several datasets, CSV | A `.zip` with one CSV per dataset |
| Any number, Excel | One `.xlsx` workbook with a sheet per dataset |

A CSV holds one table, which is why several of them arrive zipped. A workbook
does not, so choosing Excel gives you one file with tabs instead of an archive
to unpack.

<Aside type="tip" title="Excel keeps your identifiers intact">
Product codes like `007`, long barcodes and reference numbers stay exactly as
written. Spreadsheets normally read those as numbers and quietly drop the
leading zeros or round the long ones; the export deliberately keeps every cell
as text so your identifiers survive the trip.
</Aside>

## Two speeds, and you do not choose

<Figure
  label="How an export is delivered depending on its size"
  caption="The split is automatic. You never pick a delivery method, and near the line the platform prefers the email path so a large file never holds up your browser."
>
<svg viewBox="0 0 700 190" xmlns="http://www.w3.org/2000/svg">
  <text x="0" y="14" class="d-eyebrow">ONE REQUEST, TWO PATHS</text>

  <rect x="0" y="30" width="150" height="46" rx="8" class="d-box" />
  <text x="14" y="50" class="d-label">You ask</text>
  <text x="14" y="66" class="d-sub">pick datasets</text>

  <path d="M154 53 L168 53" class="d-arrow" />
  <polygon points="174,53 167,49.5 167,56.5" class="d-arrow-head" />

  <rect x="186" y="6" width="240" height="44" rx="8" class="d-box-accent d-pulse" />
  <text x="200" y="26" class="d-label">Small and single</text>
  <text x="200" y="42" class="d-sub">downloads straight away</text>

  <rect x="186" y="62" width="240" height="44" rx="8" class="d-box" />
  <text x="200" y="82" class="d-label">Large, or several</text>
  <text x="200" y="98" class="d-sub">built in the background</text>

  <path d="M430 28 L444 28" class="d-arrow" />
  <polygon points="450,28 443,24.5 443,31.5" class="d-arrow-head" />
  <rect x="456" y="6" width="242" height="44" rx="8" class="d-box" />
  <text x="470" y="26" class="d-label">In your browser</text>
  <text x="470" y="42" class="d-sub">no email, no waiting</text>

  <path d="M430 84 L444 84" class="d-arrow" />
  <polygon points="450,84 443,80.5 443,87.5" class="d-arrow-head" />
  <rect x="456" y="62" width="242" height="44" rx="8" class="d-box" />
  <text x="470" y="82" class="d-label">Emailed to you</text>
  <text x="470" y="98" class="d-sub">a private, expiring link</text>

  <text x="186" y="140" class="d-accent-text">both paths are recorded, so every export of customer data is on the record</text>
</svg>
</Figure>

**Small and single** means one dataset of modest size: a few hundred catalog
items, a contact list. It is built while you wait and downloads immediately.

**Everything else** is built in the background and emailed to you as a private
link. That covers a whole-workspace export, several datasets at once, and any
single dataset large enough that building it in the browser would keep you
waiting.

<Aside type="tip" title="Why the big ones go by email">
Conversations and messages grow forever. A workspace that has been busy for a
year can produce a file large enough that building it during a page load would
simply time out. The background path has no such limit.
</Aside>

## Download links expire

An emailed link is private and time-limited. When it lapses, the file itself is
deleted, not just hidden.

This is deliberate. An export is a complete copy of your customer list sitting
behind a URL, and a link that worked forever would be a copy of your customer
data living somewhere you had forgotten about. If you need it again, run the
export again.

<Aside type="caution" title="Treat the link like the data">
Anyone with the link can download the file for as long as it lasts. Send it to
a person, not a channel, and do not paste it into a shared document.
</Aside>

Opening an export from the console refreshes its link if it is close to
lapsing, so a slightly stale page still gives you a working download. It does
not extend how long the data is kept.

## Every export is recorded

Both paths write an entry: what was exported, by whom, and when. Instant
downloads are recorded exactly like emailed ones.

An export is one of the few actions that removes a complete copy of customer
data from the platform, so the record exists whether or not the export
involved an email, and it is visible under
[Data and privacy](/workspace/data-and-privacy/).

## Deleting a workspace deletes its exports

If you erase a workspace, its exports go with it. The files are removed and the
links stop working, without waiting for them to expire on their own.

An export is a copy of exactly the data an erasure is meant to destroy, so
leaving it behind would make the erasure untrue. Cancelling an erasure inside
its grace window leaves your exports alone.

## Practical notes

- **CSV opens everywhere.** Spreadsheets, database importers, other CRMs. Long
  text like descriptions and message bodies is quoted correctly, so a
  conversation containing a comma or a line break survives the round trip.
- **Messages honour deletions.** Deleted messages are left out, and content
  that was erased on request is marked rather than restored. A previously
  purged message never reappears in an export.
- **Agent exports carry the brief, not credentials.** You get the agent's
  configuration and prompt. Provider keys and connection secrets are never
  included.
- **Re-run rather than re-share.** Because links expire and files are deleted,
  the reliable way to get a file to someone later is a fresh export.