Bond vs AiGuild
AiGuild generates a server from a /setup questionnaire or a prompt on its site. Its own docs say /setup deletes the existing channels, roles and categories before it builds, and advise trying it on an empty server first; there is a separate modify mode for changes, and a backup you can roll back to.
We build Bond. Everything below about AiGuild comes from its own public pages.
What AiGuild is known for
Generating a whole server from a questionnaire, configured in its own interface and switched on per feature.
What Bond does differently
Bond does not generate a server to put in place of yours. It changes the one you already run, a request at a time, and a delete has to name the exact channel or role it resolved and get a yes before it happens. Bond's invite also leaves out Administrator, which AiGuild's asks for, because every action it takes maps to a specific Discord permission.
One sentence, instead of the panels.
@Bond Add a Support category with a ticket channel and let only the Staff role see it
When to stay on AiGuild.
Stick with AiGuild if you are starting a brand new server and want the whole structure made for you in one pass.
It is good at generating a whole server from a questionnaire, and there is no prize for switching a tool you are happy with. Add Bond for the jobs AiGuild 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
AiGuild 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 AiGuild changes when you add it.