DataPacts

ConnectWise, Autotask and HaloPSA: Exporting and Licensing MSP Ticket Data for AI

Checked

At a glance

ConnectWise, Autotask and HaloPSA agreements leave the managed provider with its customer data on paper, but each vendor reserves its own uses, and ConnectWise and Kaseya both write AI training or aggregated use into documents read on November 18, 2026.

Independent reference. Every buyer is covered on the same terms, every figure carries its source and check date, and no buyer pays to be listed or placed higher.

Request an independent introduction

Tell us what data your company holds. We reply with the buyers that fit and what their terms leave out. Your details reach a buyer only after you agree to a named introduction.

IndependentYour details stay with us until you agreeNot selling is a valid outcome

ConnectWise's SaaS Addendum says the Client "exclusively owns" Client Data, and Autotask's developer help caps a query at 500 records.

A PSA ticket describes the provider's clients, so the client contract comes first, and no program on record names any of the three PSAs. A PSA is one source in AI training data licensing, and every vendor statement below is a dated reading of a document, not a statement of practice.

DataPacts Editorial Team: how we source, date and check every figure. The vendor documents were read on their own pages on November 18, 2026; program terms carry the date each was checked.

What a PSA Holds and What a License Could Cover

A professional services automation (PSA) system holds a managed provider's tickets and time entries, the client companies and contacts behind them, agreements and projects, and a license could cover any of these that the provider controls.

Ticket families, their value and credentials are covered on the page about IT service-desk tickets for AI training; this page stays on the three vendors. RMM tools are separate products.

Who Controls PSA Ticket Data in a License

Five vendor documents read on November 18, 2026 decide what a provider may do with PSA data: ConnectWise's Master Agreement and AI Agents Terms of Use, Kaseya's Master Agreement, Datto's PSA terms and HaloPSA's privacy policy. The table compares them by version, ownership, export and retention, and AI wording, as of 2026-11-18.

Document Version as read Ownership of customer data Export and retention AI and aggregate wording Source
ConnectWise Master Agreement and Addendums (SaaS Addendum s.5; Master Agreement s.10.5, s.10.6) "Revised July 1, 2026" Client "exclusively owns" Client Data, which is Confidential Information export on request within 30 days after termination, then deletion; reports in CSV or XML no AI wording in the text read; collects meta data and operations data connectwise.com/legal (PDF)
ConnectWise AI Agents Terms of Use (s.4, s.5) "Last Updated June 30, 2026" customer "retain[s] ownership" of data submitted to the AI Agents services not stated may train, validate, evaluate and improve AI and machine learning models; may generate aggregated, anonymized and de-identified information connectwise.com/legal (PDF)
Kaseya Master Agreement (s.5, s.8, s.18) "Updated as of November 17, 2026" customer or End User "retain all existing rights" in Content may delete Content or disable access after termination Aggregate Data may be used to "train, evaluate and improve artificial intelligence and machine learning models" kaseya.com/legal/kaseya-master-agreement/
Datto, PSA, Datto RMM and Kaseya Quote Manager Terms of Use (s.4) "Updated as of November 17, 2025" not stated; Content is defined by the Kaseya Master Agreement Autotask PSA retained 30 days after termination; Datto RMM zero days and not exportable none datto.com/legal
HaloPSA privacy policy (s.2.3, s.2.5, s.8) "Effective date: 1 January 2026" Halo is processor for hosted data, on "documented instructions" hosted log data after termination up to 4 weeks OpenAI subprocessor for optional AI; data sent "is not used to train its models" usehalo.com/privacy-policy

The Layers: the MSP, Its Clients and the Vendor

In a PSA three parties hold rights over one ticket: the end client whose request and staff appear in it, the managed provider that wrote it, and the vendor whose platform stores it.

ConnectWise (Master Agreement s.4.1) and Kaseya (Master Agreement s.8) make the customer answer for the legality of the data and for "the means by which" rights in it were acquired.

Whether a provider owns the tickets in its PSA turns on its client agreements, which no vendor document settles; those contracts and the buyers that name providers are covered under managed IT service providers licensing data to AI.

For EU clients, Regulation (EU) 2016/679 Article 28(3)(g) and (h), applicable from 2018-05-25, requires the processor contract to provide for deletion or return of personal data and for audits.

ConnectWise: Client Data, Reports and the 30-Day Window

ConnectWise's Master Agreement and Addendums, revised July 1, 2026, say in the SaaS Addendum (s.5.1) that the Client "exclusively owns all rights, title and interest in and to all Client Data which may include personally identifiable information", and treat Client Data as Confidential Information.

On a request made within thirty days after termination, ConnectWise makes Client Data available for export as provided in its documentation (s.5.4); after those 30 days it has "no obligation to maintain or provide any Client Data" and deletes it unless the law prohibits.

Section 10.5 is a separate category: ConnectWise "will collect, modify and analyze meta data and/or operations data", such as log files and transaction counts, for utilization, performance and maintenance. The Data Processing Addendum, listed as of 04/04/2023, was not read.

Autotask and Datto: the Kaseya Master Agreement and Product Terms

Autotask PSA sits under two Kaseya documents: the Master Agreement, updated as of November 17, 2026, that defines Content and keeps rights with the customer or End User, and Datto's PSA, Datto RMM and Kaseya Quote Manager Terms of Use, updated as of November 17, 2025, that set export and retention.

On termination Kaseya "may permanently delete all related Content or disable access to such Content" (Master Agreement s.5), subject to the DPA, the product terms and any retrieval period the law requires. Datto's terms (s.4) allow export "in a format supported by us" and state "no obligation to maintain or provide any Content" afterward.

They keep Autotask PSA content for the subscription and 30 days after it, and for Datto RMM read "Export or transfer of Datto RMM information is not possible." The two stamps are as shown on the pages, one year apart, unexplained there.

HaloPSA: Processor Role and the Terms Not Published

HaloPSA's vendor, Halo Service Solutions Limited, publishes a privacy policy effective January 1, 2026 in which it acts as processor for hosted customer data "only on your documented instructions", but no terms document was located.

Hosted log data is kept after contract termination for up to 4 weeks unless otherwise agreed. On November 18, 2026 the home page link labeled "Terms & Conditions" pointed nowhere, so what the contract says on ownership, export or AI is not stated here.

What the Three Say About AI and Aggregate Data

Two of the three vendors write AI training into a document read on November 18, 2026, and the third states a limit on its AI subprocessor. Each reading below is of the document, not of what the vendor does.

  • ConnectWise: the AI Agents Terms (s.4) let ConnectWise use data submitted to those services to train, validate, evaluate and improve AI and machine learning models, and s.5 gives it the aggregated and de-identified data. The Master Agreement text read has no AI wording.
  • Kaseya: the Master Agreement (s.8) lets Kaseya "use and share such Aggregate Data freely", including to train AI and machine learning models, provided it complies with applicable law; Administrative Data does not include Content itself (s.18).
  • HaloPSA: optional AI functions route data to OpenAI as a subprocessor, and Halo states that data sent "is not used to train its models"; the functions can be disabled. The home page calls the platform "the AI foundation that learns from your data" without saying whether customer data trains shared models.

Practice is not stated in the documents. Vendor training across platforms is covered under user data and platform terms.

How Ticket and Time Data Leaves the PSA

Ticket and time data leave a PSA through reports and exports the product offers and through its API, and the three vendors document these differently. The table compares the routes, limits and gaps, as of 2026-11-18.

PSA Route documented Limits documented Not read Source
ConnectWise PSA reports and information in "standard readable format (e.g., CSV, XML)" until license end; REST API exists, documents need sign-in custom reports requested at the end of the term charged by scope API pagination, rate limits, bulk export connectwise.com/legal (PDF)
Autotask PSA REST API 500 records per entity per query; 10,000 external requests per hour per database; added latency from 50 percent of the limit time-entry entity detail autotask.net developer help
HaloPSA API documentation and SQL schema guide linked from the home page none read everything behind the API reference login usehalo.com

ConnectWise: Reports, and an API Whose Documents Sit Behind Sign-In

ConnectWise's agreement says a Client may access reports and information through the offering until the end of the license term, in standard readable formats such as CSV or XML (Master Agreement s.10.6), and charges end-of-term requests "based on the scope of the request".

The developer and documentation sites returned sign-in redirects on November 18, 2026, so API limits are not recorded here.

Autotask: 500 Records per Query and 10,000 Requests per Hour

Autotask's developer help states that it "returns no more than 500 records per entity at once, sorted by internal ID" and sets a limit of 10,000 external requests per hour per database, shared across integrations.

A client loops on the ID above the highest one received, and latency of 0.5 seconds is added from 50 percent of the hourly limit and 1 second from 75 percent. Programs that read in place are compared under control under buyer connectors vs native exports.

HaloPSA: API and SQL Schema Pages

HaloPSA's home page links API documentation and a SQL schema guide, and the API reference sat behind a login redirect on November 18, 2026. No export capability, pagination or limit is stated here beyond the links.

What a PSA Export Holds Beyond the Ticket Text

A PSA export carries the provider's client companies and contacts, agreements and time entries beside the ticket, so the client's identity is in the structure as well as the text.

  • Client company and contact names, with email addresses and phone numbers.
  • Technician names and time entries.
  • Free-text hostnames, IP addresses and credentials pasted into notes.
  • Attachments such as screenshots and configuration files.

Removal of identifiers and screening of credentials are set out under PII removal and de-identification.

What Programs Name When They Ask for MSP Ticket Data

No program on record names ConnectWise, Autotask or HaloPSA; five name ticket or IT-service records in general, each checked on the date shown. The table gives each program's own statements, as of 2026-11-18.

Program Role What it names Terms that matter for PSA data Checked Source
Mercor, Cybersecurity listing program with listings alert-to-resolution records the company owns "customer data only with customer agreement" 2026-11-09 api.data.mercor.com
micro1 program "customer support tickets and knowledge bases" per the program page 2026-11-09 micro1.ai
SuperAnnotate program "tickets, approvals, escalations, incident reviews, QA trails" "licensing rights for a set period, not selling the data" 2026-11-09 superannotate.com
Turing Project Lazarus program (revenue share) tickets (Jira, Linear), support (Zendesk, Intercom) 6-month exclusive license to Turing; may license the same record to more than one lab 2026-11-17 lazarus.turing.com
Centific, Enterprise Data program "service/IT records" in-scope systems connected read-only 2026-11-17 centific.com

A listed category is not acceptance of a PSA export. Programs are compared in AI data partnership payouts and program terms compared.

Licensing PSA Ticket History: Benefits, Risks, Downsides and Alternatives

Licensing PSA ticket history is a choice with benefits and risks, and not licensing is an equally valid result.

Benefits

  • History that a vendor deletes after termination (30 days at ConnectWise and Autotask) can be put to use before then.
  • ConnectWise leaves ownership, and Kaseya all existing rights, with the customer or End User in the text read.

Risks

  • The tickets describe the provider's clients, and the provider answers for the legality of the data under ConnectWise s.4.1 and Kaseya s.8.
  • Vendor rights to aggregated data and AI training may sit beside a buyer's no-prior-grant or exclusivity terms, a question for the buyer and counsel.
  • Exclusivity, such as Turing's first 6 months, blocks other buyers.

Downsides

  • Client names, hostnames and credentials run through free text, so preparation is heavy.
  • Export limits and gated API documents slow a full history run.

Alternatives

The PSAs Among the Service-Desk Systems and the Seller Steps

ConnectWise, Autotask and HaloPSA are the managed-provider end of the service-desk systems, next to ServiceNow, Zendesk, Freshdesk and Jira. The parent page compares export rights and mechanics by source system.

Siblings: the ServiceNow data export, the Zendesk ticket export, the Freshdesk ticket export and the Jira issue history; customer support tickets and chats for AI training covers support. The steps for a provider:

  1. Build a data inventory of tickets, time entries and attachments.
  2. Run a rights audit over each client's agreement.
  3. Check customer consent and confidentiality clauses; the clients are the consenting parties.
  4. Write the data manifest, including the export route.
  5. Plan delivering licensed data to an AI buyer.
  6. Weigh should you sell or license your data at all.

PSA Data After a Subscription Ends

ConnectWise SaaS Client Data is available for export on a request made within 30 days after termination, Autotask PSA content is retained 30 days after termination and HaloPSA hosted log data up to 4 weeks.

These are vendor terms, not law. Deadlines for a closing provider are set out in deadlines for exporting company data before shutting down. This page is information, not legal advice.

  • ConnectWise: export request within 30 days, then deletion.
  • Autotask PSA: 30 days; Datto RMM: zero days.

Buyer Programs Cited on This Page

This page cites five programs.

The wider list is who buys AI training data.

Frequently Asked Questions

How do I export tickets from ConnectWise PSA?

The agreement provides reports and information in a standard readable format such as CSV or XML until the license ends. The API documents need sign-in, so they are not recorded here.

How many records can the Autotask API return?

Autotask returns no more than 500 records per entity per query and allows 10,000 external requests per hour per database.

Do ConnectWise, Kaseya or HaloPSA train AI on customer data?

The ConnectWise AI Agents Terms and Kaseya's Aggregate Data clause allow training for the data they cover, HaloPSA states that its OpenAI subprocessor does not train, and practice is not stated.

Can an MSP license its PSA tickets to AI companies?

Not on vendor terms alone, because the client agreements decide.

The limits are set out under MSP data licensing to AI.