Discord migration results explained

A finished migration is a page full of numbers. Some are wins, some are expected skips, and a few are signals you should act on. This guide walks through every line RestoreCord shows you, and what to do next.

Short answer

RestoreCord splits every migration into outcomes: members pulled, already in server, unauthorized, in the maximum number of servers, banned, blacklisted and failed. Only pulled means a new arrival; the rest explain why someone wasn't added. Check the warnings first, invite unauthorized members the normal way and, on Business or Enterprise, read the Migration Activity graph for leaves.

Everything lives under Dashboard, Migrations. The Active tab lists migrations that are still running; History keeps the finished ones with their pulled, failed and total counts, start time and destination. Open any migration to see its details and the live queue.

The status column

A migration is always in exactly one of these states:

StatusWhat is happeningYour move
Queued / WaitingCreated, waiting for its start time or its turnNothing, unless the start time is wrong
PendingPreparing: fetching and checking membersLet it finish; large servers take a while
PullingMembers are being added right nowWatch the first wave in the queue
PausedHeld by you; picks up where it stoppedFix the cause, then Resume
StoppedHalted for good; cannot be undoneStart a new migration if needed
FinishedEvery eligible member was attemptedReview the outcomes below
FailedThe run could not continueRead the warning, fix it, start again

Need a breather? Pause. Stop asks for confirmation because it ends the migration immediately and permanently.

Reading the outcome counts

Each attempted member lands in one bucket. Most of them are not failures at all:

  • Members Pulled: added to the destination with their earlier authorization. These are your real arrivals.
  • Members in Server: already there, so RestoreCord didn't add them twice. High numbers are normal in a merge.
  • Members Unauthorized: they revoked access, or the token can no longer be refreshed. A regular invite is the only route.
  • Members in Maximum Servers: Discord won't let the account join another server until it leaves one.
  • Members Banned and Members Blacklisted: the destination or its firewall is keeping them out, usually on purpose.
  • Failed: Discord limits or a bot permission problem rejected the add.

Filters also shrink the pool before anyone is attempted. If you used country, churn risk, left server duration, retention or activity filters, the people they excluded never show up as failures, which is exactly what you want.

Warnings worth acting on

The migration failed straight away

The bot is missing permissions in the target server. Re-invite it or grant its role Create Instant Invite, then start a new migration.

Pulling is slower than expected

If the bot can't read the target server's members, people already there can't be skipped up front, so each of them costs an attempt. Turn on Server Members Intent for the bot in the Discord Developer Portal.

Discord has limited member pulling

Discord itself is throttling additions to this server. Pause, give it time and resume. RestoreCord adds no pull cooldown of its own, so this is never a plan limit. Wider delays help, as covered in Consistent vs Batching.

The Migration Activity graph

On Business and Enterprise, each migration gets an activity graph: a line for cumulative members pulled and a line for members who left afterwards, plus the leave rate and markers such as the start, batch waits and the end of the run. It answers the question raw counts can't: did people stay?

PatternLikely cause
Leaves spike right after a waveMembers weren't told about the move
Steady trickle of leavesThe new server feels empty or confusing on arrival
Flat leave lineThe announcement and welcome flow did their job

Share the numbers without the dashboard

A share link exposes a small, member-free summary: status, progress, counts, the destination server and when the link expires. Notice what's missing: no usernames, no IDs, no member list. Expired or deleted links show a not-found message instead.


The follow-up routine

  1. Post a normal invite in the old server for unauthorized members and anyone who never verified.
  2. Check that every banned or blacklisted entry is someone you meant to keep out.
  3. If failures cluster at one point, compare it against the warnings and the bot's role position.
  4. Take a snapshot of the destination now that it holds the community.

Still planning? Start with how to move a large community, or head back to RestoreCord Migration.

Migration results questions

Know exactly where every member landed

RestoreCord reports each outcome of a migration separately, so you always know who arrived and who still needs an invite.