Import your StatBot history

What this is for

If your server has been running StatBot, it holds years of your activity history. Starting again from zero makes a new bot look like a new server, and the charts everyone recognises reset.

This brings that history across. It is free — charging for the door in would be charging somebody to stop being a competitor's customer.

What comes across, and what does not

✅ imported	⛔ not imported, deliberately
Messages, voice minutes, per-channel and per-hour history	Levels
Membership growth — joins, leaves, the running count	Money
	Anything else a member has earned

⛔ The split is not a limitation, it is the rule. Statistics describe what happened; levels and money are standings. Importing standings would move members past people who earned their place here, which is the one thing no import is allowed to do.

The five steps

Open /menu › Other › Admin › Stats › Import:

step	what happens
Fetch	Pulls your history and builds a preview. Nothing is written yet
Status	What the preview contains and how far it got
Apply	Writes it. This is the only step that changes anything
Cancel	Throws the preview away
Undo	Puts the archive back as it was

⭐ Fetch and Apply are separate on purpose. You see exactly what would land before any of it does, and a fetch that stops part-way can be resumed rather than restarted.

You will need a StatBot API key. ⚠ It is never shown back to you, never pre-filled into a re-opened form, and is forgotten five minutes after you stop using it — the form says so.

⚠ Imported history is marked, for ever

Every month the import touches is stamped as imported. That is not bookkeeping:

• Your own server's charts show everything, imported and measured alike — it is your history.
• The cross-server total never counts it. Partly because a number that mixes what we measured with what somebody else did is not a measurement, and partly because StatBot's own terms permit their data for your guild and forbid cross-guild datasets.
• Member leaderboards use measured data only.

⛔ The mark had to exist before the first import ran. An unmarked imported row is indistinguishable from a measured one for ever afterwards — there is no later repair.

Questions people actually ask

Can I run it twice? Yes, but you rarely want to — check Status first. An Apply while a preview is ready tells you it is replacing that preview.

What if somebody asked to be erased between the preview and the Apply? The Apply re-reads the erasure list and refuses rather than quietly restoring them. A purge cannot be walked back by an import.

MEE6 is not supported and will not be — there is no official API and their terms bar automated access, so no other bot's levels can be brought across either. StatBot is the migration door that actually exists, and it carries history rather than standings.

Will my numbers match StatBot's exactly? Close, not identical. Voice is the reason: StatBot counted time connected, and this bot counts time engaged, which runs about 85% of connected. The charts say which is which rather than pretending one number.