> 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/rdm/ribbon-menu-bar/file/import/import--json.md).

# Import (.json)

Import Remote Desktop Manager entries from a JSON file, choosing the destination folder and selecting which entries to bring in.

Remote Desktop Manager allows you to import entries from JSON files stored on your computer.

{% hint style="info" %}
For an overview of the JSON file format and the impact of decisions made in this entry, see [JSON import strategies and file format](/rdm/ribbon-menu-bar/file/import/import--json/json-import-strategies-and-file-format.md).
{% endhint %}

### Steps

1. In the ***navigation pane***, select the vault in which to import the entries.
2. Go to ***File – Import – Import (.json)***.
3. Select the JSON file to import from your computer, then click ***Open***.
4. Choose to ***Import in root***, ***Import in current folder***, or ***Import in specific folder***.
5. In the next dialog box, a list of all the entries that are in the data file will be displayed. Select specific entries you wish to import or ***Select All*** to import all of your entries.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>If you have users who override entry properties with <em><strong>User-specific settings</strong></em> , uncheck <em><strong>Change ID</strong></em>.</p></div>
6. Click ***OK***. The import will proceed using your chosen settings.


---

# 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/rdm/ribbon-menu-bar/file/import/import--json.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.