Definitions and comparisons
What is CRM data? Record types, examples and what is worth licensing
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
CRM data is everything a customer relationship management system stores about the people and companies a business sells to and serves: contact, account, lead and opportunity records, the activity history of calls, emails, meetings and tasks, field change history, free-text notes, attachments and third-party enrichment. For licensing, structured history is usually the valuable core, while notes, email bodies, files and enrichment need permission review first.
Key takeaways
- CRM data covers contacts, accounts, opportunities and activities, plus change history, notes, emails, files and enrichment fields.
- Much of the value sits outside the record page: in field history, activity logs and related objects that a standard export may skip.
- Structured first-party history, with identifiers removed, is usually the strongest licensing candidate.
- Email bodies, notes, attachments and vendor enrichment usually need separate permission review, and some will be excluded.
- Access, privacy permission, ownership and contract terms are four separate tests; de-identification alone does not create a right to license.
What is CRM data?#
CRM data is the set of records a customer relationship management system keeps about prospects, customers and the work done with them. In Salesforce, HubSpot, Microsoft Dynamics 365 or Zoho CRM that means the core business objects (people, companies, deals, support cases), every logged interaction, and the metadata that shows who changed what and when.
The useful way to think about it is as a database, not a contact list. Each record type is a table with fields (Salesforce calls them fields, HubSpot calls them properties), and records are linked to each other: a contact belongs to an account, an opportunity belongs to an account, and a call or email is attached to one or more of those records. Those links are what turn a list of names into a history of how deals actually progressed.
Most people searching for CRM data mean one of three things: what the system stores, what the records look like in practice, or what the data is good for. This page answers all three, then goes one step further for operators deciding whether any of it could be licensed as a dataset.
What are the main types of CRM data?#
By content, CRM data falls into four core types: contact data, account data, opportunity (deal) data and activity data. Around them sit supporting types such as case or ticket records, products and line items, campaigns, users and owners, change history, notes, attachments and enrichment fields.
By purpose, the older textbook split is operational, analytical and collaborative CRM data. These describe how data is used rather than separate databases, and the same record often serves all three. Some frameworks add a fourth category, strategic CRM, which is about customer-focused planning rather than a distinct data type.
| Type | What it contains | Typical example | Why it matters |
|---|---|---|---|
| Contact data | People: names, titles, emails, phone numbers, lifecycle stage, owner, consent and subscription flags | A buyer at a customer company with job title and lead source | Identifies individuals, so it carries the most direct privacy obligations |
| Account data | Organizations: company name, industry, size, region, parent company, account tier | A customer account with segment, territory and renewal date | Firmographics that are rarely personal data but may include enrichment from vendors |
| Opportunity data | Deals: amount, stage, close date, probability, products, competitors, loss reason | A renewal opportunity that moved from Proposal to Closed Won | The sales outcome record; the basis for forecasting and win-loss analysis |
| Activity data | Calls, emails, meetings, tasks and their timestamps, outcomes and linked records | A logged discovery call with duration and disposition | Shows the sequence of work behind each outcome, not just the result |
| Operational data | Records used to run day-to-day sales, marketing and service processes | Lead routing rules, case queues, task due dates | Reflects how the business actually operates |
| Analytical data | Records and history used for reporting, segmentation and forecasting | Pipeline snapshots, stage conversion reports | Depends on history being kept; current values alone hide the trend |
| Collaborative data | Shared context across teams: notes, feeds, handoffs, internal comments | A Chatter post or a sales-to-success handoff note | Often free text, so it is rich but needs the most careful review |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
What does a CRM actually hold beyond the record you see?#
A CRM holds far more than the fields on a record page. Related activities, change history, emails, files, feed posts and system metadata mostly appear only in related lists, audit tables or the API, so a standard export can miss them. Change history is the clearest case: Salesforce keeps OpportunityHistory for the stage history of an opportunity and OpportunityFieldHistory for changes to other tracked fields, and with Field Audit Trail off, field history is kept for up to 18 months (up to 24 months through the API), while Field Audit Trail adds longer retention policies.
Activities are the second layer: HubSpot stores notes, tasks, emails, meetings and calls as engagements associated with records, and redacts email engagement details unless the app has the sales-email-read scope. The third layer is enrichment and imported fields that arrive with their own license terms. For why history beats a snapshot, see the page on CRM activity history versus the current snapshot.
CRM record-type inventory: what each one reveals and how sensitive it is#
Use this table as a working inventory. For each row, note whether your company uses that record type, how many years of history exist, and who administers it. Object names vary with edition and configuration, and custom objects (for example a Salesforce object ending in __c) often hold the most industry-specific data, so add them as rows of their own.
| Record type | Salesforce / HubSpot examples | What it reveals | Sensitivity and licensing review note |
|---|---|---|---|
| People records | Salesforce Lead, Contact; HubSpot contacts | Who was contacted, their role, source and lifecycle stage | High. Direct identifiers; usually removed or replaced before any release, and privacy notices must be checked |
| Organization records | Salesforce Account; HubSpot companies | Customer mix by industry, size, region and tier | Low to medium. Names of customers can be confidential under customer contracts even when not personal data |
| Deals and pipeline | Salesforce Opportunity, OpportunityLineItem; HubSpot deals | Deal size, stage, cycle length, products, win and loss outcomes | Medium. Commercially sensitive; amounts and customer names may need bucketing or removal |
| Field and stage history | Salesforce OpportunityHistory, OpportunityFieldHistory | How values changed over time and how long each stage took | Medium. Often the most valuable layer for analysis; check how far back it goes before scoping |
| Activities | Salesforce Task, Event; HubSpot calls, meetings, tasks | Volume, timing and sequence of sales and service work | Medium. Subjects and descriptions can contain names and free text; structured fields are lower risk |
| Email content | Salesforce EmailMessage; HubSpot emails | Full correspondence with customers, including what was promised and asked | High. Third-party personal data and confidential terms; needs separate permission review and heavy redaction |
| Notes and feeds | Salesforce Note, FeedItem; HubSpot notes | Rep and success-manager judgments, objections, internal context | High. Unstructured; can include health, HR or opinion data about named people |
| Files and attachments | Salesforce ContentDocument, ContentVersion | Contracts, proposals, quotes, recordings, screenshots | High. Often contain customer contract terms or third-party IP; usually excluded unless reviewed one by one |
| Support cases | Salesforce Case; HubSpot tickets | Issues raised, resolution path and time to resolve | Medium to high. Valuable for service AI; descriptions and comments carry personal and customer data |
| Enrichment and imported fields | Vendor-populated firmographic or contact fields in either system | Company size, revenue band, technographics, job seniority | Restricted. The vendor's terms usually decide whether it can be passed on; often excluded by default |
Which CRM data could be licensed?#
Structured, first-party history such as deal stages and durations, activity timing, case categories and account segments is the part most likely to be licensable after de-identification. Free text, email bodies, attachments and vendor enrichment usually need separate permission review, and some of it stays out. De-identification lowers privacy risk but does not create a right to license. The full answer is on the page about whether CRM data can be licensed, and enrichment fields have their own page on third-party data in your CRM.
Four permissions that apply to CRM data#
Four separate questions decide whether any record type in the inventory can be used in a dataset: who can access it, whether privacy permission covers the new use, who owns it, and what CRM vendor, customer and data vendor contracts allow. A yes to one never answers the others, so mark each inventory row against all four. The full framework is in the guide to data privacy and the right to license business records.
What privacy rules usually come up with CRM data?#
The rule that most often matters is purpose limitation: personal data collected for one purpose generally cannot be reused for an incompatible one. Under the EU GDPR, Article 6(4) lists compatibility factors and Article 9 separately restricts special categories such as health data, which can surface in notes and support cases. The CCPA likewise requires notice at collection and bars incompatible additional purposes without notice. That is why contact data and free text get more scrutiny than deal stages. See what free-text notes in CRM records reveal and notice versus consent for business records.
How do you inventory your own CRM in an afternoon?#
Start from the object list, not from a single export. A standard export or report shows current values, while history, activities, emails and files often sit in separate objects that need their own extracts.
- List every standard and custom object in use with its record count and the date of its oldest record.
- Check which fields have history tracking turned on, and how far back that history actually goes in your edition.
- Count activities by type and year, and note whether email bodies are stored in the CRM or only logged as metadata.
- Identify free-text fields (descriptions, notes, comments, custom long text) and sample 50 records from each to see what they contain.
- Flag fields populated by enrichment tools, imports and marketplace apps, and find the contract behind each.
- Record who administers the org, which integrations hold API access, and whether any past migration dropped history.
- Fill in the inventory table above and mark each record type against the four permissions.
How this applies if you are considering licensing CRM data#
If the inventory shows several years of consistent history in one system, it may be worth a closer look. As a general guide, buyers look for years of consistent history, typically two or more, and tens of thousands of records or more, though smaller sets can qualify when the work is rare; every case is assessed deal by deal.
SourceX runs sourcing, rights review, contracting, data preparation, delivery and payment for businesses licensing operational data to AI developers, and works with U.S., Canadian and EU companies that had 50 or more full-time employees at their peak. The first step is a short company assessment with no data uploads, and the company approves exactly what is released, once per deal, before anything is shared. Under standing terms, de-identification is performed by SourceX directly or through its processing partner.
Frequently asked questions
What is CRM data in simple terms?
CRM data is the information a company's customer relationship management system stores about its prospects and customers and the work done with them. It includes contacts, companies, deals, support cases, logged calls, emails and meetings, notes, files and the history of changes to those records.
What are examples of CRM data?
Examples include a contact's job title and lead source, an account's industry and tier, an opportunity's amount and stage history, a logged call with its duration and outcome, a support case with its resolution time, and a sales note written after a meeting. In Salesforce these sit in objects such as Contact, Account, Opportunity, Task and Case; in HubSpot in contacts, companies, deals, calls and tickets.
What are the types of CRM data?
By content, the core types are contact, account, opportunity and activity data, with supporting types such as cases, products, campaigns, change history, notes, files and enrichment. By purpose, CRM data is often described as operational, analytical or collaborative, depending on whether it runs daily processes, feeds reporting or captures shared team context.
Is a spreadsheet a CRM database?
A spreadsheet can hold customer data, but it lacks what makes a CRM a database of relationships: linked records, activity logging, permissions and change history. Spreadsheet-based customer lists also tend to lose history when rows are overwritten, which limits their value for analysis.
Does removing names make CRM data safe to license?
No. De-identification lowers privacy risk, but free text can still identify people, and anonymized data can remain restricted by customer contracts or vendor licenses. Removing identifiers is one preparation step, not a grant of rights.
Sources
- The Salesforce Object Reference documents the EmailMessage object, which represents an email in Salesforce. Source
- The Salesforce Object Reference documents ContentDocument as a document uploaded to a library in Salesforce Files or Salesforce CRM Content, and ContentVersion as a specific version of such a document. Source
- The Salesforce Object Reference documents FeedItem as an entry in the feed, such as a record feed change, a text post, a link post or a content post. Source
- Salesforce documents Tasks and Events as activity records that can relate to objects such as Account, Case and Contact. Source
- Salesforce documents OpportunityHistory as the stage history of an opportunity. Source
- Salesforce documents OpportunityFieldHistory as the history of changes to the values in the fields of an opportunity. Source
- Salesforce documents that with Field Audit Trail off, field history is retained for up to 18 months, and up to 24 months through the API. Source
- Salesforce documents that Field Audit Trail extends Field History Tracking so field history can be kept for longer. Source
- Salesforce Trailhead explains that a Field Audit Trail retention policy sets how long field history stays in the History related list before archiving and how long it is kept in the archive. Source
- HubSpot developer documentation lists standard CRM objects including contacts, companies, deals and tickets, each with an object type ID (0-1, 0-2, 0-3, 0-5). Source
- HubSpot documents that records store information about interactions through associated engagements (activities) such as emails, calls and meetings. Source
- HubSpot states that engagement requests without the sales-email-read scope get the details of EMAIL, INCOMING_EMAIL and FORWARDED_EMAIL engagements redacted. Source
- The GDPR requires personal data to be collected for specified purposes and not further processed incompatibly (Article 5(1)(b)), sets compatibility factors in Article 6(4) and restricts special categories of data in Article 9. Source
- The CCPA (Cal. Civ. Code 1798.100) requires notice at or before collection of categories and purposes and bars use for additional incompatible purposes without notice. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.