Migration guide
A good migration plan is not a dramatic overnight switch. It is a staged move: prepare the new server, seed activity, keep your core members informed, and give people a reason to join the new space before they are forced to. That matters even more in 2026, while Discord's age-verification and teen-by-default changes keep pushing some communities to rethink where they want to live long term.
Most communities lose momentum when owners try to shut one home and open another on the same day.
Structure, announcements, moderation routines, events, and key channels matter more than old chat logs in the first phase.
People move faster when the new place already feels active and useful instead of empty and purely theoretical.
Before creating anything, list the workflows your community depends on: announcements, support, events, moderation, onboarding, bot actions, and the channels members really use. Migration gets easier when you identify the essential parts instead of trying to clone every category, every joke channel, and every historical message.
The first version of your Stoat server should already include clear rules, a welcome area, announcement channels, a few live discussion spaces, and moderator presence. If people click through and land in an empty shell, they will interpret the migration as unfinished and return to old habits on Discord.
A practical rule is to invite moderators, trusted regulars, and a small early cohort first. Seed a bit of conversation and make the place look inhabited before you do a broad public push.
Members need to understand what is happening. Explain why you are opening a Stoat server, what the benefits are, what is changing, and what is not changing yet. The goal is to reduce uncertainty. If the move sounds like pure ideology or urgency, people treat it as optional noise.
Keep Discord open during the transition window. Pin one clear message, link the Stoat invite, and repeat the call to action in announcements, events, and regular community touchpoints.
Most communities overestimate the importance of full historical migration and underestimate the importance of current utility. What gets people to adopt the new space is active value: new announcements, scheduled events, live support, fresh discussions, and moderator presence.
If you have a website, docs, pinned resources, or FAQs, move those references first. Then make sure your most important links, intros, and recurring activities point toward Stoat instead of leaving Discord as the only obvious home.
A migration works faster when Stoat is where the next thing happens. That could be early event access, a role for early adopters, cleaner onboarding, more visible announcements, or simply the message that this is where the future version of the community is being built.
Once your Stoat server is usable, list it on StoatBoard. That creates a shareable public landing point, helps searchers discover your community outside of Discord itself, and gives the migration a visible home on the open web. For many communities, that is the difference between a private experiment and a real transition strategy.
Document your essential channels, roles, and moderation routines.
Prepare your Stoat server with welcome, rules, announcements, and core discussion spaces.
Invite moderators and a small early-adopter group before the public announcement.
Announce the transition clearly inside Discord and explain the reason in plain language.
Move live value first: events, support, new announcements, and recurring discussions.
List the new Stoat server on StoatBoard so members and searchers can find it easily.
If you are preparing a migration, the next practical move is to browse how current Stoat communities present themselves, then list your own server once your structure and announcement plan are ready.
Pulse+