Overview
Pull Members moves verified RestoreCord members into a Discord server using the authorization they granted during verification. It is the member-recovery side of RestoreCord: snapshots restore structure, while pulls restore people.
Only members who previously verified with the relevant bot and still have usable authorization can be pulled. Discord rate limits and account state determine how quickly a migration completes.
Before You Pull
- Invite the RestoreCord bot to the destination Discord server.
- Give the bot permissions to add members and manage any role you want assigned.
- Move the bot role above the destination role in Discord's role hierarchy.
- Confirm Join Scope is enabled on the source server if you expect RestoreCord to add members.
- Decide whether you are pulling into the original server, a replacement server, or an additional pull server.
Start a Pull
Open the pull popup
Go to Dashboard -> Servers, find the source server that owns the verified member database, and click Pull Members.
Configure your migration
Select the destination server, choose any role to assign on join, set limits and filters, then start or queue the migration.
Pull members drawer preview
Mirrors the migration start drawer from the server dashboard.
Quality filters
Keep members with missing analytics data eligible for the migration.
Grouping settings
Members per group
Delay between groups
Remove pulled members again after the migration flow finishes.
Pull Options
- Option
- Add roles on join
- What it does
- Assign one or more roles to pulled members after they enter the destination server.
- Option
- Pull amount
- What it does
- Limits how many eligible members the migration should attempt. Leave unset to use the available eligible pool.
- Option
- Fixed pull delay
- What it does
- Sets a consistent delay between pull attempts to reduce pressure on Discord rate limits.
- Option
- Delay range
- What it does
- Premium+ range-based delay instead of one fixed delay.
For large communities, use conservative delays and monitor the first batch before increasing throughput. Discord rate limits are normal during large migrations.
Monitor Progress
After a pull starts, RestoreCord creates a migration record. Open Dashboard -> Migrations to monitor active migrations and review history.
- Status area
- Active migrations
- What it tells you
- Current pull progress, queue state, attempted count, and success count.
- Status area
- Queue modal
- What it tells you
- Live queue and progress details for the selected migration.
- Status area
- History
- What it tells you
- Completed migrations, success rate, timestamps, and destination server information.
- Status area
- Analytics
- What it tells you
- Business+ migration analytics and activity graphs where available.
Why Members May Not Pull
- Unauthorized: The member revoked authorization or the access token can no longer be refreshed.
- Already in server: Discord reports the member is already in the destination server.
- Banned or blocked: The destination server or firewall state prevents the member from joining.
- Bot permission issue: The bot cannot add the member or assign the selected role.
- Discord limits: Discord rate limits or account constraints slow or reject specific operations.
- Filtering: Country, retention, churn, or activity filters excluded the member from the eligible set.