What confirms migration
In the Trenches feed, migration means a confirmed transition from a launch mechanism to its next trading pool. It does not mean bridging funds to another network or replacing a token contract.
The migration state requires launchpad or provider confirmation. Rising price, volume or curve progress alone does not confirm graduation.
For Solana event coverage, PumpPortal documents separate creation and migration streams (opens in a new tab). The Robinhood Chain feed reads Pons V2 launch and graduation events.
Verify the transition in four steps
- Match the tokenKeep the same full mint or contract and network when following the launch. A repeated ticker is not enough.
- Identify the eventUse the launchpad or provider confirmation and its timestamp. Keep event time separate from the time the row reached the feed.
- Check the new poolConfirm its base token, quote asset and pool identity. A new pool can exist without representing this launch’s graduation.
- Start a new comparisonRead the destination pool’s measurements with their own timestamps. Recheck liquidity, quote and activity where those fields are available.

Read a migration timeline correctly
Illustrative example: These times describe an invented launch to demonstrate the clocks; they are not a historical trade.
| Time UTC | Observation | Interpretation |
|---|---|---|
| 10:00 | Token launch confirmed | Launch age starts |
| 10:42 | Graduation event confirmed | Transition is supported by an event |
| 10:43 | Destination pool first indexed | The provider can now report that market |
| 10:44 | The row appears in Migrated | Feed arrival includes discovery and display delay |
At 10:44 the token is 44 minutes old. A newly indexed pool or row does not make it a new token. The time gap alone cannot tell you the execution price or whether the destination pool currently supports your intended order size.
The lane rules differ by network
Robinhood New keeps the latest supported launches under one hour old. Progress alone does not move an ungraduated fresh token into Active. Migrated requires a confirmed graduation event or previously saved confirmation; a token occupies only one lane.
Solana New requires supported token-creation evidence within ten minutes and no migration evidence. Active uses measured recent trading activity. Migrated requires a confirmed or observed event, or a completed curve corroborated by a real PumpSwap or Raydium pool. A pool name, fresh pool timestamp or price rise alone never establishes migration.
Read the network-specific selection rules before comparing column counts across terminals.
Recheck the destination pool
Verify the quote asset, reported liquidity and activity interval for the destination pool. Keep curve volume and pool volume separate unless the source defines a combined measurement.
Retain the graduation event with your notes and use the market-data checklist to compare the new pool. Confirmation establishes the transition; it does not establish token safety or future demand.
Find your next research target