> 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/cloud/es/web-interface/help-and-tools/import.md).

# Importar

Importe ficheros de entradas JSON y CSV a Devolutions Cloud desde RDM, Bitwarden, Chrome, KeePass, LastPass y 1Password en una bóveda y una carpeta elegidas.

Importe ficheros de entradas JSON y CSV en Devolutions Cloud.

1. En ***Ayuda y herramientas***, haga clic en ***Importar***.
2. Seleccione el formato del fichero importado (JSON o CSV) entre las siguientes opciones:
   * RDM (.json)
   * Bitwarden (.json)
   * Bitwarden (.csv)
   * Google Chrome (.csv)
   * KeePass (.csv)
   * LastPass (.csv)
   * 1Password (.csv)
3. Suba el fichero (uno a la vez) a Devolutions Cloud arrastrándolo y soltándolo directamente o seleccionando un fichero mediante el explorador de ficheros de su dispositivo.
4. Seleccione una ***Bóveda de destino*** (solo Devolutions Cloud) y una ***Carpeta de destino***, o cree una nueva carpeta. Ahí es donde se importan las entradas.
5. Haga clic en ***Importar***.
6. Aparecerá un resumen de todas las entradas que se van a importar. Haga clic en ***Completar importación***.

   El proceso de importación tarda un tiempo en función del tamaño de su fichero. Una vez importado el fichero, se le llevará al lugar donde se encuentran las entradas.


---

# 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/cloud/es/web-interface/help-and-tools/import.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.
