> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/organization-administration/data-exports.md).

# Data exports

Request a multi-part zip export of everything Cogram stores for your organization, for backup, audit, or migration.

As an admin, you can export a snapshot of everything Cogram stores for your organization as multi-part zip files: every project's records and files, and the organization-level data they refer to. The [package layout](https://docs.cogram.com/organization-administration/data-export-package-layout.md) page shows where each kind of record sits in the zip, and the [field reference](https://docs.cogram.com/organization-administration/data-export-field-reference.md), generated from the export itself, lists every record type and every field. Exports run asynchronously in the background; once complete, every part is available to download from the same screen.

Common reasons to run a Data Export:

* Periodic offline backups outside Cogram.
* Audit trails for a specific project or time window.
* Bulk handover at the end of a project or engagement.

Data Exports live in the **Data Exports** section of [Organization Settings → General](https://app.cogram.com/dashboard/settings/admin/overview#data-exports). Only **organization administrators and owners** can see the section and create exports.

## Keep a copy in your own bucket instead

A data export is a snapshot you request and download. To have Cogram copy your organization's data to an Amazon S3 bucket you own, brought up to date every day without anyone requesting it, use [Continuous Data Export (S3 Push)](https://docs.cogram.com/organization-administration/continuous-data-export.md). It writes the same records and files as this export, as plain files instead of zips, except projects created as Cogram examples. The rendered `report.docx` and `observation.docx` files are written only when you turn them on. When a record is removed in Cogram or moves to another project, the next run records the change. In **Archive** mode, the default, its files stay, and its state file says `delete: true`. In **Mirror** mode, Cogram deletes or moves its files. See the two [export modes](https://docs.cogram.com/organization-administration/continuous-data-export.md).

## Choosing a meeting template before exporting

Exports ship meeting minutes as `.docx` files. Cogram provides a default template (**Default Cogram Concise Minutes**), but you can upload your own organization-branded template and mark it as the **Organization Default**. Every meeting `.docx` in subsequent exports will then use your layout.

Go to [Organization Settings → Templates](https://app.cogram.com/dashboard/settings/admin/templates), upload your `.docx`, open the row menu (`⋯`), and choose **Set as Organization Default**:

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-bd3fa9fc55a8bbb7989dc12fabf4639be1daed8a%2F08-templates-set-as-org-default.png?alt=media" alt=""><figcaption><p>The row menu on the Templates page exposes a "Set as Organization Default" action.</p></figcaption></figure>

Once applied, the row gets an **Organization Default** badge. Cogram's provided template stays available as a fallback if your custom template is ever removed.

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-dc2fe7cad09b8f2a1e1f44ea0cbd87bdd08c4546%2F09-templates-org-default-applied.png?alt=media" alt=""><figcaption><p>A custom template marked as Organization Default sits alongside the Cogram-provided templates.</p></figcaption></figure>

> Set the Organization Default **before** kicking off an export: exports use the template that's marked default at the moment the worker renders each meeting's `.docx`.

## The Data Exports section

This section lists every export your organization has created, with its status, scope, time window, who requested it, and when the download links expire.

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-cda910cffdbb1d78ca4a9c62181284e8bb7a345b%2F01-data-exports-page.png?alt=media" alt=""><figcaption><p>The Data Exports section lists every past and active export.</p></figcaption></figure>

Each row shows:

* **Status**: `Pending`, `Running`, `Cancelling`, `Cancelled`, `Completed`, `Failed`, or `Expired`.
* **Requested by**: the user who clicked **New Data Export**, or an `API Key` chip when the export was created via the [Cogram API](https://docs.cogram.com/integrations/cogram-api.md).
* **Scope**: `Org-wide`, `Single Project`, or `N Projects`; hover for the project names, or open the row for the full list. Multi-project exports are created through the [Cogram API](https://docs.cogram.com/integrations/cogram-api.md); the dialog here covers org-wide and single-project.
* **Time window**: the date range, or `All time` for project-scoped exports.
* **Created**: when the export was requested.
* **Expires**: when the download links will be removed (7 days after completion).

## Creating an export

Click **+ New Data Export** in the top-right. The dialog asks for two things: a **scope** and a **time window**.

### Scope: org-wide or a single project

The **Scope** selector lets you target either your entire organization or one project.

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-4d10c77accbc184a958649af0c46f75abd24c820%2F02-create-dialog-project-picker.png?alt=media" alt=""><figcaption><p>Choose between an org-wide export or a single project.</p></figcaption></figure>

### Time window

The available time-window options depend on the scope you picked.

#### Org-wide → date range only (max 6 months)

For org-wide exports, the time window is a **date range**, and capped at **6 months**. This keeps the package size predictable and the build time bounded.

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-c47e3897e70a1a785eb218060299eda6a23ffe3d%2F03-create-dialog-orgwide-daterange.png?alt=media" alt=""><figcaption><p>Org-wide exports always require a date range.</p></figcaption></figure>

The dialog reminds you about the cap inline:

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-c47e3897e70a1a785eb218060299eda6a23ffe3d%2F03-create-dialog-orgwide-daterange.png?alt=media" alt=""><figcaption><p>The 6-month cap is enforced for org-wide exports. To cover a longer span, run several back-to-back exports.</p></figcaption></figure>

#### Project-scoped → All time or a date range

For project-scoped exports, the cap is lifted and an **All time** option is available alongside **Date range**, useful for handovers or full archives of a single project.

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-ec57b224398e03d948624a1a6d51dcc24e2adaf5%2F05-create-dialog-project-alltime.png?alt=media" alt=""><figcaption><p>Project-scoped exports offer the "All time" option.</p></figcaption></figure>

### Rendered documents

Every export ships JSON metadata, `meeting.md`, `meeting.docx`, and the raw files. Select **Include rendered documents** to also get a `.docx` for each field report, and for every observation its report does not already show.

Leave it off when you want the data, the original files, and the meeting minutes only. Rendering reports makes the build slower and the zip larger, and each field report needs the default template of its report type. A report with no template still gets its `.json`. Observations use Cogram's built-in observations template rather than one of yours, and an observation is skipped only when its field report's `.docx` already lays its observations out.

Click **Create Data Export** to start the build. The dialog closes and the new export appears at the top of the list in `Pending` status. It will transition through `Running` and into `Completed` (or `Failed`) as the worker progresses.

> Only **one** export can be active per organization at a time. If a `Pending`, `Running`, or `Cancelling` export already exists, the **+ New Data Export** button will be rejected until it finishes. This keeps the worker queue fair across orgs.

## Downloading a completed export

Once an export reaches `Completed`, a **download icon** appears in its row's **Actions** column.

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-87af0a484eb7136283ebd4023961da8f7d68202d%2F06-list-row-download.png?alt=media" alt=""><figcaption><p>Click the download icon on any completed row to inspect and download the parts.</p></figcaption></figure>

Clicking the icon (or the row itself) opens the **Data Export details** dialog with a per-part download list:

<figure><img src="https://1170756420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpPm3rHOzFMoBqV20UQl%2Fuploads%2Fgit-blob-f3c22741430f30b42540612331f68ab76ce12bc0%2F07-detail-dialog.png?alt=media" alt=""><figcaption><p>Each export is split into one or more zip parts. Click "Download" to grab a part.</p></figcaption></figure>

The detail dialog shows:

* The export's status, scope, time window, who requested it, when it was created, and when its links expire.
* The list of **zip parts**, each with its size and a **Download** button.

Large exports are split into multiple parts so each zip stays a manageable size. Download every part and unzip them into the same folder to reconstruct the full package. For what's inside (the folder structure, file types, and how to tell Cogram's example/demo data apart from your own), see [Data Export Package Layout](https://docs.cogram.com/organization-administration/data-export-package-layout.md#identifying-example--demo-data).

> Each **Download** link is a short-lived signed URL valid for **one hour**. If a link expires before you click it, just reopen the detail dialog; fresh links are minted every time you load it.

## Lifecycle and retention

* **Build time** scales with the volume of meetings, emails, and documents in scope. Most exports finish within minutes.
* **Download links expire one hour after generation**: reopen the detail dialog to mint fresh links.
* **Parts are retained for 7 days after completion**, then transition to `Expired`. The row stays in the list for audit purposes, but the zips are deleted from storage and the **Download** buttons disappear.
* **Cancellation**: `Pending` exports cancel immediately; `Running` exports finish the part they're on and then stop, so cancellation can take a few seconds to settle.

## API access

Everything on this page is also available via the [Cogram API](https://docs.cogram.com/integrations/cogram-api.md#data-exports). Use the API if you want to schedule recurring exports, drop the resulting zips into your own backup pipeline, or run an export from your own internal tools.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cogram.com/organization-administration/data-exports.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
