On this page
A server owner migrating a community from Discord can request a Data Package, which Discord's help documentation describes as "a ZIP folder of files that you can request through your User Settings that contains all of your Discord data for your account", with a messages folder that "contains all the messages that you have sent on Discord". Your own messages. Plus server metadata: settings, channel lists, audit logs. The rest of the conversation belongs to the accounts that wrote it, the request takes up to 30 days, and there is no owner-side button that hands over the server's discussion.
Anyone about to migrate a community from Discord is therefore not moving a database. They are rebuilding one place inside another while the first one is still running, and the two variables that decide how it goes are how much of the old material gets carried across by hand and how long both places stay open.
The parts that move and the parts that stay
Attachments are the part that decays fastest. Since late 2023 Discord signs attachment CDN URLs, and its developer reference documents three parameters on every one: ex, a "hex timestamp indicating when an attachment CDN URL will expire", is, the issue timestamp, and hm, the signature. Discord refreshes those links inside its own client and nowhere else. An archive scraped today has dead images in it by tomorrow unless the files themselves were downloaded in the same pass.
Facebook Groups have the same shape. Meta's Download Your Information tool exports the content of an account, and posts and comments written by other members are not in it unless they landed on that account's own timeline. No admin-side export of a group's discussion exists.
Accounts do not transfer either. There is no Discord importer that creates members on a forum, so every member registers again, and that registration form is the narrowest point in the whole move. Cut it to what the board cannot run without.
What does move is anything a person is willing to rewrite. That is the honest version of a migration plan: the knowledge moves because somebody retypes it, and any automated copy of the raw chat log is a bonus sitting on top of that work.
The order the move runs in
Governance goes first. Rules, the code of conduct, the moderator roster and the escalation path belong on the new board before any content does, because the first serious dispute gets adjudicated wherever the rules live, and a dispute that gets settled on Discord teaches everyone that Discord is still where decisions happen.
Pinned knowledge goes second. Every Discord server has channels that are documentation pretending to be chat: the FAQ, the setup guide, the known-issues list, the read-this-before-asking pin. Rewriting each as a proper thread with an owner who can keep editing it is a few evenings of work, and those threads are what people find in search a year later.
Build all of that before anyone outside the moderator team sees the board. Categories, rules, working search, thirty or forty real threads. A first visit is spent reading, and an empty board offers nothing to read.
Then announce with a date attached and no cutover. Say what the new place is for, what stays on Discord, and what happens to the old space, because an announcement without those three answers produces curious first visits and nothing after them.
Run both for months. Read on 6 September 2026, Obsidian was running a Discord server listing 195,900 members with 24,300 online, alongside a forum carrying 100,088 registered users, 51,610 topics and 362,685 posts, of which 2,475 were made in the previous thirty days. Home Assistant's Discord showed 164,023 members next to its own forum on the same day. Chat takes the immediate questions and the social noise, the board holds what a future member will need, and moderators carry the good threads across by hand.
The archive moves last, and selectively. Copying a whole chat log into a forum produces a wall nobody reads and pages search engines have no reason to rank. Pick the twenty or thirty conversations people still link back to, rewrite each as one clean thread with attribution and a date, and ask the original authors first where the substance is theirs, since an export gives an owner no rights they did not already have.
The first thirty days on the new board
Elisabeth Joyce and Robert Kraut, studying 2,777 newcomers across six public newsgroups for the Journal of Computer-Mediated Communication in 2006, found that a newcomer who got a reply to a first post went from a 44 per cent chance of posting again to 56 per cent. The tone and the usefulness of the reply made no measurable difference in their data. Getting a reply at all did.
So the staffing rule for the first month is that no first post sits unanswered overnight, written into a rota as an assignment with names on it. Seeded threads work on the same mechanism, which is why a seeded thread with no replies is worse than no thread: seed fewer, answer all of them.
Give people a weekly reason to open the board instead of a daily one. A recurring thread, a summary of what happened in chat, a decision that only gets made on the forum. From the board's point of view a community with ten thousand people on Discord is still starting from zero.
The shape of the losses
Published, audited retention figures for community migrations barely exist. Community consultant Tonya Kubo writes on her own site that every group she has seen leave Facebook lost members on the way, an observation from her client work rather than a measured figure. Anyone promising a move that keeps everyone is promising something nobody has measured.
Codecademy's November 2024 migration shows what the avoidable share of the loss is made of. Its help article dated 8 November 2024 told members they "will need to create a new account", links to the forums and the Discord server were removed the same day, the forums were redirected by the end of that month, and the Discord server was renamed and left officially unsupported after 11 November. Hard cutover, new account, no overlap, all inside a month.
The URLs are the part that cannot be undone later. Checked on 6 September 2026, the old forum domain discuss.codecademy.com does not resolve, so the indexed answers behind those addresses return nothing to anyone who searches for them. A community that owns its old domain can keep it reachable and redirect thread by thread. A community leaving Discord never owned the archive in the first place, and the version that survives is whatever somebody rewrote by hand while the server was still up.