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

SAP’s customer platform has gone through four distinct eras in about two decades. That’s a lot of name changes, acquisitions, and architectural pivots. I know it’s confusing. People at conferences still mix up C4C with C/4HANA, and half the SAP partners I talk to can’t explain where V2 actually came from.

But here’s the thing: each transition wasn’t just marketing renaming stuff. It was a fundamentally different way of building and running the software. If you’re sitting on an older version, knowing what changed (and why) is the only way to plan what comes next without burning money.

This guide walks through each phase. On-prem SAP CRM to cloud C4C, through the C/4HANA years, and into 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 didn’t appear overnight. It’s the result of two decades of migrating away from on-premises.

SAP CRM launched around 2000 as an on-prem application running on SAP NetWeaver. It covered sales, marketing, and service. Companies installed it on their own servers, customised it with ABAP, and upgraded manually. For its era, SAP CRM was proper good. It integrated natively with SAP ERP (R/3, later ECC), offered deep configuration, and could handle complex B2B sales processes that simpler CRMs couldn’t touch.

Then Salesforce showed up in 1999 and grew like wildfire. I remember the first time a prospect told me they were looking at Salesforce instead of SAP CRM. I thought they were joking. By the early 2010s, nobody was laughing. The market had moved decisively to SaaS. On-prem CRM meant slow upgrades, high maintenance costs, and limited mobile access. SAP needed a cloud answer. Fast.

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, and CRM was one of the first to make the leap.

SAP’s first cloud CRM was SAP Cloud for Customer (C4C), launched around 2013. It combined Cloud for Sales and Cloud for Service into one SaaS platform. The big shifts from on-prem CRM:

• Multi-tenant cloud: no on-prem servers to manage
• Quarterly updates delivered automatically by SAP
• Mobile-first design, built for phones and tablets
• Pre-built connectors to SAP ERP and third-party systems

C4C was a solid step forward. But it was still a first-generation cloud product. Customisation was limited, the extension model felt restrictive, and the architecture wasn’t designed for the side-by-side extension patterns that SAP BTP would later make possible. We implemented C4C for quite a few customers during this period. It worked. It wasn’t elegant.

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 had 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 was neat: a unified platform covering the entire customer lifecycle.

The reality was messier. These were separate products with different architectures, different data models, different extension frameworks. Integration between them required significant middleware work. The “suite” was, if we’re honest, more of a portfolio than a platform. I gave a talk at an SAP event around that time and called it “five products in a trench coat pretending to be a suite.” Got some nervous laughter from the SAP people in the audience.

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. Getting it wrong costs real money.

In 2020, SAP dropped the C/4HANA branding and consolidated under SAP CX (SAP Customer Experience). More importantly, they launched V2 versions of Sales Cloud and Service Cloud. And I want to be clear here: these are genuinely different products from C4C, not incremental upgrades.

SAP Sales Cloud V2 is not C4C with a fresh coat of paint. 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. We’ve seen partners who delivered 50 C4C projects struggle with V2 because everything under the hood is new. I’ve sat in rooms where experienced C4C consultants looked genuinely lost.

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 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. Don’t let anyone tell you it’s a quick project.

If you’re running C4C (V1): SAP has shifted all new development to V2. C4C still gets maintenance patches but no new features. Plan your migration sooner rather than later. Expect 3-6 months. The longer you wait, the wider the gap gets between what you have and what V2 can do.

If you’re evaluating SAP CX for the first time: Start with V2. There’s zero reason to implement C4C in 2026. V2 gives you modern architecture, BTP-based extensions, and Clean Core compatibility from day one. We won’t even quote C4C projects anymore. It doesn’t make sense.

FAQ

Is C4C the same as SAP Sales Cloud V1?

Yes. C4C (Cloud for Customer) is what people commonly call V1. SAP Sales Cloud V2 is the successor, but “successor” doesn’t quite capture it. It’s a completely different product with a new data model and extension framework. Same name, different system. De facto two separate products sharing a brand.

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. Expect 3-6 months.

Why did SAP drop the C/4HANA name?

Fair enough question. The C/4HANA branding confused people because it implied a single product rather than a suite. “SAP CX” is clearer: it’s a portfolio of customer experience products. The products themselves (Commerce Cloud, Sales Cloud V2, Service Cloud V2, Emarsys, CDP) remained largely the same. The name was the problem, not the products.

Is SAP CX only for SAP ERP customers?

No. SAP CX products work with any ERP through standard APIs. That said, integration is significantly easier with SAP S/4HANA thanks to pre-built BTP connectors. Non-SAP ERP customers should budget extra integration effort: typically 30-50% more. I’ve done both. The S/4HANA projects go noticeably smoother.

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

Depends on scope, but typical DACH-market ranges: CHF 150,000-400,000 for Sales Cloud V2 migration, covering data migration, configuration, integration, training, and go-live support. The investment pays back through lower maintenance costs, automatic updates, and modern functionality. And you stop paying for on-prem infrastructure, which adds up fast.