SAP Sales & Service Cloud Version 1 is running, customer relationships are being managed, sales processes are moving through, service cases are being handled. So why would anyone consider a transition right now, without any immediate pressure to act?
Anyone who wants to stay competitive in sales and service over the long term — and in today's market, that is no longer a luxury but an increasingly strategic necessity — is better off not investing their resources in a platform that is no longer evolving.
Two Product Generations, Two Different Approaches
One thing upfront: SAP Sales & Service Cloud V2 is not an upgrade of V1. It is a standalone product that SAP has built from scratch.
The fundamental difference lies in how individual requirements are handled. In V1, processes can be adapted directly within the solution — through configuration, but also through customer-specific developments that are deeply embedded in the system. Midsize companies have made extensive use of this over the years: whether customer-specific pricing logic with different conditions for different buyer groups, individual escalation and complaint processes in service, or the mapping of multi-level sales structures with field sales, inside sales, and key account teams — the flexibility of V1 was a genuine advantage for many companies.
V2 follows the Clean Core principle: the system core remains close to standard and therefore permanently update-ready. Individual requirements are no longer developed within the CRM system itself, but through separately developed extensions on the SAP Business Technology Platform (BTP) or with SAP Build — technically decoupled from the core. This is not a limitation, but a technical necessity: a clean data and process structure is the foundation that allows AI functions to operate reliably and efficiently within the system. It also brings a decisive practical advantage: when SAP advances V2, these extensions remain untouched. Updates go through without every single customization needing to be individually reviewed and reworked.
For companies where configuration layers have built up over many project years, a transition is also an opportunity to simplify: what is genuinely necessary business logic — and what has simply grown over time and is no longer needed?
V2 Is Evolving — V1 Is Not
What makes the transition strategically pressing for many companies is not the end of V1 — which remains productively usable for now. It is the direction of development: SAP is continuously expanding V2 with new functionality, while V1 is no longer receiving any significant updates. Companies that stay on V1 are working in a system that runs stably, but is increasingly falling behind the capabilities of V2.
This gap spans several areas. V2's user interface was rebuilt from scratch and is designed with mobile use firmly in mind — field sales staff can manage customer visits, opportunities, and service cases directly on their smartphones, without needing a separate app or working with cut-down views. Integrated analytics brings sales forecasts, pipeline reports, and service dashboards directly into the system, with no need to export data into separate tools. And the integration architecture toward SAP S/4HANA and external systems has been rebuilt on the basis of modern APIs — with tangible benefits for data consistency and long-term maintenance overhead.
The development momentum of V2 is most visible right now in the area of artificial intelligence. V1 has a supplementary AI add-on whose functional scope is no longer being extended. In V2, SAP is continuously and systematically expanding the embedded AI capabilities: account and opportunity summaries, AI-assisted lead management, automated email creation, intelligent next-step recommendations for sales, and Joule as an integrated AI assistant that brings these functions together.
For midsize B2B companies, this is not an abstract roadmap announcement. Sales staff often manage dozens of customers simultaneously. AI-powered summaries that automatically compile the most relevant developments on an account before a customer meeting can save meaningful time and reduce errors — without having to manually work through CRM notes, emails, and call logs first. In sales cycles with long decision timelines, intelligent next-step recommendations can help identify the right moment to reach out — or flag risks in an opportunity early.
What the Move to V2 Actually Involves
Because V2 is a standalone product, the transition involves implementation work again. That is no cause for concern — provided the project is approached in a structured way.
The processes currently mapped in V1 need to be assessed from a business perspective and rebuilt in V2. Three cases need to be distinguished:
Standard processes — sales and service processes already covered by the V2 standard — are configured in the new system. This is typically the largest share.
Individually adapted processes are either migrated to a suitable standard process or rebuilt as extensions. This is where the widest range of situations tends to arise: some V1 customizations reflect genuine business requirements; others have grown organically over time and are no longer needed.
Existing integrations and special requirements — such as connections to SAP S/4HANA, ERP systems like SAP Business One, or external systems — are reviewed separately and need to be redefined within the V2 architecture.
SAP provides tools for data migration, but a full 1:1 transfer is not possible for all objects. For transactional data in particular — such as leads and opportunities — it needs to be established during the inventory phase what can be migrated automatically and where an alternative strategy is required.
For companies that already use V1 in multiple countries and have further rollouts planned, it makes sense to start those directly on V2 — the processes defined there then form the global blueprint and avoid duplicate implementation effort.
PART Supports You on Both Sides
PART Business Solution has specialized in the process industry for over 30 years and supports midsize companies from the food, chemical, and cosmetics sectors on SAP projects. We work with existing customers on both product generations and have hands-on project experience in both worlds. Anyone implementing today starts directly on V2.
For a structured transition, we recommend the following approach:
If you'd like to understand where you stand today and what a transition would concretely mean for your company, get in touch. We'll take a first look at your V1 landscape together.
Is SAP Sales & Service Cloud V2 an upgrade of V1?
No. V2 is a standalone product that SAP has built from scratch. A technical migration is not possible — the transition requires a new implementation project in which existing processes are assessed from a business perspective and rebuilt in V2.
What happens to my individual customizations from V1?
V1 customizations cannot be carried over directly. During the transition, each customization is evaluated: can it be covered by a V2 standard process, does it need to be redeveloped as an extension on SAP BTP — or is it simply no longer needed?
Can my sales data (leads, opportunities) be transferred to V2?
SAP provides tools for data migration, but a full 1:1 transfer is not possible for all objects. For transactional data such as leads and opportunities in particular, the project needs to establish what can be migrated automatically and where an alternative approach is more appropriate.
When do I have to move from V1 to V2?
SAP has not yet communicated an official end-of-support date for V1. The strategic pressure to act comes less from a fixed deadline and more from the direction of development: new functionality — AI above all — is being developed exclusively for V2.
What is the Clean Core principle?
Clean Core means the V2 system core stays close to standard and therefore remains permanently update-ready. Individual requirements are not developed within the CRM core, but as separate extensions on SAP BTP or with SAP Build — technically decoupled. This ensures that SAP updates can be applied without every customization needing to be individually reviewed and reworked.
What AI capabilities does SAP Sales & Service Cloud V2 offer?
V2 includes embedded AI features such as automatic account and opportunity summaries, AI-assisted lead management, automated email creation, intelligent next-step recommendations for sales, and the AI assistant Joule, which brings these functions together. The functional scope is continuously being expanded.
We currently use V1 only in Germany — does it make sense to go live on V2 directly in other countries?
Yes. If further subsidiaries are still pending rollout, it makes sense to introduce them directly on V2. The processes built there form the global blueprint, which can subsequently replace the existing V1 installation as well — avoiding duplicate implementation effort.