Moving NFTs to a new wallet is usually straightforward, but a wrong address, network, or approval can make recovery difficult or impossible. This guide provides a reusable migration checklist for transferring NFTs safely, confirming ownership and metadata, reconnecting marketplaces, and documenting the new wallet before you move valuable assets.
Overview
An NFT transfer changes the blockchain address that controls a token. It does not normally rewrite the token’s metadata or replace the media referenced by the token. However, wallets and marketplaces may need time to index the new ownership, and some applications may require you to reconnect the new wallet before your collection, profile, or token-gated access appears correctly.
Before starting an NFT wallet migration, identify four things:
- The source wallet: the address currently holding the NFT.
- The destination wallet: the new address that should receive it.
- The network: such as an EVM-compatible network or Solana. The destination must support the network and token standard involved.
- The transfer method: a wallet app, marketplace, hardware wallet, or application using WalletConnect.
Use a destination wallet that you control and have already secured. Write down its recovery instructions according to the wallet provider’s documented process, and never share a recovery phrase or private key with another person, website, support account, or “verification” service. For broader wallet selection and custody considerations, see our guide to choosing the best NFT wallet for security, trading, and multi-chain storage.
Checklist by scenario
1. Moving an NFT between two wallets you control
- Prepare the destination wallet. Create or import it using the wallet’s official software. Confirm that the wallet supports the relevant chain and token type, such as ERC-721 or ERC-1155. A wallet that displays one network’s NFTs may not support every other network.
- Copy the destination address. Copy it directly from the destination wallet rather than typing it. Compare the first and last several characters, and confirm that the address format matches the selected network.
- Fund the source wallet for network fees. The asset may be free to transfer, but the transaction can still require the network’s native asset for gas. Estimate the transfer cost shortly before acting because network fees can change. Our NFT gas fee calculator guide explains the inputs to check.
- Open the send function. Select the exact collection and token ID, then choose “send” or the equivalent command. If the asset is held through a marketplace contract or a smart contract wallet, confirm that the platform supports direct transfers.
- Paste and verify the address. Do not approve a transaction if the address changes after pasting, appears truncated in a misleading way, or was supplied through an unsolicited message.
- Send a test first when practical. For a high-value collection, test the workflow with a low-value NFT or another asset on the same network. A small test confirms that the destination wallet, chain, and receiving interface behave as expected; it does not guarantee that every future transfer will be safe.
- Review the wallet confirmation. Check the token, recipient, network, and fee on the wallet’s signing screen. If using a hardware wallet, verify the destination address on the device’s own display, not only on the computer or phone screen.
- Wait for confirmation. Save the transaction hash and verify ownership using a reputable block explorer or the destination wallet. Marketplace display may lag behind the confirmed blockchain state.
2. Replacing a compromised or exposed wallet
If the source wallet may be compromised, prioritize speed and isolation over convenience. Create a clean destination wallet on a trusted device, secure it before receiving assets, and avoid signing unrelated messages. Move valuable NFTs first, then review token approvals and connected applications. An NFT transfer does not automatically revoke permissions previously granted to marketplace or smart contract addresses. Approval management is network- and tool-specific, so use a trusted interface and read each action carefully.
Do not send funds or NFTs to an address supplied by someone claiming to “rescue” your wallet unless you independently verified the address and the process. If an attacker controls the source wallet, they may be able to move assets as soon as funds arrive for gas.
3. Moving NFTs to a hardware wallet
Set up the hardware wallet according to its official instructions, record the recovery information offline, and confirm that the hardware device supports the required network and asset type. Connect it only through the official wallet software or a trusted connection flow. When transferring, verify the destination address on the hardware device itself. Afterward, disconnect the device and confirm that the NFT appears in the intended account.
A hardware wallet protects signing keys, but it does not make an unsafe transaction safe. You still need to check the recipient, contract, network, and requested permissions.
4. Relinking a marketplace, game, or token-gated service
After the blockchain confirms the transfer, disconnect the old wallet from applications that no longer need access. Connect the new wallet using the service’s normal connection flow, and verify that the selected account and network are correct. Some applications identify users by wallet address, so profile history, listings, game progress, or access rights may not migrate automatically.
For applications using WalletConnect, review the requested chain and signature before approving. Our WalletConnect NFT integration guide covers connection, chain switching, and signature handling. If the NFT controls access to a service, check its verification and revocation rules rather than assuming ownership will update immediately.
What to double-check
- Network compatibility: An address can look valid while being used on the wrong network. Select the network where the NFT is actually recorded.
- Token standard and collection: Confirm the contract address and token ID, not only the artwork thumbnail or collection name. Similar names and copied images can be used in scams.
- Metadata behavior: A transfer generally changes ownership, not the token’s metadata. If the image or traits look wrong, wait for indexing and check the contract and token URI before taking further action.
- Marketplace listings: Cancel or review active listings before moving an NFT. A platform may have separate requirements for delisting, custody, or approval changes.
- Approvals: Review existing marketplace and contract permissions, especially after a security incident. Transferring an NFT is not the same as revoking an approval.
- Gas funding: Keep only the amount needed for the planned operation in a wallet that may be exposed. Confirm the fee asset required by the selected network.
- Transaction status: A submitted transaction is not necessarily confirmed. Keep the transaction hash and check the recipient and token on-chain.
- Recovery records: Document the new wallet address, network, account label, hardware device identifier if relevant, and the date of migration. Store this inventory separately from the recovery phrase.
Common mistakes
Sending to an address copied from a message: Clipboard-replacement malware, address poisoning, and social engineering can alter or disguise addresses. Always verify the complete address in the wallet or hardware device.
Assuming every wallet supports every NFT: An NFT may be on a chain or standard that the new wallet does not display. Lack of display is not proof that the asset is lost, but it should be resolved before transferring valuable items.
Using a bridge when a normal transfer is required: A bridge can create a wrapped or representation asset rather than moving the original token. Use the collection’s documented process and confirm what asset will exist on the destination network.
Signing an unexplained approval: A transfer prompt should identify the intended NFT and recipient. Stop if the wallet requests an unrelated unlimited approval, blind signature, or contract interaction you do not understand.
Sharing the recovery phrase to fix a problem: Legitimate wallet support does not need your secret recovery phrase. If it has been exposed, treat the wallet as unsafe and migrate assets to a newly secured wallet.
Deleting the old wallet too soon: Keep the source wallet securely documented until you have verified every transfer, canceled or reviewed relevant listings, and completed any required access migration.
When to revisit
Use this checklist whenever you replace a device, rotate custody, respond to a suspected compromise, move assets into cold storage, change marketplaces, or prepare for a major collection or gaming launch. Recheck the workflow before seasonal planning cycles and whenever a wallet, marketplace, network, or hardware-wallet interface changes.
For each migration, record the destination address and network, test transaction result, transaction hashes, marketplace status, approval review, and final ownership check. Revisit the record if an NFT fails to appear, metadata looks delayed, token-gated access does not update, or an application asks for an unexpected signature. For ongoing custody practices, pair this process with how to store NFTs safely. A deliberate transfer takes longer than a rushed one, but it gives you clear checkpoints before an irreversible transaction is signed.