Bond vs Carl-bot
Carl-bot is best known for reaction roles and has a deep set of options for them. You would look elsewhere to get the rest of the server handled the same way, without learning a second interface.
We build Bond. Everything below about Carl-bot comes from its own public pages.
What Carl-bot is known for
Reaction roles and logging, configured in its own interface and switched on per feature.
What Bond does differently
Reaction roles are one sentence to Bond, and the same sentence covers channels, permissions, moderation and scheduled posts, instead of a separate configuration screen per feature.
One sentence, instead of the panels.
@Bond Post a role picker in #roles for Gaming, Music and Art, and give the role when someone reacts
When to stay on Carl-bot.
Stick with Carl-bot if reaction roles are the only thing you need and you want the deepest possible options for them.
It is good at reaction roles and logging, and there is no prize for switching a tool you are happy with. Add Bond for the jobs Carl-bot does not cover, and leave the rest where it is.
And if you do switch, in three moves.
Both bots can run at once. There is no import step and nothing to migrate.
Add Bond alongside
Carl-bot keeps doing exactly what it does today. Bond joins without touching a single existing setting.
Move one thing across
Pick the part you like least. Describe what it does to Bond, approve the changes, and watch it run for a week.
Turn the old one off
Only once the new one has run. Repeat for the next part, or stop here and keep both.
Try Bond on one thing this week.
Free to start, and nothing you have set up in Carl-bot changes when you add it.