How it runs
- Run
/gf-migratein your server. It needs Manage Server, because it changes everybody’s level. - It reads. Which levelling bots are in your server, whatever those bots make public, the roles whose names carry a level — “Level 10”, “Lv 25”, “Tier 3” — and who holds them right now.
- You get a preview. The ladder it found, how many members have a level, and ten of them shown before and after. Nothing has changed at this point.
- You press Apply. That is the only step that writes, and every member’s XP and level is recorded before it does.
- Undo works for seven days and puts every one of them back exactly as they were.
Nothing is uploaded and no screenshot is asked for. The version of this that asked owners to type their leaderboard in by hand was deleted on 21 September 2026: in its whole life it produced one unfinished draft.
Nobody goes down
A level read from your old bot is converted to the point on the GroupFinds curve where that level begins, and written only where it is higher than what the member already has. Somebody already above it keeps what they have. A migration that could lower a member is a migration nobody can be asked to run.
What each levelling bot lets anyone read
Established by asking those services directly, not by reading their websites. Six of the seven give nothing, and it matters less than it sounds — see below.
| Bot | What it makes public |
|---|---|
| MEE6 | Everything, when the owner has left the leaderboard public: every member’s level, XP and message count, the role rewards with their levels, and the XP-per-message settings. |
| Arcane | Nothing. Its API refuses an unauthenticated caller and its leaderboard is drawn in the browser. |
| AmariBot | Nothing without an API key it will not issue to us. |
| Tatsu | Nothing without an API key it will not issue to us. |
| ProBot | Nothing. Its site answers anything that is not a browser with a challenge page. |
| Carl-bot | Nothing, and no public leaderboard exists to read. |
| Lurkr | Unestablished: it answered 404 for every server tested, so it is treated as unreadable until one proves otherwise. |
If your old bot exposes nothing
Levels still come across, from your own roles and who holds them today. That path works for every bot on the list above, including the ones that publish nothing at all: a server with “Level 5” through “Level 50” roles comes over in full.
What is lost is the exact XP between two levels, not anybody’s standing. A role that does not name a level — “Veteran”, “Regular” — is never guessed at; it is matched only where the old bot’s own reward data says which level it belongs to.
What does not come with it
No levelling bot publishes per-day message or voice history, so your GroupFinds analytics start from the day the bot joins. Your members’ voice hours start counting from that day too, which is stated on the Passport page for the same reason.
What your old bot could not do
- Voice counts. Time in calls earns XP, and calls are the thing most levelling bots cannot see at all.
- A weekly card posted in your server, showing what actually happened in it.
- A public page for your server with figures read from Discord, and a free report card comparing it with the servers like it.
- A verified activity badge for your other listings, carrying voice hours and active members the bot watched itself.