> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/integrations-and-data-exchange/imports-exports/exports/configuration-exports.md).
# Configuration Exports
Find how to export the configuration of listed modules from the admin panel.
{% hint style="warning" %}
Please be aware that certain configurations may rely on other modules, such as a campaign that issues a reward or a reward that targets a specific tier or segment. These dependencies must be imported or created beforehand.
After each configuration import, you will receive a notification prompting you to adjust the imported settings to address any missing dependencies.
{% endhint %}
## Campaigns
You can export any number of campaigns and save it as a JSON file for later upload.
## Achievements
You can export any number of achievements and save it as a JSON file for later upload.
***
## Custom Event Schemas
You can export any number of custom event schemas and save them as a JSON file for later upload.
***
## Wallets
You can export any number of wallets and save them as a JSON file for later upload.
***
## Rewards
You can export any number of rewards and save them as a JSON file for later upload.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/implementation-guide/integrations-and-data-exchange/imports-exports/exports/configuration-exports.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
