Support tickets and Jira issues are usually priced as part of a wider company record, not on their own. A shut-down transcription company sold 13 years of Slack, Jira, email and Google Drive files for "hundreds of thousands of dollars" (Forbes, April 2026). micro1 publishes tiers that start at $100,000 for operating companies with 30 or more full-time staff (micro1, October 2026).
On this page
- Why do AI labs want tickets and Jira issues?
- How much are support tickets and Jira issues worth?
- Which tickets are worth more?
- How do I check how many tickets I have?
- How do I export ticket data safely?
- What should I leave out of a ticket export?
- How is ticket data de-identified?
- What should I do next?
- Questions
- Sources
Resolved tickets with the full thread count most, because each one shows a problem, the back-and-forth, the fix and the outcome.
Why do AI labs want tickets and Jira issues?
AI companies are building agents that answer customers, triage bugs and run IT requests. A ticket system is a log of exactly those tasks, with timestamps, status changes and a recorded outcome, which makes it easy to turn into training and test examples.
Buyers say what they want. Labelbox Prism lists "longitudinal customer support" as high demand: six or more months of multi-channel support logs with resolution tags, with a preference for high-volume B2C companies. It marks cross-system Salesforce, Jira and Slack workflows as urgent (Labelbox, October 2026). Troveo writes that "a thousand resolved support tickets with full context and outcomes are worth more than a million log lines" (Troveo, September 2026). micro1 lists support documentation, ticket workflows and QA processes among the records it licenses (micro1, October 2026), and Endless lists tickets, incident records, change requests and runbooks from IT services firms (Endless, October 2026).
Others that name ticket tools include Scale AI (Jira, Linear, ServiceNow, Zendesk), Polyshares (Zendesk, Jira, Linear), Grepped (Jira, Zendesk, ServiceNow), SellMyData (Zendesk, Jira, Linear) and Troveo. AfterQuery lists engineering tickets and incident response. See Labelbox for its terms. Data Licensors, the company that publishes this page, also licenses company records, including tickets and project histories. Our buyer page sits next to the others.
How much are support tickets and Jira issues worth?
| Company | Records named | Amount | Kind of figure | Source |
|---|---|---|---|---|
| Transcription company, shut down, 13 years | Slack, Jira tickets, email, Google Drive | "Hundreds of thousands of dollars" | Press report of a sale | Forbes, April 2026 |
| Software company, operating | Stripe, Amplitude, Jira, Slack, email "and so much more" | "Six-figure" offer, declined | Founder post | X, August 2026 |
| Freight company, 340 staff, 8 years | Workspace, team chat, CRM, support tickets | $850,000 | Broker example; the broker names no company and says none are its clients | Your Data Value, October 2026 |
| Industrial manufacturer, 760 staff, 12 years | Engineering tickets, documentation, ERP | $1,100,000 | Same broker example list | Your Data Value, October 2026 |
Shut-down startups have received $10,000 to $100,000 per company through one shutdown service, SimpleClosure (Forbes via Fast Company, April 2026). For buyer ranges, see how much company data is worth and our deal ledger.
Which tickets are worth more?
| Worth more | Worth less |
|---|---|
| Resolved tickets with the full thread and a clear outcome | Open or abandoned tickets with no resolution |
| Status history, priority changes, SLA timers, reassignments | Only the final state |
| Links to the Slack thread, pull request or CRM account | Tickets with no context anywhere else |
| Years of history from a real product or service | A short trial period |
| Specialist work: billing disputes, field repairs, IT incidents | Password resets and "how do I log in" |
| Internal notes where agents reason about the fix | Only canned macro replies |
How do I check how many tickets I have?
- Jira: run a search in the issue navigator with a JQL query such as
created >= "2018-01-01"and read the result count. Run it per project to see where the history is. - Zendesk: a view of all tickets, or a report in Explore, gives the total and the date of the first ticket.
- ServiceNow: open the incident, request or case list, remove filters, and read the record count.
- Linear: a workspace-wide issue view or Insights shows the issue count per team.
Write down the totals, the years covered, the share that is resolved, and how many agents or engineers worked in each system at its peak.
How do I export ticket data safely?
| Tool | Built-in export | Limits to know |
|---|---|---|
| Jira Cloud | Settings, System, Backup manager, Create backup for cloud, with an option to include attachments. CSV export from the issue navigator for filtered sets | CSV handles up to 10,000 work items per export. Backups with attachments need 48 hours between them. Atlassian recommends staying within 25 GB of data and 50 to 100 GB of attachments |
| Zendesk | Admin Center, Account, Tools, Reports, then JSON, CSV or XML | Off by default: the account owner must ask Zendesk Customer Support to enable exports. CSV leaves out ticket comments. JSON recommended above 200,000 tickets; XML is not available above that. Not on Team plans, which can use the API. Download links last at least three days |
| ServiceNow | Export a list to CSV or Excel from the list menu | Default limit of 10,000 records per export, and 500,000 cells for Excel. Admins can change limits or export in batches |
| Linear | Settings, Administration, Import Export, Export data, with a toggle for private teams | Admins only, owners only on Enterprise. Link expires after 12 hours. The CSV has no comment field and no attachment files; the API covers more |
Sources: Atlassian Support, Zendesk Help, ServiceNow Docs and Linear Docs, checked October 2026.
Check that your export holds the full comment history and internal notes, not just the ticket fields, because the thread is what buyers pay for. In Zendesk that means the JSON export, since the CSV leaves comments out. In Linear, comments come through the API, not the CSV.
Keep exports on encrypted company storage and send them only through an encrypted transfer. At Data Licensors your team runs the export with our step-by-step guidance, or grants a limited read-only connection you can revoke. We never ask for passwords.
What should I leave out of a ticket export?
- Attachments with customer data: screenshots of accounts, uploaded IDs, invoices with card numbers. Payment card data and government ID numbers are on our never accept list.
- Logs and configs pasted into tickets with API keys, tokens or passwords. They are removed either way, but excluding them is safer.
- Security incident tickets that describe open vulnerabilities.
- HR and internal IT tickets about named employees, such as leave or equipment issues.
- Tickets that involve health details. Health records are out of scope for us.
- Clients whose contracts restrict use of their support history. This is common for IT service firms and agencies.
How is ticket data de-identified?
Tickets carry identifiers in many fields at once, so de-identification works field by field:
- Requester names, emails, phone numbers and organization names become placeholders such as [Customer] or [Customer org].
- Agent and engineer names become consistent roles such as [Agent 4], so you can still follow who handed off to whom.
- Order, account and invoice numbers, IP addresses and URLs with tokens are replaced.
- Free text and internal notes are scanned for names and addresses, because people paste them in.
- Status changes, timestamps, priority, tags and the resolution stay, because they make the ticket useful.
A person reviews samples from every batch, and you see a de-identified sample before you sign. See how de-identification works.
What should I do next?
Count resolved tickets per system, decide which projects or queues are in scope, and list what stays out. If your tickets link to a CRM or a codebase, read our guides on CRM data and codebases, since linked records are priced higher. Then get a quick estimate and ask more than one buyer to price the same scope in writing.
