> For the complete documentation index, see [llms.txt](https://docs-new.klayswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-new.klayswap.com/book-en/product/v3-pool/v2-to-v3-migration/v2-to-v3-migration-policy.md).
# V2 to V3 Migration Policy
## Migration Policy
1\) Migrating from V2 pool to V3 pool usually involves the following steps:
**Approve (asset approval) - remove asset from V2 pool - supply asset to V3 pool.**
2\) In order to remove assets, you must have an LP NFT asset, corresponding to the supply certificate, in your wallet and the NFT asset approval transaction must be completed. When a transaction is executed on the Klaytn chain, a fee is incurred. It is the wallet (key) owner's right to transfer the LP token asset; therefore, if the asset is transferred to another wallet, it cannot be removed.
3\) During the removal process, the difference between the price at the time of supply and removal may result in asset loss. Due to balance changes, your wallet will automatically receive all rewards distributed up to that point (pool usage fee profit, KSP, airdrop tokens, etc.).
4\) Removed assets are automatically supplied at an optimal rate based on the pool exchange rate of the price range the user selects by the smart contract.
5\) Assets removed from the V2 pool are supplied into the V3 pool at maximum, based on the price ratio selected by the user.
6\) When supplying in a new V3 pool price range, supplies are only permitted within the transaction range (Slippage) set by the user, and if the range is exceeded, the supply transaction may not proceed. Please proceed with the supply after checking all related information in the estimated returns section at the bottom.
7\) Some assets (wei) may remain after supplying to the V3 pool, and the remainder will be automatically returned to the user's wallet.
---
# 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-new.klayswap.com/book-en/product/v3-pool/v2-to-v3-migration/v2-to-v3-migration-policy.md?ask=&goal=
```
`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.