> ## Documentation Index
> Fetch the complete documentation index at: https://yieldxyz.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from OAV v1 & v2

> OAVs run behind upgradeable proxies, so moving a vault from v1 or v2 to the current implementation does not change its address or require user action.

OAV contracts are deployed behind upgradeable proxies. Moving an existing OAV from its v1 or v2 implementation to the current OAV v3 implementation is a proxy upgrade yield.xyz performs: the vault's address, its share token, and user balances are unchanged. Users do not withdraw and redeposit, and you do not need to redeploy or re-point your integration.

## What changed since v1

| Version | What it adds |
| - | - |
| v1 | ERC-4626 vault with deposit, performance, and management fees |
| v2 | Adds whitelisted reward-token claiming, so incentive tokens can be pulled out of the strategy and reinvested |
| v3 | Refines deposit-fee share accounting, adds a dedicated pauser role and a deposits-only pause switch, and adds a configurable reward-forwarding address for reinvestment |

v1 vaults have no reward-claiming mechanism: incentive tokens paid by the underlying strategy accumulate unclaimed unless the vault is upgraded. See [OAV v3](/documentation/platform/vaults/oav-v3) for the current fee and reward-handling model, and [automatic off-ramping](/documentation/platform/vaults/oav-mechanics/automatic-off-ramping) for how reward claiming works once available.

## What stays the same for your integration

The ERC-4626 interface (`deposit`, `withdraw`, `mint`, `redeem`) and the Yield API surface do not change with a vault's implementation version. If you integrate through the Yield API:

| Endpoint | Purpose |
| - | - |
| `GET /v1/yields` | Discover the vault, its APY, and TVL |
| `POST /v1/yields/balances` | Fetch current positions |
| `POST /v1/actions/enter` | Generate the deposit flow |
| `POST /v1/actions/exit` | Generate the withdrawal flow |

An upgrade to a newer implementation changes what the vault can do (for example, whether it can claim reward tokens) but not how you call it.

## Requesting an upgrade

Contact yield.xyz to upgrade an existing v1 or v2 vault to the current implementation. Because fee accounting depends on the vault's recorded asset value at the time of upgrade, yield.xyz performs a one-time reconciliation as part of the upgrade so the next fee calculation does not compute a false gain or loss from the change.

## Next steps

<Columns cols={2}>
  <Card title="OAV v3" icon="circle" href="/documentation/platform/vaults/oav-v3">
    Vault mechanics, fees, and reward handling on the current implementation.
  </Card>

  <Card title="Off-the-shelf OAVs" icon="store" href="/documentation/platform/vaults/off-the-shelf-oavs">
    Pre-deployed OAVs already running the current implementation.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.