Autotask PSA data export: ticket and project history in an MSP sale or license

What history does Autotask PSA hold?

Autotask PSA is where many managed service providers run the whole service business: tickets, time, projects, contracts and billing in one database. A mature instance records every client request, who worked it, how long it took, what fixed it and whether the SLA was met, often back to the year the MSP adopted the platform.

How far back it really goes depends on what came along at adoption. MSPs that moved from another PSA frequently imported only open tickets and active contracts, so the earliest years may live in an older system or a flat file. In diligence, ask for the date of the oldest closed ticket with notes, not the date the subscription started.

What makes an Autotask history valuable?

Value comes from structure and outcomes, not ticket counts. A ticket that records the symptom, the steps tried, the time spent and the final fix is a worked example of IT support. Thousands of them across many client environments, categorized consistently over years, show how technicians reason through problems. That is the kind of multi-step work record AI developers need to train and evaluate agents, and it barely exists on the public web.

Links between modules add more. A ticket tied to a configuration item, a contract SLA, a change approval and a survey response tells a complete story: what broke, on which device, under what service promise, who approved the fix and whether the client was satisfied. Project records add the longer arc of migrations, rollouts and security remediation.

Export and retention realities

Plan any export with the person who administers Autotask, not only with the owner. Options generally include exporting list views and reports, pulling records through the API and, on some subscriptions, reporting or warehouse access. Which of these a given MSP can use depends on its subscription, security settings and the admin's permissions, so check the vendor's current documentation rather than assuming a method or a limit.

Points that come up in nearly every export:

1. Fix the date range and record types first: tickets, notes, time entries, projects, contracts, configuration items.
2. Keep record IDs so tickets, time entries and configuration items can be joined back together.
3. Export notes and resolutions, not only ticket headers; the narrative is where the value sits.
4. List custom fields and user-defined categories, with a one-line meaning for each.
5. Store the export with access controls; ticket notes can hold client network details and, too often, passwords.

A referral partner never runs or receives this export. SourceX works with the MSP directly, and nothing is delivered before an executed agreement, agreed redaction rules and the company's authorization.

When to raise it: before a PSA consolidation

The risky moment comes after an acquisition. Platforms that buy several MSPs often standardize on one PSA. When an add-on's Autotask instance is migrated, open work moves across, while closed history may be archived in summary form or lost when the subscription ends.

The M&A closing checklist includes a post-closing line for keeping systems intact until the new owner decides what to retain, and the guide on how to sell an MSP covers valuation and buyer questions in more depth.

How a partner spots an MSP using Autotask well

• 50+ full-time employees at peak (contractors excluded), at the MSP itself or at the combined platform company after a roll-up
• Closed-ticket history going back several years, with any older instances still readable
• Issue and sub-issue types applied consistently rather than left on a default
• Time entries with real summary notes, not blank or one-word entries
• Resolutions recorded on closed tickets
• Projects tracked with phases, tasks and budget against actual hours
• Change approvals and satisfaction surveys in regular use
• An admin who can run exports and explain the custom fields
• An owner, CEO or other authorized officer who would entertain an exclusive AI-training deal limited to an agreed term

The data inventory builder helps an MSP list Autotask alongside its RMM, documentation platform, email and chat, which is where the rest of the operational story sits.

Pitfalls specific to MSP records

The biggest question is whose information sits in the tickets. An MSP's notes describe its clients' networks, users and incidents. The MSP created the records, but its master services agreements and confidentiality terms decide what it may do with them. FTC staff have stated that a company's promises not to use customer data for undisclosed purposes, such as training models, are enforceable whether made in privacy policies, terms of service or marketing materials. Read the MSAs before assuming anything is licensable; the answer on whether an MSP can license ticket history that mentions client systems goes further.

Other pitfalls to flag early:

• Credentials, IP addresses and security incident details in notes must be removed under agreed redaction rules.
• Clients in healthcare or finance may have pasted regulated data into tickets; those records may need to be excluded.
• MSPs that deliver services under another provider's brand may not control the records at all.
• Acquired MSPs sometimes lose admin access to an old instance; secure access before the seller's team leaves.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

Next step

If you advise MSP owners or roll-up platforms, check the baseline on who qualifies, see how a license is documented in what a data license agreement contains, and register as a partner before the old instance is retired. IT services dealmakers can read how the program works for M&A advisors.