Pull Members
Restore Discord members or move them to a new server. Pull Members adds your verified members to any server your bot is in, with no cooldown or member cap.
Pull Members adds your verified members to a Discord server using the authorization they gave your bot when they verified. Each pull runs as a migration: RestoreCord works through your eligible members one by one, adds them to the server you pick, and gives them the role you chose. Snapshots restore a server's structure; pulls restore its people.
Overview
| Question | Short answer |
|---|---|
| Who can be pulled? | Members who verified with this server's bot and still authorize it. See Before You Pull. |
| Where can they go? | Any Discord server the server's bot is in, including the original server. |
| Is there a cooldown or member cap? | No. There is no RestoreCord pull cooldown or member cap on any plan, including Free. Unlimited pulls every eligible member; a typed pull amount can be up to 50,000. |
| How fast is it? | One member at a time, with a fixed delay you set between members, or a delay range on Premium and higher. Discord rate limits can slow it down. |
| Which plan do I need? | Pulling works on Free. Premium, Business and Enterprise unlock extra options. See Pull Settings. |
| Who can start one? | The server owner, or a sub-user with the Pull Members permission. |
Only members who verified with this server's bot and still authorize it can be pulled. Discord rate limits and each member's account decide how quickly a migration finishes.
The Pull Members Guides
Before You Pull
Pull Settings
How a Pull Runs
Monitor and Control
Results and Troubleshooting
Pull One Member
Automate Pulls with the API
Before You Pull
- Your server has a custom bot linked, and the bot token still works.
- The bot is in the destination Discord server.
- The bot's role is above any role you want to give, and it can create invites there.
- Server Members Intent is on for the bot in the Discord Developer Portal, so RestoreCord can skip members who are already in the server.
- Join Servers For User was on when your members verified. Without the
guilds.joinscope, Discord refuses to add them.
The full checklist and eligibility rules are in Before You Pull.
Start a Pull
Open the pull popup
Open Servers, find the server that holds the verified members, and click Pull Members. The button is greyed out if no bot is linked to the server.
Pick the destination, role and amount
The popup is titled Migration. It shows your bot, then three main fields:
| Field | What to pick |
|---|---|
| Select Server | The Discord server members are added to. It lists every server your bot is in, with member counts, and starts on the server's own Discord server. |
| Add roles on join | One role given to each pulled member. Roles above the bot's role are listed under Roles with Missing Permissions and can't be picked. |
| Pull amount | How many members to pull successfully. Leave it empty (Unlimited) to pull every eligible member. |
Open More Options for nicknames, country and quality filters, scheduling, pull style, delay and leaving the server. Each one is explained in Pull Settings.
Check the summary and start
The Migration Summary shows the Target, Target members (your pull amount), Pullable members (how many are eligible after filters) and Estimated time.
Click Pull Members. If another migration is already running for this server, the button reads Queue Migration and the new migration waits its turn.
Pull Options
These are under More Options in the popup. Plan labels mean that plan or higher.
| Option | Plan |
|---|---|
| Member Nickname | Premium |
| Schedule Migration | Premium |
| Delay Range | Premium |
| Leave server after migration | Premium |
| Country Specific | Business |
| Max Leave Rate and Left Server Duration | Business |
| Min. Stay Duration and Min. Activity | Enterprise |
| Grouping pull style | Enterprise |
| Fixed Delay and Include New Members | All plans |
For large communities, start with a conservative delay and watch the first few minutes before speeding up. Discord rate limits are normal during large migrations.
Monitor Progress
Each pull creates a migration you can follow on the Migrations page. Active shows running, queued and paused migrations, plus any that finished in the last 10 minutes. History lists every migration. You can pause, resume, stop, open the member queue and share a live status link.
Statuses, counters and every action are explained in Monitor and Control.
Why Members May Not Pull
- Unauthorized: the member removed your bot under Authorized Apps in Discord, or their authorization expired. They have to verify again.
- Already in the server: they were already a member, so they're counted under Members in Server.
- Too many servers: Discord won't let them join any more servers.
- Banned: they are banned from the destination server.
- Filtered out: country, quality or firewall rules removed them before the pull started.
- Bot problem: the bot lost access, its token or secret changed, or it's missing permissions in the destination server.
Each result, and what to do about it, is in Results and Troubleshooting.
FAQ
Related Features
- Add verified members adds members to your server automatically as they verify.
- Multi-server pulling (Business) also adds them to up to 25 other servers when they verify.
- OAuth Authorization Checks (Premium) regularly finds members who stopped authorizing your bot.