How to move a large Discord community to a new server

Big moves rarely fail on the migration itself. They fail on a bot role in the wrong place, a missing permission or members who don't know why they ended up somewhere new. Here is the plan that avoids all three.

Short answer

Grow your verified pool first, build and secure the new server, fix the bot's role, Create Instant Invite permission and Server Members Intent, announce the move, then run a RestoreCord migration and watch the first wave before letting it run.

Communities move for plenty of reasons: a rebrand, a fresh start after years of messy permissions, leaving a server you no longer fully control, or joining forces with another group. RestoreCord's member migration does the heavy lifting by adding people who verified with your bot to the new server, using the authorization they already gave.

Who can be moved

Only members who verified through your RestoreCord bot and still have valid authorization. If verification went live only recently, keep it running for a while before the move so more of your community becomes eligible. Some people will never verify; they'll need a regular invite, so plan for both.

Prepare the destination first

  1. Set up channels and roles. Keeping the old layout? Restore a snapshot of the old server into the new one.
  2. Invite the same bot members verified with and drag its role above every role it should give.
  3. Make sure the bot has Create Instant Invite in the target. A migration missing required permissions fails early.
  4. Enable Server Members Intent for the bot in the Discord Developer Portal, so members already in the target can be skipped quickly.
  5. Set up verification and the firewall in the new server, so it's protected from the first minute.

Configure the migration

In the dashboard, open Servers, find the source server that holds the verified members and choose Pull Members.

OptionPlanUse it for
Add roles on joinAll plansGiving movers a role the moment they arrive
Pull amountAll plansCapping how many members this migration attempts
Fixed delay / delay rangeRange on Premium+Controlling the gap between pull attempts
Start timePremium+Starting the move exactly at launch
Country, churn risk, left durationBusiness+Targeting specific groups
Retention and activity filtersEnterpriseBringing only your most engaged members

For a full community move, most owners leave the filters off and let everyone eligible come along.

Announce it before it happens

People who suddenly find themselves in a server they've never heard of tend to leave. Explain the move in the old server and everywhere else you reach your community: what's changing, why, when, and what the new server is called. A share link lets everyone follow the progress live.

During the move

Pick a pull style and watch the first wave closely in Dashboard, Migrations. The live queue shows attempted and successful pulls. If something looks wrong, pause, fix it and resume.

Expect some skips

OutcomeMeaning
Already in serverThey joined on their own; reconciled, not a failure
UnauthorizedThey revoked access, or the token can't be refreshed
Banned or blockedThe destination or its firewall keeps them out
Discord limitsRate limits or account state rejected the add

RestoreCord adds no pull cooldown on any plan. If a big move feels slow, that's Discord's rate limits doing their job, not a cap you can buy your way past.

After the move

Keep the old server open for a while with a pinned pointer to the new one, take a fresh snapshot of the destination, and keep verification mandatory so every new arrival is recoverable too. When it finishes, learn how to read the results, or go back to RestoreCord Migration.

The move plan in four steps

  1. Grow your verified pool

    Run verification in the old server for a while before the move, so more members are eligible.

  2. Build and secure the new server

    Restore a snapshot or build channels, set up verification and the firewall, and fix the bot's role and permissions.

  3. Announce the move

    Tell members when and why it's happening, in the old server and wherever else you reach them.

  4. Run the migration in waves

    Watch the first wave closely, pause if anything looks wrong and resume once it's fixed.

Read the Pull Members docs

Launch-day checklist for the new server

Tick these off in the hour before you press Start.

Bot role sits high enough

It is above every role the migration will hand out on join.

Create Instant Invite granted

Without it the migration aborts early with a permissions warning.

Server Members Intent enabled

Lets people already in the target be skipped instead of retried.

Verification live in the target

People who join by invite verify too, so they become recoverable from day one.

Announcement posted

The old server knows the name, date and reason for the move.

Staff on shift

Someone is watching the first wave and can pause it if needed.

Community move questions

Move house without losing anyone

RestoreCord migrations carry your verified members into the new server while you stay in control of the pace.