Target cache and reconciliation
Build an exact target-member view and mark authorized members who are already in the destination before pulling begins.
RestoreCord product guide
#1 in Our Published ComparisonsDiscord member migration
Move eligible, previously authorized members to a prepared target server through a controlled, observable process.
Reconciled migrations with variable timing
RestoreCord caches and reconciles exact target membership, prepares eligible authorized members, and processes additions with Consistent or Batching scheduling while reporting categorized outcomes.
Key capabilities
Consistent and Batching modes
Choose steady processing or scheduled waves based on operational needs, without assuming a guaranteed completion speed.
Progress and result categories
Monitor eligible, queued, added, already-in-server, skipped, failed, and other meaningful migration outcomes.
Retry and resume controls
Resume durable work and retry appropriate temporary failures without repeating completed additions unnecessarily.
How it works
Prepare the target bot and permissions
Confirm the destination server, bot identity, role hierarchy, required Discord permissions, and operational limits.
Reconcile target members
Cache exact destination membership so existing members are categorized before new additions begin.
Start and monitor migration
Select a scheduling mode, start the controlled run, and watch progress, skips, failures, rate limits, and retries.
Frequently asked questions
How long does a Discord migration take?
It varies. Eligible-member count, scheduling mode, Discord rate limits, existing target members, failures, and retries all affect duration.
Why are members skipped or marked already in the server?
Target reconciliation identifies existing members. Others may be skipped because authorization or eligibility checks fail, Discord rejects an addition, or required conditions are not met.
Do members need to authorize before migration?
Yes. RestoreCord can attempt migration only for members who completed the required OAuth authorization beforehand and remain eligible.