Moving a Discord server is not really a file transfer. Discord does not hand you an export button that packs up your members, message history and bots and drops them somewhere else. What you can move is the structure of the server and, far more importantly, the habits of the people in it.
That second part decides whether a migration works. Plenty of communities have announced a move, posted a new invite link and watched half their members quietly stay behind. This guide is about avoiding that: a step-by-step plan for moving a Discord server to another platform (or to a fresh Discord server) without losing the people who made it worth moving.
It applies whether you're heading to Recline, a forum, Matrix, another chat app, or simply rebuilding on Discord after a compromised or messy server. Where something depends on Discord's own settings, check Discord's current help documentation, because those details change.
Step 1: Write down why you're moving
Members will ask, and “we're moving” is not an answer. Write one or two sentences you can repeat in every announcement. Common, legitimate reasons include:
- Privacy and identity concerns, such as age or ID verification policies. We covered that in Discord's government ID requirement.
- Ownership and control: wanting a space where the community's rules and data aren't subject to sudden platform changes.
- A fresh start after a raid, a compromised admin account, or years of channel sprawl.
- A better fit for how the group actually talks: long-form discussion, encrypted conversation, or a smaller and quieter space.
If you can't state the reason clearly, members won't feel it either. And if the reason only matters to the moderators, consider whether a move is worth the disruption at all.
Step 2: Audit what you actually have
Before you build anything new, take inventory of the old server. A simple shared document is enough:
| Item | What to record | Does it move automatically? |
|---|---|---|
| Categories and channels | Names, order, topics, which ones are actually used | Structure can be copied with a server template |
| Roles and permissions | Role names, colours, who holds staff roles, private channel access | Role definitions yes; role assignments no |
| Members | Rough count of genuinely active people | No—everyone has to join again |
| Message history | Which pins, FAQs and resources people still rely on | No, not with built-in tools |
| Bots | Each bot, its commands, and any stored data (levels, currency, logs) | No—re-add and reconfigure; check each bot's own export options |
| Rules and onboarding | Rules text, welcome messages, screening questions | No—re-post them |
This is also the moment to prune. Channels nobody has posted in for months don't need to come with you. A new space with eight active channels feels livelier than one with forty empty ones.
Step 3: Copy the structure with a server template
Discord's built-in server templates are the closest thing to an export. With the Manage Server permission, you can generate a template link from Server Settings. A template captures the skeleton—channels, categories, roles and permission overrides—but not members, messages or bots.
A few practical notes:
- Some channel types, particularly Community-only ones like forums and stage channels, may not carry over cleanly. Note them in your audit and recreate them by hand.
- A template is a snapshot. If you change the original server afterwards, sync the template before you use it.
- If you're leaving Discord entirely, the template is still useful as a checklist even when the destination can't import it.
Some platforms and third-party tools can read a Discord template or connect with a bot to rebuild your structure for you. Before granting any migration tool access to your server, read what permissions it asks for and what it stores. A tool that needs full administrator rights deserves the same scrutiny you'd give a new moderator.
Step 4: Build and test the new space before anyone arrives
Set the new space up completely before the announcement. An empty, half-configured server is the fastest way to lose momentum.
- Recreate channels from your trimmed list, with topics that explain what belongs where.
- Recreate roles with the minimum permissions each one needs. Migrations are a good time to fix years of permission creep.
- Re-post rules, FAQs and key resources. Don't rely on members digging through the old server.
- Test as a regular member. Use a test account or a test role to confirm private channels are actually private and the welcome channel is writable.
- Test moderation. Make sure each moderator can delete a message and remove a test account before real members arrive.
- Test calls on the devices your members use if voice matters to your group.
If privacy is part of your reason for moving, check precisely what the new platform protects. “Private channel” and “end-to-end encrypted” are not the same thing. For Recline, our encryption explainer and beta status page spell out what is encrypted today and where the limits are.
Step 5: Move your core people first
The single biggest predictor of a successful migration is whether people are already talking when everyone else arrives. So invite in this order:
- Moderators and admins. Assign their roles by hand and let them settle in.
- Your 10–20 most active members. Ask them personally, explain the reason, and give them a few days to start conversations.
- Everyone else, via a public announcement.
When a regular member clicks the new invite and sees familiar names mid-conversation, joining feels like following friends rather than starting over.
Step 6: Announce once, clearly, with a date
A good migration announcement fits on one screen and answers four questions: why, where, when and what happens to the old server. For example:
We're moving to [new space] because [one-sentence reason]. Join here: [invite link]. From [date], events and announcements happen only in the new space. This server becomes read-only on [later date] and will stay up as a signpost.
Pin it, post it in your announcement channel, and repeat it in the channels people actually read. Avoid “soon”. Dates create momentum; vague timelines give people permission to wait.
Step 7: Move one activity at a time
People don't move to a platform; they move to wherever the thing they care about happens. Pick your community's anchor activity—a weekly game night, a feedback thread, a study session, an AMA—and run it only in the new space from the announced date.
Once that activity has moved, move the next one. Within a few weeks the old server has nothing left to offer except the link to the new one.
Step 8: Make the old server read-only, not deleted
Deleting the old server is tempting, but it strands everyone who was away, on holiday, or simply slow to notice. Instead:
- Remove send-message permissions for regular members across the old server.
- Leave one visible channel with the reason, the new invite link and the date of the move.
- Keep moderators around long enough to catch spam or questions.
Some communities keep the signpost up for months. It costs little and keeps bringing stragglers home.
What you will lose (and how to soften it)
Be honest with your members about what doesn't come along:
- Message history. Copy the handful of pins, guides and FAQs that matter into the new space. Most old chat history is rarely read again.
- Bot data. Levels, currencies and custom commands live in each bot's own storage. Ask the bot's developer whether an export exists, or treat the move as a reset and say so.
- Some members. Not everyone will follow, and that's normal. A smaller, active community usually beats a large, silent member list.
A migration checklist
- A one-sentence reason for the move.
- An audit of channels, roles, bots and must-keep resources.
- A synced server template (or a written structure checklist).
- A fully configured, tested new space.
- Moderators and core members moved first.
- One clear announcement with an invite link and dates.
- Anchor activities moved one at a time.
- The old server locked as a read-only signpost.
Choosing where to go
The right destination depends on what pushed you to leave. If it's identity requirements or data collection, compare platforms on what they require at sign-up and what they can read. Our roundup of the best Discord alternatives in 2026 compares several options honestly, including ones that aren't Recline.
Recline is built for exactly this kind of move: creator-owned Spaces, roles and permissions, voice calls, no email or phone number required to sign up, and client-side encryption for channel and DM text. It's also still in open beta and doesn't currently offer an automatic Discord import, so plan to rebuild your structure by hand using your template as a checklist. Read why people choose Recline as a Discord alternative, then run a small pilot with your core members before moving everyone.
Whatever you choose, remember the order of operations: reason, structure, people, then activity. Get the people part right and the rest follows.