Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryCCustomer Relationship Management (CRM)
AnalyticsAdvanced

Customer Relationship Management (CRM)

Customer Relationship Management (CRM) is the category of business software that centralizes a company customer-facing data and processes: who the customers are, what they have bought, what conversations the company has had with them, what opportunities are in flight, and what issues need resolving.

§ 01

Definition

Customer Relationship Management (CRM) is the category of business software that centralizes a company customer-facing data and processes: who the customers are, what they have bought, what conversations the company has had with them, what opportunities are in flight, and what issues need resolving. A CRM stores all of this in a structured database and surfaces it through interfaces tailored to sales, service, marketing, and commerce roles. Salesforce is the largest CRM vendor by revenue and the originator of cloud-delivered CRM.

CRM as a category predates Salesforce; it grew out of contact management software in the 1980s and pipeline management software in the 1990s. Salesforce founded itself in 1999 specifically to deliver CRM through a web browser instead of an installed desktop application, which became the dominant delivery model. Today CRM also extends beyond traditional sales-and-service into marketing automation, commerce, AI-driven insights, and unified data platforms. The Salesforce platform covers all of these as integrated products that share the same customer record.

§ 02

What CRM is and how Salesforce delivers it

The core CRM data model

Every CRM uses a small set of core records. Account holds the customer organization (or person, in B2C). Contact holds an individual at that Account. Lead holds an unqualified prospect not yet matched to an Account. Opportunity holds a sales deal in progress. Case holds a customer service interaction. Activity (Task and Event) holds the conversations and touchpoints. These five or six objects are the spine of any CRM; Salesforce ships them as standard objects with extensive customization options.

Sales Cloud: the pipeline side of CRM

Sales Cloud is the Salesforce product that handles the sales side of CRM: leads, accounts, contacts, opportunities, products, quotes, forecasts, sales activity tracking, sales process automation, and territory management. It is the original Salesforce product and remains the largest revenue contributor. Sales-Cloud-only is a common starting point for companies new to Salesforce.

Service Cloud: the support side of CRM

Service Cloud is the Salesforce product for customer service: case management, omni-channel routing, entitlements and SLAs, knowledge management, field service, and (in modern releases) AI-driven case deflection. It shares the Account and Contact objects with Sales Cloud, which is how the same customer record drives both pipeline and support views.

Marketing Cloud and Marketing Cloud Account Engagement

Salesforce sells two marketing products. Marketing Cloud Engagement (MCE) is the B2C-flavored email, journey, and channel orchestration platform. Marketing Cloud Account Engagement (formerly Pardot) is the B2B marketing automation tool. Both are connected to the Salesforce CRM through Marketing Cloud Connect and are part of the Customer 360 vision; both are also their own substantial platforms.

Beyond traditional CRM: Commerce, Data, Agentforce

Modern Salesforce CRM extends well beyond pipeline and service. Salesforce Commerce (B2B and B2C) is the e-commerce platform. Data Cloud is the customer data platform. Agentforce is the AI agent platform. Tableau is the analytics platform. These extensions reflect that customer data is needed everywhere a company touches a customer, not just in sales and service.

CRM vs ERP

CRM focuses on the customer-facing parts of a business: sales, service, marketing, commerce. ERP (Enterprise Resource Planning) focuses on the internal operations: finance, supply chain, HR, manufacturing. The two are complementary and usually deployed together. Salesforce is the dominant CRM; SAP, Oracle, and Microsoft Dynamics dominate ERP. Integration between CRM and ERP is a major architectural concern in any enterprise.

Why CRM keeps getting bigger

The CRM category has expanded continuously because the surface area of customer interaction grows. In the 1990s, CRM was a contact database. In the 2000s, it added pipeline and email integration. In the 2010s, it added marketing automation and case management. In the 2020s, it added commerce, AI, and unified data. Salesforce has tracked each expansion through product acquisitions (ExactTarget, Demandware, MuleSoft, Tableau, Slack) and organic development. The category will keep expanding as long as companies have new customer-facing touchpoints to manage.

§ 03

How to plan a Salesforce CRM implementation

A CRM implementation is a multi-quarter project. The technical setup is largely solved by Salesforce out of the box; the harder work is data migration, process design, and adoption.

  1. Define the CRM scope

    Pick which Salesforce clouds you will deploy and in what order. Sales Cloud first is the most common start for B2B; Service Cloud first is common for support-heavy organizations. Marketing and Commerce typically come later.

  2. Design the data model

    Customize Account, Contact, Lead, Opportunity, and Case with the fields your business needs. Resist the temptation to add hundreds of custom fields on day one; start with what reps actually populate.

  3. Migrate legacy customer data

    Export from spreadsheets, ACT, HubSpot, or whichever system you are leaving. Clean the data (deduplicate, standardize, enrich). Import through Data Loader or the Data Import Wizard. Validate counts and field values match the source.

  4. Configure sales and service processes

    Customize sales stages, validation rules, automation Flows, approval processes, and dashboards. The Salesforce defaults are starting points; every org modifies them.

  5. Train users and roll out

    User adoption is the biggest CRM failure mode. Train in cohorts, build internal champions, and tie usage to manager goals. Reps will not use CRM that does not save them time.

  6. Iterate post-launch

    The first 90 days surface every gap. Build a backlog of refinements and ship updates monthly. CRM implementations are never done; treat them as a continuous-improvement program.

Gotchas
  • Adoption is the failure mode, not technology. The Salesforce platform works; users not using it is the project killer.
  • Over-customization in year one creates maintenance debt forever. Add fields and automation as needed, not preemptively.
  • Data quality before migration matters more than CRM features. Bad data into a clean CRM is still bad data; the CRM cannot fix it.
  • Sales Cloud and Service Cloud share data but not processes. Configuring one cloud does not implicitly configure the other; budget accordingly.
  • Integration with ERP, marketing, and other systems is usually 30 to 50 percent of the implementation cost. Plan for it from day one.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Customer Relationship Management (CRM).

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What does CRM stand for?

Q2. What is Salesforce's position in the CRM market?

Q3. What's the core goal of CRM?

§

Discussion

Loading…

Loading discussion…