Restoring from Backup
Restore your bot configuration from any backup snapshot. Learn the restore process, preview changes, and handle conflicts.
Restore Process Overview
Restoring from backup is a simple 3-step process: select backup → preview changes → confirm restore.
Step 1: Select Backup
Dashboard → Backup → "Restore" button on any backup row
- • Click restore icon on backup
- • Restore dialog opens showing selected backup details
- • Review timestamp and description
Step 2: Preview Changes
Review what will change before proceeding:
- • Diff view shows current vs. backup settings
- • Green highlights = new/changed settings
- • Red highlights = deleted/removed settings
- • Scroll through all changes
- • "Selective Restore" option to pick specific modules
Step 3: Confirm Restore
Click "Restore Now" button to execute:
- • Confirmation dialog appears
- • Type server name to verify intent
- • Click final "Confirm Restore" button
- • Restore completes in 2-10 seconds
- • Success message confirms restoration
What Restoration Does & Doesn't Affect
Understanding what gets restored and what stays unchanged:
GETS RESTORED
- • All automations and workflows
- • All events and schedules
- • Moderation rules and filters
- • Welcome messages and templates
- • Role rewards and leveling config
- • RBAC policies and permissions
DOES NOT GET RESTORED
- • Member data (levels, experience, stats)
- • Analytics and behavior insights data
- • Incident history
- • Discord server structure (channels, roles)
- • Member profiles or relationships
Selective Restore
Restore only specific modules instead of entire backup:
Choosing Modules
In preview step, click "Select Modules" to choose:
- • Checkboxes for each module
- • All checked by default
- • Uncheck to exclude specific modules
- • Restore only selected modules
Use Cases
When to use selective restore:
- • Only restore automations, keep events as-is
- • Restore dashboard customization without touching rules
- • Recover specific module after accidental change
Handling Conflicts
What happens when restore conflicts with current settings:
Conflict Detection
Conflicts occur when channels/roles in backup don't exist in current server:
- • Channel was deleted
- • Role no longer exists
- • Webhook URL is invalid
Resolution Options
When conflicts detected, choose resolution method:
- • Skip Conflicting: Ignore items with conflicts (safest)
- • Remap: Auto-map to similar channels/roles
- • Force: Restore anyway, may break some settings
Conflict Preview
Review detected conflicts before confirming restore
Restore Preview (Diff View)
Detailed preview showing exactly what will change:
Diff Sections
- • Added: New settings from backup (green)
- • Modified: Changed settings (blue)
- • Deleted: Settings being removed (red)
- • Unchanged: No change (gray)
Expandable Details
Click on each change to see details:
- • Current value
- • Backup value
- • Why it changed
Rollback & Recovery
If restore causes problems, rollback to previous state:
Automatic Rollback Backup
Before any restore, SYNTHET automatically creates a backup of current state
- • Automatically saved with name like "Pre-Restore-[timestamp]"
- • Available immediately in backup list
- • Can be restored if something goes wrong
Quick Rollback Button
After restore completes, "Rollback" button is available for 1 hour
- • Click to instantly revert to pre-restore state
- • No confirmation needed, reverts immediately
- • Button disappears after 1 hour
Manual Recovery
If more than 1 hour passed, manually restore the pre-restore backup
Restoring to Different Server
Migrate your bot configuration to a different server:
Migration Steps
- 1. Download backup from original server
- 2. Add SYNTHET bot to new server
- 3. Go to new server's backup dashboard
- 4. Click "Import Backup" or "Upload File"
- 5. Select downloaded backup file
- 6. Remap channels/roles to new server names
- 7. Proceed with restore as normal
Server Remapping
Channels and roles are automatically remapped:
- • If same name exists in new server, auto-mapped
- • Manual mapping available for different names
- • SearchableSelect shows available channels/roles
Restore Best Practices
- • Always review preview before confirming restore
- • Create fresh backup before testing major restores
- • Use selective restore when only fixing specific issues
- • Test restore in test server first if possible
- • Use rollback button immediately if something seems wrong
- • Check specific channels/automations after restore
- • Document which backup version you restored
- • Notify team members before major restore