Systems and records
Do helpdesk exports include internal notes and audit events?
By SourceX Editorial · Updated
Short answer
Helpdesk exports include internal notes and audit events only with some export methods. Report and CSV exports usually flatten tickets into fields and drop private notes, change history and attachment files, while full account exports and API pulls can carry them. Before you cancel a plan or migrate, trace a few known tickets through the export end to end.
Key takeaways
- The export method, more than the helpdesk brand, decides whether internal notes survive.
- Internal notes and ticket events hold the resolution reasoning that public replies leave out.
- Audit events and attachment files are often separate resources that need their own pull.
- A test on a handful of feature-rich tickets reveals more than any row count.
- Internal notes carry more personal and confidential detail than replies, so plan redaction before sharing an archive.
Why internal notes and audit events matter in a support archive#
Internal notes and audit events record the part of support work customers never see: who escalated, what engineering said, which workaround was tried, and why a ticket changed priority or owner. Public replies show the answer. Notes and events show how the team got there.
That difference decides what an archive is good for. A dispute review needs the event trail with timestamps. A new support lead learning a legacy product needs the internal reasoning. And when a software company considers licensing support history, the linked request, investigation and outcome is what makes the records useful rather than a pile of polite replies.
What each export method usually carries#
Each helpdesk export method trades convenience for completeness in its own way. The table describes typical behavior across products; plans and versions differ, so read it as a list of things to verify rather than a promise.
Attachment links deserve a specific warning. An export that lists attachment URLs is not an archive of the files, and once the account closes those links usually stop working. Download the files themselves while access lasts.
| Export method | Internal notes | Audit events | Attachments |
|---|---|---|---|
| Report or view export to CSV | Usually absent or reduced to a count | Usually absent; often only the latest status | Usually absent |
| Built-in full account export | Often included; check the visibility flag | Varies by product and plan | Often links rather than files |
| REST API pull | Generally available with the right endpoints | Often a separate resource to request | Downloadable while links are valid |
| Third-party migration tool | Usually carried if the target supports notes | Often dropped or summarized | Usually carried |
| Vendor-assisted export at offboarding | Depends on what you request in writing | Depends on the request | Depends on the request |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
What to confirm for Zendesk, Freshdesk, Intercom, Help Scout and Gorgias#
Zendesk, Freshdesk, Intercom, Help Scout and Gorgias all let agents write internal notes, but each vendor documents different export routes, switches and deadlines, and those details decide what you can still get out. The table lists what the vendors' own help pages say, then what you still need to test on your account. Menus, plans and limits change, so check the current pages before you plan a cutover.
Two patterns stand out. Several of the simplest exports, such as a CSV from a view, carry ticket metadata rather than full conversations. And some full-history routes need setup or a support request first, which takes time you may not have in the last week of a contract. For any helpdesk not listed, ask the same three questions: can the export tell a note from a reply, does it include the change history, and does it deliver files or only links.
| Helpdesk | How notes are modeled | What the vendor documents | What to confirm |
|---|---|---|---|
| Zendesk | Private comments on a ticket alongside public ones | Data exports are off by default; the account owner asks Zendesk support to enable them. Exports run from Admin Center > Account > Tools > Reports, JSON is recommended above 200,000 tickets, and AI agent tickets cannot be exported. Closed tickets auto-archive after 120 days but stay reachable through the API. | How comment visibility is marked in your export, and how you will pull ticket audits, which hold the change history |
| Freshdesk | Private notes inside the ticket conversation | An older help article says an Account Administrator can export full helpdesk data from Admin > Account, delivered as XML to the registered email. Freshworks partner support says the account and its data are deleted 14 days after the subscription ends and that the export can take up to 10 business days. | Whether the export carries conversations and notes or only ticket fields; request it well before the end date |
| Intercom | Notes as parts of a conversation | Data Export writes Conversations data to your own Amazon S3 bucket in JSON or JSON Lines: a historical export covering two years, hourly or daily periodic exports, and attachments. | How you will reach conversations older than the two-year historical window, and whether notes and assignment parts arrive |
| Help Scout | Note threads inside a conversation | Check current Help Scout documentation for export and API options | Whether thread types are preserved and how attachment files are downloaded |
| Gorgias | Internal notes among ticket messages | A view can be exported to CSV in bulk; the emailed link lasts 14 days and the file holds fields such as ticket ID, tags, channel, subject, dates, survey score and assignee. Custom exports through Gorgias support can include message bodies. Cancellation takes effect at the renewal date, when helpdesk access ends. | Whether internal notes are separated from customer messages, and whether the REST API or a custom export is needed for full history |
How to test an export for completeness#
Testing an export means tracing known tickets from the helpdesk screen into the exported files. A matching row count proves very little; one ticket that uses every feature proves a lot.
- Pick a handful of tickets with internal notes, attachments, merges, reassignments, macros and a reopen.
- Run the export exactly as you plan to run it at full scale.
- Check that each note appears, is marked internal, and keeps its author and timestamp.
- Check that status, priority, group and assignee changes appear with times, not only final values.
- Open the exported attachments after logging out of the helpdesk.
- Confirm that custom fields, tags and satisfaction ratings map to readable names.
- List the gaps and decide whether a second pull, such as an audit or events pull, closes them.
Internal notes need more privacy care than public replies#
Internal notes carry more personal and confidential detail than public replies, because agents write them for colleagues. Notes often contain customer phone numbers, credentials pasted during troubleshooting, frank opinions about a customer, and details about other clients.
Automated detection helps but does not finish the job. Presidio, an open-source, MIT-licensed tool for identifying and anonymizing personal information in text and images, now run as an independent community-governed project, warns in its own documentation that there is no guarantee it will find all sensitive information and that additional systems and protections should be employed. Plan for automated scanning plus human review of samples, and agree what gets removed before any archive leaves the support team.
Illustrative: a SaaS company leaves its helpdesk#
Illustrative: a fictional vertical software company that sells scheduling tools to commercial cleaning contractors is consolidating helpdesks after an acquisition. The migration vendor quotes a tool-based transfer of tickets, public replies and attachments. The CTO asks for a completeness test first.
The test shows that internal notes arrive but lose their internal flag, so they would display as customer-visible replies in the new system, and that reassignment and escalation history is dropped. The team keeps the vendor migration for open tickets only, adds an API pull of notes and ticket events into an IT-owned archive, and downloads every attachment before the old contract ends.
Months later the archive settles a customer dispute about an escalation timeline. It also gives the company an accurate description of its support history for a metadata-only data licensing review.
How SourceX approaches support archives#
SourceX reads support archives through the SourceX Enterprise Data Value Framework, where human-generated signal, domain expertise, data cleanliness and rights raise value, while privacy burden and preparation cost reduce net value. Internal notes often push both sides up at once.
In the SourceX five-step transaction, the Supply step needs only metadata, such as the helpdesk name, years of history and whether notes and events were exported. Preparation removes personal and confidential details, the supplier approves each step, and the SourceX Evidence Packet records the privacy record alongside provenance and permitted use.
Frequently asked questions
Can internal notes become visible to customers after a migration?
They can if an export drops the internal flag and the records are imported into the new helpdesk as ordinary replies. Check how notes appear after a test import, before the full migration runs. Fixing visibility after customers have been notified is far harder than catching it in testing.
Do we need audit events if we already have the final ticket fields?
Final fields show where a ticket ended up, not how it got there. Audit events capture reassignments, priority changes, reopenings and automation, which matter for disputes, service-level questions and any analysis of how problems were solved. If the export lacks them, pull them separately while the account is active.
Can we ask the vendor for a complete export when we cancel?
Often, but terms vary. Check your contract and the vendor's offboarding documentation for export rights, available formats and how long data stays available after cancellation. Put the request in writing and name notes, events and attachment files explicitly.
Should side conversations and chat transcripts be included?
Include them if your team used them for escalations. Side conversations, linked chats and call transcripts often hold the exchanges with engineering or partners, and they may be stored as separate objects. Confirm whether your export method captures them or needs its own pull.
Who should own a support archive after the helpdesk is retired?
IT usually holds the files while the head of support decides who may access them and legal sets retention. Record the owner, location, format and retention decision in your records retention schedule so the archive does not become an orphaned folder.
Sources
- Zendesk data exports are not turned on by default; the account owner must contact Zendesk Customer Support to enable them. Exports run from Admin Center > Account > Tools > Reports, JSON is recommended for accounts with more than 200,000 tickets, and AI agent tickets cannot be exported. Source
- Zendesk automatically archives tickets 120 days after they reach Closed status; archived tickets remain available through search, direct link, user profile and API endpoints. Source
- An Account Administrator can export full Freshdesk helpdesk data from Admin > Account, delivered as XML to the account's registered email. Source
- Freshdesk permanently deletes the account and its data 14 days after the subscription end date, and the export can take up to 10 business days. Source
- Intercom's Data Export sends Conversations data to the customer's Amazon S3 bucket, with a Historical export of two years, Periodic hourly or daily exports and Attachments, in JSON or JSON Lines only. Source
- Gorgias view exports to CSV are emailed via a link active for 14 days and include fields such as ticket ID, tags, initial channel, subject, dates, survey score and assignee; custom exports through Gorgias support can include message bodies. Source
- Gorgias cancellation takes effect on the next renewal date, when the customer loses access to the helpdesk subscription and add-ons. Source
- Presidio's own documentation warns that "because it is using automated detection mechanisms, there is no guarantee that Presidio will find all sensitive information. Consequently, additional systems and protections should be employed." Source
- Presidio has moved from a Microsoft-owned project to an independent, community-governed open-source project under the GitHub organization Data Privacy Stack, and remains MIT-licensed. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.