> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/concepts/basic-concepts/import-and-export.md).

# Import and export

Import and export in Devolutions Server move entries, templates, and vaults between instances, supporting rdm files, KeePass XML, and CSV formats.

Import and export in Devolutions Server let you create backups, move entries, templates, and even entire vaults between instances or into other Devolutions products. Administrators can import data from .rdm, KeePass XML, or Google Password CSV files in the web interface, and export vaults when migrating to Devolutions Cloud or seeding test environments. Because these operations can include large sets of credentials, they should be restricted to trusted roles and combined with secure storage for any intermediate files.

For example, you might export a production vault to an encrypted file, then import it into a staging instance to validate new policies before rollout.

#### Related topics

* [Import entry templates](/server/web-interface/administration/templates/entry-templates/import-entry-templates.md)
* [Migrate vaults from Devolutions Server to Devolutions Cloud](/server/knowledge-base/how-to-articles/migrate-vaults-from-devolutions-server-to-devolutions-cloud.md)
* [Backup manager](/server/web-interface/administration/backup/backup-manager.md)


---

# 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://docs.devolutions.net/server/concepts/basic-concepts/import-and-export.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.