Migrating from Matrica
Re-verify without role flapping, and measure exactly when the old bot can go.
Holder verification can't be transferred between bots (why): each member re-verifies with one signature. The craft in this migration is role hygiene, so two bots managing the same roles never fight, and knowing when you're done, which is what the snapshot tracker is for.
Concept map
| Matrica | Fealty |
|---|---|
| Token-gated Discord roles | Role rules |
| Verified collections / cNFTs | Solana collections, compressed included |
| Staking integrations | Staking as a rule condition |
| Attribute/amount role tiers | Amount-based role rules |
| Role snapshot / holder export | Collection holder export; leaderboard export |
| Periodic re-checks | Real-time webhooks + daily reconciliation |
The one rule that prevents chaos
Two bots must never auto-manage the same Discord role. Both re-check holders on their own schedules; each removes the role the other just granted, and your members watch their roles blink. Pick one of these:
- Same roles, one manager (recommended): map Fealty's role rules to your existing holder roles, and turn off the old bot's automatic sync/removal for the migration window. Members re-verify with Fealty and visually nothing changes; their
@Holdernever left. - Fresh roles: create new roles for Fealty's rules and retire the old roles with the old bot. Cleaner separation, but members see a role swap.
Before you cancel: export a snapshot
From your Matrica dashboard, export a role snapshot (or collection holder export) as CSV or JSON. If your plan includes Discord IDs in exports, include them; matching gets more accurate. Do this while your subscription is active.
Track re-verification progress
Upload the snapshot at Manage → Migration tools. Fealty reads the wallet addresses (and Discord IDs when present) and shows one number that answers the only question that matters: how many of your old bot's holders have re-verified here.
- Matching prefers Discord ID (a member may verify a different wallet with Fealty than the one snapshotted) and falls back to wallet address.
- The snapshot is inert by design. It never grants roles, points, or anything else; every role in Fealty comes from a member's own signature. It exists purely so "can I kick the old bot yet?" has an answer better than vibes.
- Delete it whenever you're done; it's your uploaded file, nothing depends on it.
Suggested order
Set up verification in Fealty
Add your collections, map role rules to your existing holder roles, and disable the old bot's auto-sync.
Upload the snapshot
So progress is measured from day one.
Announce the move
One announcement with the verify channel link. One click, one signature, roles stay put.
Watch the number, then retire Matrica
When re-verification crosses ~90% and the stragglers have had their nudge, remove the old bot. Fealty's webhooks and daily sweep now own role correctness.
Matrica is a trademark of its owner. Fealty is not affiliated with, sponsored by or endorsed by it; feature and export details reflect its public documentation and may have changed since we checked.