How to recover a Discord server after a nuke.

1. Review access before rebuilding

Inspect administrator access, bot permissions and recent audit events. If an account or bot still has the ability to delete channels and roles, a restore can be damaged again. Remove access you no longer trust and review account security through the relevant service's controls before starting the rebuild.

Keep a record of what happened and use an announcement channel your community recognizes for updates. If the incident involves Discord enforcement or loss of ownership, follow Discord's support process. A recovery service cannot restore ownership or reverse an enforcement decision.

2. Inspect your last useful recovery point

Open Backups and review the source server, snapshot contents and capture time. A recent snapshot may reflect the damage if it was taken after the incident; choose a recovery point that contains the structure you want. Inspect which channels, roles and assets were actually captured.

Separately review member authorization health. A structure snapshot does not include member recovery credentials. A recorded member count is not a promise that every account can be re-added.

3. Prepare and review the destination

Select a connected server you are allowed to manage. Confirm the bot can create the needed channels and roles, then review the restore preview for objects to add, reuse or skip. Guardcord preserves existing destination objects, so check for naming collisions and content you want to keep.

Channels with member-specific overwrites, and children of skipped categories, need manual setup. Review access before people return. Apply saved server identity only if you want that icon, banner and description on the destination.

4. Restore structure, then attempt member recovery

Run the structure restore and inspect its log. Resolve missing permissions or unsupported items before starting a separate member recovery. The member job attempts joins for eligible consent and authorization records and reports individual outcomes.

Do not keep retrying withdrawn authorizations. For permitted members whose joins fail, inspect the reason: bans, revoked application access, Discord limits and bot permissions can all affect the result. Use a recognizable invitation route for members who want to return but cannot be recovered automatically.

5. Check the rebuilt community and prepare the next backup

Optional read-only archives can preserve a record of captured conversations, but Guardcord does not recreate message history or attachments in Discord. Document those gaps so members know what to expect.

• Review channel visibility with an appropriate member role.
• Check role hierarchy and manually recreated member-specific permissions.
• Publish a community update with the destination and remaining limitations.
• Review completed, skipped and failed recovery outcomes.
• Create a new structure snapshot after the rebuilt layout is correct.
• Revisit team permissions and test the recovery plan before the next incident.