Export, reset, or delete community data
Download a redacted community archive and understand permanent reset and deletion controls.
Last updatedOpen Settings → Delete Data to reach the Community data page. The sidebar keeps its Delete Data label. The page can offer a community download, a reset of selected records, and permanent deletion.
These controls have separate access checks. A community download is available to the actual Discord server owner (Super Owner). Reset also depends on its capability being available; seeing a deletion control does not guarantee reset or export access.
Before downloading, resetting, or deleting, verify your identity with Discord. Verification remains valid for ten minutes. Reset and deletion are each limited to three attempts per community per hour.
Download community data
- Select the intended community and open Settings → Delete Data.
- Under Download community data, choose Verify to download if requested.
- Choose Download ZIP and allow the download to finish.
- Open the downloaded ZIP and check that it contains
manifest.jsonand the expected collection files before relying on it.
A main-community export includes its registered divisions. Exporting a division includes that division only. You must own every included Discord server when access is checked; an ownership change or a division owned by someone else can block the download.
The ZIP is generated for that request and is not retained for a later download. Current limits are ten export attempts per ten minutes and three export starts per hour per user. If limited, wait for the response's retry interval.
What the archive contains
The ZIP contains a manifest.json describing its format, community scope, and redaction policy, plus per-community .ndjson files. Each line in an NDJSON file is one JSON record. The collections cover members, settings, ranks, group binds, medals, qualifications, events, warnings, suspensions, blacklists, audits, and asset logs.
Member identifiers are replaced with pseudonyms that remain consistent within that export. Pseudonyms change between exports. Personal names, free-form text, contact details, links, secrets, and other sensitive content are redacted. Billing, authentication, and session stores are excluded, as are integration tokens. Community IDs remain in the manifest.
This is a redacted portable archive, not a complete restorable backup. There is no community import workflow. Check the redaction policy before treating the download as a record of specific members or moderation details.
If a download fails
Refresh your Discord verification, confirm ownership of every included community, and read the exact error. Restricted accounts cannot export. Another community operation can temporarily block access; wait for it to finish before trying again.
A streamed download can fail after it starts. An incomplete or unreadable ZIP is not a successful export. Wait for any retry interval, restart the download when access is available, and verify the new archive. If the problem persists, contact support with the community IDs, time, and error.
Reset selected data
A reset keeps the community, its Discord server connection, and its settings. Select one or more groups to clear:
- Roster & progression — members, experience, quota points, and rank history;
- Audit & asset history — audit entries and stored asset logs;
- Moderation records — warnings, suspensions, and blacklists;
- Events — hosted and scheduled events;
- Medals & qualifications — definitions and member awards; and
- Ranks & group binds — rank configuration and Roblox group-bind rules.
Settings are never cleared because they contain the Discord and Roblox connections the community needs. Resetting a main community also clears the selected data from its divisions. Active suspensions must be restored or cancelled before clearing moderation or rank data.
Review the record count in the confirmation dialog, enter the community name exactly, and select Permanently clear data. If the reset stops partway through, some records may already be gone; run the same reset again to finish before making unrelated changes.
Delete the community
Deleting a community removes its database, settings, members, ranks, awards, moderation records, events, and audits. Deleting a main community also removes every registered division database.
Deletion also removes community-specific Roblox account links and unbinds attached subscriptions. It does not remove account-wide Roblox verification. Billing history, subscription ownership, the existing 30-day binding cooldown, and the durable deletion record remain.
Clan Labs blocks deletion while the community has an active managed partnership or active suspension. End the partnership and restore or cancel every suspension first. Deletion does not reverse Discord role changes or Roblox rank changes that have already happened outside the dashboard.
Review every database listed in the confirmation dialog, enter the community name exactly, and select Permanently delete community. If Clan Labs reports that deletion did not complete, contact support before making other changes.
Connection cleanup after deletion
Community deletion also handles outstanding Roblox authorization revocation. If deletion itself did not finish, contact support before making unrelated changes.
A completed deletion can still report follow-up cleanup problems. If Finish former Discord server cleanup appears, check the listed deleted community and former Discord server, use Reconnect Discord if requested, then Retry cleanup. You can dismiss the expanded notice and reopen its Cleanup pending reminder during the session; dismissal does not complete the cleanup. This warning does not mean the community should be deleted again.
Before confirming
- Download the community archive if useful, and check its redaction limits before relying on it.
- Check the selected community and every listed division.
- Reconcile active subscriptions, partnerships, and suspensions.
- Inspect Discord and Roblox afterward because external changes are not reversed.
- Do not repeat a deletion while its result is uncertain.
For personal exports or account erasure, use Privacy and account controls. For a service failure, follow Temporary service problem.