> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/using-oisy-wallet/how-tos/migrating-wallets.md).

# Migrating Wallets

If you’re moving your assets from another wallet to OISY Wallet, follow these steps carefully to ensure a smooth migration.<br>

### Step 1: Retrieve Your OISY Wallet Address

1\. Open OISY Wallet at [OISY.com](https://OISY.com).

2\. Click ‘Receive’ on the main dashboard.

3\. Select the blockchain network corresponding to the tokens you’re transferring.

4\. Copy the wallet address displayed or scan the QR code.

📌 *Make sure the selected network matches the tokens you’re migrating—sending assets to an incorrect network can result in loss.*

### Step 2: Send Assets from Your Existing Wallet

1\. Open the wallet you are migrating from (e.g., Metamask, Phantom, NFID, or another crypto wallet).

2\. Navigate to the ‘Send’ or ‘Transfer’ function.

3\. Paste the OISY Wallet address you copied earlier in the recipient field.

4\. Select the correct token and network for the transfer.

5\. Enter the amount you want to send.

6\. Double-check that all details are correct, then confirm and submit the transaction.

📌 *Depending on the network, you may need to pay a gas fee to process the transfer. Fees vary by blockchain.*

### Step 3: Verify Assets in OISY Wallet

1\. After sending, return to OISY Wallet.

2\. Go to ‘Assets’ and check if the transferred tokens appear.

3\. If the tokens do not show up immediately:

* Wait a few minutes—some networks take longer to process transactions.
* Click ‘Manage Tokens’ and search for the token.
* &#x20;If the token is missing, follow the steps in ‘[Managing & Adding Tokens](/using-oisy-wallet/how-tos/managing-and-adding-tokens.md)’ to manually import it.

📌 *Blockchain congestion or network delays may impact how quickly your assets appear in OISY Wallet. If you experience delays, check the transaction status on a blockchain explorer (e.g., Etherscan, Solscan, or ICScan).*

### Important Notes on Migration

* You may need to transfer tokens individually—some wallets do not support bulk transfers.
* Certain wallets charge withdrawal fees, so check the cost before initiating a migration.
* If you encounter issues, refer to ‘[Managing & Adding Tokens](/using-oisy-wallet/how-tos/managing-and-adding-tokens.md)’ or reach out to OISY Support for assistance.

✅ Once the transaction is complete, your assets will be available in OISY Wallet, and you can begin using them across supported dApps and DeFi protocols.


---

# 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.oisy.com/using-oisy-wallet/how-tos/migrating-wallets.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.