How to Move a Discord Community to a New Server

Handing the server over? The owner can transfer ownership to another member from the member list. The previous owner stays in the server with whatever permissions their roles give them. Discord's support team cannot reverse a completed transfer, so choose the new owner carefully.

Voice quality? Voice regions are set per voice channel, not per server. The default is Automatic, and you can set a Region Override in each voice channel's settings. That is no reason to move.

Hitting limits? Discord caps a server at 500 channels (text, voice and categories combined), 50 channels per category and 250 roles, and these caps are the same at every boost level. A new server has the same caps, so moving does not raise them; cleaning up does.

Reasons that can justify a move: the structure has become too tangled to fix in place, two communities are merging, or the server's owner account is lost and ownership cannot be transferred.

Discord's server templates clone existing categories, channels, roles and permissions into a new server. You need to be the owner or have the Manage Server permission, and templates can only be created on desktop or in the browser. Voice region settings are copied too.

Know the gaps: Community-only channel types (Forum, Announcement and Stage channels) are not included. A template also does not update itself; after changing the original server, press Sync Template before using it. Servers with more than 1,000 channel permission overwrites cannot create a template until the number is reduced.

Messages, members and bot setups are not part of what a template copies. Plan for them separately: re-invite each bot, redo its configuration and re-post the resources members need, such as rules, FAQs and guides.

Write down what the old server contains: each bot and its settings, custom commands, pinned messages and any resource channels. Then set up the new server completely, including the channels a template leaves out.

Test it before anyone joins. View Server As Role, available to owners and Administrators, shows what a given role can see, so you can confirm that new members reach the right channels and staff areas stay hidden.

Announce the move with a reason, a date and a single invite link. Pin the announcement in the old server so late readers still find it.

Members have to join the new server themselves through an invite. Bring over staff first, so the new server is moderated and has visible activity when regular members arrive.

Roles do not come with members. Reassign staff roles by hand; self-assigned roles can be picked again from a role panel. Levels, currencies and similar data live in each bot's own storage, so check with the bot provider whether that data can move.

Keep the old server open for a while as a signpost. Deny Send Messages to @everyone on its categories so it becomes read-only, and leave a short channel pointing to the new invite.

Boosts do not move automatically, but each booster can transfer their boost to another server they are a member of. After a boost has been used, there is a 7-day cooldown before it can be transferred.

Moving boosts can drop the old server's level. Discord keeps level perks for a 72-hour grace period after a server loses a level; after that they become invalid until the level is regained. See the server boost guide for what each level includes.

Watch where members get stuck in the first days and fix permissions or missing channels quickly. Ask for feedback in one channel rather than in several.

Before you delete or archive the old server, save what you want to keep. The backup and recovery guide covers what is worth preserving and how.