> 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/engage/community-relationships/export.md).

# Export

The Community Relationships (CRM) export generates an Excel (.xlsx) workbook containing your contact records and their interaction history. The export includes contact details and interactions across multiple worksheets.

## Getting Started

To export community relationships, navigate to the Community Relationships (CRM) list under the **Engage** menu and click the **Export** button. The export includes all contacts matching your current filters.

![Screenshot: The Community Relationships list view with the Export button highlighted and active filter options visible above the contacts table](/files/ic55oIxjeEjYow4pg1rf)

{% hint style="info" %}
**TIP:** Apply filters before exporting to limit the results to a specific unit, category, or search term. 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 **person\_id** column.

* **Codebook** — Describes each column in the workbook and provides notes about the exported data.
* **Contacts** — One row per contact with fields including name, title, email addresses, phone numbers, mailing address, organization site, unit, demographics (gender, age, race, ethnicity), categories, communication preferences, social media links (Facebook, X/Twitter, and Instagram), and custom data.
* **Interactions** — One row per interaction, including the contact(s) involved, the PEARS user who created it, interaction date and time, length, communication method, program areas, and notes.


---

# 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/engage/community-relationships/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.