Switching from another bot
The parallel-run playbook, what to export before you cancel, and the built-in migration tools.
Moving a live community is mostly about not breaking anything while you move. The pattern that works is the same regardless of which bot you're leaving:
Run both bots side by side
Add Fealty and set it up (/setup, collections, role rules) while the old bot keeps working. Nothing conflicts as long as the two bots don't fight over the same Discord roles; the per-bot guides below cover that.
Export your data from the old bot
Do this before your old subscription lapses; export buttons have a habit of living behind the paywall. What's worth taking with you, per bot, is listed in each guide.
Announce once, migrate members over a week or two
One announcement: "we're moving to Fealty; press Verify and reconnect your X". Wallet verification is a single signature and members keep their roles throughout, because both bots are still granting them.
Import points, watch progress, retire the old bot
Import your members' earned points with the points import, watch re-verification progress with the snapshot tracker, and kick the old bot when the numbers say everyone has moved.
The built-in migration tools
Both live at Manage → Setup → Migration tools (/guild/…/manage/migrate), on every plan including Free:
| Tool | What it does | What it can never do |
|---|---|---|
| Points import | Pays members the points (and XP) they earned on your old bot, from a CSV export, with a multiplier to convert old points into Fealty value. Staged first; nothing is paid until you review and press Apply. Revertible for 30 days. | Pay the same file twice, overwrite points earned in Fealty, or pay someone who isn't in your server. |
| Re-verification snapshot | Reads a holder snapshot from your old verification bot and shows how many of those wallets have re-verified with Fealty, so you know when it's safe to retire it. | Grant roles. Verification in Fealty always comes from the member's own signature. |
Why wallets can't be "transferred"
Wallet verification is a cryptographic signature given to a specific service. No bot can hand its verifications to another, and you wouldn't want one that could; the entire trust model of holder roles rests on members proving ownership themselves. In practice this costs each member one click and one free signature, and the parallel-run window means nobody loses a role while it happens.
Per-bot guides
- Migrating from Engage: bring your whole points economy over.
- Migrating from Matrica: re-verification without role flapping.
- Migrating from Alphabot: the simplest move; raffles are ephemeral.