> For the complete documentation index, see [llms.txt](https://docs.eth.solhuger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eth.solhuger.com/project/transfer.md).

# Transfer

Move tokens between wallets.

Go to **Project → Transfer**.

<figure><img src="https://437700151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg55WaahfDDbRuav0Znxp%2Fuploads%2Fgit-blob-ed122e73487f7b886b5410e092cd2837c5cff2b1%2F10-transfer.png?alt=media" alt="Transfer tokens page"><figcaption><p>Transfer tokens page</p></figcaption></figure>

## Toolbar

**Download Wallets**, **Set Anti-Drainer** and **Set Blacklist**, which work as described on the [Sell](https://docs.eth.solhuger.com/project/sell.md) page.

## Wallets table

| Column                  | Description           |
| ----------------------- | --------------------- |
| **Address**             | Source wallet         |
| **ETH Balance**         | ETH available for gas |
| **Token Balance**       | Tokens held           |
| **Address To Transfer** | Destination address   |
| **Tokens To Transfer**  | Amount to send        |

## Steps

1. Select the wallets to transfer from.
2. Enter the **Address To Transfer** and **Tokens To Transfer** for each.
3. Set the gas multiplier if needed.
4. Click **Transfer**.

Use **Collect All ETH** with a **Target Wallet** to sweep leftover ETH from all project wallets.

{% hint style="warning" %}
Blockchain transfers are irreversible. Verify every destination address.
{% endhint %}


---

# 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.eth.solhuger.com/project/transfer.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.
