Copy Settings pulls the portable parts of one Discord server's bot configuration — wording, colors, templates, thresholds and module switches — into another server you also manage, in one click instead of retyping everything. It is not the same thing as Discord's own server template feature, and it deliberately refuses to copy anything tied to a specific channel, role or record. This guide covers exactly what moves, what stays behind, and why.
This is not a Discord server template
Discord itself lets you generate a template of a server's channel and role structure and use it to scaffold a new server. That is a completely different, native Discord feature — it copies structure (channels, categories, permission layout) but knows nothing about a bot's configuration. Copy Settings is the opposite: it assumes the channels and roles already exist in both servers and copies what a bot like Noxyr remembers about how to behave, not the server's shape. Use a Discord template to build the skeleton of a new server; use Copy Settings afterward to make the bot on it sound and act like your other one.
What actually gets copied
Copy Settings only moves presentation and behavior — the parts that mean the same thing regardless of which server they land in:
- Module switches: every on/off toggle from the Modules page.
- Invoice branding: brand name, logo URL, ID prefix, accent color, footer text.
- Welcome wording: message, embed title, embed color and button label (not the channel, the enabled switch, or the image).
- Leave wording: message, embed title and embed color.
- Verification wording: embed title, message, button label and embed color.
- Review settings: embed title and color, footer text, rating emoji, and the show-reviewer / show-product / auto-publish / require-approval toggles.
- Security thresholds: the entire anti-spam configuration, and anti-nuke's max actions, window, action type and timeout length.
- AI chat: the mention-reply setting and the system prompt.
- Ticket presentation: panel color, button label, button emoji, button style, channel naming format, the welcome/open-message templates, embed footer, and the require-close-reason / confirm-close toggles.
What never gets copied, and why
Anything that names a specific object in the source server is refused outright, because a channel or role ID from one server points at nothing in another — copying it would produce a configuration that looks complete on the settings page but silently does nothing where it matters:
- Channels and roles — welcome/leave/log/catalog channel IDs, verify role and channel, review channel, AI chat channel list, anti-nuke's trusted roles and users, ticket category and staff role IDs.
- Products, categories, vouchers and invoices — these are business records, not settings.
- API keys — a credential is never duplicated across servers.
- Enabled switches and images on welcome, leave and verify — so copying settings can never accidentally turn a feature on in a server where you deliberately left it off, and an image URL that only made sense next to the source server's branding does not show up somewhere it looks out of place.
How to copy settings, step by step
- Open the server that should receive the settings, and go to Copy Settings in its dashboard.
- Pick a source server from the dropdown — only servers your own account can also manage and where the bot is present are offered.
- Confirm the warning. This overwrites the target server's wording, colors, templates and module switches; it does not touch channels, roles, products or API keys.
- Reload the target server's dashboard to see the new settings reflected everywhere.
The copy is recorded in the activity log, so if something looks different afterward and you cannot remember why, that log names exactly what changed.
Who this is actually for
Copy Settings earns its keep for anyone running more than one server on the same bot: a community with a public server and a private staff/beta server, an agency managing several client servers with the same house style, or someone spinning up a second server for an event who wants the same anti-spam limits and ticket presentation without redoing every field by hand. If you only run one server, this page has nothing for you.
What to double-check afterward
Because channels, roles and the enabled switches are never copied, the target server almost always needs a short follow-up pass: set the welcome/leave/log channels, pick the verify role, and flip on whichever modules should actually run. The Overview page's setup checklist catches most of this automatically — a module that is on with wording copied in but no channel set shows up there as unfinished.
Common questions
Will Copy Settings turn on modules I had off, or vice versa? Module switches themselves are copied, so yes — that is one of the things that does transfer. If you only want wording and not the on/off state, review the Modules page after copying and adjust it back.
Can I copy from a server I do not own? Only if your account can manage it (owner or Administrator) and the bot is in it. The source list only ever shows servers meeting both.
Does it copy ticket categories or staff roles? No. Ticket presentation (colors, labels, message templates) copies; the category and staff role IDs do not, since they only exist in the source server.
Is there an undo? No built-in undo, which is why the confirmation names exactly what it overwrites before you commit. The activity log records the before/after values if you need to manually revert something.
Does this work between a normal server and a Custom Bot server? Yes — settings live in the same database regardless of which bot name is answering in a given server, so Copy Settings works the same way either direction.
Related reading: why a dashboard beats slash-command configuration for the broader case, and the dashboard access docs for who can open which server.