> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/reflect/success-stories/export.md).

# Export

The Success Stories export generates an Excel (.xlsx) workbook containing data from your success stories. The export includes story details, collaborators, and partners across multiple worksheets.

## Getting Started

To export success stories, navigate to the Success Stories list under the **Reflect** menu and click the **Export** button. The export includes all success stories matching your current filters.

{% hint style="info" %}
**TIP:** Apply filters before exporting to limit the results to a specific reporting period, program area, or completion status. Large exports are processed in the background and you will receive an email when the file is ready to download.
{% endhint %}

## Workbook Structure

The export workbook contains the following worksheets. Data can be linked across worksheets using the **story\_id** column.

* **Codebook** — Describes each column in the workbook and provides notes about the exported data.
* **Success Story Data** — One row per success story with fields including title, reporting periods, organization, unit, program areas, site details, linked program activity and action plan(s), keywords, background, story narrative, favorite quote, priority indicators, socioecological frameworks, approaches, and timestamps.
* **Collaborators** — One row per collaborator per success story, including the user's name, access level, contributor status, and contribution description.

### Conditional Worksheets

* **Partners** — Included when the partnerships feature is enabled and success stories have associated partners. Lists each partner's name, contributions, and linked partnership ID.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.pears.io/reflect/success-stories/export.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.