A contact in a CRM is any individual person your business has a relationship with – or wants one with. That’s the short answer. But the moment you open most CRM platforms for the first time, you’ll notice the word “contact” sitting alongside “lead,” “customer,” and sometimes “prospect” – and it’s not always obvious where one ends and the other begins.

This guide is for anyone who’s just started using CRM software, or who’s been using it for a while but never got a clear explanation of how these terms fit together. If that’s you, you’re not alone. It’s one of the most common points of confusion in CRM, and it genuinely matters for how your sales process runs day to day.

What Is a Contact in a CRM, Really?

Think of a contact record as a single source of truth for one human being. Not a company, not a deal – a person. Their name, job title, email address, phone number, which company they work at, and every interaction your team has ever had with them: emails sent, calls logged, meetings booked, notes left.

Simple, right? The reason it matters is that your entire sales pipeline is built on top of these records. If a contact’s information is incomplete, duplicated, or just plain wrong, every downstream activity – outreach, follow-up, forecasting – gets messier than it needs to be.

One way to think about it: a contact record is less like a business card and more like a running conversation log. It captures not just who someone is, but the full history of how your company has engaged with them. That context is what makes a CRM genuinely useful rather than just a glorified address book.

How Contacts Differ from Leads

Here’s where it gets slightly technical – but stay with it, because this distinction has real operational consequences.

A lead is an unqualified person. Someone who filled out a form on your website, downloaded a guide, or was imported from a list. You know they exist, but you don’t yet know if they’re worth pursuing. Leads sit at the very top of your funnel, and the whole point of working them is to figure out whether they match your Ideal Customer Profile (ICP).

A contact, in most CRM platforms, is what a lead becomes once you’ve decided they’re worth tracking properly. Some CRMs – HubSpot is a good example – store everyone as a contact from the start and use lifecycle stages to distinguish between someone brand new and someone deep in a sales conversation. Others, like Salesforce, keep leads and contacts in completely separate buckets until a lead is formally “converted.” Neither approach is wrong; they just reflect different opinions about how the qualification process should work.

The practical upshot: if your CRM has both a Leads section and a Contacts section, you’ll want to convert a lead to a contact once you’ve confirmed they’re a real person at a real company who could actually buy from you. Before that point, they’re a lead.

What Makes Someone a Customer – and Why It’s a Different Record

A customer is a contact who has bought from you. Simple enough. But in CRM terms, “customer” usually isn’t a separate record type – it’s a status or lifecycle stage applied to an existing contact record.

This matters because you want all the history in one place. When a contact becomes a customer, you don’t want to lose the record of how long their sales cycle took, which rep closed them, or what objections came up during the deal. That information feeds into renewal conversations, upsell opportunities, and your understanding of Customer Lifetime Value (LTV).

What changes when someone becomes a customer is usually who owns the relationship. Pre-sale, it’s typically a sales rep; post-sale, it might shift to a customer success manager. The contact record stays – the ownership and the associated activities change around it.

A Concrete Example: From Stranger to Contact to Customer

Let’s make this tangible. Say you work in sales at a B2B software company.

Day 1: Someone named Sarah Chen, a marketing director at a mid-sized e-commerce brand, downloads your pricing guide. Her name and email land in your CRM as a lead.
Day 3: You look her up, confirm the company size fits your ICP, and convert her to a contact. You attach her to the company record for her employer and open a deal.
Week 2: You have a discovery call. You log notes on the contact record. Her colleague James, who’d be a secondary decision-maker, gets his own contact record, linked to the same company and the same deal.
Week 6: Sarah signs. Her contact record gets updated to “Customer.” The deal closes. Everything – every email, every call note, every activity – stays attached to her record for whoever manages the account going forward.

That’s the lifecycle, and every part of it depends on the contact record being accurate and up to date. If someone forgot to log that Week 2 call, whoever handles the renewal has no idea what was discussed during the sale. It’s a real problem – and it happens constantly in teams that treat CRM as an afterthought.

What Fields Should a Contact Record Actually Contain?

Most CRMs give you a default set of fields. These are the ones that genuinely earn their keep:

Full name and job title – sounds obvious, but titles matter for personalisation and for understanding someone’s buying authority
Email address and phone number – the basics of reaching them
Company name – linked to a separate company (or “account”) record
Lead source – how they first came to you (paid ad, referral, inbound form, outbound outreach)
Lifecycle stage or status – lead, qualified lead, opportunity, customer, churned
Contact owner – which rep or CSM is responsible for this person
Last activity date – when someone last touched this record; a useful early warning for contacts going cold

Beyond the defaults, most platforms let you create custom fields – and that’s where teams get into trouble, adding twenty custom fields that nobody fills in. Keep it lean. Every field on a contact record should answer a question your team actually asks.

Why Contact Data Quality Matters More Than Quantity

This is probably the most overlooked point for teams new to CRM. It’s tempting to think a bigger contact database is automatically better. It’s not.

A contact record no one maintains becomes noise. Duplicate contacts – where Sarah Chen appears three times under slightly different email addresses – create confusing activity histories and mess with reporting. Bad data in, bad decisions out. Your sales forecast is only as reliable as the data underneath it, and that data starts with whether your contact records are clean.

Good habits here aren’t complicated. Deduplicate regularly. Make lead source a required field so you can’t save a contact without it. Set a clear rule for when a lead becomes a contact – and make sure everyone on the team follows the same rule. Consistency matters far more than sophistication. You can read more about how contacts fit into the broader structure of your CRM in our article on CRM Database Explained: Contacts, Companies, Deals and Activities.

It’s also worth thinking about contact data as part of your RevOps foundation. When sales, marketing, and customer success all look at the same contact records – with consistent fields and consistent lifecycle stages – handoffs stop being chaotic. That alignment is where a lot of revenue gets saved or lost.

Contacts Across Different CRM Platforms

The concept of a contact is universal. The implementation varies quite a bit.

In HubSpot, contacts are the central object. Everything – companies, deals, tickets – orbits around the contact. You can set lifecycle stages (subscriber, lead, marketing qualified lead, sales qualified lead, opportunity, customer) directly on the contact record, which makes the whole pipeline visible in one place.

In Salesforce, the distinction between leads and contacts is more rigid. Leads live in their own separate object, and once converted, they become a contact linked to an account and an opportunity. It’s a more structured model that suits enterprise sales teams with clear qualification stages, but it can feel unnecessarily complicated for smaller teams.

In Pipedrive, contacts are called “People” – a small but meaningful naming choice that keeps the focus on the human relationship rather than the data record.

If you’re still deciding which CRM fits your team’s contact management style, our CRM Tools Directory is a good place to compare options side by side. And if you want to go deeper on how any of the terms in this article connect to broader go-to-market (GTM) strategy, the CRM Glossary has plain-English definitions for the concepts that come up most often.

The CRM Daily Newsletter also covers contact enrichment tools, data quality practices, and platform updates regularly – worth bookmarking if you’re building out a CRM process from scratch.

Think back to Sarah Chen from our earlier example. She started as an unfamiliar email address attached to a downloaded guide. By the end of the process, her contact record held two months of conversation history, a closed deal, a linked company account, and a secondary contact in James. None of that value exists without the contact record as the foundation. Get that right first, and the rest of your CRM starts making a lot more sense.

What Is a Contact in a CRM? Contacts, Leads and Customers Explained

CRM Daily Digest

Get this kind of intelligence every morning.