Export Rights and Mechanics by Source System: Slack, Microsoft 365, Jira, GitHub and More

A company can license data held in Slack, Teams, Jira, GitHub or any other workplace system only as far as the system lets it export the records and the vendor's terms let it pass them on. This hub maps 37 source systems and system families plus one connectors guide, with each vendor's export route, the term that limits onward licensing and how many company data programs name the system, checked 2026-11-09.

Programs are counted, never ranked, and no fee appears in the system table. The page covers the source-system side of AI training data licensing: how records leave a system and under which term, not what each data type is worth.

What Decides Whether Company Data Can Leave a Source System for AI Licensing?

Three layers decide it: the export tool and plan, the vendor's API and developer terms, and the customer terms that govern the data itself. Ownership of the records and the claims of the people in them are a separate test, set out in the rights audit before licensing.

1. Export tool and plan: the export, backup or eDiscovery tool and the plan tier that unlocks it. Zendesk offers export tools only on Suite Growth or Support Professional and above, and the account owner has to ask Zendesk Support to enable them.
2. API and developer terms: the rules for apps that pull data. Slack's API Terms (effective 2025-10-10) bar apps offered outside the organization from training a large language model on API Data or bulk exporting it without an additional agreement, and Atlassian's Developer Terms s.9.2 (effective 2025-12-01) bar apps from selling End User Data.
3. Customer terms: the subscription contract over the data. Accounting platforms carry the clearest clauses, while no relicensing clause in Slack's or Microsoft's customer terms is on record as of 2026-11-10.

The route decides which layer applies: Slack's API Terms govern apps, not the owner's own export. A vendor training its own models on customer data is a separate question (FAQ).

Every Source System at a Glance

The table lists 37 source systems and system families plus one guide to buyer connectors, grouped in seven families, with each vendor's export route and the term that limits licensing. It is as of 2026-11-10, with vendor and program pages checked 2026-11-09.

• "Not on record": no vendor page verified by the check date, never "no limit".
• "Programs naming it": program pages naming the system, buyers and intermediaries alike, never an endorsement.
• Families follow the sections below.

Export Routes and Vendor Terms, Family by Family

Each family below names the export route, the hard limits and the binding vendor term, all as read on 2026-11-09.

Chat and Meetings: Slack, Teams, Zoom, Gong, Discord and WhatsApp

Chat exports depend most on the plan: Slack exports private channels and direct messages only on Business+ by application and on Enterprise through Support, and Teams content leaves through the Export API or eDiscovery. Since 2024-08-26, free Slack workspaces lose history older than one year. Microsoft's Export API needs an active Teams license for each exported user, has not been metered since 2025-08-25 and retrieves user-deleted messages for 21 days.

Discord's Terms s.9 (effective 2025-09-29) bar selling, licensing or commercializing content or data obtained from the services. WhatsApp exports one chat at a time, and the WhatsApp Business Platform terms (last modified 2026-09-23) bar selling Platform Data, including anonymous, aggregate and derived forms (s.4.1(b)), and AI training on it except fine-tuning for the business's exclusive use (s.4.7).

What chat histories are worth and who asks for them is covered under selling chat messages.

Email, Files and Design: Microsoft 365, Google Workspace, Dropbox, Notion and Figma

Office suites export whole tenants through admin tools: Google Workspace's Data Export for super admins and Microsoft Purview eDiscovery for E3 or E5 licensed users. Google requires a super admin account at least 30 days old, delivers in 48 hours to 14 days and deletes the bucket 60 days after the export starts. Purview packages expire after 14 days.

Google's Workspace API user data policy bars selling API user data and training AI models on it. Notion exports HTML or Markdown and CSV through a link valid for 7 days. Figma's training default concerns the vendor's own models, not a license route.

Mailbox archives as a licensable asset are covered under licensing a company email archive.

Work Trackers and Wikis: Jira, Confluence, Linear, Asana and Monday.com

Jira Cloud exports through site backups that exclude automation flows, third-party app data and Assets, and Linear's CSV export leaves out comments and attachments. A Jira backup with attachments can run every 48 hours, and since 2026-01-22 a restore accepts backups no older than 30 days. Linear's view export stops at 250 issues for members and 2,000 for admins; its Markdown copy keeps comments.

Atlassian's Developer Terms s.9.2 apply to Jira and Confluence apps alike. Atlassian's data contribution feeds the vendor's own models and is not a license route. For Asana and Monday.com, no export limit or vendor term is on record.

Ticket histories as a data type have their own page on issue trackers and project histories.

Code Hosts: GitHub, GitLab and Bitbucket

GitHub's Terms leave ownership with the customer (section D.3), but code-host export archives expire fast: seven days for a GitHub organization migration archive and 24 hours for a GitLab export file. GitLab allows six exports per minute by default and caps GitLab.com imports at 5 GB. Bitbucket Cloud offers no metadata backup; feature request BCLOUD-19832, created 2020-01-24, still shows "Gathering Interest".

GitHub's Terms (effective 2026-04-27) grant GitHub a license in section D.4 that covers training its own AI features and models, which GitHub states is not a sale. Its Acceptable Use Policies bar selling personal information gathered through the API, for example to recruiters or job boards.

Buyers, per-token rates and code rights sit under selling or licensing source code.

CRM, Support and Service Desks: Salesforce, HubSpot, Zendesk, Intercom, Freshdesk and ServiceNow

CRM and support exports are capped by the vendor: HubSpot allows 300 exports per rolling 24 hours and leaves engagements out, and Zendesk's XML export stops at 500 MB. HubSpot's export links stay valid for 30 days. Zendesk's XML cap equals about 200,000 tickets, and its JSON export drops the comments of any ticket larger than 1 MB.

Intercom's dataset CSV carries no conversation content, its Export API returns 90 days per request, and a Saved View CSV has existed since 2026-08-28. ServiceNow's default export limit is 10,000 records in the Zurich release. No vendor term on resale or AI training is on record for this family, and Salesforce and Freshdesk have no verified export record yet.

Customer relationship histories as a data type are covered under selling CRM records.

Finance, ERP, HR and Warehouses: QuickBooks, Xero, NetSuite, SAP, Workday and Snowflake

Accounting platforms carry resale and AI-training terms of their own: Xero clause 56 bars reselling data accessed through the service, and QuickBooks Online bars AI training on information derived from its platform without authorization. Xero's terms of 2026-10-26 apply to current customers from 2026-12-28, and clause 62 ends data access at termination with no read-only period stated. Intuit's terms add that Intuit owns de-identified and aggregated data, and how far the training clause reaches a customer's own content is not clear from the text.

For NetSuite, SAP, HR and payroll systems and the data warehouses, no export limit or vendor term is on record. HR systems hold employee records, which bring employment and privacy rules on top of any vendor term.

Those rules are set out under employee data and AI training rules.

Industry Systems: Procore, ServiceTitan, ConnectWise, Clio, AppFolio and Deltek

No vendor term or export limit for the six industry systems is on record yet; what is on record is that buyers name them, as Mercor's construction and law firm listings name Procore and Clio. Mercor's construction listing also names Autodesk Construction Cloud (Mercor's statement, checked 2026-11-09), and Handshake AI names ServiceTitan on its own page.

No program page names ConnectWise, Autotask, HaloPSA, AppFolio, Buildium or Rent Manager.

Sector holdings and their limits are compared under data licensing by industry.

Which Extraction Route the Vendor Terms Allow

Data leaves a system by one of three routes, and each answers to a different term: the owner's native export, an API pull by an app, or a read-only connection run by a buyer or intermediary. A buyer's own app counts as an app, so vendor API terms bind it even when the owner approves the connection.

The table compares the three routes, as of 2026-11-10, with terms and program pages checked 2026-11-09.

Program pages describe the third route in their own words, among them, in alphabetical order: Centific states read-only connections with exclusions enforced in extraction code, Magma a read-only encrypted connection limited to the approved scope, and Mercor names "100+ supported tools". Pangea.ai connects code hosts read-only, Scale AI anonymizes inside the company's environment, Troveo states "No OAuth access or install required" and Turing collects samples through a private folder, all checked 2026-11-09. Each program's steps are compared under company data partnership programs.

What Court Records and Program Pages Show About Systems in a Data Sale

The Spirit Airlines asset schedule, filed in the bankruptcy court, counts company data by system and lists 500,000,000 Teams items, 20,577,677 SharePoint and 17,082,644 OneDrive items and 667,563 IT tickets among the data offered. The schedule, filed with the auction results in Bankr. S.D.N.Y. 25-11897 (SHL) on 2026-08-14 (Dkt. 1463), names the line "Teams Count" and includes 516 code repositories, 43,170 pull requests and 372,585 commits; 97,500,000 passenger profiles are not included. Google LLC holds the successful bid of USD 10,000,000 and Mercor.io Corporation the alternate bid of USD 7,500,000; the sale is not approved as of 2026-11-09, with a hearing set for 2026-11-17 (Dkt. 1779).

On program pages, Slack is named 16 times, Teams and Google Workspace 11 times each. SimpleClosure, a shutdown service, states that 95 % of the workspaces offered through its AssetHub include Slack and 82 % include GitHub (article of 2026-09-03, checked 2026-11-09).

How trustees run such sales is covered under data assets in insolvency.

Exporting to License: Benefits, Risks, Downsides and Alternatives, Including Not Licensing

Exporting records to license them turns systems a company already pays for into a possible income source, but an export cannot be recalled once a buyer has trained on it.

Benefits

• Existing records: chat, ticket and code histories already sit in systems the company runs.
• Costs carried by some programs: Mercor states it covers extraction, anonymization and transfer, and Turing states it covers de-identification, cleanup and packaging, both checked 2026-11-09.
• Owner control: a native export sets scope, date range and redaction before any copy leaves.

Risks

• Breach of platform terms, such as WhatsApp Business Platform s.4.1(b) or Discord s.9.
• People in the records: staff appear in chat and email exports, which raises employee notice and consent duties.
• No recall: micro1's Data License Master Terms (2026-11-08) grant an irrevocable, perpetual license, and Labelbox Prism states that trained models cannot be unlearned.

Downsides

• Hard limits reshape the dataset, such as missing comments in Linear and Zendesk exports.
• Admin effort: plan upgrades, Support requests and expiring links.

Alternatives

• Not licensing at all: the records stay under the company's own retention policy.
• A narrower license: one system, one date range, redacted.
• A scoped read-only connection under a program's agreement.
• Deletion at the end of the retention period.

The wider decision is weighed on the page "should you sell or license your data".

How the System Table Is Built: Vendor Pages, Check Dates and No Fees

Every cell comes from the vendor's own help center, API terms or customer terms, read on the date in the table, and every program count from the program's own page. Counts exclude a vendor's training of its own models, and seller guides and competitor pages are never a source.

DataPacts charges a company nothing for an enquiry, takes no cut of any sale and has joined no referral program, as set out under how we source, date and check every figure.

Where Export Meets Rights, Data Types, Readiness and the Seller Guide

The system decides how records leave; the rights audit decides whether they may be licensed, the data type decides who wants them, and the seller guide decides the order of steps.

• Data types AI companies buy and who asks for them.
• The seller guide to sell or license company data to AI companies.
• Data sale readiness, including export access.
• Data from a shut-down or defunct company.
• AI training data law by jurisdiction.
• How DataPacts is funded.

Where export sits in the sale:

1. Map the records: data inventory for an AI data sale.
2. Clean the export: PII removal and de-identification.
3. Hand it over: delivering licensed data to an AI buyer.

Frequently Asked Questions

What is data export?

Data export is copying records out of a system into a portable format, such as JSON, CSV, PST or a backup archive. In the EU, Chapter VI of the Data Act (Regulation (EU) 2023/2854, Arts. 23 to 31) gives cloud and SaaS customers a switching route, applicable since 2025-09-12. It is not a right to export for sale; see the EU Data Act.

Does exporting data give a company the right to license it?

No: an export gives the company a copy, not a right to license it. The plan, the vendor's API terms and the customer terms each have to allow the onward use, and customers, employees and contributors in the records keep their own claims. Records that fail those tests are described under what company data cannot be licensed.

Can a buyer connect to company systems directly?

Some programs connect directly, usually read-only and inside an agreed scope, as the routes table above shows. Such a connection is an app under the vendor's API terms, so Slack's bar on LLM training and bulk export by outside apps applies unless an additional agreement exists.

What happens to system data when a company shuts down?

Vendors delete or lock system data on their own schedules once a subscription ends. Zoom deletes recordings 30 days after a downgrade to the free plan, Gong accepts export requests for 30 days after termination (s.9.4), GitHub deletes organization migration archives after seven days and Xero ends data access at termination. Deadlines by vendor are collected under exporting company data before shutting down.

Does a system vendor train AI on company data?

Some vendors train their own models on customer data, which is separate from a company licensing its data to a third party. Figma trains on Starter and Professional files by default since 2024-08-15 and Atlassian's data contribution runs since 2026-08-17, while Slack requires opt-in, Google the customer's prior permission, and Zoom's ToS s.10.2 excludes communications-like content. More under user data and platform terms.