> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/data-and-platform-administration/event-forwarding-and-data-portability.md).

# Event forwarding and data portability

Learn how to export Cortex XDR event data, query results, detection rules, playbooks, scripts, and layouts for integration or migration.

You can export your data and the content you build, for archiving, integration with other tools, or migration.

| What                        | How                                                                                                              | Format                               |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| Ingested and parsed data    | **Event Forwarding** add-on. Data is exported to a temporary Google Cloud Storage bucket, available for 14 days. | Line-delimited JSON, gzip-compressed |
| Query results               | XQL Search export, or the XQL APIs                                                                               | TSV or JSON                          |
| Correlation rules           | Export from the rules table, or with the API                                                                     | JSON (XQL logic)                     |
| Playbooks, scripts, layouts | Export individual items or a custom content bundle                                                               | YAML and JSON                        |
| Agents                      | Uninstall in bulk from the console                                                                               | Not applicable                       |

### Event Forwarding

Enable **GB Event Forwarding** (non-endpoint data, such as firewall, cloud, and identity logs), **Endpoints Event Forwarding** (raw endpoint telemetry), or both. Cortex XDR creates the bucket and gives you the path and service account credentials. Optionally subscribe to the Pub/Sub topic to be notified of new files; messages are available for 7 days. Data can take up to two hours to appear. See [Manage Event Forwarding](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/data-management/manage-event-forwarding).

{% hint style="info" %}
Playbooks and detection rules are exported in open formats (YAML, JSON, and XQL text). Another platform needs to translate the logic into its own language.
{% endhint %}


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/data-and-platform-administration/event-forwarding-and-data-portability.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.