Cautious import path · AmariBot
Start with your
GDPR data request.
Guardy Bot has not obtained a verified sample of AmariBot's actual self-service export, so this import is built on an unverified proxy: the member field names Amari publishes. A newly requested package may not match, and if it does not, Guardy Bot tells you instead of guessing.
Checked at every step
Four checks between export and apply.
Guardy Bot checks each file against the format that bot really exports, so a file it does not recognise is rejected, not guessed at.
- 1
Request your account-level AmariBot data package and keep the original JSON unchanged.
- 2
Select Amari in the Guardy Bot import wizard. Uploads are limited to 8 MB.
- 3
Confirm that the wizard recognizes member id and exp rows. A file in an unfamiliar format is rejected with a clear message instead of guessed at.
- 4
Review matched members, rejected rows, and computed Guardy Bot levels. Apply when the preview looks right.
Amari's own level value is not imported because its curve is not MEE6's. Reward-role settings are not imported from this source.
Keep the progress
Your community earned those levels.
Bring them with you. Guardy Bot shows you every change first, and you decide when it goes live.