Treat recovery as a controlled sequence, not one big button. Rebuild the destination, restore structure if needed, then pull verified members and verify the result before announcing the server is live again.
Overview
A full RestoreCord recovery usually has two parts: pull verified members back into a Discord server, and restore server structure from a snapshot if you have one. These are separate operations because Discord member authorization and Discord server structure are different data sets.
Snapshots do not restore member authorizations. Pull Members is the recovery path for people; Snapshots is the recovery path for roles, channels, settings, emojis, and messages.
Create or pick the Discord server, then invite the correct bot.
Use a snapshot when channels, roles, or permissions also need to come back.
Recover verified members with the authorizations already stored by RestoreCord.
Restore Paths
- Situation
- Original server still exists
- Recommended path
- Fix bot permissions, optionally restore a snapshot to repair structure, then pull missing verified members.
- Situation
- Original server was deleted
- Recommended path
- Create a new Discord server, invite the bot, restore the latest snapshot if available, then pull members into the new server.
- Situation
- Only members need to move
- Recommended path
- Use Pull Members. A snapshot restore is not required.
- Situation
- Only roles/channels were damaged
- Recommended path
- Restore a snapshot. Member pulling is not required unless members left or were removed.
- Situation
- You do not have a snapshot
- Recommended path
- Create the Discord server structure manually, then use Pull Members for verified users.
Recover Members
Prepare the destination
Create or choose the Discord server where members should be restored. Invite the same RestoreCord bot connected to the source RestoreCord server.
Fix bot permissions
Give the bot permissions to add members and manage selected roles. Move the bot role above roles it will assign.
Start a pull
Open Dashboard -> Servers, click Pull Members on the source server, select the destination, configure roles and limits, then start the migration.
Monitor migration
Use Dashboard -> Migrations to monitor progress, queue state, and completion history.
Restore Structure
Find the snapshot
Open Dashboard -> Snapshots, search for the server or snapshot ID, and open the snapshot details.
Preview when available
For current snapshots, use preview to inspect channels, roles, members, and messages before restoring.
Select bot and destination
Choose a valid bot and the Discord server to restore into. The bot must be installed in the destination server.
Choose restore options
Set messages per channel within your plan limit and decide whether to clear the destination server before restore.
Run the restore
Confirm the restore. Large servers may take time because Discord applies API rate limits to channel, role, and message operations.
The clear-server option is destructive for the destination server. Use it only when you intend the snapshot to replace the current structure.
After Restore Checklist
- Verify the bot role is still above roles it needs to manage.
- Run a staff verification and confirm the correct role action happens.
- Check webhook logs or custom webhook delivery if you rely on audit events.
- Review channel permissions, especially private staff and verification channels.
- Open the Migrations page and confirm member pull status before announcing completion.
- Create a fresh snapshot after the restored server is stable.
Constraints
- Constraint
- Member authorization
- Impact
- Only members who verified and remain pullable can be added back.
- Constraint
- Discord rate limits
- Impact
- Large pulls and restores can take time. Rate limits are expected behavior.
- Constraint
- Bot permissions
- Impact
- Missing permissions can block role assignment, member adds, channel creation, or message restore.
- Constraint
- Snapshot age
- Impact
- A snapshot restores the server state from the time it was created, not the current desired state.
- Constraint
- Plan limits
- Impact
- Snapshot count and message restore limits vary by plan.