Discord bot migration guide
Switching leveling bots is a trust exercise. Members care about the XP, levels, and rewards they have earned, so plan the transition before touching data—and treat every import as something to verify, not a promise that every setting transfers.
Document XP rates, reward roles, leaderboard periods, rank-card choices, and special multipliers before moving. Imports address data, not necessarily the whole member experience; this record is what lets your team rebuild the rules deliberately in Atom.
Confirm that your source and current format are supported, create a backup outside the bot, and read the command’s warning carefully. Atom’s import flow warns that it removes existing Atom leveling entries before importing. Do not use a production server as the first place you learn what a source export contains.
Check a sample of established members, newer members, and reward thresholds after the import. Recreate roles and progression controls only after the data looks right. If a field is not imported, explain the change instead of implying that every prior setting survived intact.
Tell members what will remain the same, what will change, and when new features will arrive. A short explanation of rewards and ranking rules helps the new system start on the right footing.
Practical workflow
Export or otherwise back up your existing leveling data and write down the rules that data does not capture.
Run /import with the verified source in a controlled setting, acknowledging that existing Atom leveling data is replaced.
Check representative member records and rebuild reward rules before publishing the change to the full community.
Continue learning
