Kotbo 3 min read
Discord server backup: copy and restore channels, roles and settings
A Discord server is built over months: dozens of channels, roles, permissions tuned in detail. A raid, an admin going rogue or one wrong click can undo it all, and Discord has no button to go back. With Kotbo you keep a copy of your server in the Backups page of the dashboard or with the /backup command, and restore it when something goes wrong
Included in every plan, with a 15-day trial and no credit card
Why back up a Discord server
Nobody plans on losing their server, yet it happens fast
- A raid deletes channels and roles in seconds
- A hijacked admin account or an angry mod can break everything
- A restructuring that goes badly can be undone with a restore
- You can duplicate a proven structure onto a new server
What Discord offers without a bot
Discord lets you duplicate a server as a template, but a template keeps no messages, no members and no bot settings, and can’t be restored onto an existing server. There is no version history. For a real backup you need a bot that records the server’s state
Creating a backup with Kotbo
The command is reserved for administrators. It runs from Discord, or from the Backups page of dash.kotbo.fr
-
Start the backup
With /backup create, or the New backup button in the dashboard. Without a name, the backup is named after the server and the date
-
Choose what’s included
Roles, channels, emojis, stickers, members and Kotbo’s configuration (modules, staff, forms…) are included by default. Messages are not, you can add them
-
Wait for it to finish
The dashboard follows the steps: roles and channels, permissions and emojis, saving. Processing runs in the background
-
Check the list
Each backup shows how many roles, channels, emojis, stickers and members it holds
Backup commands
All of them require the administrator permission
/backup create nom:<name> description:<text>- Creates a backup. Extra options to include or skip messages, members, roles, channels, emojis, stickers and the Kotbo configuration
/backup list- Lists the server’s backups
/backup restore id:<id> mode_complet:<yes or no>- Restores a backup. Restoring is selective by default, mode_complet asks for a full restore
/backup export id:<id>- Exports a backup as a JSON file
/backup import fichier:<file>- Imports a backup from a JSON file, with an optional name
/backup delete id:<id>- Deletes a backup
Restoring: what to know before you click
A restore applies the saved roles, channels and permissions, and overwrites the server’s current configuration with the backup’s data. It can’t be undone, so take a backup of the current state first if you’re unsure. Also move Kotbo’s role to the top of the role list: it can only restore what sits below it
Exporting, importing, duplicating
The JSON format serves three purposes
Keep a copy outside Kotbo
Export the backup and file it with your archives
Move a server
Import the file on another server to rebuild the same structure there
Share a template
A file can be the starting point for a new server in your community
How many backups, and how often
Each server can keep up to 3 backups at a time. Delete the oldest to create a new one. Make one before every big structure change (a new category, a role overhaul), and export the latest to JSON regularly so you don’t depend on the limit