Migrating from Engage

Engage's core loop (X engagement earns points, points buy things) maps one-to-one onto Fealty's quests and reward economy. The one thing worth carrying over is your members' earned points, and that's exactly what the import tool does.

Concept map

Before you cancel: export the leaderboard

1. In Discord, run Engage's /userlist command; it exports the full leaderboard to a Google Sheet, including Discord IDs and points.
2. In that sheet: File → Download → Comma Separated Values (.csv).

That file is all you need. Do this while your subscription is still active.

Import your points into Fealty

Go to Manage → Migration tools and upload the CSV. Any file with a Discord ID column and a points column works; columns are detected automatically, and if your export's headers ever look different you can point at the right columns manually. The canonical format, if you're building the file yourself, is simply:

discord_id,points
123456789012345678,5000

The multiplier: converting an old economy into a new one

Engage points and Fealty points are different currencies. The multiplier sets the exchange rate: each member receives round(points × multiplier), credited as points and as XP, as if they had earned it in Fealty. Levels then follow from XP, so your most loyal members land at the levels (and level rewards) their history deserves.

The staged preview shows, live at your chosen multiplier: the total that would be paid, and the resulting level spread ("Level 5-9: 120 members"). Tune the multiplier until that spread looks right; if a like paid 10 points there and pays 2 here, a multiplier of 0.2 keeps the economies aligned.

What Apply actually does

Nothing is paid at upload. When you press Apply:

• Members Fealty already knows in your server are paid immediately.
• Members new to Fealty are checked against your Discord server one by one (a big import takes a few minutes) and paid if they're really in it. When they later sign in, everything is already waiting on their account.
• Rows that can't be paid (the member left, or Discord couldn't confirm them) are skipped and reported; download the unmatched rows CSV and re-import it later once they've joined. It only contains rows that were never paid, so re-importing it can't double-pay anyone.
• Level-ups grant your level rewards through the normal role pipeline, throttled; no member is notified, because a migration is your announcement to make, not thousands of DMs.

Safety rails

• Same file, twice: refused by content hash while the import stands. Duplicate rows inside a file are merged, not paid twice.
• Existing points: always added to, never overwritten. Points your members earned in Fealty are untouched.
• Revert: the latest applied import can be reverted for 30 days, subtracting exactly what each member received (floored at zero if they spent some). Discord roles already granted stay; the level system is grant-only.
• One at a time: one import can be staged or running per server, and Apply is atomic; a double-click can't run it twice.

Suggested order