> For the complete documentation index, see [llms.txt](https://docs.strikebit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strikebit.io/agent-migration.md).

# Agent Migration

Here’s how the migration process works using **AgentHub**:

***

#### **Step 1: Input Contract**

* Navigate to [hub.strikebit.io](https://hub.strikebit.io)
* Click on **"Migrate Agent"**
* Paste your Virtuals ERC20 agent token address

***

#### **Step 2: Fetch Details**

* Click **"Fetch Token Details"**
* StrikeBit automatically retrieves agent metadata (symbol, name, decimals, supply, etc.)

***

#### **Step 3: Define Your Agent**

* Add your custom agent name and image
* Describe the capabilities or intent of your agent (e.g., “trading signals,” “social feed,” etc.)
* Set optional metadata like tier, categories, or skillset

***

#### **Step 4: Upload Holder Snapshot**

* Download your agent’s token holder CSV from [BaseScan](https://basescan.org/)
* Upload the file into AgentHub
* This will be used to generate NFT claim rights for the original token holders

***

#### **Step 5: Verify & Mint**

* Submit for **Binary AI verification** to ensure contract safety and non-malicious origin
* Once verified, **mint your ERC721 NFT agent** on StrikeBit
* The NFT now represents your agent — with ownership, claimability, and future programmability

***

#### **Step 6: Enable Claiming**

* Once the NFT is live, click “Enable Claim”
* This allows all past ERC20 holders to **claim their mirrored agent NFTs** in proportion to their token holdings