Bring supported Discord audit events or a previous bot export into the staff-only member timeline with validation and deduplication.
How to import moderation history into GuildPilot
When moving moderation workflows, GuildPilot can import supported Discord audit events or a UTF-8 CSV or JSON export. Imported records appear as clearly labelled, staff-only reference history and do not recreate old punishments.
Before you start
You need dashboard access and the permission shown on the import page. Discord audit import also requires access to View Audit Log; Discord retains that source for a limited period. For a file import, use real Discord user IDs and ISO 8601 UTC timestamps.
Warning: Review the source and preview carefully. Imported records become part of the staff-only member timeline, although they do not add warning points, trigger escalation, contact members or apply Discord actions.
Import previous records
1. Open Import moderation history
Choose Safety → Moderation, then open Import moderation history. Read Legacy records remain reference-only before selecting a source.
2. Choose Discord or a file
Use Import Discord audit history for supported actions still retained by Discord. For another bot, download the CSV template or prepare a UTF-8 CSV or JSON file using the exact schema shown.
3. Validate and preview a file
Enter a stable lowercase Source key, choose the file, then select Validate and preview. Review valid, warning and error rows; correct the source rather than inventing missing identifiers or timestamps.
4. Commit the valid records
Confirm the preview token is still current, then choose Import valid records. Review the batch summary for imported, skipped and failed rows.
Test the setup
- Prepare a small fictional export containing one resolved warning for a test Discord ID. Validate it, inspect the preview, import it and open that test member's staff profile. Confirm the event is labelled with its external source and that active warning points did not change.
What a successful setup looks like
The batch summary reports the outcome, valid records appear in the staff-only timeline with source labels, and repeated imports using the same stable identifiers do not duplicate the same record.
Common problems
Old Discord actions are missing
Cause: They are older than Discord's available audit window or were stored only inside another bot.
Fix: Export the previous bot's history and use the documented CSV or JSON file path.
Rows fail validation
Cause: A required user ID, supported action or UTC timestamp is missing or invalid.
Fix: Use the downloadable template and correct the source file before validating again.