From SAP CRM to SAP CX: How SAP's Customer Platform Evolved

SAP’s customer management platform has been through three major transitions over two decades. Understanding this history matters because it explains why SAP CX is architecturally different from what came before — and why organisations running older versions face real migration decisions.

This guide covers each phase of the evolution: from on-prem SAP CRM to cloud-based C4C, from the C/4HANA rebrand to today’s SAP CX suite with V2 products.

TL;DR: The global CRM market is valued at $112.91 billion in 2025 (Fortune Business Insights, 2025). SAP’s CRM platform evolved through four phases: on-prem SAP CRM (2000-2013), cloud-based C4C (2013-2018), C/4HANA suite (2018-2020), and today’s SAP CX with V2 products (2020-present). Each transition introduced a fundamentally different architecture. Organisations still running C4C or on-prem CRM face migration timelines that are now urgent.

What Was SAP CRM (2000-2013)?

SAP’s total cloud revenue reached EUR 17.14 billion in FY 2024, up 25% year-over-year (SAP News, 2025). That cloud revenue is the direct result of a two-decade migration away from on-premises.

SAP CRM launched around 2000 as an on-premises application running on the SAP NetWeaver platform. It covered sales, marketing, and service — the traditional CRM triangle. Companies installed it on their own servers, customised it with ABAP code, and upgraded it manually.

For its era, SAP CRM was capable. It integrated natively with SAP ERP (R/3, later ECC), offered deep configuration options, and handled complex B2B sales processes that simpler CRMs couldn’t.

The problem: cloud-native competitors like Salesforce launched in 1999 and grew rapidly. By the early 2010s, the market had shifted decisively toward SaaS. On-prem CRM meant slow upgrades, high maintenance costs, and limited mobile access. SAP needed a cloud answer.

What Changed with Cloud for Customer / C4C (2013-2018)?

Thirty per cent of organisations are now fully live on SAP S/4HANA Cloud Private Edition, up from 19% in 2024 (ERP Today, 2025). Cloud adoption is accelerating across all SAP products — CRM included.

SAP’s first cloud CRM response was SAP Cloud for Customer (C4C), launched around 2013. It combined Cloud for Sales and Cloud for Service into a single SaaS platform. Key changes from on-prem CRM:

• Multi-tenant cloud — no on-prem servers to manage
• Quarterly updates — delivered automatically by SAP
• Mobile-first — designed for phones and tablets, not just desktops
• Standard integrations — pre-built connectors to SAP ERP and third-party systems

C4C was a significant step forward. But it was still a first-generation cloud product. Customisation was limited, the extension model was restrictive, and the architecture wasn’t designed for the side-by-side extension patterns that SAP BTP would later enable.

What Was C/4HANA (2018-2020)?

In 2018, SAP rebranded its customer experience portfolio as C/4HANA — positioning it as the CX counterpart to S/4HANA. This wasn’t just a name change. SAP acquired Hybris (commerce), Gigya (identity), CallidusCloud (CPQ), and Emarsys (marketing automation) to build a complete CX suite.

C/4HANA grouped these acquisitions plus C4C into five “clouds”: Marketing Cloud, Commerce Cloud, Sales Cloud, Service Cloud, and Customer Data Cloud. The vision: a unified platform that covered the entire customer lifecycle.

The challenge: these were separate products, often with different architectures, different data models, and different extension frameworks. Integration between them required significant middleware work. The “suite” was more of a portfolio than a platform.

What Is SAP CX Today (2020-Present)?

Seventy-five per cent of ERP implementation projects get derailed (Gartner, 2024). The transition to SAP CX V2 products is one of the most significant architectural shifts in SAP’s customer portfolio — and getting it wrong is expensive.

In 2020, SAP dropped the C/4HANA branding and consolidated under SAP CX (SAP Customer Experience). More importantly, SAP launched V2 versions of Sales Cloud and Service Cloud — fundamentally different products from C4C.

SAP Sales Cloud V2 is not an upgrade of C4C. It’s a new product with a new data model, new extension framework (side-by-side via BTP), and new integration patterns (REST APIs, Event Mesh). Configuration options are broader. The extension model follows Clean Core principles.

SAP Service Cloud V2 follows the same pattern — rebuilt from the ground up with a modern architecture designed for BTP-based extensions.

SAP Commerce Cloud continues to evolve on its Hybris heritage but has moved fully to cloud with the Composable Storefront replacing the Accelerator-based approach.

SAP Emarsys handles marketing automation as a distinct product within the CX portfolio.

SAP CDP (Customer Data Platform) unifies customer profiles across all products.

What Does This Mean If You’re Running an Older Version?

Legacy SAP ECC and Business Suite usage has fallen below 50% for the first time (ERP Today, 2025). The same migration urgency applies to CRM products.

If you’re running on-prem SAP CRM: Your platform is end-of-life. SAP no longer releases feature updates. Migration to SAP CX V2 is necessary — and it’s a reimplementation, not an upgrade. Plan 6-12 months.

If you’re running C4C (V1): SAP has shifted investment to V2 products. C4C still receives maintenance but no major new features. Migration to V2 is recommended, and SAP provides migration tooling to help. Plan 3-6 months.

If you’re evaluating SAP CX for the first time: Start with V2. There’s no reason to implement C4C in 2025. V2 products offer modern architecture, BTP-based extensions, and Clean Core compatibility.

FAQ

Is C4C the same as SAP Sales Cloud V1?

Yes. C4C (Cloud for Customer) is commonly referred to as V1. SAP Sales Cloud V2 is the successor — a completely different product with a new data model and extension framework. They’re not the same system with a version number.

Can I migrate from C4C to V2 without losing data?

Yes, with proper planning. SAP provides migration tools that map C4C data structures to V2. Custom fields, workflows, and integrations need to be rebuilt for the V2 architecture. It’s a migration project, not a button click — typically 3-6 months.

Why did SAP drop the C/4HANA name?

SAP found that the C/4HANA branding created confusion — it implied a single product rather than a suite. “SAP CX” is clearer: it’s a portfolio of customer experience products. The underlying products (Commerce Cloud, Sales Cloud V2, Service Cloud V2, Emarsys, CDP) remained largely the same.

Is SAP CX only for SAP ERP customers?

No. SAP CX products work with any ERP through standard APIs. However, the integration is significantly easier with SAP S/4HANA through pre-built BTP connectors. Non-SAP ERP customers should budget additional integration effort — typically 30-50% more.

What’s the total cost of migrating from on-prem SAP CRM to SAP CX?

It depends on the scope, but typical DACH-market ranges: CHF 150,000-400,000 for Sales Cloud V2 migration, including data migration, configuration, integration, training, and go-live support. The investment pays back through lower maintenance costs, automatic updates, and modern functionality.