Importing
Preview the move before it touches the leaderboard.
Imports are admin-only and staged first. Guardy validates identifiers, XP, duplicates, source levels, and row failures before an atomic apply.
Supported source paths
user_id,xp header is detected automatically; other columns require explicit mapping.Before uploading
- Keep the original file unchanged and select the matching source.
- JSON and CSV uploads are limited to 8 MB. Oversized files are rejected before parsing.
- The raw upload is parsed into temporary staging rows and is not retained as a file.
- Make a private record of the preview counts before applying a large migration.
Choose an apply mode
- Replace
- For each member present in the source, use the source XP. Guardy-only members who are absent from the source are left untouched.
- Merge maximum
- For each imported member, keep whichever XP total is higher. Re-running the same file converges to the same result.
Guardy never offers a sum merge because running the same import twice would double-count progress.
Review and apply
- Confirm the detected source and apply mode.
- Review accepted, skipped, duplicate, and rejected rows.
- For MEE6, confirm every source level agrees with the independently calculated curve.
- Apply once. The leaderboard mutation is transactional; a failed apply leaves current XP intact.
The direct MEE6 API can carry a reward-role ladder; other supported source paths do not import reward definitions. A captured MEE6 ladder is summarized separately and is applied only after an explicit opt-in—it is never bundled silently with the XP apply. After a successful import, Guardy posts a member notice naming the source and the privacy controls.
Source evidence checked 4 August 2026: MEE6 public leaderboard instructions,Lurkr export format, andPolaris export implementation. The AmariBot envelope remains explicitly unverified; see its migration page before relying on it.