# Guide: Add your wallet as a wallet migration option

We are very excited that your team would like to add your wallet as a migration option for Near Wallet users to help with our efforts with the [wallet transition](https://near.org/blog/update-on-the-near-wallet-transition/) to give users more wallet options to choose from. To help onboard more wallets, we have created this guide to help you.

## Wallet Requirements

- Your wallet must support **batch import of private keys**
- **Wallet Security is very important** and we strongly advise that your wallet has gotten proper auditing done.
- Make sure your wallet does not log private/sensitive information about users.

## PR instructions

1. Fork [Near/Near-wallet](https://github.com/near/near-wallet)
2. Create a new branch e.g walletName/add-wallet-option
3. Add your wallet **at the end** of the `WALLET_OPTIONS` array like [such](https://github.com/near/near-wallet/blob/5611ce30e161704c02bc9610e98b73737ef58988/packages/frontend/src/components/wallet-migration/SelectDestinationWallet.jsx#L55-L59)
4. If your wallet is a mobile only wallet, then add `checkAvailability: () => isMobile()` like FiNER's Mobile Wallet in [this Pull Request](https://github.com/near/near-wallet/pull/2903/files#diff-133f50f707eb791d6963507c2cdb6f305d087105bb4484ffc3a44a1af9928d55R53)
5. Test your changes locally and ensure that changes show up on relevant devices only.

## Tips
- Make sure URL of the wallet is static. e.g. don't dynamically resolve the Wallet URL through a link.
- Use SVG image in logo if possible.
- Make sure the diff of the PR is as clean as possible so we can review it and approve it faster.
- Follow Naming conventions. e.g name your image file as ImgWalletName.svg, e.t.c.