> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/drive-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/drive-support/playbooks/transfer-a-drive.md).

# Transfer a Drive

**What you'll do:** Move or reassign your Drive to another device or owner, while your Vault data stays isolated and intact.

**Why it matters:** Under the separated **Drive & Vault** model, your everyday Drive and your security-first Vaults are handled independently. Transferring a Drive lets you hand off or relocate everyday storage without touching Vault contents.

**Steps**

1. Open the Drive's actions and choose **Transfer Drive**.
2. Follow the prompts to reassign the Drive to the target device or account.
3. Confirm. The Drive moves; **Vault data remains isolated** and is not affected by the transfer.
4. On the receiving side, sign in and open the Drive to access it.

**Good to know**

* **Restore vs transfer.** To simply set up your *own* Drive on a new device, use [Add a new device](/drive-support/playbooks/add-a-new-device.md) with your User Recovery Key. Transfer is for reassigning ownership/location.
* **Restore Drive with User Key.** Under the separated model you can restore Drive access using your personal User Key, preserving end-to-end encryption.
* Sync state for Drive and Vault is tracked separately, so each shows its own real-time status.

**Common mistakes**

* **Assuming a Drive transfer moves your Vaults too.** It doesn't — Vaults are independent by design.
* **Transferring without confirming sync completed**, leaving the destination without the latest data.