Bond vs ProBot
ProBot bundles welcome images, moderation and levelling into one install. The bundle covers a lot, right up until the thing you need is not in it.
We build Bond. Everything below about ProBot comes from its own public pages.
What ProBot is known for
Welcome images, moderation and levelling in one bot, configured in its own interface and switched on per feature.
What Bond does differently
Bond is not a fixed feature set. It picks from its whole tool set for each request, across channels, roles, moderation, automation, events and voice, so a new requirement does not mean a new bot.
One sentence, instead of the panels.
@Bond Set up the whole server: channels, roles, a welcome flow, and lock announcements to mods
When to stay on ProBot.
Stick with ProBot if you specifically want generated welcome images out of the box.
It is good at welcome images, moderation and levelling in one bot, and there is no prize for switching a tool you are happy with. Add Bond for the jobs ProBot 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
ProBot 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 ProBot changes when you add it.