Transfer a community to another Discord server

A server transfer moves an existing Clan Labs community connection to another Discord server. It is a high-impact action reserved for the current Discord server owner (Super Owner).

Before transferringCopy link to Before transferring

• Install the Clan Labs bot in both servers and give it the required permissions.
• Sign in again with Discord if Clan Labs requests fresh authorisation.
• Confirm you own the current server and the destination is listed as eligible.
• Review active events, channel settings, role binds, audit delivery, and divisions.
• Tell staff when the move will occur so they do not make simultaneous configuration changes.

Divisions are not transferred as part of the main community move. Manage their connections separately.

Transfer the connectionCopy link to Transfer the connection

1. Open the community’s transfer control in Clan Labs.
2. Select the destination Discord server.
3. Review the exact source and destination names and IDs.
4. Read the role and channel impact summary.
5. Confirm the transfer as Super Owner.
6. Open the community in the destination server and re-check settings.

Clan Labs attempts to match configured roles by the exact same role name. When needed, it can create a role using the stored name and colour, but it does not copy Discord permissions, members, role icons, or every role property. Move the Clan Labs bot role above managed roles afterward.

Server-specific channel references and event mention settings that do not belong to the destination are cleared. Re-select channels for welcome messages, audits, events, quotas, and other delivery settings. An event created before the transfer may still reference its old announcement; verify or create a supported fresh announcement.

The destination Discord server owner becomes the community’s Super Owner.

Reconcile Discord command permissionsCopy link to Reconcile Discord command permissions

After the move, open Settings → Permissions in the destination and choose Sync Discord commands if synchronization is pending. The account performing the sync needs the relevant Clan Labs access and Discord command-permission authorization.

If Finish former Discord server cleanup appears, review the listed Clan Labs community, former Discord server name and ID, and whether the pending work came from a transfer or deletion. Use Reconnect Discord if requested and then Retry cleanup. This removes old slash-command permission settings from the former server separately from applying permissions in the destination.

You can dismiss the expanded reminder while continuing other work; Cleanup pending remains available to reopen it during the session. Dismissing the reminder does not complete the cleanup. A cleanup warning does not mean you should repeat the transfer.

Verify the transferCopy link to Verify the transfer

1. Run /community in the destination.
2. Refresh Discord resources in Clan Labs.
3. Reconfigure cleared channels and mention roles.
4. Run /update on a test member and inspect roles and nickname.
5. Test one read-only Roblox action before any rank write.
6. Review the transfer audit record.

Do not retry immediately after an uncertain response. Refresh both server states first, because the transfer may already have committed.

For missing servers, see Discord server is missing. For role problems after the move, see Discord role does not update.