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

# Gmail

> Import historical email conversations into Chatarmin CX from a Google Takeout mbox export.

Import historical email conversations into Chatarmin CX from a Google Takeout `.mbox` export.

## When to use it

Use this import when you are moving a Gmail inbox's history into Chatarmin CX — for example when switching your support email to a Chatarmin CX channel and you want prior conversations available in the inbox.

## Before you start

* Create an email channel in Chatarmin CX so imported conversations have a destination.
* Export your mailbox from [Google Takeout](https://takeout.google.com) as `.mbox`.

## Set it up

<Steps>
  <Step title="Export from Google Takeout">
    Go to **Google Takeout**, deselect all products, select only **Mail**, and start the export. Google delivers one `.mbox` file per label/folder you included.
  </Step>

  <Step title="Open the Gmail import">
    Go to **Settings** → **Integrations**, scroll to **Import tickets**, and choose **Gmail**.
  </Step>

  <Step title="Upload your mbox files">
    Upload one or more `.mbox` files (up to 20 files, 200 MB each). Chatarmin CX scans them and shows the number of threads, number of emails, and date range covered.
  </Step>

  <Step title="Map the email channel">
    Choose the channel these conversations should land in, or skip channel mapping.
  </Step>

  <Step title="Review and start">
    Review the preview, confirm, and start the import. Watch live progress and cancel if needed.
  </Step>
</Steps>

## How mbox files map to tickets

* Chatarmin CX groups messages into threads using Gmail's internal thread ID, so each Gmail conversation becomes one ticket.
* Gmail's **Sent** label tells Chatarmin CX which messages came from your team versus the customer.
* Draft messages are skipped.
* Imported tickets are created as **closed**, tagged **gmail-import**, and excluded from AI auto-replies — they're historical records, not live conversations.
* Re-uploading the same file is safe: tickets and messages that were already imported are not duplicated.

## After import

Imported conversations appear in the mapped channel with their original timestamps, message history, and attachments. Review a sample of imported tickets before you point customers or automations at the new workspace.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.