MSPs and IT service providers
ConnectWise, Autotask and HaloPSA data export: who owns MSP data and what the AI terms say
On this page
The short answer
ConnectWise, Kaseya (Autotask, Datto RMM, IT Glue), HaloPSA, NinjaOne, N-able and Hudu all say, in different words, that the MSP keeps its rights in its data as against the vendor. The catches are elsewhere. The Kaseya API License bars AI training on and sublicensing of API-pulled Content without the Content owners' permission. HaloPSA §4(a)(iv) needs Halo's written permission before materials resulting from the Services go to a third party. Datto RMM data is not exportable.
Post-termination windows run from 45 days (NinjaOne) down to zero (Datto RMM and Hudu). The safe route for ConnectWise Manage, Autotask and HaloPSA ticket exports is each product's own export, while you are still subscribed.
What your PSA, RMM and documentation platform store
An MSP's records sit in three kinds of system, and each holds a different mix of your own work and your clients' information.
- PSA (ConnectWise PSA, Autotask, HaloPSA, Syncro). Tickets with time entries, boards and queues, SLAs, agreements and billing, projects, quotes and CSAT. The metadata is largely yours; the ticket text describes clients' users and systems.
- RMM (ConnectWise Automate, Datto RMM, NinjaOne, N-able). Alerts, monitors, patch status, automated remediation results and your script library. Telemetry is about client devices; generic scripts are your code.
- Documentation (IT Glue, Hudu). Your internal runbooks and KB articles sit next to client environment documentation and password vaults. The first usually qualifies for a license; the second stays out.
The vendor terms below decide how you can get each record out. What your client MSAs allow decides whether a record can be licensed once it is out; our guide to MSP client data, MSAs and what stays out covers that half.
Who owns PSA data under ConnectWise, Kaseya and HaloPSA terms
| System | Ownership clause | AI or third-party clause | After termination |
|---|---|---|---|
| ConnectWise PSA (Manage) | “Client exclusively owns all rights, title and interest in and to all Client Data” (5.1) | None found in the 2024 revision we read | Retained no more than 30 days (5.5) |
| Autotask PSA (Kaseya) | “you or the End User (as applicable) retain all existing rights in and to Content” (MA 8(b)) | API License 5: no AI training or sublicensing of API Content unless the owners of Content permit it | 30 days |
| Datto RMM (Kaseya) | Same Master Agreement clause | Same API License clause | Zero days; Content is not exportable |
| IT Glue (Kaseya) | Same Master Agreement clause | Same API License clause | No export after termination; may be destroyed after 30 days (2(c)) |
| HaloPSA | “You reserve all rights in Your Data” (12(b)) | 4(a)(iv): no materials resulting from the Services to a third party without Halo’s written permission | No export or retention clause |
| NinjaOne | “You own all right, title, and interest in and to Your Data” (5.1) | 3.1: no AI training or automated extraction for a competitive purpose | 45 days (8.3.3.1) |
| N-able | N-able takes a license to process and improve with Your Data (7.1) | “Your Data will not be used to train shared or third-party AI models without Your agreement” (7.1) | 30 business days to retrieve (5.4) |
| Syncro | No customer-ownership statement found | Syncro may train on anonymized, aggregated User Content; go-forward opt-out | Up to 90 days, copy on request |
| Hudu | “Licensee is and will remain the sole and exclusive owner” (8(a)) | No bots or automated access (3(e)) | Inaccessible immediately (13(b)) |
Read the table as two separate questions. The ownership column answers “can my vendor stop me from using my own records?” Mostly, no. It does not answer “are the records about my clients mine to license?” ConnectWise's clause, for example, settles ownership between ConnectWise and the MSP, and Kaseya's Master Agreement expressly allows for the End User holding the rights (source: ConnectWise Master Agreement (revised Sept 30, 2024), Kaseya Master Agreement (updated Oct 7, 2025)). That second question runs through your client contracts.
The Kaseya API License and AI training on Autotask and IT Glue data
The single clause that most shapes MSP data licensing on Kaseya products is in the API License, last updated March 1, 2026. Section 5 says that, as between you and Kaseya, Content accessed through the API is Kaseya's Confidential Information and “owned by Kaseya.” It then lists what you will not do “Unless expressly permitted by the owners of Content, or by Applicable Law,” including “scrape, build databases, or otherwise create permanent copies of Content” and “perform AI training or sublicense Content to any third party” (source: Kaseya API License (updated Mar 1, 2026)).
The Master Agreement, updated October 7, 2025, points the other way on ownership: “you or the End User (as applicable) retain all existing rights in and to Content” (§8(b)). It also lets Kaseya process Content in aggregated and anonymous form (§8(f)) and has no general export right; after termination Kaseya may permanently delete Content (§5(f)) (source: Kaseya Master Agreement (updated Oct 7, 2025)).
Our reading: the API License governs programmatic pulls, so any licensing extract from Autotask, Datto or IT Glue should come from the product's own export rather than an API connector or a third-party sync tool. Even then, the “owners of Content” for client-facing records are often your clients, which is why MSP deals center on MSP-authored material and de-identified metadata.
ConnectWise Manage: export tickets while you are subscribed
ConnectWise PSA (still called Manage by many MSPs) has the cleanest ownership language of the PSAs we read: the client “exclusively owns all rights, title and interest in and to all Client Data,” and Client Data is treated as Confidential Information (§5.1). After expiration or termination, ConnectWise may retain Client Data for no more than 30 days, and other than billing audit records it is deleted from all environments within 60 days (§5.5) (source: ConnectWise Master Agreement (revised Sept 30, 2024)).
We read the revision dated September 30, 2024; check the version that governs your account. For a data license, the useful ConnectWise Manage ticket export is the metadata layer: board, type and subtype, priority, status history, SLA fields, time entries, reopen and CSAT. Exporting ticket notes is a separate decision that depends on your client MSAs. Use ConnectWise's own reporting and export features, and keep the raw export inside your environment until the scope is agreed.
Autotask: export tickets to CSV, and the 30-day window
Kaseya's product terms for Autotask say that “While your Subscription is active, you export or download a copy of Content in a format supported by us,” conditional on payment “including any applicable standard fee for the export.” Autotask retains data throughout the subscription and for 30 days after termination; after that, Kaseya has no obligation to maintain or provide any Content (source: Kaseya terms for Autotask PSA and Datto RMM (updated Nov 17, 2025)).
In practice, owners asking how to export all tickets from Autotask to CSV are usually planning a migration or an archive. The same export serves a data license, with two adjustments. First, stay inside the product export rather than an API integration, for the API License reasons above. Second, export ticket metadata and ticket text as separate files, so the free text can be held back or scrubbed under its own rules.
HaloPSA: export tickets, and the third-party clause
Halo's terms, updated March 18, 2026, say “You reserve all rights in Your Data and Halo does not claim ownership of Your Data” (§12(b)). The restriction to read closely is §4(a)(iv): you may not “make the Services or materials resulting from the Services available in any manner to any third party” for use in its business operations, unless such access is expressly permitted in writing by Halo. The terms we read contain no clause on data export or on retention after termination, and they do not mention AI (source: Halo Terms and Conditions (updated Mar 18, 2026)).
Whether a de-identified ticket dataset counts as “materials resulting from the Services” is our question, not a statement from Halo, but the plain words are broad. So a HaloPSA export of tickets for a data license is a needs-review item: ask Halo for written permission for the specific materials, or limit the license to records that do not come from Halo, such as runbooks and scripts kept elsewhere. If you are moving from ConnectWise to HaloPSA, consider exporting the ConnectWise history before the move, while ConnectWise's own terms still apply to it.
RMM data: Datto RMM, NinjaOne, N-able and Syncro
- Datto RMM. “Content is not exportable,” and “Export or transfer of Datto RMM information is not possible.” Datto RMM keeps the most recent 90 days during a subscription and zero days after termination (source: Kaseya terms for Autotask PSA and Datto RMM (updated Nov 17, 2025)). Keep scripts you wrote in a repository you control.
- NinjaOne. You own Your Data (5.1). Section 3.1 bars using Platform Materials to train AI with a “Competitive Purpose” and bars systematic or automated extraction for a competitive purpose, while allowing “exporting or transferring Your Data on a reasonable and non-recurring basis” for backup, compliance, continuity or migration. You have 45 days after termination to retrieve your data (8.3.3.1) (source: NinjaOne EULA (updated June 8, 2026)). Whether a buyer building IT management tools raises the competitive-purpose clause is our question to flag, not NinjaOne's statement.
- N-able. N-able takes a license to process Your Data, and says “Your Data will not be used to train shared or third-party AI models without Your agreement” (7.1). You must retrieve Your Data within 30 business days of termination (5.4) (source: N-able Software Services Agreement (updated Jul 31, 2026)).
- Syncro. Syncro “may use User Content and other Usage Information in an anonymous and aggregated form” to train its AI tools, with an opt-out that applies only on a go-forward basis. Syncro retains User Content, and you may request a copy, for up to 90 days after termination (source: Syncro Service Terms (effective Oct 1, 2025)). If you plan to license Syncro records, send the opt-out first.
RMM telemetry is a needs-review item in any case, because alerts and device data describe client machines. The RMM asset that usually qualifies is the script and policy library your team wrote.
IT Glue and Hudu export: passwords, KB articles and timing
Documentation platforms hold the most valuable MSP-authored records and the most sensitive client records, side by side.
- IT Glue. During a subscription “you may export a current snapshot of the information held in your IT Glue instance.” After termination “it is no longer possible to export Content or reports,” and Kaseya may destroy the data 30 days after the subscription ends (§2(c)). Network Glue exports are not possible (source: IT Glue Product Terms of Use (updated Mar 21, 2025)). Kaseya describes IT Glue exports with “the ability to include or exclude passwords from exports” (source: Kaseya, IT Glue customizable exports). For a data license, exclude passwords and export only your internal runbooks and KB, not client organizations.
- Hudu. “Licensee is and will remain the sole and exclusive owner of all right, title, and interest in and to all Licensee Data” (8(a)). You may not access the software through bots or other automated methods (3(e)). You are responsible for extracting all data before termination, and data is “inaccessible from the Software immediately upon termination or expiration” (13(b)) (source: Hudu Terms (effective Mar 19, 2026)). A Hudu KB export, including the central KB, has to happen before the end date.
Passwords never leave
Whatever the platform, password vaults, API keys, tenant IDs and client configurations stay out of any licensing export. Buyers typically refuse them, and one broker that names MSPs excludes “client environment details and credentials” outright (source: program terms, Regulr buyer directory).
Export windows after you cancel
| System | Export while subscribed | After termination |
|---|---|---|
| NinjaOne | Reasonable, non-recurring exports | 45 days to retrieve |
| Syncro | Not addressed in the clauses we read | Up to 90 days; copy on request |
| N-able | Your responsibility to back up | 30 business days to retrieve |
| ConnectWise PSA | Available during the term | No more than 30 days |
| Autotask PSA | Yes, subject to any standard export fee | 30 days |
| IT Glue | Current snapshot | No export; may be destroyed after 30 days |
| HaloPSA | No export clause | No retention clause |
| Hudu | Your responsibility before the end date | Inaccessible immediately |
| Datto RMM | Not exportable | Zero days |
These windows matter most to MSPs that are closing, selling or switching tools. If your MSP is being acquired, an acquirer that moves you onto its own stack may let your old subscriptions lapse, and with them the history. Our guide to selling an MSP and your records covers that timing.
PSA migrations: ConnectWise to HaloPSA and keeping the history
A PSA migration is the moment an MSP is most likely to lose its ticket history, and the moment it already has an export in hand. Some migration projects bring over only open tickets, companies and agreements, so ask whether closed history comes across intact. If you are moving from ConnectWise to HaloPSA, or from Autotask to anything else, take a full export of closed tickets with time entries and status history before the old subscription ends, and store it where you control it.
That archive is the core of an MSP's value to a buyer: years of triage decisions on one consistent schema. It also means the export happened under the old vendor's terms, which, for ConnectWise, are the ownership terms quoted above (source: ConnectWise Master Agreement (revised Sept 30, 2024)).
Export checklist for an MSP data license
- List every PSA, RMM and documentation platform you have used, with the years each holds.
- Find the terms version that governs each account, and note any post-termination window.
- For Kaseya products, plan in-product exports only; do not use the API or a third-party sync for this.
- For HaloPSA, decide whether to ask Halo for written permission or leave Halo-sourced records out.
- For Syncro, send the AI opt-out before anything else.
- Export ticket metadata and ticket text as separate files.
- Export runbooks and KB articles from IT Glue or Hudu with passwords excluded and client organizations left out.
- Move generic scripts out of the RMM into a repository you control, with secrets removed.
- Keep every export inside your environment until you approve the scope in writing.
Once you know what you can export, the next question is what buyers will take. The MSP and IT services page shows which buyers want which records, and our MSP data licensing guide covers the full picture. For comparison, the same export questions come up for law firms in our practice-management data export guide.
How Regulr is paid, and how we write these pages
Regulr is a sell-side advisor. When a business we introduce signs a license, we may be paid a fee by the buyer or through a program's referral terms. We list every program we can verify whether or not it pays us, order is never set by fees, and every figure is the company's own advertised term with a link to where it says so. Regulr has not closed a data deal yet, so nothing here describes our results.
Frequently asked questions
Who owns the data in ConnectWise Manage?
As between ConnectWise and the MSP, the MSP does. The ConnectWise Master Agreement we read (revised September 30, 2024) says the client exclusively owns all rights, title and interest in and to all Client Data. That clause does not decide what your own clients' MSAs say about their information inside your tickets, which is a separate question.
Can I export all tickets from Autotask?
Kaseya's product terms say that while your subscription is active you may export or download a copy of Content in a format Kaseya supports, subject to any applicable standard export fee. Autotask keeps data for 30 days after termination, after which Kaseya has no obligation to keep it. Run the export with Autotask's own tools; the Kaseya API License restricts AI training on, and sublicensing of, Content pulled through the API.
Does the Kaseya API License stop me from licensing my Autotask or IT Glue data?
It restricts one route. The API License says that, unless expressly permitted by the owners of Content or by law, you will not perform AI training on or sublicense Content to any third party, and you will not scrape or build databases of it. It governs Content accessed through the API. The Master Agreement separately says you or the End User retain rights in Content, as applicable, so the usual route is an in-product export of records you own.
Can I export tickets from HaloPSA for a data license?
Halo's terms say you reserve all rights in Your Data, but section 4(a)(iv) bars making the Services or materials resulting from the Services available to any third party unless Halo expressly permits it in writing. The terms we read have no export or post-termination retention clause. Our reading is that a licensing extract could be caught, so ask Halo for written permission before any Halo-sourced records go to a buyer.
Can IT Glue export passwords?
Yes. Kaseya describes IT Glue exports with the option to include or exclude passwords. For any data license, choose exclude, and leave client environment documentation out as well. IT Glue's product terms say exports are a current snapshot, are not possible after termination, and that Kaseya may destroy the data 30 days after the subscription ends.
What happens to my Hudu data when I cancel?
Hudu's terms say the licensee is responsible for extracting all data before termination or expiration, and that data will be inaccessible immediately upon termination or expiration. There is no grace period, so export your KB and any other records you want before the end date.
Can I export Datto RMM history?
No. Kaseya's product terms say Datto RMM Content is not exportable, that it keeps the most recent 90 days during a subscription, and that retention after termination is zero days. RMM alert history is a needs-review item anyway, because it describes client devices.
Sources
Every vendor document was read on its own page on October 18, 2026. The ConnectWise agreement read is the revision dated September 30, 2024; later versions were not reviewed. Program terms were checked on October 15, 2026; our buyer directory lists the programs and links to their published terms.
- ConnectWise Master Agreement (revised Sept 30, 2024)
- Kaseya Master Agreement (updated Oct 7, 2025)
- Kaseya API License (updated Mar 1, 2026)
- Kaseya terms for Autotask PSA and Datto RMM (updated Nov 17, 2025)
- IT Glue Product Terms of Use (updated Mar 21, 2025)
- Kaseya, IT Glue customizable exports
- Halo Terms and Conditions (updated Mar 18, 2026)
- NinjaOne EULA (updated June 8, 2026)
- N-able Software Services Agreement (updated Jul 31, 2026)
- Syncro Service Terms (effective Oct 1, 2025)
- Hudu Terms (effective Mar 19, 2026)
- program terms, Regulr buyer directory
Brian Boesen · Founder, Regulr AI
Brian runs Regulr AI, which works for established businesses that want to license de-identified records to AI companies. He checks each program's published terms against its own pages and updates these guides when they change. Last updated October 18, 2026.
This page is general information, not legal advice, and Regulr is not a law firm. Rules vary by state, by profession and by contract, and they apply to your facts, not to a category. You approve exactly what is in scope before anything is shared.
Keep reading