This page is general information, not legal, tax or financial advice. Talk to a qualified professional about your situation.

A support queue is a record of thousands of real problems and how a team solved them: the customer’s words, the agent’s questions, the escalation, the fix and the follow-up. That is exactly the kind of workflow AI developers want to learn from. micro1, Nyne, Troveo and Mode name support data on their pages for companies; micro1 also asks for support QA and knowledge-management material.

What is in it, and what to leave out

Tickets are written by and about customers, so they carry more personal data than most business records:

  • Names, emails, phone numbers and addresses in every ticket. Buyers de-identify these; see privacy and de-identification.
  • What your privacy policy promised. If it says customer data is used only to provide the service, licensing tickets may not fit that promise even after de-identification.
  • Business customers’ contracts. B2B agreements often treat support communications as the customer’s confidential information.
  • Sensitive categories: health details, payment card numbers or account numbers pasted into tickets. Card data and health records covered by HIPAA usually stay out; see legal considerations.
  • Attachments: screenshots and files customers sent, which can contain anything.

The help-center articles and macros your team wrote are usually the easiest part to license: they are your own work and rarely contain customer data.

How long tickets survive after you cancel

  • Zendesk: automated deletion starts 90 days after cancellation. Zendesk says support can temporarily reactivate an expired account so you can export.
  • Jira Service Management (Atlassian Cloud): the app is deactivated 15 days after the subscription period ends; data is kept 60 days on paid plans (15 on free) after deactivation, then deleted.

The data retention clock dates these from your cancellation day.

If the company is closing

Customer data is the part of a closing company’s records with the most rules attached. Read customer data when a company closes before deciding, and for call-center operations see call centers.

What buyers say about support tickets

From each buyer’s own page for companies; open the profile for its other requirements.

BuyerWhat its page names
micro1Customer support: tickets, QA and knowledge management (source)
NyneSupport tickets and service histories (source)
TroveoZendesk and Intercom, under CRM and support (source)
ModeZendesk among its sources (source)

Questions people ask

Our tickets are full of customer names and emails. Is that a problem?

Buyers remove names, contact details and other identifiers before passing data on. The bigger question is what you promised customers: if your privacy policy or contracts limit how their data is used, that decides what can be included.

We cancelled Zendesk last month. Are the tickets gone?

Zendesk says automated deletion starts 90 days after cancellation, and that you can ask support to reactivate the account temporarily so you can export. Do it soon.

Sources

  1. micro1: Monetize your company's operational data
  2. Nyne: Sell company data
  3. Troveo: License your business data
  4. Mode: Get paid for your operational business data
  5. Zendesk: Service Data Deletion Policy
  6. Zendesk: Can I export data from an expired account?
  7. Atlassian: Cloud licensing
  8. Atlassian Support: Reactivate a subscription

Other kinds of company data

Email

Years of customer, vendor and internal threads. Export before you cancel Google Workspace or Microsoft 365: deleted mailboxes do not come back.

Team chat

Slack and Teams show how decisions were made. Free Slack plans delete history after a year, and only some plans export private channels.

Documents and files

SOPs, proposals, specs and wikis in Drive, SharePoint, Dropbox, Box, Notion or Confluence. Each vendor deletes on its own schedule.

CRM and sales records

Deals, accounts and the notes behind them. Valuable to AI buyers, and also to anyone buying your business, so decide which comes first.

Source code

Repositories, commits, pull requests and issues show how software is really built. Third-party code and client work need sorting out first.

Projects and tasks

Jira, Asana and Monday boards record who did what, when and why. Asana's export right after termination lasts only 30 days.

Meeting and call recordings

Recorded calls and transcripts capture decisions as they happen. Only two buyers name them, and consent to recording matters most here.