How to sell Salesforce data to AI labs.

Which objects in your org labs pay for, how your admin exports them, what Salesforce’s contract says about ownership, and where customer and contact data stop. Checked 10 November 2026. If your company has 30 or more office employees, Allied arranges a direct license with an AI lab and gets you a written offer.

I

The short answer

Yes, a company can license a copy of its own Salesforce history to an AI lab. Salesforce does not own what your team typed into it. Its Main Services Agreement says Salesforce acquires no right, title or interest in or to any Customer Data under the agreement, apart from the limited license it needs to run the service.1

The value sits in the activity record, not the contact list. Labs building sales and service agents want the sequence: the call that was logged, the email that followed, the stage that moved, the case that was escalated and how it was closed. Names, email addresses and phone numbers come out before anything leaves your org.

Allied arranges the license; your company licenses directly to the lab. Your own admin runs the export and removes identifiers inside your systems, and the copy goes straight from you to the buyer. Allied never sees it. For the commercial overview of CRM licensing, see CRM history; for every record type labs license, see what we license.

This page is about licensing your org’s records. It is not about moving off Zendesk Sell, reselling Salesforce seats, or Salesforce’s own AI features.

II

What in a Salesforce org AI labs pay for

A Salesforce org stores the same deal in many linked objects. A lab cares about the links, because the links turn a pile of rows into a worked example: this account, these touches, this outcome.

ObjectWhat it holdsWhy a lab wants itIdentifier risk
Opportunity, with OpportunityHistory and field historyStage, amount, close date and every change to themThe outcome a sales agent is graded against, and the path to itLow once account names and exact amounts are replaced
Task and Event (activity history)Logged calls, meetings and their Description notesWhat a rep did next, and whenHigh: notes name people and quote them
EmailMessage (Enhanced Email)Email bodies and headers tied to recordsReal buyer and seller language across a cycleHigh: signatures, addresses, quoted threads
Notes, Next Step and Description fieldsReps’ free-text reasoning on dealsWhy a deal moved or stalled, in the rep’s wordsMedium to high
Case and CaseComment (Service Cloud)Customer problems, internal comments, resolutionsThe full arc an AI service agent is built to repeatHigh: customer details in the text
Account, Contact and LeadWho the company and people areContext only; the identity layer is mostly removedVery high

Lab suppliers list Salesforce by name. Mercor’s intake page shows Salesforce among the tools a company connects, described as accounts, contacts, opportunities, and reports.7

micro1’s company data page lists sales and CRM among its categories: CRM data, sales processes, playbooks, customer lifecycle documentation, and revenue operations.8

Check how far back your history really goes. Standard field history tracking covers 20 fields per object; field history data is retained for 18 months in the Salesforce UI and is available for up to 24 months via the API. Field Audit Trail, a paid add-on, tracks up to 200 fields per object and keeps the history longer. Without it, stage changes from five years ago may already be gone, even though the opportunities themselves remain.6

Activities survive better than field history. Logged tasks, events and emails stay attached to their records, so an org with years of disciplined logging holds most of its value even where stage history has aged out.

III

How to export Salesforce data for a license

  1. Data Export Service (Setup)

    The in-browser export under Setup lets an admin export manually once every 7 days (weekly export) or 29 days (monthly export), or schedule it. Weekly exports are available in Enterprise, Performance and Unlimited Editions; Professional and Developer Editions are limited to every 29 days. Large exports are split into several zip files, and the zip files are deleted 48 hours after the email is sent, so download promptly.3

  2. Data Loader

    A client application your admin installs, run from its wizard or the command line. Salesforce lists support for large files with up to 5 million records with Bulk API and 150 million records with Bulk API 2.0. It exports one object at a time with the fields you pick, which suits a scoped export.4

  3. Bulk API 2.0

    The REST-based API for querying large datasets asynchronously. Bulk query jobs are designed for queries that return 2,000 records or more, and the API is enabled by default for Performance, Unlimited, Enterprise and Developer Editions. The user needs the API Enabled permission.5

For a license, the field-level tools are usually the better fit. The Data Export Service hands you every object and every column; Data Loader and Bulk API 2.0 let your admin write a SOQL query that leaves Email, Phone, MailingStreet and similar fields out of the file from the start. A column that is never exported never has to be scrubbed.

If the company is closing or leaving Salesforce, mind the contract clock. On request made within 30 days after termination or expiration, Salesforce will make Customer Data available for export; after that 30-day period it has no obligation to keep it and will delete it. Take the export first. See the shutdown checklist for the order of steps.1

IV

What Salesforce’s contract and AUP say

The Main Services Agreement defines Customer Data as electronic data and information submitted by or for Customer to the online Services, excluding Non-SFDC Applications. That covers your accounts, opportunities, activities, emails and cases. Salesforce takes a limited license to host, copy, use, transmit and display it as needed to run the service, and acquires no right, title or interest in or to it beyond that.1

The restrictions in section 3.4 are about the service, not your records. You may not sell, resell, license, sublicense, distribute, rent or lease any Service. Licensing an exported copy of your own Customer Data to a lab is a different act from reselling Salesforce, and nothing in the agreement reserves that data to Salesforce.1

Section 3.3 puts the legality on you. The customer is responsible for the accuracy, quality and legality of Customer Data and the means by which it acquired that data. If a list came from a purchased list or a scraping tool, its license terms travel with it.1

Data that arrived through AppExchange packages or enrichment vendors is a separate question. Non-SFDC Applications sit outside the Customer Data definition, and an enrichment vendor’s contract often bars passing its records to third parties. Leave enriched fields out unless that contract allows it.1

The Acceptable Use and External-Facing Services Policy bars using a Salesforce service for selling to, exchanging with, sharing with, or distributing to a third party personal information, including email addresses, without the person’s knowing and continued consent. A violation counts as a material breach of the MSA. That rule sits in the anti-spam section and governs use of the service, but its direction is clear: contact details stay out of any CRM license.2

Large customers sign negotiated order forms that can change these terms. Read your own signed agreement and order forms, not only the online version.

V

Customer and contact data: where the limits are

B2B contacts are personal data. California’s partial exemption for business contact information in a business-to-business relationship, in section 1798.145, became inoperative on January 1, 2023. A Salesforce Contact record for a buyer at another company is personal information under the CCPA.11

The CCPA’s deidentified standard has three parts. The business takes reasonable measures so the information cannot be associated with a consumer or household, publicly commits not to reidentify it, and contractually obligates any recipients to comply. A lab license should carry that third condition in writing.11

Watch the privacy policy. The FTC warned on February 13, 2024 that it may be unfair or deceptive for a company to adopt more permissive data practices, such as using data for AI training, and only inform consumers through a surreptitious, retroactive amendment to its terms of service or privacy policy. If your policy never mentioned this use, the safe course is a license limited to records with identifiers removed, not a quiet edit to the policy.12

For contacts in the EU, the GDPR stops applying only when data is truly anonymous. Data that can still be attributed to a person with additional information, such as a lookup table of swapped names, remains personal data.13

Your customer contracts can be stricter than any statute. MSAs and NDAs with your own customers often treat what they told you in emails and cases as their confidential information. List the accounts whose contracts restrict use of their information and exclude their records. The legal overview covers the general rules; this section is the CRM-specific part.

VI

De-identifying a Salesforce export

Your team does this inside your own systems before any file leaves. Allied never sees the records. The order that works for CRM history:

  1. Drop identity columns at the query

    Leave out Name, Email, Phone, Title, MailingAddress and social fields on Contact and Lead, and Name, Website and BillingAddress on Account. If a field is not needed for the task, do not select it.

  2. Replace record IDs with consistent tokens

    Swap each Salesforce record ID for a token that is the same everywhere it appears, so a task still points to its opportunity and an email to its case. Keep the mapping table inside your company; it never goes to the lab.

  3. Scrub the free text

    Task and Event descriptions, EmailMessage bodies, Case descriptions and CaseComment bodies carry names, phone numbers, email signatures and quoted threads. Run a scrubber over every long-text field and review a sample by hand.

  4. Coarsen what reveals the business

    Bucket opportunity amounts into ranges and keep relative dates if exact ones would expose a known deal. Competitors’ names in notes can be replaced too.

  5. Exclude by default

    Attachments and files, HR and legal cases, accounts with restrictive contracts, and anything from enrichment packages. Opt back in only on purpose.

For the general method across Slack, email and tickets, see how to anonymize company data for AI training. Where reps’ own notes are involved, read employee consent for AI training.

VII

What company data AI labs are buying right now

The buying is active and funded. On October 9, 2026, micro1 announced a commitment to spend $1 billion over the next 12 months acquiring and licensing enterprise operational data.9

micro1 looks for established companies with 30+ full-time employees and substantial historical operational data, naming CRM records and support tickets alongside internal communications and SOPs. Its page states payments typically ranging from $100K to over $3M, paid within 30 days of acceptance.8

Whole archives change hands in wind-downs. In Spirit Airlines’ bankruptcy, Google outbid Mercor for the carrier’s records; MIT Technology Review reported the price as $10 million. The same report says 47% of SimpleClosure deals now include code or data sales.10

The common thread is records of real work with outcomes attached. CRM history qualifies when it holds years of logged activity, not just a contact table. See what data AI companies buy for every record type and who buys AI training data for the buyers.

VIII

What a license for CRM history looks like

A license grants a lab the right to use a defined copy for defined purposes. You keep your org and your originals. Allied’s direct licenses are non-exclusive, so the same history can be licensed again.

A typical license runs $100K–⁠$2M. Years of history, volume of logged activity and how complete the links are between objects set where yours lands. See what company data is worth.

The written terms name the objects and date range in scope, the fields removed, the uses allowed (training and evaluating models, nothing else), a ban on reidentification and resale, how long the lab may keep the copy, and deletion at the end. The licensing agreement guide covers each clause.

Delivery goes straight from your team to the lab, after you approve a sample. Payment arrives by wire 30 to 60 days after the lab accepts delivery.

IX

How to sell CRM data to AI companies, step by step

  1. Size the org

    Count opportunities, activities, emails and cases by year, and note which editions and add-ons you have. Check whether field history has aged out.

  2. Read the paper

    Your Salesforce agreement and order forms, your privacy policy, your customer contracts, and any enrichment vendor terms.

  3. Request an offer

    Answer a few questions on the request form. If the records fit, a discovery call follows. Once you sign with Allied, the target is a written offer naming the lab within two weeks.

  4. Export and de-identify a sample

    Your admin runs a scoped export and your team removes identifiers. The lab reviews the sample, not the full set.

  5. Sign and deliver

    Sign the license, deliver the full scoped copy directly to the lab, and get paid after acceptance.

The broader process for every record type is in how companies license data to AI labs. Allied’s usual fit is 30 or more office employees with several years of history. How Allied works.

X

The risks of selling company data to AI companies

  1. Privacy enforcement

    Contact data licensed with identifiers intact, or under a privacy policy that never allowed it, is the main exposure. The CCPA11 and the FTC guidance12 above are where enforcement starts.

  2. Breach of customer contracts

    Confidential information your customers shared in cases and emails may be off limits under their contracts, whatever privacy law says.

  3. Breach of your Salesforce terms

    Using the service itself to share personal information without consent breaches the AUP, and an AUP breach counts as a material breach of the MSA.2

  4. Reidentification through free text

    Most leaks in CRM exports come from notes and email bodies, not from the columns you dropped. Sample review before delivery is the control.

  5. Revealing your own business

    Exact deal sizes, discount patterns and named competitors tell a reader how you sell. Bucketing and replacement reduce this; some companies exclude recent years.

  6. Locking yourself in

    An exclusive license can stop you licensing the same history again. Non-exclusive terms keep that option.

XI

Questions about licensing Salesforce data

How do you sell CRM data to AI companies?

You license a de-identified copy rather than sell the database. Confirm the records are yours to license, export the objects in scope with Data Loader or the Bulk API, remove names, contact details and identifying free text in your own systems, agree a written license, and deliver the copy directly to the lab. Allied arranges the license with the lab and never sees the data.

What company data are AI labs buying right now?

Records of real work with outcomes attached: CRM history with logged activity, support tickets, workplace chat and email, call recordings and code. Lab suppliers such as micro1 and Mercor name Salesforce and CRM records on their own intake pages.

What are the risks of selling company data to AI companies?

Privacy enforcement if contacts can be identified, breach of customer contracts that protect what customers told you, breach of your Salesforce terms if the service itself is used to share personal information, reidentification through notes and email bodies, exposing how you sell, and exclusivity that blocks a second license.

Does Salesforce own the data in our org?

No. The Main Services Agreement gives Salesforce a limited license to host and process Customer Data to run the service, and says it acquires no right, title or interest in it beyond that. Your signed order forms can add terms, so read them.

Can we just send the weekly Data Export Service file?

It is a full dump of every object and column, including the contact fields a license excludes. A scoped export through Data Loader or the Bulk API, with identity fields left out of the query, is cleaner and leaves less to scrub.

Do we need our customers’ consent?

Not usually for records with identifiers removed, but check two things first: what your privacy policy said when the data was collected, and whether customer contracts treat their information as confidential. Exclude accounts whose contracts restrict it.

Will Allied see our Salesforce records?

No. Allied never sees, reads or receives your records. Your admin exports and removes identifiers inside your systems, you approve a sample, and the copy goes straight to the lab.

Our field history only goes back a short way. Is the org still worth licensing?

Often yes. Logged calls, meetings, emails and cases stay attached to their records even after field history ages out, and that activity is most of what labs want.

Does HubSpot or Dynamics history work the same way?

Mostly. The objects have different names and the export tools differ, but the value in activity history and the limits on contact data are the same.

Find out what your Salesforce history is worth.

A few questions. About two minutes. How Allied works.

Request an offer