Can You Merge Two Discord Servers Into One? (The Real Answer Plus a Migration Playbook)

No, Discord has no native "merge" feature. You cannot combine two servers into one with a button. To merge two Discord servers, you pick one server as the permanent home, rebuild the combined channel and role structure inside it, then re-invite and re-role the members from the other server before retiring it.

That is the honest answer most guides dance around. There is no merge tool hidden in Server Settings, no bot that can absorb one server into another, and no way to transfer message history between servers. But a clean merge is still very doable. Below is exactly what moves, what does not, and a step-by-step playbook to get both communities living under one roof.

The short answer: Discord has no native merge

Discord treats every server (guild) as a completely separate, self-contained object. There is no API call, setting, or official tool that fuses two of them. So when people ask how to merge two Discord servers, what they actually want is a migration: choose a primary server, recreate the missing pieces from the second server inside it, and move the people over.

The good news is that the people are the only thing that truly matters, and people are the easiest part to move. Channels and roles can be rebuilt in minutes. Message history almost never needs to come along.

What you can and can't move between servers

Before you start, it helps to know exactly what is portable and what is locked to its original server. This list saves you from chasing impossible transfers.

What you can move (by rebuilding or re-adding):

• Members - via a fresh invite link to the home-base server. This is the real goal.
• Channels and categories - you recreate them; names and structure copy over in seconds.
• Roles and their colors/permissions - you recreate them and re-assign to members.
• Pinned reference content - rules, FAQs, announcements; copy/paste the text into the new channels.
• Emojis and stickers - download from the old server, re-upload to the new one.
• Webhooks and bot integrations - re-add each bot to the home-base server and reconfigure.

What you cannot move:

• Message history - chat logs are bound to the server they were sent in. There is no export-and-import for normal messages.
• Member join dates, XP, and stats - these reset unless a bot stores them externally (most leveling bots are per-server).
• Boosts - Nitro boosts stay with the server they were applied to and cannot be transferred.
• Roles automatically - members arrive in the new server with no roles; you assign roles fresh.
• Channel-specific reactions and threads - they live with their original messages.

Knowing this upfront changes your plan: you stop trying to preserve old chat logs and instead focus on rebuilding structure and moving people. That is a one-evening job, not a project.

Step 1: Decide which server becomes home base

Pick the server that will survive. Everything else gets rebuilt inside it. Choose the one that is hardest to recreate or most valuable to keep, usually based on:

• Member count - keep the bigger server so fewer people need to be re-invited.
• Boost level - a Level 2 or 3 boosted server keeps its perks (better audio, more emoji slots, banner); a fresh server loses them.
• Vanity URL - if one server has a custom discord.gg/yourname invite, that is worth keeping.
• Established integrations - the server with your payment bots, role-sync, or partnerships already wired up.
• Brand recognition - the server your audience already knows the invite link for.

Once you choose, name it clearly so nobody is confused during the transition. The other server becomes the "source" you are pulling structure and people from.

If neither server is in great shape and you would rather start clean, that is a legitimate option too. Spinning up a fresh, well-organized server and merging both old ones into it can be cleaner than dragging old clutter forward. Our guide on how to create a Discord server from scratch walks through that path.

Step 2: Rebuild the combined structure

Now you recreate the second server's useful channels and roles inside your home base. The aim is a single combined layout, not two parallel sets of channels that confuse everyone.

Audit both servers first. Open them side by side and list every channel and role worth keeping. You will usually find overlap - both servers probably have a #general, a #rules, and an @everyone-style role. Merge duplicates instead of copying them twice.

Rebuild roles before channels. Roles drive channel permissions, so create them first. Recreate each role's name, color, and permission set. Watch the role hierarchy - the order of roles in the list determines who can manage whom, so place moderator and admin roles above member roles exactly as they were.

Then rebuild channels and categories. Group related channels under clear categories (for example, an "Info" category for rules and announcements, a "Community" category for chat). Set channel-level permission overwrites so private or staff-only channels stay locked to the right roles.

Combine, don't duplicate. If both servers had an events channel, you want one events channel in the merged server, not #events and #events-2. Decide the canonical version of each space.

If you are unsure what the combined layout should even include, our breakdown of what channels a Discord server should have gives a sensible default structure you can adapt to your merged community's size.

This is the most tedious part of a merge if you do it by hand - clicking through dozens of channels, roles, and permission overwrites one at a time. There is a much faster way, covered below.

Step 3: Re-invite and re-role members cleanly

With the structure ready, move the people. Discord does not let you bulk-transfer members, so you bring them over with an invite and a clear announcement.

Post a migration announcement in the old server. Pin it. Explain plainly that the community is consolidating, link the home-base invite, and give a date when the old server will go read-only or close. Keep the copy simple - "We're combining both servers into one. Join here: [invite]. This server closes on [date]." No hype needed; people just want the link and the deadline.

Create a clean, non-expiring invite to the home-base server. Set it to never expire and remove any max-uses cap so latecomers can still get in. Drop it in the old server's announcement, pin it, and ideally DM it to active members who might miss the announcement.

Re-role people as they arrive. This is where good setup pays off. Instead of manually assigning roles to every new arrival, lean on automation:

• Reaction roles let members self-assign their own roles (interests, pings, color roles) by clicking an emoji. Set these up once and they handle most role assignment for you.
• Welcome auto-role can drop a baseline "Member" role on everyone who joins automatically.
• For staff and special roles, assign those manually - there will only be a handful.

Keep the old server alive briefly, then retire it. Leave it open and read-only for a week or two so stragglers find the invite, then delete it or archive it. Do not delete it the same day you announce the move - you will lose people who only log in occasionally.

A bot makes this whole step painless. PeakBot's free welcome messages and auto-role greet every arriving member and assign a starter role automatically, and its unlimited reaction roles let people pick the rest themselves. That covers the bulk of re-roling without you touching the member list.

Using an AI builder to recreate the merged layout fast

The slowest part of any merge is Step 2 - rebuilding the combined channel and role structure by hand. Clicking through categories, setting permission overwrites, and recreating a role hierarchy can eat an entire evening, and it is easy to miss a permission and accidentally expose a staff channel.

This is exactly where an AI server builder helps. PeakBot's AI Server Builder generates a complete server - channels, categories, roles, permissions, and automations - from a plain-English description in under 60 seconds. Instead of rebuilding by hand, you describe the merged community you want ("a gaming community with separate areas for two former servers - one for Valorant, one for Minecraft - plus shared general chat, staff-only channels, and self-assign game roles") and it builds the whole structure for you. It is the only Discord bot that generates fully custom server layouts from natural language rather than dropping in a fixed preset template.

That turns the hardest step of a merge into a 60-second prompt. You get a clean, permission-correct structure, then you just move people in. For a full walkthrough of that approach, see our guide on how to build a Discord server with AI.

PeakBot is a free, AI-powered Discord bot powering 500+ communities, and it carries the rest of the merge too. The 30+ free features include AI moderation, XP and leveling, a ticket system, analytics, welcome messages, unlimited reaction roles, anti-raid protection, and full logging - so a freshly merged server is fully equipped from day one, replacing MEE6, Carl-bot, Dyno, and TidyCord with one bot. The AI Server Builder is a Pro feature at $8.25/month (or $69/year) per server; everything else listed above is free with no time limit. You can compare the full split on the features page.

FAQ: merging Discord servers

Can you merge two Discord servers into one automatically?

No. Discord has no automatic merge tool, bot, or API to combine two servers. You have to choose one server as the home base, rebuild the combined structure inside it, and re-invite members from the other server manually.

Can you transfer message history between Discord servers?

No. Messages are permanently tied to the server they were posted in, and there is no native export-and-import for chat history. If you need to preserve specific content, copy/paste important reference posts (rules, FAQs, announcements) into the new server's channels.

Do members keep their roles when they join the merged server?

No. Members arrive in the home-base server with no roles. You re-assign roles using welcome auto-role for a baseline member role, reaction roles for self-assignable roles, and manual assignment for staff and special roles.

Will I lose my Nitro boosts if I merge servers?

Yes, for the server you retire. Boosts stay with the server they were applied to and cannot be transferred. This is why you should pick the more heavily boosted server as your home base whenever possible.

What happens to bots and integrations when I merge?

Bots do not move automatically. You re-add each bot to the home-base server and reconfigure its settings there. A single all-in-one bot like PeakBot reduces this work, since you set up one bot instead of reconnecting four or five separate ones.

Should I delete the old server right away?

No. Keep the old server open and read-only for a week or two with a pinned invite to the new server, so members who log in infrequently can still find their way over. Delete or archive it only after the migration window closes.