Moving an NFT to a new wallet is usually straightforward, but an incorrect address, network, token ID, or approval can make the result difficult or impossible to recover. This same-chain migration checklist walks you through preparation, address verification, test transfers, marketplace checks, and post-transfer confirmation so you can send an NFT safely and document what changed.
Overview
An NFT transfer changes the blockchain address recorded as the asset’s owner. It does not move the NFT in a traditional app-to-app sense, and a wallet interface may take time to display the updated balance. The transaction must be sent on the network where the NFT currently exists, using a destination address that supports the relevant asset and wallet format.
This guide assumes a same-chain migration: for example, moving an NFT from one Ethereum wallet to another Ethereum-compatible wallet on Ethereum, or moving a Polygon NFT between wallets on Polygon. A same-chain transfer is different from a cross-chain move, which may involve a bridge, wrapped assets, network-specific contracts, and additional risks. For that workflow, see Cross-Chain NFT Transfers Explained.
Before beginning, decide whether the new wallet is a long-term cold wallet, a trading wallet, a creator payment wallet, or a temporary burner wallet. The purpose matters because a wallet used for frequent marketplace connections has a different risk profile from a wallet kept offline. A structured hot, cold, and burner setup may be useful; review NFT Wallet Setup for Collectors for a broader custody workflow.
Keep a record of the collection name, contract address, token ID, source wallet, destination wallet, network, transaction hash, and date. This information helps with portfolio tracking, tax records, payment reconciliation, and later troubleshooting.
Checklist by scenario
Scenario 1: Planned move to a new personal wallet
- Set up the destination wallet first. Create or import it using the wallet provider’s official process. If it is a self-custody wallet, write down the recovery phrase offline and never enter it into a website, form, chat, or support message.
- Confirm the network. Identify the NFT’s current chain and make sure the destination wallet can receive that asset on the same chain. Do not assume that a wallet supporting one network supports every NFT or token standard on that network.
- Copy the destination address. Copy it from the wallet’s receive screen, then compare the first and last several characters with the wallet display. For a high-value NFT, verify the complete address on a trusted device or through an independently confirmed communication channel.
- Fund the correct wallet for gas. The source wallet generally needs the network’s native asset to pay the transfer fee. Review the NFT Gas Fee Planning Guide before initiating several transfers or moving assets during a busy period.
- Open the source wallet’s send flow. Select the exact NFT, check its collection and token ID, paste the destination address, and inspect every transaction detail before signing.
- Use a test transfer when practical. Some collections or wallets allow a low-value NFT to be sent first. A test confirms that the address, network, and receiving interface behave as expected, but it is not a substitute for checking the full destination address. NFTs are often indivisible, so do not assume a test can be reversed or cheaply repeated.
- Sign only after reviewing the final prompt. Check the recipient, network, asset, and fee. Reject any unexpected request to approve an unrelated contract or grant broad spending permission.
- Save the transaction hash. Use a reputable block explorer reached through a known bookmark or the wallet’s trusted interface. Confirm that the transaction is finalized according to the network’s normal transaction behavior before treating the migration as complete.
Scenario 2: Moving NFTs out of a wallet used for trading
If the source wallet has connected to many marketplaces or applications, moving an NFT does not automatically remove old approvals or disconnect those applications. After the asset is secure, review connected apps and token or operator approvals using a reputable wallet approval revoke tool. Revoke only permissions you understand, and remember that revocation itself may require a network fee.
Check whether the NFT is currently listed, escrowed, staked, locked in an application, or used as collateral. A transfer may cancel a listing, make an application position unavailable, or cause a marketplace interface to show stale information. Consult the relevant platform’s current interface and terms before moving an asset involved in an active workflow.
Scenario 3: Responding to a suspected compromise
Do not treat a compromised wallet like a routine migration. Prepare a clean destination wallet on a separate device or trusted wallet environment, and avoid connecting that destination to suspicious sites. Prioritize moving assets that can be transferred without signing risky approvals, but pause if the attacker appears to be monitoring or automatically sweeping the wallet.
Never share a recovery phrase or private key with a person claiming to provide recovery help. Record the suspicious transaction hashes, disconnect questionable applications, and consider getting professional incident-response assistance. The NFT Wallet Security Checklist can help organize the broader review.
Scenario 4: Moving a creator or payment wallet
For a creator, a wallet migration can affect marketplace profiles, royalty or payout settings, checkout integrations, team access, and accounting records. Update only the specific setting that needs to change, and verify the new wallet with a small controlled payment where possible. Keep the old wallet available for recordkeeping, but do not leave valuable assets there solely because a marketplace profile still displays its address. For payment workflows, also review NFT Payment Reconciliation.
What to double-check
Use this quick verification table immediately before signing:
| Item | What to verify | Why it matters |
|---|---|---|
| Network | Source and destination are using the same chain. | A wrong network can prevent the destination interface from recognizing the asset and may require a separate recovery process. |
| Address | The full destination address matches the intended wallet, not only the first and last characters. | Address poisoning, clipboard replacement, and simple copy errors can redirect funds. |
| Collection | Contract address and collection name match the intended NFT. | Similar names can make it easy to select a counterfeit or unrelated asset. |
| Token ID | The token ID is the one you intend to move. | Many collections contain multiple NFTs with similar images or metadata. |
| Transaction type | The wallet is requesting a transfer, not an unexpected approval, signature, or contract interaction. | Approvals can authorize future asset movement without transferring the NFT now. |
| Marketplace status | Listings, loans, staking, escrow, and connected applications have been reviewed. | External workflows may change or restrict what happens after a transfer. |
After confirmation, check the transaction on a trusted block explorer using the contract address and token ID. Then open the destination wallet and, if relevant, the marketplace profile. Wallet interfaces can cache balances, so rely on the confirmed on-chain record rather than an immediate display alone. A portfolio tracker can help compare the source and destination holdings, but treat third-party labels as convenience features and verify important details on-chain. See the NFT Portfolio Trackers guide for tracking considerations.
Common mistakes
- Sending to a marketplace deposit address or contract address. Send only to a wallet address specifically controlled by the intended recipient unless the platform explicitly provides a supported deposit workflow.
- Using a similar-looking address. Do not select an address from transaction history without confirming that it belongs to the intended wallet. Clipboard contents can also be replaced by malicious software.
- Ignoring network differences. An Ethereum-compatible address format does not mean every Ethereum-compatible network or NFT is interchangeable.
- Assuming a transfer removes approvals. Approvals and connected applications need their own review. Moving the NFT does not clean up the source wallet.
- Signing under pressure. Urgent messages, fake support accounts, claim links, and airdrop pages are common reasons people approve the wrong transaction. Close the site and restart from an official bookmark.
- Discarding records. Save transaction hashes, dates, values used for accounting, and the reason for the move. This is especially important for investors, tax filers, creators, and businesses managing multiple wallets.
- Testing from a compromised wallet. If the source wallet may be exposed, avoid unnecessary interactions and do not connect the clean destination wallet to it.
When to revisit
Return to this checklist whenever you replace a phone or hardware wallet, reorganize cold storage, add a trading or burner wallet, respond to phishing, change a creator payment address, or move an NFT connected to a marketplace or application. It is also worth reviewing before seasonal planning cycles, large collection reorganizations, and periods when you expect to make several transfers.
Wallet labels and transaction screens change over time. Before acting, confirm the current network support, token-standard handling, marketplace transfer rules, hardware-wallet prompts, and any fee displayed by the wallet. Do not rely on an old screenshot or a saved workflow if the interface has changed.
Final action list: identify the NFT and network; prepare the destination wallet; verify the complete address independently; fund the source wallet for gas; review listings and approvals; test with a suitable low-value asset when practical; sign only the expected transaction; save the hash; confirm ownership on-chain; then update your portfolio, payment, and tax records. If any detail does not match, stop before signing.