Discord → Matrix + Mumble migration kit (practical plan)

What this guide is (and isn’t)

This is a field-tested migration checklist for communities that want to reduce platform dependency. It assumes a group size of roughly 5–200, with a small admin/mod team.

• Focus: pilot design, onboarding, roles/permissions, and operational hygiene.
• Not focus: turning Matrix into a clone of Discord, or building a sprawling “all things” stack.

The core rule: voice first

In most Discord communities, voice is where the social glue lives. People will tolerate a new chat app if voice still works. They will not tolerate chat stability if voice becomes a mess.

So treat Mumble as the critical path:

• One server address.
• One join password (or registered users if you’re stricter).
• One short onboarding doc.
• Push-to-talk guidance for people on noisy mics.

If you already have a Mumble server: great. Don’t “improve” it during the migration. Freeze changes until the move is done.

0) Run a pilot (48–72 hours)

Pick 5–15 trusted people (mods + friendly regulars). The pilot’s job is not “feature completeness” — it’s to identify friction, especially on mobile and on voice.

Pilot checklist

• Create the Matrix space + a few rooms (see below).
• Stand up Mumble and test from Windows + mobile.
• Write a 1-page onboarding doc with screenshots.
• Test permission boundaries (who can invite, create rooms, kick, etc.).
• Simulate a moderation incident: spam + a bad actor joining voice.

At the end of the pilot, you should be able to answer one question: can a normal member join voice in under 2 minutes?

1) Decide the “stack” (keep it boring)

For most groups, this is enough:

• Chat: Matrix + Element client (desktop + mobile)
• Voice: Mumble + official Mumble client (desktop) + Mumble client on mobile
• Docs: a single “Start here” page (Google Doc, GitHub page, or website guide)

Avoid adding a third “bridge” tool or a bot framework during the move. Every extra component becomes a support ticket.

2) Matrix structure that actually works

The most common failure mode is room sprawl. Discord lets you create lots of channels without people feeling lost. Matrix will punish you for that.

Recommended starting layout

• #announcements (post-only)
• #general (default landing)
• #support (how to join, client issues, onboarding)
• #voice (voice server info + etiquette + “who’s on”)
• #offtopic (optional)

Roles & permissions (Matrix)

In Matrix, room power levels are your “permissions”. Keep it simple:

• Admins: can change room settings and ban.
• Mods: can kick/ban and redact spam.
• Members: can chat and invite (or not, depending on your risk tolerance).

Decide early whether you allow federation (open to other servers) or keep it closed (single homeserver). You can change later, but it’s easier if you choose a posture upfront.

3) Voice structure that works (Mumble)

The goal isn’t “lots of channels.” It’s predictable voice that doesn’t break under load.

Channel layout

• Lobby (default)
• General
• Quiet / Work
• AFK
• Mods (optional, restricted)

Join model

• Small trusted group: shared server password is fine.
• Higher-risk groups: require registered users and keep admin/mod permissions tight.

Write one paragraph that tells members what you expect: push-to-talk by default, no recording, and how to report issues.

4) Onboarding: write one “start here” page

People don’t read long docs during a migration. Make onboarding boring, short, and obvious. You want a single link you can paste anywhere.

Start here page template

1. Install Element (desktop and/or mobile). Include one official link.
2. Join the space (invite link).
3. Install Mumble (desktop or mobile client).
4. Add server: address + port + password.
5. Audio sanity: set push-to-talk, set input device, test whisper/shout if you use it.

Add a “known issues” section with 3 bullets. It will cut support load more than any feature work.

5) A sane rollout plan

Avoid “big bang” unless your community is already in active revolt. A staged approach preserves trust.

Day 1: announce + invite

• Post the Start Here link in Discord.
• Invite key members first (regulars who help the vibe).
• Run a scheduled voice hangout on Mumble.

Day 3: make the new place the default

• Stop creating new channels in Discord.
• Pin the Start Here link everywhere.
• Move events/voice first: “join voice here.”

Day 7+: downgrade Discord to a lobby

• Lock most channels read-only.
• Keep a single room for “how to join.”
• Announce that support happens in Matrix.

6) Moderation & safety notes (minimal, but real)

• Matrix: ensure mods can redact spam and ban quickly.
• Mumble: keep admin permissions limited; use server passwords and registration if needed.
• Logging: don’t collect more than you need. Don’t build a surveillance machine “just in case.”

If your Discord move is triggered by identity/age verification policy changes, be explicit about your posture: you want less sensitive data collected, not more.