Pull Settings
Every option in the RestoreCord pull popup, with its plan, default, range, what it does and the matching API field.
Every option in the pull popup, what it does, the plan it needs, and its default. Plan labels mean that plan or higher, in the order Free → Premium → Business → Enterprise. The popup checks the plan of the account you're signed in with. The API field column names the matching field for starting a migration with the API.
All Settings at a Glance
| Setting | Plan | Default | API field |
|---|---|---|---|
| Select Server | All | The server's own Discord server | targetGuildId |
| Add roles on join | All | The server's verified role | selectedRoles |
| Pull amount | All | Unlimited | customPullCount |
| Member Nickname | Premium | None | nickname |
| Country Specific | Business | All | countryCode |
| Schedule Migration | Premium | Now | startTime |
| Max Leave Rate | Business | Off | maxChurnRate |
| Min. Stay Duration | Enterprise | Off | minRetentionDays |
| Min. Activity | Enterprise | Off | maxActivityInterval |
| Left Server Duration | Business | Off | minDaysSinceLeft |
| Include New Members | All | On | includeUnknownMembers |
| Pull Style | Consistent: All · Grouping: Enterprise | Consistent | memberPerGroup, delayBetweenGroups |
| Fixed Delay | All | 0.8s | delayMin = delayMax |
| Delay Range | Premium | 0.4s – 1.5s | delayMin, delayMax |
| Leave server after migration | Premium | Off | leaveServer |
Main Fields
Select Server
The Discord server members are added to. The list shows every server your bot is in, largest first, with its member count. Search by name or ID. When two servers share a name, the ID is shown next to it. Sub-users only see servers they have Pull Members access to.
- It starts on the Discord server your RestoreCord server is linked to. Pick another server to pull into a new or backup server.
- Changing the server clears the role and reloads that server's roles.
- Invite Bot on the bot card adds your bot to another server.
- If the bot token is invalid, the popup shows Invalid Bot Token with a Manage Bots button and won't load servers.
Add roles on join
One role given to every pulled member. Despite the label, you pick a single role.
- No role gives no role.
- Roles managed by bots or integrations aren't listed.
- Roles at or above your bot's highest role appear under Roles with Missing Permissions and can't be picked. Click Why? for the fix: in Discord, open Server Settings › Roles and drag your bot's role above the role you want to give.
- Before the pull starts, RestoreCord checks the role by giving it to your bot in the destination server. If that fails, the pull doesn't start (see start errors).
- Members who were already in the server get the role too when RestoreCord reaches them with Discord. Members it skipped up front don't (see How a Pull Runs).
Pull amount
How many members to pull successfully. Leave it empty (Unlimited) to pull every eligible member.
- Whole numbers from 1 to 50,000. A number above the eligible count is lowered to it.
- RestoreCord keeps going until this many members have joined, or it runs out of members. Members already in the server and failed members don't count towards it.
More Options
Open More Options to see these. A setting your plan doesn't include is dimmed, can't be changed, and shows the plan it needs.
Member Nickname
Premium. A nickname set on each member as they join. 2 to 32 characters.
- The nickname is used exactly as you type it, for every member. The placeholder
%USER%in the field is not replaced with the member's name. - It's only set on members who are newly added. Members who were already in the server keep their nickname.
none(any case) means no nickname.
Country Specific
Business. Only pull members from one country. Pick All to turn it off. Members whose country RestoreCord doesn't know are left out while a country is set.
Schedule Migration
Premium. Start the migration later instead of now: Now or 1 to 48 hours ahead, in whole hours. The migration waits as Pending until then. The Estimated time doesn't include the wait.
Smart Filters
Quality filters that remove members before the pull starts, based on RestoreCord's analytics about each member across servers. Each one is Off by default. The Pullable members count updates about a second after you change a filter.
Max Leave Rate
Business. Skip members who leave servers too often. Keeps members whose leave rate is at or below the value. 0% to 100% in 5% steps; 100% (Off) turns it off.
Min. Stay Duration
Enterprise. Only pull members who stayed at least this long on average. Keeps members whose average stay in servers is at least this many days. 0d (Off) to 90 days.
Min. Activity
Enterprise. Only pull members who were active in the selected time window. Keeps members whose average time between activity (messages, voice joins and reactions) is within the window: Past 6h, Past 12h, Past 24h, Past 3 days, Past week, Past 2 weeks, Past month, or Off.
Left Server Duration
Business. Only pull members who left the target server at least this many days ago. Keeps members who left the destination server at least this many days ago. 0d (Off) to 90 days.
Include New Members
All plans. Also pull members with no past activity data. Shown once any filter is on. On by default: members RestoreCord has no data about stay eligible. Turn it off to pull only members who pass the filters with real data.
If member analytics are briefly unavailable, a pull with filters fails to start rather than ignoring them. Try again in a moment.
Pull Style
Click the info button for a chart of both styles.
| Style | Plan | What it does |
|---|---|---|
| Consistent | All | Members join at a steady rate, one after another, with your pull delay between them. |
| Grouping | Enterprise | Members join in bursts: a group at your normal delay, then a long pause, then the next group. |
Grouping Settings appear when you pick Grouping:
| Setting | Range | Default |
|---|---|---|
| Member per Group | 1 to 1,000 members | 50 |
| Delay between Groups | 0.5h to 12h, in 0.5h steps | 1h |
Groups are counted over every eligible member, so members skipped because they were already in the server still take up a place in their group. If the group size is larger than the number of eligible members, there's only one group.
Pull delay
The wait between members, shown as tabs:
| Tab | Plan | Range | Default |
|---|---|---|---|
| Fixed Delay | All | 0.1s to 30.0s, in 0.01s steps | 0.8s |
| Delay Range | Premium | Minimum and maximum, each 0.1s to 30.0s | 0.4s to 1.5s |
- With Delay Range, each member waits a random time between the minimum and maximum.
- The wait is measured from the start of the previous member's request, so a slow Discord response doesn't add to it.
- Discord rate limits come on top of this. When Discord asks RestoreCord to slow down, the whole migration waits.
Leave server after migration
Premium. Your bot leaves the destination server once the migration has finished. Pulled members are not removed; they stay in the server.
- The bot only leaves when the migration ends as Finished and the number of members pulled reached the pull amount. With Unlimited, that means every eligible member was pulled, so any member who was already there or failed keeps the bot in the server.
- It never leaves after a Stopped or Failed migration.
Once your bot leaves, it can't give roles, run commands or pull more members into that server until you invite it back.
Migration Summary
| Row | What it shows |
|---|---|
| Target | The destination server's name. |
| Target members | Your pull amount, or Unlimited. |
| Pullable members | Eligible members after your filters. When filters remove some, it shows eligible / all authorized. Members already in the destination are still included. |
| Estimated time | Members to pull × (average delay + 0.5s), plus the pauses between groups. Rate limits and scheduling aren't included. |
If another migration is running for this server, the popup says Will start after current migration completes.
Start Buttons
| You see | When | What happens |
|---|---|---|
| Pull Members | No other migration is running for this server | The migration starts. |
| Queue Migration | Another migration is running for this server | The migration is added to the queue and starts after the current one. |
| Start Immediately and Queue Migration | Enterprise, with another migration running | The migration isn't put in the queue, but it still waits for the running migration on this server to finish before it starts pulling. Both buttons work the same way. |
The button reads Processing members while the eligible count is loading. It stays disabled if the count can't be loaded, the bot token is invalid, or no server is picked.
You can start up to 5 migrations per minute.
Settings Lock When a Pull Starts
Everything in the popup is saved with the migration when it starts: the member list, delays, groups, role, nickname, Leave server and your bot's credentials. Changing server settings afterwards doesn't affect a queued or running migration. To change a setting, stop the migration and start a new one.