Is your ServiceNow or ConnectWise history worth money?
In this article
What is in a ServiceNow, ConnectWise and Autotask exportWhy buyers want itHow to export itWhat is removedWhat it pairs withWhich buyers name itWhat is actually in a ServiceNow, ConnectWise and Autotask export
- Every ticket, incident, problem and change with time entries and resolution notes
- Service catalog requests and approvals
- Change management records and the approvals behind them
- Knowledge base articles
Why buyers want it
A ticket that went from alert to diagnosis to fix, with time entries, is a complete unit of work. Change management adds the approval process. Buyers want the volume and the structure. For an MSP, the question is whether client agreements allow a de-identified copy to be licensed; many are silent, some forbid it.
- One enterprise buyer
- names business process outsourcing and IT firms in its hiring for this program; lists tickets in its core categories (published, 2026).
- Another enterprise buyer
- names support transcripts (published, October 2026).
- The multi-lab licensing platform
- has a dedicated MSP data assessment (published, 2026).

How to export it
You do not have to do this before talking to a buyer. The buyer walks your admin through it once a deal is scoped. For reference, as of October 6, 2026:
- ConnectWise Manage: reports and the API; a full data export is arranged through ConnectWise support or an integration partner.
- Autotask (Datto): the API and the Export data tools under Admin.
- ServiceNow: table exports to CSV or XML, or Export Sets for scheduled bulk exports; the REST API for everything else.
- Knowledge base articles export separately.
Vendors move menus. Check the vendor's help center for the current path.
See what your company's records could get.
Ten questions, under five minutes, built from the buyers' own published ranges.
Get my estimate →What is removed before anyone sees it
- Client company names become tokens
- Client employee names in tickets
- Credentials, network diagrams and anything that could access a client system
- Client programs whose contracts forbid secondary use, excluded entirely
How scrubbing works, and what every buyer commits to.
What it pairs with
One system is a record. Two linked systems are a story. This is where the number moves most.
- Microsoft Teams
- The engineer-to-engineer help behind the ticket.
- QuickBooks and Xero
- The contract and the billing.
- HubSpot
- The client account and renewal.
Which buyer types name it
Every buyer type, what it publishes, and who it wants.
Industries that run on it
In short
- ServiceNow, ConnectWise and Autotask: high demand among buyers. 2 of the 6 buyer types name this kind of record.
- Years of history and links to other systems drive the number. A snapshot is worth little.
- Names, credentials and anything under a restrictive contract are removed or excluded before use.
- You do not export anything before a deal is scoped. The buyer handles it with your admin.
Questions owners ask.
Our client MSAs are strict.
Then those clients are out of scope. The rest, plus your own operations data, can still be a deal. Read three big contracts before the first call.
Do they want the RMM alerts?
Only where an alert became a ticket and a fix.
Documentation tool with passwords?
Never in scope.
Which buyer?
An enterprise buyer at 30+ staff, another at 20+, the multi-lab platform for larger MSPs.
Briggs Analytics