How RestoreCord restores your Discord members
Channels can be rebuilt from a snapshot. People are harder: they have to agree to be added. Here's how RestoreCord gets that agreement up front, and how it uses it when your server is lost.
Short answer
Members who verify approve your bot through Discord's OAuth2 flow with permission to join servers for them. If your server is lost, you create a new one, add the bot and start a pull, and RestoreCord adds those verified members back.
It starts at verification
Discord doesn't let a bot add someone to a server on its own. The user has to authorize it, through Discord's official OAuth2 consent screen. RestoreCord's verification is that consent screen. When a member presses Authorize with Join Scope enabled on your server, your bot gains permission to add them to servers later. No login token or password is ever involved.
That's why verification matters from day one. The members you can restore tomorrow are the members who verified with your bot today.
When you'd use it
- Your server was nuked or deleted by a compromised account
- Discord removed the server and you're starting again
- You're rebranding or merging communities into a new server
- You want to move members into a fresh, cleaner server layout
How a pull works
A pull, also called a migration, takes the verified members of a source server and adds them to a destination. You pick the destination, optionally a role to assign on arrival, and any limits or filters, then start it or schedule it. Progress appears in a real-time migration log, member by member.
| Option | What it does | Plan |
|---|---|---|
| Pull cooldown | None: start another pull whenever you need to | Every plan |
| Pull delay | Fixed delay on Free, a configurable delay range on paid plans | Every plan |
| Scheduled migrations | Start the pull at a set time | Premium and up |
| Leave-rate and left-duration filters | Skip members who hop servers or left long ago | Business and up |
| Stay and activity filters, multi-server pulls | Fine control over who moves | Enterprise |
How fast it goes
RestoreCord doesn't throttle you, but Discord does. Large pulls are paced by Discord's rate limits and by each account's state, which is normal. For big communities, start with conservative delays and watch the first batch before speeding up.
Who can't be restored
Members who never verified, and members who later removed your bot from their Authorized Apps, can't be pulled. Announce the new server's invite in your other channels for them. Members already in the destination are reported as already in server rather than added twice.
Pull with the same custom bot your members verified with. Their authorization belongs to that bot, so a different bot can't use it.
Rebuild the channels first with a RestoreCord snapshot, check what the Free plan covers, or go back to the RestoreCord home.
Bring your community back
Create the new server
Set up a fresh server, or pick the one you want to move your community into.
Invite your custom bot
Add the same bot members verified with and place its role above the roles it will assign.
Restore the snapshot
Rebuild channels, roles and permissions from your latest snapshot before anyone arrives.
Start the member pull
Pull verified members in and watch progress in the real-time migration log.
Member restore questions
Start making members restorable
Every member who verifies today is a member you can bring back tomorrow. Set up verification on the Free plan.