SAP C4C Guide: What It Was, What Replaced It, and What to Do Now

If you search for “SAP C4C” today, you are probably in one of two camps. Either you run C4C and wonder what comes next, or you have heard the name and want to know what it is.

The short answer: C4C still runs and SAP still maintains it, but its successor is SAP Sales Cloud V2 and SAP Service Cloud V2. V2 is not an upgrade with a new version number. It is a new product with a different codebase and data model, and that is where SAP puts its new CRM capabilities.

TL;DR: SAP C4C (Cloud for Customer) is SAP’s first-generation cloud CRM, launched in 2011. Its successors, Sales Cloud V2 and Service Cloud V2, are a complete rebuild on SAP BTP with REST APIs, a Fiori-based UI and Joule. C4C is still supported, and as of September 2026 SAP has not announced an end-of-maintenance date. If you run C4C, you can plan the move on your own schedule, but plan it as a reimplementation, not an upgrade.

What Was SAP C4C?

SAP Cloud for Customer (C4C) launched in 2011 as SAP’s first cloud CRM. It combined sales and service in one platform and went through several names:

• 2011: launched as SAP Cloud for Customer
• Mid-2010s: marketed as SAP Hybris Cloud for Customer
• 2018: positioned as SAP Sales Cloud and SAP Service Cloud within the C/4HANA suite
• From 2023: SAP introduced Sales Cloud V2 and Service Cloud V2 as successors; C4C is now often called “V1”

C4C brought SAP into the cloud CRM market. Over time, its architecture showed its age: APIs were added after the fact, the UI predated today’s Fiori design, and extensions had to live inside the application through the PDI/SDK. Things that should have been simple, such as a clean event-driven integration, often took workarounds.

What Replaced C4C and Why?

SAP decided to rebuild instead of patching. These are the changes that matter in practice.

API-first architecture. Every V2 business object is available through REST APIs, documented on the SAP Business Accelerator Hub. C4C had APIs too, but coverage was uneven. Integrations and automation are more predictable in V2.

Fiori-based UI. V2 follows SAP’s current design system. It is responsive, consistent across devices and easier to learn. Sales reps use it on their phones without extra apps. Our Sales Cloud V2 features and user handbook walks through what users actually work with day to day.

BTP-native extensions. V2 customisations run on SAP BTP as side-by-side extensions, keeping the core clean and upgradeable. In C4C, extensions lived inside the application, which made some customers wary of taking every release.

AI where SAP invests. C4C has some embedded AI, for example lead and opportunity scoring. The new generation, Joule and Joule agents, targets V2. Our hands-on Joule guide shows what works today.

A cleaner data model. Custom objects, fields and relationships are easier to manage than in C4C. The price: nothing maps one to one.

What Does C4C to V2 Migration Look Like?

It’s a migration, not an upgrade. There is no upgrade button. Core data (accounts, contacts, opportunities) moves with SAP’s Readiness Check and Data Transfer Tool; configuration, extensions and workflows are rebuilt. Our step-by-step DTT guide shows how the tool works.

Plan 3 to 6 months for sales. A focused migration (core CRM, data migration, basic reconfiguration) takes 3 to 4 months. Complex extensions, several integrations or a multi-country rollout push it beyond 6 months. A combined sales and service migration usually takes longer; our migration strategy guide breaks it into five phases.

Clean up before you migrate. Do not move bad data. Use the migration to remove duplicate accounts, incomplete contacts and inconsistent opportunity stages. Cleaning in C4C is much easier than cleaning after the import.

Phase the transition. Go live on V2 with the core features first, then move advanced configuration and extensions in a second phase. Trying to replicate 100% of C4C before launch is the most common cause of missed dates.

For a feature-by-feature comparison, see SAP Sales Cloud V2 vs. C4C: what actually changed.

What Can You Do with Sales Cloud V2 Today?

Pipeline and opportunity management. Configurable sales stages, weighted forecasts and required-field validation. Management sees the pipeline in real time instead of in a monthly spreadsheet. At Nussbaum Matzingen, full pipeline transparency was the main reason for the project; they went live on V2 in five months.

AI assistance with Joule. Natural-language queries, opportunity summaries, activity suggestions and email drafts, inside the V2 interface. Availability depends on your licence and release, so check the V2 documentation for your tenant.

Mobile access. The UI works on phones and tablets, so field reps can update an opportunity right after a meeting. At intelligentfood, we added mobile field-sales apps on BTP for visit planning.

ERP integration. SAP provides standard integration content between V2 and S/4HANA for accounts, products, prices and orders, typically run through SAP Integration Suite. It still needs mapping, error handling and monitoring. If you plan S/4HANA Public Cloud as well, read how the two work as an integrated stack.

Territory and quota management. Geographic, product-line and named-account territories with quota tracking.

What Should You Do If You’re Still on C4C?

Don’t panic, but don’t sit on it either. SAP still supports C4C, and as of September 2026 no end-of-maintenance date has been announced. But new capabilities go to V2, and the gap widens with every release. Check the SAP Roadmap Explorer for the features you depend on. One concrete deadline already exists: SAP Jam Collaboration, part of the V1 bundle, will no longer be accessible from 1 January 2027 (release briefing).

Assess your current setup. Document customisations, integrations and extensions. Decide what V2 covers through configuration and what needs rebuilding. Many C4C customisations turn out to be workarounds for platform limits that V2 has solved.

Start with a pilot. Move one team or one region first. Validate the process, train key users and build internal know-how before the full rollout.

Budget for data cleanup. Treat the migration as your chance to fix data quality. You will not get a better one.

Our V1-to-V2 comparison and the V1-to-V2 wizard help you size the move before you talk to anyone.

---

Need help planning your C4C to V2 migration? We will show you what is realistic for your timeline and setup. Get in touch.

Frequently Asked Questions

Is SAP still supporting C4C?

Yes. SAP still maintains C4C (Sales and Service Cloud V1) and ships regular releases, but new innovation such as Joule and Joule agents goes into V2. As of September 2026, SAP has not announced an end-of-maintenance date for C4C. Plan your migration proactively, on your own schedule, rather than waiting for a deadline.

Can I run C4C and V2 side by side during migration?

Yes, and we recommend it. A parallel period of several weeks lets you validate the V2 configuration, train users and compare data before cutover. Both systems can read master data from the same S/4HANA backend during that time.

What happens to my C4C customisations in V2?

They do not transfer directly. PDI/SDK extensions, mashups and workflow rules are rebuilt with V2 configuration or as side-by-side extensions on SAP BTP. Many turn out to be workarounds that V2 covers in standard, so the rebuild is often smaller than expected.

How much does a C4C to V2 migration cost?

It depends on custom objects, integrations, data volume and user count. A focused migration with core CRM, one ERP integration and clean data is far cheaper than a setup with many PDI extensions and interfaces. A discovery phase of 2 to 4 weeks gives you a reliable estimate. For licence costs, see our Sales Cloud V2 pricing guide.

What’s the difference between C4C, C/4HANA and SAP CX?

C4C (Cloud for Customer) was the product. C/4HANA was the 2018 suite name that grouped it with Commerce, Marketing and customer data products. SAP CX (Customer Experience) is today’s umbrella for SAP’s customer-facing cloud products, including Sales Cloud V2, Service Cloud V2, Commerce Cloud, SAP Engagement Cloud (formerly SAP Emarsys), the Customer Data Platform and SAP Customer Identity.