Updated October 2026
MSPs and IT shops: ticket history and runbooks
Your MSP has years of tickets, runbooks, onboarding checklists and escalation notes, each one a problem, a diagnosis and a fix written by people who document for a living. AI companies now pay to license copies of records like these, and support tickets are among the records in highest demand. The catch is that much of your queue is about your clients' systems, so a deal usually starts with what is yours.1,2
What buyers want
What would a buyer want from my MSP?
Tickets and incident records, change requests, runbooks, onboarding checklists and escalation notes. Buyers take tickets and connect to tools such as Zendesk, Jira and ServiceNow, and micro1 lists technology among the industries it takes.3,4,5,6
A ticket tied to the change that fixed it shows a whole piece of work from start to finish, and a PSA that links tickets, changes and time entries already holds that history, and brokers list the same records as in scope for MSPs.7
Your clients
My clients' details are all through my tickets
Tickets name client users, server names, IP ranges and sometimes passwords. Some buyers will not take data held on behalf of clients, and the rest remove names, account numbers and credentials before anything goes out. For an MSP, that can take a large share of the archive off the table.2,7,8
A cleaner first offer is your own knowledge: the internal knowledge base, runbooks written for your techs and onboarding checklists, with client-specific tickets held back until the buyer has answered the questions below. Your managed services agreements weigh more here than in most trades, so talk those questions through with the buyer, and bring your own advisor if you like.
Do you qualify
Is my MSP big enough?
What it could pay
What could an MSP's records pay?
Next step
How much work is it for my team?
Your techs already know how to export from the PSA, so the work is light. It is mostly an export, about 1-3 hours by the buyers' own count, or read-only access to the sources you approve with no ongoing work. Take the quiz with your headcount and tools, and we will introduce you to the buyers we work with that take IT companies.19,20,21
FAQ
Questions, answered with sources
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Before you sign
Questions to talk through with your buyer
Every business is different, so these are best talked through with the buyer you're working with. Their team goes over them with you before anything is signed.
Questions for this kind of business
- Which of our client agreements address data about their systems that we hold?
- Do customer, vendor or platform contracts, NDAs or API terms restrict this?
- Could the data include privileged material or trade secrets?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?