# Migration guide ### TL;DR (Quick Start) 1. Open the official migration bot: [**https://t.me/hello\_bitbot**](https://t.me/hello_bitbot) 2. Run: `/migrate` 3. Review the asset list pulled from your Bitbot wallet 4. Tap **Confirm migrate** to move everything to the new infra 5. After a few minutes, open the [EVM\_Bitbot](https://t.me/EVM_Bitbot) and run `/positions` to see your migrated positions 6. If you don’t have an Bitbot EVM or APM EVM wallet yet, you’ll be prompted to create one (or set it up beforehand) *** ### What’s Moving ✅ **Spot tokens** held in your Bitbot wallet *** ### Not Moving Automatically (manual action may be needed) ⚠️ **Airdropped tokens** (often spam/scam tokens sent to your wallet) *** ### Before You Begin * **Use only the official bot:** `@Hellp_Bitbot` (double-check the handle) * **Have a little gas ready** on the relevant chain(s) for migration transactions (network fees). * **Do NOT share seed phrases** or private keys—no staff will ever ask for them. > Tip: Complete the migration first, then run `/positions` in the Bitbot EVM bot. ### Step-by-Step #### A) Start the migration 1. Open [**https://t.me/hello\_Bitbot**](https://t.me/hello_Bitbot) 2. Send `/migrate` 3. The bot compiles a list of assets from your Bitbot wallets 4. Review the list and amounts #### B) Create/Select your destination wallet * If you **already have** an Bitbot/APM EVM wallet, the bot will link to it * If you **don’t have** one yet, you’ll be prompted to create it on the [**https://t.me/hello\_Bitbot**](https://t.me/hello_Bitbot) during the flow * You can also set it up first: open the and follow the wallet setup prompts #### C) Confirm & move * Tap **Confirm migrate** * The migration executes on-chain (allow a few minutes) * You can close Telegram—transactions continue on-chain #### D) Verify positions * In the Bitbot EVM bot, run: `/positions` * Confirm balances and any supported open positions have arrived *** ### After Migration * Trading continues on the new infra with faster execution and improved stability * You can continue using Bitbot via & after the migration * Bitbot now runs on a much faster and more reliable infrastructure *** ### Security Checklist (read this!) * Only use **@hello\_Bitbot** * Never share **seed phrases** or **private keys** * Beware of DMs from imposters; we only support via official channels below *** *** We’re beyond excited to welcome you to the upgraded APM infrastructure. Faster execution, cleaner UX, and a more unified experience await. Let’s build the next chapter together. 🚀 --- # Agent Instructions: 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: ``` GET https://docs.bitbot.tg/welcome-to-bitbot/migration-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.