Migrating from Discord to Stoat

The migration trend is not hypothetical. We see it in our own data at Arcalotl and in the broader community builder ecosystem. Here are the most common reasons:

Open-source values. Many community builders, especially in tech, privacy, and creator spaces, want their community infrastructure to align with their principles. Running on a closed-source platform owned by a corporation that mines user data creates cognitive dissonance. Stoat solves this.

Privacy. Discord collects extensive telemetry on user behavior, conversations, and engagement patterns. For communities focused on security, activism, or sensitive topics, this is a dealbreaker. Stoat does not collect telemetry, and self-hosted instances keep data entirely under your control.

No ads and no upsells. Discord increasingly promotes Nitro subscriptions, server boosts, and premium features throughout the interface. These prompts are designed to extract money from your members for Discord's benefit, not yours. Stoat's interface is clean and focused.

Self-hosting. Running your own Stoat instance means your community data lives on your servers. No risk of platform policy changes, no dependence on Discord's uptime, no possibility of your server being banned or restricted due to opaque moderation decisions.

Discord policy concerns. Discord's terms of service and community guidelines have become more restrictive over time. Servers have been removed with limited recourse. For communities that discuss controversial or sensitive topics within legal bounds, platform independence is risk mitigation.

Here is where migration gets complicated. If you are running a free community, moving to Stoat is relatively straightforward: set up the server, invite members, done. But if you have paying subscribers on Discord, you face a real problem:

Before moving members, identify which billing tool owns each subscription and how it grants access. Closing a Discord server does not migrate billing or link member identities. An abrupt move can leave paying members without the access they expect.

Plan billing continuity separately from moving conversations. If you use another payment tool, confirm its migration options before changing or cancelling any memberships.

Arcalotl supports Discord and Stoat within one connected community. Existing Arcalotl plans and entitlements can cover roles on both platforms.

Arcalotl was designed from the ground up for multi-platform communities. You define your subscription plans once, and they work on both Discord and Stoat. Members on either platform can subscribe, and the same dunning, cancel save, and term optimization flows protect your revenue regardless of where the subscriber lives.

One dashboard shows you analytics across both platforms. You see your total MRR, subscriber count, churn rate, and recovery rate, broken down by platform or aggregated. This means you can track your migration progress in real numbers: how many subscribers are on Discord, how many have moved to Stoat, and how your overall revenue is trending.

This is the foundation of a safe migration. You do not need to choose one platform or the other. You run both simultaneously and let the transition happen naturally.

When you run Arcalotl on both platforms, the following are shared across Discord and Stoat:

• Subscription plans. Same plan names, same pricing, same billing intervals. You define them once and they work on both platforms.
• Stripe integration. The same Stripe Connect account powers both platforms. Your payout schedule, tax configuration, and payment settings are unified.
• Retention settings. Dunning sequences, cancel save offers, term optimization rules. All configured once and applied everywhere.
• Analytics. One dashboard shows revenue, subscribers, churn, and recovery across both platforms, with per-platform breakdowns.
• Stripe customer data. If a subscriber moves from Discord to Stoat, their Stripe customer profile (payment history, card on file, billing address) persists. They are the same customer in Stripe regardless of which platform they subscribe through.

Some things do not automatically transfer between platforms, and it is important to set expectations with your community:

Members need to re-subscribe on Stoat. A Discord subscription does not automatically grant a Stoat role. Each platform manages its own role assignments independently. When a member moves to Stoat, they subscribe through Arcalotl on Stoat, and when they cancel on Discord, the Discord role is revoked. This is two separate actions from the member's perspective.

Platform-specific role assignments. Roles exist independently on each platform. A “Premium” role on Discord and a “Premium” role on Stoat are separate entities managed by Arcalotl on each platform. The subscription plan is the same, but the role object is platform-specific.

Message history does not transfer. Your Discord conversations, pinned messages, and channel history will not move to Stoat. This is a platform limitation, not an Arcalotl limitation. Consider archiving important Discord content before sunsetting, or simply keep the Discord server in read-only mode as an archive.

Bot ecosystem differences. Moderation bots, music bots, and other integrations you use on Discord may not have Stoat equivalents yet. Audit your bot stack before migrating and identify gaps. The Stoat bot ecosystem is growing quickly, but some niche tools may not exist yet.

Run both platforms in parallel for as long as needed. There is no rush. Arcalotl does not charge you extra for running on two platforms. The dual-platform approach protects your revenue during transition and gives members time to adjust. Some communities run both indefinitely and that is perfectly fine.

Do not force migration. The fastest way to lose members is to make them feel pressured. Present Stoat as an option, highlight its benefits, and let people choose. Forced migrations create resentment and churn. Voluntary migrations create enthusiasm and loyalty.

Let the community move naturally. Your most engaged members will move first. They are the ones who care most about your community and are most likely to follow you anywhere. Once they establish themselves on Stoat, the rest of the community will follow because the conversations are happening there.

Create Stoat-exclusive value. Give members a reason to be on Stoat beyond ideology. Host events there first, post exclusive content, run AMAs in Stoat channels. If Stoat has something Discord does not, migration becomes pull rather than push.

Communicate transparently. Tell your community why you are migrating. If it is about privacy, say so. If it is about open-source values, say so. If it is about platform independence, say so. People respect honesty and are more likely to follow a leader with clear principles than one who moves without explanation.

Monitor your numbers. Use Arcalotl's analytics to track MRR across both platforms throughout the migration. If revenue dips, slow down. If it holds steady or grows, you are on the right track. Data-driven migration beats gut-feeling migration every time.

Migrating from Discord to Stoat does not have to mean losing revenue or members. With Arcalotl running on both platforms, you can transition at your own pace, protect every subscription, and give your community the open-source home it deserves. Head to the Stoat integration page to get started.