> For the complete documentation index, see [llms.txt](https://academy.decisionrules.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.decisionrules.io/rules/export-and-import-of-the-rules/export-rule.md).
# Export Rule
### Exporting from Rule List
As you know, your decision rules can be accessed from the “Rules” in the left sidebar menu. From there you can export your rule by clicking on the context menu button **...** according to that rule, and choosing **Export** .
Export Rule from Rule List
### Exporting from Rule Structure Design
At the top bar of your 'Rule' you can do various actions. Select the context menu button **...** and a dropdown list will appear. Click on **Export** .
Export Rule from Rule Structure Design
## Choose export format
### Choosing export format of Decision Table:
When exporting the decision table you can choose from two different file formats based on your further actions. For transporting rules to another space you can choose JSON format. If you want to modify a decision table and for example input more data in it, choose XLSX format.
### Choosing export format of other Rule types:
Other rule types - Rule Flows, Decision Tree and Scripting rule have a single export option - JSON format. These types should be created and modified in the DecisionRules application.
Once you choose the right format, your export will start automatically. The exported file can be found where your browser stores downloaded files.
{% hint style="info" %}
*These are manual methods of exporting rules. Using Management API methods and external tools you can export rules in one click. More information about API functioning can be found in documentation link* [*here*](https://docs.decisionrules.io/doc/api/api-introduction)
{% 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 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://academy.decisionrules.io/rules/export-and-import-of-the-rules/export-rule.md?ask=&goal=
```
`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.