How to Move a Discord Server to Another Platform

By the MOT team · Published October 13, 2026

Moving a community is mostly a people problem with a small technical problem attached. The technical half (recreating channels, roles and permissions) takes minutes if you do it right. The people half (getting members to actually show up in the new place) takes weeks and is where most moves fail. This guide covers both, in the order you should do them.

It applies whatever platform you're moving to. We mention MOT where it's relevant, because MOT can import a Discord server's layout directly, but every step here is general.

Step 1: Decide why you're moving, and write it down

Members follow a reason, not a link. Before you touch any settings, write two or three sentences that explain what the move gets the community. "Discord is bad" is not a reason anyone acts on. Concrete reasons are:

• You want members to find teammates by game and rank instead of scrolling an LFG channel.
• You want your community's posts, events and voice rooms in one place with your players' gaming profiles.
• You want a smaller, calmer space for a core group, separate from a big public server.

That paragraph becomes your announcement later. If you can't write it, you're probably not ready to move, and that's a useful thing to learn before you ask hundreds of people to change apps.

Step 2: Audit the server you have

Most servers that have been running for a year or more carry dead weight: channels nobody posts in, roles from an event two seasons ago, permission overrides nobody remembers adding. A move is the cheapest moment to clean that up, because you're rebuilding anyway.

Walk through the server and sort every channel into three buckets:

• Keep: channels with regular activity (announcements, general chat, your main game channels, voice rooms people actually use).
• Merge: channels that split one conversation in two, such as separate "clips" and "highlights" channels.
• Drop: channels with no messages in months, and one-off event channels.

Do the same for roles. A role should exist for one of three reasons: it grants a permission (moderators), it routes people to channels (game or region roles), or it's an identity people are proud of (event winners, founders). Anything else is clutter.

Delete the dead weight on Discord first, then make the template. The template copies what's there, so a clean source means a clean copy.

Step 3: Make a server template

Discord has a built-in way to copy a server's structure: server templates. If you have the Manage Server permission, open Server Settings, find Server Template, give it a name and generate the link. You'll get a link that starts with discord.new/.

A template is a snapshot of the server's structure. It copies:

• Categories and channels, including their order and topics.
• Roles, with their names, colours and permissions.
• Channel permission overrides (which roles can see or post in which channel).
• Some server-wide settings, such as the AFK channel and the verification level.

It does not copy messages, members or bots. Check Discord's own help article for the current, complete list, because what a template includes is up to Discord. Plan as if you're starting with a well-organised empty building.

Step 4: Import the layout on the new platform

How you import depends on where you're going. Some platforms read a template link directly; on others you recreate the channels by hand using the template as a checklist.

On MOT, open Create Server, choose Import from Discord and paste the discord.new link. MOT shows a preview first (categories, channels, private channels and roles), so you can check it before anything is created. When you import, it recreates text, voice and announcement channels, puts them in the same categories, copies role colours and maps Discord permissions to their MOT equivalents. Channel types without a direct equivalent, such as stage and forum channels, are created as the closest MOT type. Private channels stay private, and the default @everyone role never inherits administrator rights from a template, even if the original had them.

Whichever platform you use, check three things straight after importing:

1. Private channels are still private. Open the server as a regular member (a second account or a test role) and confirm staff channels are hidden.
2. Moderators can moderate. Give a moderator their role and check they can delete a message and kick a test account.
3. New members can post where they should. The welcome and general channels should be writable by everyone; the announcements channel usually shouldn't be.

Step 5: Rebuild what a template can't carry

Some things live outside the structure and need a short to-do list of their own:

Step 6: Move the people

This is the step that decides whether the move works. A practical sequence:

1. Tell the core first. Moderators and your 10–20 most active members should hear about the move before anyone else and join the new server early. A new space with people already chatting is far easier to move into than an empty one.
2. Announce with the reason from Step 1. One announcement, pinned, with the invite link and a date. Say what stays the same (the people, the channels they know) as well as what's better.
3. Give it a date, not "soon". For example: "From the 1st, events and LFG happen on the new server. This server becomes read-only on the 15th."
4. Move one activity at a time. Start with the thing people come for, such as weekly game nights or LFG for your main game. When that activity only happens in the new place, people follow it.
5. Make the old server read-only, not deleted. Lock posting, leave one pinned message with the invite, and keep it around. People who were away for a month will still find their way over.

Common mistakes

• Moving everything at once. A big-bang switch on one evening loses everyone who wasn't online that evening.
• Running two active servers forever. Splitting conversations across two places for months kills both. Set the read-only date and stick to it.
• Copying the clutter. Importing 60 channels into a fresh server makes it feel empty. Ten busy channels feel alive.
• Forgetting permissions. A private moderator channel that becomes public after a move is the fastest way to lose trust. Test as a regular member.

Where MOT fits

MOT is a gaming social network: servers with text and voice channels, plus finding teammates by game, rank and region, squads, events and a feed. If your community is built around playing together, the template import gets your layout across in a minute, and members get matchmaking alongside the chat. If your community is mostly about something other than games, a general-purpose chat platform may suit you better, and the steps above still apply.