How to Archive a Discord Server (and Where the Community Goes Next)

Discord has no built-in "archive server" button. There is no menu item that turns an active server into a permanent, read-only record. If you are winding a server down, splitting a community, or moving somewhere else, "archiving" is really three separate jobs: freezing the server so nothing new happens in it, exporting the message history so it survives even if the server is deleted later, and, optionally, giving the community a new place to land.

It helps to be honest about what Discord is and is not. Discord message history is not indexed by search engines. If someone outside your server searches for a question that was already answered inside it, they will never find that answer, no matter how good it was. Once a server goes quiet or gets deleted, that history effectively disappears from view for anyone who was not already a member. Archiving well means deciding, on purpose, what happens to years of conversation before that happens by accident.

Step 1: Freeze the server

Freezing comes first because it stops new messages from complicating your export later, and it gives members a clear signal that something is changing.

1. Announce a date. Pin a message and post it in every active channel, telling members when the server is going read-only and why.
2. Set every channel read-only. In Server Settings, edit permissions for the @everyone role and remove Send Messages. Do this channel by channel, or on the categories that contain them, so nothing gets missed.
3. Disable invites. Discord lets you pause invites from Server Settings, so no one new can join a server that is about to stop being active.
4. Turn off community features you no longer need. If the server has Community mode enabled for things like server discovery or announcement channels you are not using, turn those off to stop new signups and noise.
5. Keep one announcements channel open for staff. Leave a single channel writable, restricted to moderators or admins, so you can post updates about the migration itself.

A note on terminology: some Discord clients show an "Archive" option next to threads or channels. That only hides a thread from the active channel list. It is not server archiving, it does not export anything, and it does not protect the content if the server is later deleted.

Step 2: Export the history

Discord's official Data Package, requested from Settings, Privacy & Safety, Request all of my data, only covers messages you personally sent. It does not give you a copy of the whole server, and there is no setting that lets an admin request everyone else's messages this way.

For a full server export, most admins turn to third-party tools. DiscordChatExporter is the best known option: it is open source, actively maintained, and can export channels to HTML, JSON, CSV, or plain text. A few things to know before you rely on it:

• It authenticates with either a bot token or a user token. A bot token, added to your server with read-only permissions on the channels you want to export, is the safer choice. Using a personal user token to automate exports is against Discord's Terms of Service, so avoid it even though some guides describe it.
• Large servers take time. A server with years of history and many channels can take hours to export in full, especially with attachments included.
• Attachments are not bundled automatically. Images, files, and other uploads typically need to be downloaded separately from the export itself, and old attachment links can expire.
• Check your jurisdiction's privacy rules before publishing anything. An export contains other people's words, usernames, and sometimes personal details. What you are allowed to do with that later depends on where you and your members are, not just on Discord's own rules.

We are not going to walk through extracting a token step by step here. If you go this route, follow the tool's own documentation and set up a bot token specifically for the export rather than reusing an existing one.

Step 3: Decide what happens to the exported history

An export is just a pile of HTML, JSON, or text files until you decide what it is for. Three common paths:

1. Keep it private as a backup. This is the minimum. Store the export somewhere durable, note the date, and move on. Nobody outside the old server ever sees it again, but it is not lost either.
2. Publish selected channels as static HTML on a website. DiscordChatExporter's HTML output can be uploaded as-is. This works well for a handful of channels that matter, like a rules channel or a highlights reel, but it does not give readers search or navigation the way a real site does.
3. Import the valuable threads into a forum by hand. FAQ answers, setup guides, and pinned messages are usually a small fraction of the total history, but they are the part worth the effort of manually rewriting into proper posts.

Be clear with yourself about the limits here. There is no one-click Discord-to-forum importer on Forumera, or, as far as we know, anywhere else. Every export we have seen requires a person to read it and decide what is worth keeping.

Step 4: Give the community a next home

Freezing and exporting protect the past. What members actually want to know is where to go next. There are three reasonable answers, and they are not mutually exclusive.

Another Discord server. If real-time chat is the main thing your community values, spinning up a fresh server and inviting everyone over keeps the format members already know. It does nothing for discoverability or search, since the new server starts with the same limitations as the old one.

A forum. A forum is a better fit for anything that should still be findable a year from now: guides, troubleshooting threads, product feedback, long debates worth revisiting. Threads live at their own URLs, they can be searched, and depending on how the forum is configured, they can be found by people who were never members in the first place.

Both. Many communities keep Discord for live conversation and add a forum for anything worth finding later. Chat handles the moment, the forum handles the memory.

If you want a hosted forum without running your own server, Forumera is one option: there is a free plan, no ads, and each forum gets its own subdomain with categories, boards, and threads. On a public forum, those threads are indexable by search engines, which solves the specific problem that started this whole process. You can create a forum here, and if you are still comparing platforms, our Discord alternatives guide covers more ground.

Checklist

• Set a freeze date and announce it in every active channel
• Remove Send Messages from @everyone in all channels
• Pause invites in Server Settings
• Turn off Community features you no longer need
• Leave one staff-only channel open for migration updates
• Choose an export tool and set up a dedicated bot token with read-only access
• Run the export and confirm channels, attachments, and message counts look complete
• Decide whether the export stays private, gets published, or feeds a manual forum import
• Pick the community's next home: another Discord server, a forum, or both
• Post the new home's link in the frozen server's staff-only channel and pin it

FAQ

Can you archive a Discord server without deleting it?

Yes. Freezing a server (removing Send Messages permissions, pausing invites, and turning off features you no longer need) leaves the server intact and visible to existing members while stopping new activity. Nothing forces you to delete it, and many communities keep a frozen server around indefinitely as a reference.

Does deleting a server delete the messages for members?

Deleting a server removes it and its message history from Discord for everyone, including members who had access before. Individual members do not retain a personal copy of the conversations unless they exported their own messages beforehand or someone ran a full server export in advance.

How long does an export take?

It depends on the size of the server. A small server with a few channels and light history can export in minutes. A large, years-old server with many channels and heavy attachment use can take several hours. Rate limits imposed by Discord's API are usually the bottleneck, not the export tool itself.

Is exporting other people's messages legal?

This depends on where you and your members are, and on what you do with the export afterward. Keeping a private backup is generally low risk. Publishing other people's messages publicly raises different questions depending on local privacy law and Discord's own Terms of Service. Check both before you publish anything, rather than assuming an export you are technically able to make is one you are free to share.