HubSpot
Salesforce
Pipedrive
Intercom
MailchimpCRM data quality
The condition of CRM data at a point in time: is it accurate, complete, consistent, unique, valid, and timely?
CRM Data Management Glossary
CRM data terms, explained clearly.
Understand the language behind CRM data management, data quality, Data Integrity, governance, automation, integrations, and AI-ready customer data.
- Plain-language definitions
- CRM-specific examples
- Stable links to every term
Glossary search
D
Data drift
When governed CRM data stops conforming to its assigned standard.
D
Deduplication
Finding and consolidating records that represent the same entity.
S
Sync conflict
When connected systems disagree about which state should prevail.
From cleanup to continuous integrity
Data management fixes the record. Data Integrity keeps the standard holding.
Data management covers the work used to inspect, clean, organize, and update CRM data. Data Integrity defines what right looks like, applies those standards, and measures whether they continue to hold as people, systems, and agents change the CRM.
Start with the fundamentals
Four related concepts. Four different jobs.
These terms are often used interchangeably. The distinction is whether you are describing the condition, the work, the organizational controls, or the continuous operating system.
CRM data management
The work used to inspect, organize, clean, update, import, associate, assign, and otherwise control CRM records.
Data governance
The policies, ownership, decision rights, and accountability that determine how an organization manages data.
CRM Data Integrity
The system that defines company standards, applies them consistently, and measures whether CRM records continue to conform.
The glossary
Browse CRM data management terms.
Search by term, definition, or example, or filter by the kind of work you are trying to understand.
58 definitions shown
01 · Foundations
The baseline concepts used to describe reliable customer data, ownership, and operating responsibility.
Accuracy#
The degree to which a CRM value correctly represents the real-world person, company, activity, or event it describes.
CRM example: A contact’s current employer and business email match the person’s actual employment.
Related:ValidityCompleteness
CRM data management#
The ongoing work of inspecting, organizing, cleaning, updating, importing, and controlling customer records so CRM data remains usable for operations, reporting, automation, and AI.
CRM example: A RevOps team deduplicates accounts, standardizes countries, associates contacts, and validates an import before go-live.
Explore:Data Management
CRM data quality#
The condition of CRM data at a point in time, commonly evaluated through accuracy, completeness, consistency, uniqueness, validity, and timeliness.
CRM example: A quarterly assessment finds complete account records but inconsistent industry values.
Related:CRM Data Integrity
Data governance#
The policies, ownership, decision rights, and accountability used to manage data across an organization.
CRM example: Sales Operations owns account-routing rules while Finance approves the customer hierarchy standard.
Related:Data stewardship
Data reliability#
The degree to which people and systems can depend on data to remain accurate, consistent, available, and fit for its intended use.
CRM example: Territory reports produce dependable results because account attributes follow one maintained standard.
Related:CRM Data Integrity
Data stewardship#
The hands-on responsibility for interpreting data policy, resolving exceptions, and helping data meet organizational standards.
CRM example: A steward reviews unmatched industries and decides which values belong in the approved taxonomy.
Related:Data governance
Source of truth#
The authoritative reference used to resolve disagreements about a value, classification, rule, or business definition.
CRM example: A versioned territory table, not scattered workflow branches, is the source of truth for routing logic.
Related:System of record
System of record#
The designated system that holds the authoritative operational record for a particular entity or process.
CRM example: Salesforce is the system of record for accounts, while HubSpot manages marketing engagement.
Related:Source of truth
02 · Quality & cleanup
Terms for diagnosing, correcting, and measuring the condition of existing CRM data.
Completeness#
The extent to which required CRM fields and records contain the information needed for their intended use.
CRM example: Every open opportunity has an amount, close date, stage, owner, and associated account.
Related:Coverage
Consistency#
The degree to which equivalent data uses compatible meanings and representations across records, fields, and connected systems.
CRM example: “United States” represents the same country in HubSpot and Salesforce.
Related:Data standardization
Data cleaning#
The process of identifying and correcting inaccurate, incomplete, inconsistent, duplicate, outdated, or unusable CRM data.
CRM example: Remove junk leads, normalize phone numbers, merge duplicates, and fill known gaps before a campaign.
Explore:Clean CRM Data
Data cleansing#
A common synonym for data cleaning. In CRM work it often emphasizes standardizing, formatting, validating, or removing problematic field values.
CRM example: Convert inconsistent job titles, phone formats, and capitalization into approved outputs.
Product:Cleanse Data
Data normalization#
The process of bringing values into a consistent structural format so they can be compared, matched, and used reliably.
CRM example: Remove protocols and paths from website values so domains can be matched consistently.
Related:Data standardization
Data profiling#
The examination of CRM data distributions, patterns, formats, blanks, and anomalies to understand its actual condition before defining changes.
CRM example: Review every distinct Industry value and its record count before creating a taxonomy.
Related:Data validation
Data standardization#
The process of converting equivalent CRM values into a consistent approved format or controlled vocabulary.
CRM example: Convert “VP Sales,” “Vice Pres. of Sales,” and “Sales VP” into one approved title or persona.
Explore:Standardize CRM Data
Data validation#
The process of checking whether data satisfies defined format, value, completeness, and business requirements.
CRM example: Flag contacts whose email is malformed or whose required lifecycle field is blank.
Related:Validity
Junk record#
A CRM record that lacks legitimate operational value, such as a test submission, spam entry, placeholder, or obviously unusable contact.
CRM example: A contact named “asdf test” with a disposable email and no meaningful activity.
Explore:Clean CRM Data
Timeliness#
The degree to which data is current enough and available soon enough for the decision or process that depends on it.
CRM example: A reassigned territory reaches the correct owner before the lead-response SLA expires.
Related:Accuracy
Uniqueness#
The degree to which each real-world entity is represented once within the relevant CRM scope.
CRM example: One company record represents Acme rather than five variations with divided activity.
Related:Deduplication
Validity#
The degree to which data conforms to the allowed format, type, range, or business rule defined for it.
CRM example: A country field contains an approved country value rather than an internal note.
Related:Data validation
03 · Identity & relationships
Terms for deciding which records represent the same entity and how people, companies, deals, and other objects connect.
Association#
A relationship between CRM records that provides business context, such as a contact connected to a company or a deal connected to an account.
CRM example: Associate a lead with the correct account using email domain, location, and other criteria.
Product:Associate
Deduplication#
The process of identifying records that represent the same entity and consolidating them according to controlled matching, master-selection, and retention rules.
CRM example: Merge three account variations while keeping the Salesforce-linked record and the newest billing address.
Explore:Eliminate Duplicates
Duplicate group#
A set of two or more records that matching logic identifies as possible representations of the same entity.
CRM example: Five contacts with related emails and the same phone number appear as one reviewable group.
Related:Record matching
Entity resolution#
The process of determining which records, within or across systems, refer to the same real-world person, company, household, or business object.
CRM example: Recognize that a HubSpot company and Salesforce account represent the same customer despite name differences.
Related:Deduplication
Exact matching#
A comparison method that treats values as a match only when the normalized values are identical according to the configured criteria.
CRM example: Match contacts whose external customer ID is exactly the same.
Related:Fuzzy matching
Exclusion#
A deliberate instruction that prevents a known record pair or group from being treated as duplicates in current and future reviews.
CRM example: Keep two related subsidiaries separate even though they share a domain and address.
Related:Duplicate group
Field retention#
The rules that determine which value is kept for each field when duplicate records are merged.
CRM example: Keep the most recent phone number, longest description, and nonblank customer ID regardless of which record is master.
Related:Master record
Fuzzy matching#
A comparison method that identifies values as similar despite spelling differences, typos, abbreviations, or other controlled variation.
CRM example: Identify “Acme Technologies” and “Akme Technology” as a possible match.
Related:Exact matching
Master record#
The surviving record selected during a merge to retain the primary identity and receive the chosen values, history, and relationships.
CRM example: Prefer the account with an active owner and a Salesforce ID as the master.
Related:Survivorship
Record matching#
The comparison of selected fields and conditions to determine whether records may represent the same entity or should be related.
CRM example: Compare company name, normalized domain, country, and external ID together.
Related:Exact matchingFuzzy matching
Survivorship#
The overall logic that determines which record and field values survive a consolidation process.
CRM example: Select the oldest customer record as master but retain the newest valid contact details.
Related:Field retention
04 · Operations
Terms for changing CRM data safely, repeatedly, and at scale.
Audit trail#
A chronological record of data operations, including what ran, when it ran, what records were affected, and what results occurred.
CRM example: Review the run report and record-level changes from a scheduled normalization job.
Related:Preview
Automation#
The execution of a repeatable data process according to a schedule, event, workflow, or other defined trigger.
CRM example: Standardize new lead fields when a HubSpot Workflow enrolls the record.
Related:Workflow automation
Bulk update#
A controlled operation that changes one or more field values across many CRM records in a single configured run.
CRM example: Reassign 18,000 accounts based on region and employee range after a territory change.
Product:Bulk Operations
Data migration#
The controlled movement of data from one system or structure to another, including mapping, transformation, validation, import, and reconciliation.
CRM example: Standardize legacy values and deduplicate accounts before a Salesforce go-live.
Related:Field mapping
Field mapping#
The specification of how a source column or field corresponds to a destination CRM field.
CRM example: Map “Company URL” in a CSV to the CRM’s Website field during import.
Related:Import
Import#
The process of loading external data into a CRM as new records, updates to existing records, or a controlled combination of both.
CRM example: Validate, deduplicate, and preview a trade-show CSV before creating contacts.
Product:Magical Import
Preview#
A simulation or report showing the records, matches, changes, exclusions, and errors expected from an operation before CRM data is written.
CRM example: Inspect proposed masters and retained values before approving a bulk merge.
Related:Audit trail
Record routing#
The assignment of CRM records to an owner, queue, team, territory, or process according to defined business logic.
CRM example: Assign enterprise healthcare accounts in the Northeast to a specialist team.
Product:Assign
Upsert#
An import operation that updates a matching record when one exists and creates a new record when it does not.
CRM example: Match on external ID, update existing accounts, and create only IDs not already present.
Related:External ID
Workflow automation#
A rules-based process that runs actions when defined CRM enrollment or event conditions are met.
CRM example: A Salesforce Flow invokes saved data logic when an account is created.
Related:Deterministic logic
05 · Integrations
Terms for keeping CRM data usable as it moves between applications and platforms.
Cross-platform data management#
The coordinated management of data quality, identity, standards, and operations across two or more connected systems.
CRM example: Use one company standard across HubSpot and Salesforce without disabling their native connector.
Explore:HubSpot + Salesforce
External ID#
A stable identifier assigned by another system and stored in the CRM to support matching, synchronization, migration, and reconciliation.
CRM example: Store an ERP customer number on each account to prevent name-based ambiguity.
Related:Upsert
Sync conflict#
A condition in which connected systems disagree about which value, identity, or record state should prevail.
CRM example: HubSpot and Salesforce each hold a different country value and both are configured to overwrite the other.
Related:Two-way sync
Sync loop#
A repeated cycle in which an update in one system triggers a return update from another, causing values or automation to oscillate.
CRM example: A normalization in HubSpot is reversed by Salesforce, then rewritten by HubSpot again.
Related:Sync conflict
Two-way sync#
An integration pattern in which selected data changes can move in both directions between connected systems.
CRM example: Contact and lead updates move between HubSpot and Salesforce according to field-level rules.
Related:System of record
06 · Integrity & AI
Terms for defining standards, applying deterministic logic, measuring conformance, and governing the CRM context used by AI.
Agentic CRM#
A CRM environment in which AI agents interpret customer data, make decisions, take actions, and write results back into operational systems.
CRM example: An agent researches an account, updates firmographics, drafts outreach, and changes the next action.
Explore:Prepare CRM Data for AI
BlueprintInsycle term#
An Insycle versioned table that expresses data standards or business logic. Each row maps input conditions to the outputs CRM records should produce.
CRM example: Match industry, employee range, and country to the intended territory, owner, and tier.
Product:Blueprints
Conformance#
The state in which a governed CRM record matches an applicable standard and its output fields hold the values that standard assigns.
CRM example: An account matches the enterprise healthcare row and holds the expected territory and tier.
Related:Data drift
CoverageInsycle metric#
In Insycle, coverage is the percentage of governed CRM records that match a row in the applicable Blueprint.
CRM example: If 9,200 of 10,000 governed accounts match the territory Blueprint, coverage is 92%.
Related:Coverage gap
Coverage gapInsycle metric#
A governed record that does not match any row in the applicable Blueprint, revealing unrecognized data or incomplete strategy coverage.
CRM example: A newly entered industry has no row in the persona-classification Blueprint.
Related:Coverage
CRM Data Integrity#
The ongoing assurance that CRM records continue to conform to company standards and operating strategy as new data arrives and systems change.
CRM example: Define the territory standard once, apply it to new and existing accounts, and monitor whether assigned values continue to hold.
Explore:Data Integrity
Data drift#
A change that causes governed CRM data to stop conforming to the standard or outcome previously assigned to it.
CRM example: An integration overwrites the territory assigned by the Blueprint with an obsolete value.
Related:Conformance
Data LogicInsycle term#
Insycle’s engine for applying Blueprint-based standards and business logic to CRM records. It maps inputs, evaluates rows, and writes intended outputs.
CRM example: Evaluate account firmographics against a Blueprint and assign territory, owner, and tier together.
Product:Data Logic
Data observability#
The practice of monitoring data condition and behavior to identify gaps, drift, failures, and changes that require attention.
CRM example: Track Blueprint coverage over time and inspect records that no longer hold their assigned values.
Product:Observability
Deterministic logic#
Logic that produces the same defined output whenever the same input and rule version are evaluated, making the result repeatable and explainable.
CRM example: The same industry, size, and country always produce the same territory under Blueprint version 12.
Related:Versioned logic
Governed recordInsycle term#
A CRM record included in the defined scope of a Data Logic template and therefore evaluated against an applicable Blueprint.
CRM example: Active customer accounts are governed; archived test accounts are outside the template filter.
Related:Coverage
Versioned logic#
Business rules stored with a traceable version history so teams can identify which definition produced an outcome at a particular time.
CRM example: A run report identifies that territory assignments used Blueprint version 12.
Related:Blueprint
Move from definition to practice
Use the term. Then see the work behind it.
See the modules used to deduplicate, cleanse, standardize, associate, assign, transform, and import data.
Explore Data Management →See how Blueprints, Data Logic, and Observability turn standards into a continuous operating system.
Explore Data Integrity →Find platform-specific terminology, limitations, and workflows for each supported integration.
View all integrations →Common questions
The glossary, explained.
What is CRM data management?
CRM data management is the ongoing work of inspecting, organizing, cleaning, updating, importing, and controlling customer records so they remain usable for operations, reporting, automation, and AI.
How is data management different from Data Integrity?
Data management includes the activities used to inspect and change data. Data Integrity is the maintained operating state created by defining standards, applying them consistently, and measuring whether records continue to conform as the CRM changes.
How is data quality different from data governance?
Data quality describes the condition of the data. Data governance defines the ownership, policies, decision rights, and accountability used to manage that data.
Why does AI make CRM data integrity more important?
AI agents consume CRM data as context and can also write data back at machine speed. Reliable standards and continuous measurement reduce the risk that poor inputs or agent-written changes quietly propagate through automated decisions.
See the definitions in your own data
Want a walkthrough of your CRM?
Book a live demo, or start a free 14-day trial with all modules included.
Keep exploring
Where to go next
Data Management
The eight modules teams use to merge, standardize, import, associate, and update records.
Explore CRM Data IntegrityDeclare the standard, apply it, and measure whether your data keeps holding.
Explore Platform OverviewHow Blueprints, Data Logic, and Observability work together across your CRM.
Explore CRM Data GraderGrade your CRM data in minutes and see where the biggest problems sit.
Explore