> 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/password-manager/knowledge-base/application-knowledge-base/transfer-otp-storage-in-devolutions-password-manager.md).

# Transfer OTP storage in Devolutions Password Manager

Transfer OTP storage from the Authenticator section to a Devolutions Cloud or Devolutions Server workspace in Devolutions Password Manager on mobile.

Transfer your one-time password (OTP) storage from the **Authenticator** section to a Devolutions Cloud or Devolutions Server workspace in Devolutions Password Manager.

1. Open Devolutions Password Manager.
2. In the ***Authenticator*** section, tap ***Transfer***.
3. Select the workspace where you want to store your OTPs. If the workspace is not available, connect to it first.
4. Tap ***Transfer*** to confirm. Your OTPs are transferred to the selected workspace.
5. Select the workspace.
6. Open the OTPs section to view the OTPs stored in the workspace.
7. Confirm that your OTP entries are available.

#### Expected result

* OTP storage is transferred to the selected workspace.
* The ***Authenticator*** phase-out message no longer requires any action.
* Existing OTP entries, if any, are available from the OTPs section of the selected workspace.


---

# 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/password-manager/knowledge-base/application-knowledge-base/transfer-otp-storage-in-devolutions-password-manager.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.