Updated October 2026
Selling an MSP: tickets and runbooks as a licensable record
Your MSP sells on its monthly contracts and the techs who service them. Behind those contracts sit years of tickets triaged, escalated and fixed, and the runbooks that told each tech what to try next, and AI companies now pay to license a copy of records like these. Buyers say support tickets are in especially high demand, and software and IT sit on their target lists.1,2
What they want
Your PSA history and your runbooks
ConnectWise or Autotask holds years of tickets with time entries, internal notes, client replies and fixes, and your documentation platform holds the procedures. Buyers name ticket systems such as ServiceNow, Zendesk and Jira alongside email, Teams and Confluence, and ask for SOPs, knowledge bases and task histories. A help desk is the repeated workflow buyers say they look for, run every day.3,4,5,6
The best tickets have the full arc: the client's first description, the tech's checks, the escalation, the fix and the runbook note so it does not happen again. Shops that enforce good ticket notes hold a far richer record than shops where tickets close with one word, and if you are tidying the PSA before a sale anyway, the same work helps a data offer.
Who fits
Is my MSP big enough?
Most buyers want 20 to 30 or more people, some count staff at your peak, and a few state no minimum and list software among their industries. A 12-tech shop is a conversation with only some of them, which is why the quiz asks your size first and introduces you to the buyers that take an MSP like yours.7,8,1,9,10
No MSP deal has been published. Published ranges mostly run $100K to $2M, as the buyers' own claims.11,12,13,14
| Fact | Value and source |
|---|---|
| Ventra ads | Meta ads from 2026-10-11: "It's a license, not a sale", "You keep your company"; US companies with 30+ employees and 3+ years of records |
| What Grepped buys | Messages, codebases, documents, business records and task histories, from Slack, Teams, Gmail, Outlook, GitHub, Jira, Google Drive, SharePoint, Notion, Salesforce, HubSpot, QuickBooks, Xero, Zendesk, Asana and ServiceNow |
| Pewter (broker) | Lists freight and logistics, agencies and consulting, trades, accounting, engineering, manufacturing, software and law firms; 20+ staff and 3+ years; paid by the licensing firm at close |
What stays out
Client credentials and environment details
Tickets are full of client details: hostnames, IP ranges, user names and the odd password pasted where it should not be. That is held on behalf of clients, which buyers say can be left out, and they commonly strip names, contact details, account numbers and credentials. Run your own sweep for secrets in tickets and docs before any sample leaves; it is good hygiene for the sale of the business too.15,16
In a sale, the acquiring MSP or platform usually moves clients into its own PSA and retires yours, so the archive has a clear end date. Most buyers start with a short intake form and make offers within a few days to two weeks, so there is time to ask before the switch-off.17,11
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
- How will client environment details and any credentials be found and removed before transfer?
- Do customer, vendor or platform contracts, NDAs or API terms restrict this?
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?