How to merge two Discord servers into one community
Two communities joining forces, or one network folding its side servers together: a merge is a set of RestoreCord migrations into a shared destination. Here is how to run one cleanly and keep everyone informed.
Short answer
Choose the destination, invite each source community's RestoreCord bot to it, and start one migration from each source server. Use a role on join per community, let RestoreCord reconcile members who are already present, and share a live status link.
When merging makes sense
- Two communities around the same game, creator or topic decide to combine.
- A network of small servers wants one active hub instead of five quiet ones.
- A regional or language server folds back into the main community.
- A project ends and its members are welcomed into a sister server.
How a merge works in RestoreCord
Each server in RestoreCord owns its own list of verified members. A merge is therefore one migration per source server, all pointing at the same destination. Overlap is handled for you: when someone from the second community is already in the destination because they were in the first one too, RestoreCord reports them as already in server instead of trying to add them again.
Choose the destination
Either one of the existing servers survives, or you create a fresh one with a new name. Keeping the larger server usually means fewer people have to move. A fresh server feels fairer to both sides and gives you a clean permission layout. If you start fresh, a snapshot of one server can restore its structure as a starting point.
Get every bot into the destination
Members authorized the bot they verified with. If the two communities used different RestoreCord bots, both need to be in the destination, each with its role above the roles it should give, and each with the Create Instant Invite permission.
Enable Server Members Intent for every bot involved. It lets RestoreCord read who is already in the destination, which is exactly what keeps a merge fast when the communities overlap.
Mark where people came from
Use Add roles on join with a different role for each source, like Sunset Veteran and Dawn Crew. It helps moderators, lets you build welcome channels for each group and makes it easy to see who still needs onboarding.
Order and timing
| Approach | How | Best for |
|---|---|---|
| Back to back | Finish the first migration, then start the second | Smaller merges, simple monitoring |
| Scheduled | Give each migration its own start time (Premium+) | A merge announced for a specific date |
| In waves | Use the Batching style on Enterprise | Large merges where staff greet each wave |
Keep both communities in the loop
Generate a share link for each migration from the dashboard. The public page shows its status, progress and counts as they change, plus the destination server. It never lists individual members. Links expire on their own, and the owner can stop sharing at any moment. Pin the link in both old servers.
What to say
Explain why the communities are merging, what the new server is called and that members who verified will be added automatically. Anyone who never verified can join through a normal invite you post in the old servers.
Sunset Guild and Dawn Collective are becoming one community: Horizon Hub. If you verified here, you will be added automatically on Saturday and get the Sunset Veteran role. Follow the move live through the pinned share link. Never verified? Use the invite below.
After the merge
- Keep the old servers read-only for a while with a pointer to the new one.
- Take a snapshot of the merged server as its first recovery point.
- Review the outcomes of each migration and invite anyone who was skipped.
Planning a straight move rather than a merge? Read moving a large community and Consistent vs Batching, or go back to RestoreCord Migration.
Merge two servers in three steps
Pick the destination
Decide which server survives, or create a fresh one for the merged community.
Invite every source bot
Each community's bot must be in the destination with its role above the roles it gives.
Pull each community in
Start a migration from each source server, with a role on join that marks where people came from.
Merging questions
Stronger together, in one server
Run your merge with RestoreCord migrations and bring both communities home without double counting a single member.