> For the complete documentation index, see [llms.txt](https://docs.uncx.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uncx.network/guides/for-developers/liquidity-lockers/lockers-v3/technical-reference/nft-migrator-v3.md).

# NFT Migrator V3

## Functions Write <a href="#functions-write" id="functions-write"></a>

### Migrate <a href="#migrate" id="migrate"></a>

```
function migrate (    uint256 _lockId,     INonfungiblePositionManager _nftPositionManager,     uint256 _tokenId)     external returns (bool)
```

Enables migration of liqudity from Uniswap Locker V2 into Locker V3.

Parameters:

| Name                 | Type                        | Description                                                                            |
| -------------------- | --------------------------- | -------------------------------------------------------------------------------------- |
| \_lockId             | uint256                     | ID of the lock to be migrated from the older contract.                                 |
| \_nftPositionManager | INonfungiblePositionManager | The position manager for the NFT.                                                      |
| \_tokenId            | uint256                     | ID of the NFT token to be transferred and then approved for the new reserves contract. |

Return Values:

| Type | Description                                                          |
| ---- | -------------------------------------------------------------------- |
| bool | Returns `true` once the migration process is successfully completed. |

## Functions Wiew <a href="#functions-wiew" id="functions-wiew"></a>

### OnERC721Received <a href="#onerc721received" id="onerc721received"></a>

Parameters:

| Name     | Type    | Description                                                                                 |
| -------- | ------- | ------------------------------------------------------------------------------------------- |
| operator | address | Address initiating the transfer or creation. This could be an external or contract address. |
| from     | address | Address from which the token was sent.                                                      |
| tokenId  | uint256 | Unique identifier for the token being transferred.                                          |
| data     | bytes   | Additional data accompanying the transfer or minting call.                                  |

Return Values:

| Type   | Description                                                                                 |
| ------ | ------------------------------------------------------------------------------------------- |
| bytes4 | Function selector for the `onERC721Received` function, confirming successful token receipt. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uncx.network/guides/for-developers/liquidity-lockers/lockers-v3/technical-reference/nft-migrator-v3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
