> 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/web-interface/administration/templates/entry-templates/import-entry-templates.md).

# Import entry templates

Import previously exported Entry Templates into Devolutions Server from Rdm, KeePass Xml, or Google Password Csv files through the Add New Entry window.

Import previously exported ***Entry Templates*** in the web interface of Devolutions Server.

{% hint style="warning" %}
The import format can only be ***Import (.Rdm)*** , ***KeePass (.Xml)*** or ***Google Password (.Csv)*** files.
{% endhint %}

#### Import entry templates

1. In the web interface of Devolutions Server, select a vault.
2. Click the ***Add*** button.
3. In the ***Add New Entry*** window, click ***Import*** and select ***Import (.Rdm)***.
4. Drag and drop or click to upload the ***.rdm*** file.
5. Click ***Next***.
6. In the ***Analyze*** step, you can validate each entry template ***Actions*** and change it to ***Ignore***. This will result by not importing these specific templates. Click ***Next***.
7. Click ***Import*** and ***Close*** the import window.

The imported list of ***Entry Templates*** are now showing in ***Administration – Entry Templates*** and are available to use in the ***Template*** section when creating a new entry.


---

# 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/web-interface/administration/templates/entry-templates/import-entry-templates.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.