Migrating 50,000 Members to a New Discord Server

Discord server migration is one of the most stressful operations a community owner can face. Whether you are fleeing a compromised server, rebranding your community, or merging two communities after an acquisition, the core challenge is the same: how do you move tens of thousands of members without losing most of them in the process?

This guide walks through the practical realities of migrating a large server, based on real-world migrations that have moved 10,000 to 100,000+ members using Restore Hub's member pull system.

Why Migrations Happen

No one migrates a thriving server for fun. The most common reasons include:

Server Compromise or Nuking

After a severe nuking attack where the server structure is destroyed and members are mass-banned, sometimes it is faster to start fresh with a new server than to try to rebuild the old one. The old server's invite links may be circulating in spam networks, and its reputation with Discord's trust and safety team may be damaged.

Rebranding

When a community undergoes a major rebrand—new name, new focus, new identity—a clean server with a new vanity URL and fresh channel structure can be the right move. This is especially common when a content creator pivots their content or when a project evolves beyond its original scope.

Ownership Transfers and Acquisitions

When a server changes hands through sale or transfer, the new owner often wants a fresh server under their own Discord account. Discord's server transfer feature works for ownership, but it does not help when the old owner wants to retain the original server for other purposes.

Discord Sanctions

In rare cases, Discord may restrict or flag a server due to reports or policy violations. If the issues have been resolved but the server's standing cannot be restored, migration to a clean server is the practical path forward.

The Challenge: Member Inertia

Here is the hard truth about discord member pull operations: you will not get 100% of your members to move. The typical migration rate depends heavily on how engaged your community is:

• Highly engaged communities (daily active users make up 20%+ of total members): Expect 40-60% migration within the first week
• Moderately engaged communities (5-20% daily active): Expect 20-40% migration
• Low engagement communities (under 5% daily active): Expect 10-20% migration

The remaining members are lurkers, inactive accounts, or people who will not see the migration notice. This is normal and expected. Quality of members matters more than quantity.

The Member Pulling Process

Member pulling—the process of programmatically inviting verified members to a new server—is the key technology that makes large-scale migrations possible.

How It Works With Restore Hub

1. Your members are already verified through Restore Hub's OAuth2 system in the original server. Each member has granted the `guilds.join` OAuth2 scope, which allows the bot to add them to servers on their behalf.

1. You create the new server and set up the channel structure, roles, and permissions.

1. You add Restore Hub to the new server and configure it.

1. You initiate a pull from the Restore Hub dashboard. This sends API requests to Discord to add each verified member to the new server.

1. Discord rate limits apply. You cannot add 50,000 members instantly. Discord's API allows approximately 10 guild joins per 10 seconds per bot. For 50,000 members, expect the pulling process to take roughly 14 hours.

1. Members appear in the new server with their roles automatically assigned based on what they had in the old server.

Rate Limits and Timing

Discord's API rate limits are the primary bottleneck. Here are realistic timelines:

| Members | Approximate Pull Time |
|---------|-----------------------|
| 1,000   | ~17 minutes          |
| 5,000   | ~1.4 hours           |
| 10,000  | ~2.8 hours           |
| 25,000  | ~7 hours             |
| 50,000  | ~14 hours            |
| 100,000 | ~28 hours            |

These are estimates. Actual times vary based on Discord's current rate limit policies, server load, and how many members have valid OAuth2 tokens.

Handling Invalid Tokens

Some members' OAuth2 tokens will have expired or been revoked. These members cannot be pulled automatically and will need to re-verify. Restore Hub tracks which pulls succeed and which fail, giving you a list of members who need a manual re-verification link.

Preserving Roles

Role preservation is critical for communities with complex permission structures. Restore Hub handles this by:

1. Mapping roles by name — If the new server has roles with the same names as the old server, members are automatically assigned the matching roles.
2. Custom role mapping — If you renamed roles during the migration, you can define a mapping (e.g., old "VIP Member" maps to new "Premium").
3. Bulk role assignment — Roles are assigned during the pull process, not after, so members land in the new server with the correct permissions from the start.

Minimizing Downtime and Member Loss

Here are practical tips from communities that have successfully migrated large member bases:

Announce Early and Often

Give your community at least one week of notice before the migration. Post announcements in:

• Your main announcement channel
• All active text channels (a single pinned message)
• Direct messages to VIP or premium members
• External platforms (Twitter, YouTube community tab, etc.)

Keep the Old Server Running

Do not delete or archive the old server immediately. Keep it running with a read-only mode (remove Send Messages from @everyone) and a persistent link to the new server. Some members check in weeks or months after a migration.

Migrate During Peak Hours

Start the pull process so that the bulk of members are added during your community's peak activity hours. More online members means more immediate engagement, which creates momentum.

Set Up the New Server Before Pulling

Have the new server fully configured before any members arrive:

• All channels created and organized
• Roles and permissions set
• Bots configured and tested
• Welcome messages and rules posted
• Verification system active

Nothing kills migration momentum like members arriving to an empty, unconfigured server.

Use DM Campaigns Carefully

Restore Hub can send DMs to verified members notifying them of the migration. However, mass DMs can trigger Discord's spam detection. Best practices:

• Send DMs in batches over several days, not all at once
• Make the DM message personal and informative, not spammy
• Include a direct invite link to the new server
• Respect members who have DMs disabled

After the Migration

Once the pull is complete:

1. Review the pull report — Check how many members were successfully pulled versus how many failed
2. Send re-verification links to members whose tokens were invalid
3. Monitor engagement in the new server for the first week
4. Keep the old server as a redirect for at least 30 days
5. Update all external links (website, social media, partner servers) to point to the new server

Key Takeaways

• Server migrations are disruptive but sometimes necessary after compromise, rebranding, or ownership changes
• Expect to migrate 20-60% of members depending on community engagement levels
• OAuth2 member pulling makes large-scale migration possible but is limited by Discord's rate limits
• Role preservation through name mapping ensures members retain their permissions
• Advance notice, a fully configured new server, and keeping the old server running are critical for success

Ready to migrate your community? Get started free at restorehub.net and set up member verification now so you are prepared for any migration scenario.