Exports
Get your data out of Kognit for reporting, backup, or migration.
On this page
What you can export
| Data | Format | Typical use |
|---|---|---|
| Contacts | CSV | Backup, migration, external analysis |
| Tickets | CSV | Reporting, compliance records |
| Campaign results | CSV | Performance analysis |
Exporting contacts
From Customers, apply any filter or segment first — the export follows what is on screen. Exporting a segment is usually more useful than exporting everything.
Large exports are prepared in the background and offered as a download when ready rather than blocking the page.
Handling an export file
Export files contain personal data. Treat them accordingly:
- Do not email them around
- Do not leave them in a shared drive indefinitely
- Delete them when the analysis is done
An exported CSV sitting in someone's Downloads folder for two years is one of the more common ways customer data leaks, and it is entirely avoidable.
Exports for data subject requests
For a GDPR access request, export that contact's record and their ticket history from the contact page. That is the data you hold about them.
See Data and privacy.
Before you cancel
Cancelling a subscription reverts you to Free limits; it does not delete your data. But if you intend to leave, export first:
- Contacts
- Ticket history you are required to retain
- Your knowledge base content — this is the part teams forget, and it is the part that took the longest to write
Programmatic access
For anything recurring, use the API rather than exporting by hand. Scheduled manual exports are reliably forgotten. See API keys and the API reference.