For a manufacturer selling through distributors, or a consumer brand serving shoppers directly, the CRM holds far more than contact records. It carries the pipeline, open quotes, account hierarchies, customer service histories and the commitments that keep customers loyal. Changing the platform underneath all of that is a business decision, not a routine IT upgrade.
That's why the customers we speak to about moving from SAP Sales and Service Cloud Version 1 (V1, also known as SAP Cloud for Customer or C4C) to Version 2 (V2) nearly always open with the same three questions. Is this a reimplementation? Is it a data migration? And what will it cost in time and budget?
Our short answer: an SAP Sales and Service Cloud V1 to V2 transition usually sits somewhere between the two. How far it leans towards a rebuild depends on how heavily your V1 tenant has been customized, and that same factor drives most of the cost and timeline. This guide covers what changes between the platforms, how SAP's transition tools scope the work, the phases to plan for and the risks we see most often.
Neither, strictly. V2 is a separate, cloud-native product rather than an upgrade of V1, which is why SAP calls the move a transition. Processes are re-established in a new V2 tenant, custom code and integrations are rebuilt against V2's APIs, and SAP's Data Transfer tool carries supported business data and configuration across from V1.
A standard, lightly customized V1 tenant moves comparatively quickly. Tenants with many PDI (Partner Development Infrastructure) solutions, mashups and custom integrations take longer, because V2 has no PDI development. That logic is either replaced by standard V2 features or redesigned as a side-by-side extension on SAP Business Technology Platform (BTP).
Those customizations usually encode years of tailoring. In B2B, that tends to mean complex pricing, account hierarchies, partner channels and service agreements. In B2C, it is more often high-volume case handling, consumer data and consent rules, and warranty or loyalty processes. Understanding them early is the best single predictor of an accurate budget.
Expectations are rising for business buyers and consumers alike. In B2B, sales cycles are long, involve several stakeholders and depend on accurate account and opportunity data. Buyers are also doing more on their own. A Gartner survey published in June 2025 found that 61% of B2B buyers prefer an overall rep-free buying experience.
When sellers do get involved, consistency counts. The same Gartner research found that 69% of B2B buyers report inconsistencies between information on a supplier's website and what its sellers tell them. A CRM that keeps sales, service and back-office data aligned is a large part of closing that gap. Consumer brands face the same test with less room for error. In PwC's 2025 Customer Experience Survey, 29% of consumers said they had stopped using or buying from a brand because of a poor customer experience, online or in person. For B2C service teams handling high case volumes, that puts order, return and service history in one place near the top of the requirements list.
SAP positions V2 as the foundation for its AI-driven customer engagement, and SAP reports more than 30 AI capabilities across Sales and Service Cloud V2. SAP has not published an end-of-maintenance date for V1, so for most organizations this is a planned move rather than a forced one. That is an advantage: you can time it around your sales calendar instead of a deadline.
| Area | SAP Sales and Service Cloud V1 | SAP Sales and Service Cloud V2 | What it means for your business |
|---|---|---|---|
| Origins | Launched in 2011 as SAP Sales On Demand, later SAP Cloud for Customer | First rolled out in 2023 as a new product, not an upgrade | V2 is designed around how sales and service teams work today |
| Platform and updates | Established multi-tenant cloud stack | Cloud-native, microservices-based stack designed for near-zero-downtime updates | Less disruption for users at upgrade time and quicker access to new features |
| Extensibility | Key-user tools plus in-app custom development with PDI | Key-user tools in-app; custom logic built side-by-side on SAP BTP with the SAP Cloud Application Programming Model (CAP) or SAP Build; no PDI | Upgrades stay cleaner, but V1 custom code has to be redesigned rather than copied |
| APIs and integration | OData and SOAP APIs, usually orchestrated through SAP Integration Suite | API-first REST APIs, plus event notifications and API hooks | Interfaces to SAP S/4HANA, ERP, commerce and third-party systems need re-pointing or redesign, and can become more timely |
| User experience | Classic interface familiar to long-time users | Redesigned, workspace-based interface with a unified selling workspace, guided selling playbooks and global search | Sellers and service agents spend less time moving between screens, and new hires get productive sooner |
| AI | Machine-learning features, some as add-ons | Embedded AI such as lead scoring, account summaries, generative email drafts and case summaries | Sellers can prioritize deals and prepare for customer conversations faster, and service agents get up to speed on cases sooner |
| Analytics and data loads | Built-in reporting; Data Workbench for imports | Embedded SAP Analytics Cloud; Data Import and Export for manual loads | Reports and dashboards are rebuilt, which is a good moment to retire the ones nobody uses |
SAP gives you tools inside your V1 tenant so scope is based on evidence rather than guesswork. Used early, they turn "how big is this?" into a report that finance, sales and service leadership, and IT can all read before anyone commits budget.
The Readiness Check tool runs in your V1 tenant, summarizes what has been implemented there and helps you estimate the effort and time to move it. You'll need an administrator with the Transition Readiness Check work center view assigned. It reports, object by object, on:
Each item is marked as supported or not supported by the Data Transfer tool, and you can recalculate the results at any time or export them to Excel. Read "not supported" as a question, not a verdict. SAP extends object coverage with new releases, so check the roadmap before designing a workaround; the answer can shape your go-live timing.
The Data Transfer tool moves business data and configuration from V1 to V2 one object at a time. SAP's documentation lists three supported scenarios:
Single or phased go-live. Move everything at once, or move one business unit, brand, region or team at a time to limit disruption to customers and revenue.
Data and business configuration together, so settings arrive alongside the records that depend on them.
Extension fields, notes and attachments, once mapping is complete for each business object. This keeps the account history, contract details, service cases and customer context your teams rely on.
Once you know what share of your implementation the tool supports, you can build a time estimate the business can trust.
A transition follows the same disciplined phases as any implementation. SAP has also published an SAP Activate roadmap for SAP Sales Cloud V2 in the SAP Roadmap Viewer, which is a useful cross-check for your own plan.
| Phase | What happens | Why it matters to the business |
|---|---|---|
| Discovery and design | Walk through current V1 scenarios in V2, review Readiness Check results, and decide what to adopt as standard, rebuild or retire | Your chance to remove workarounds and align the CRM with how teams sell and serve today |
| Build | Configuration, integrations and extensions delivered in sprints, with a demo to the business after each one | Sales and service leaders shape the solution as it is built, so go-live holds fewer surprises |
| Test (SIT and UAT) | Two cycles of system integration testing, then user acceptance testing, covering every integration and business process | Protects quoting, order hand-off and case management before customers notice any change |
| Deploy | Move configuration, integrations and extensions to production, transfer data, and run business smoke tests | A controlled cutover that keeps daily selling and service running |
| Hypercare | An agreed period of dedicated support after go-live to stabilize the new environment | Builds user confidence and adoption, which is where the business value shows up |
Of the five, discovery is the phase teams are most tempted to compress, and the one that most decides whether V2 improves how you sell and serve or simply replicates V1 on a newer platform.
| Risk | Mitigation |
|---|---|
| Treating V2 as a like-for-like copy of V1 | Run fit-to-standard sessions in discovery and rebuild only the customizations that still earn their place |
| Underestimating integrations | Inventory every interface early and decide whether to adopt, adapt, redesign or retire each one, the pattern SAP recommends for integration transitions |
| Building a workaround for an object SAP is about to support | Check SAP's roadmap and release notes before building, and let the answer inform go-live timing |
| Low adoption after go-live | Involve sales, service and operations from discovery, train by role and plan a proper hypercare period |
You haven't yet run the Readiness Check in your V1 tenant.
Your V1 tenant carries a large number of PDI solutions or mashups.
Integrations with SAP S/4HANA, your ERP or your commerce platform are due for rework anyway.
Sales or service teams are asking for AI features that are available in V2.
A new business unit, region or channel is planned in the next 12 to 18 months.
Users rely on workarounds or reports they no longer trust.
Knack Systems implements SAP Sales Cloud V2 and SAP Service Cloud V2 & Field Service Management, and our Implementation & Integration services cover the transition end to end: CX solution architecture, back-end and third-party integration, and delivery through an implementation framework built on SAP Activate. Our team brings technical, functional and integration experts together.
We start from your Readiness Check results, translate them into effort, timeline and business impact, and plan a single or phased go-live around your sales calendar and seasonal peaks. Our published customer stories include an industrial manufacturer that modernized customer service on SAP Service Cloud V2, and a transportation equipment manufacturer running sales and quoting on SAP Sales Cloud V2 and SAP CPQ.
Do we have to move from SAP Sales and Service Cloud V1 to V2?
There is no forced deadline today: SAP has not published an end-of-maintenance date for V1. SAP does position V2 as the foundation for new capability, including AI. Most organizations benefit from assessing now, so they choose timing around their business calendar rather than reacting later.
Can some teams stay on V1 while others move to V2?
Yes. SAP's Data Transfer tool supports phased go-lives, so you can move one business unit, brand, region or team at a time. A phased approach lowers risk, but agree up front which system is the record for each account or customer during the overlap, and plan integrations for both.
Will our PDI extensions carry over to V2?
No. V2 does not support PDI development. Each piece of custom logic is either replaced by a standard V2 feature or key-user configuration, or rebuilt as a side-by-side extension on SAP BTP using CAP or SAP Build. The Readiness Check shows which PDI solutions and mashups you have, which is the starting point for that decision.
How long does a V1 to V2 transition take?
It depends mainly on customization. Lightly customized tenants move much faster than those with many PDI solutions, mashups and custom integrations. Run the Readiness Check first; once you know what share of the implementation the Data Transfer tool supports, a partner can give you a credible estimate.
What do we need to run the Readiness Check?
The tool runs in your existing V1 tenant. SAP's documentation says you need an administrator user with the Transition Readiness Check work center view assigned. From there you can recalculate objects for a current view and export results to Excel for your scoping workshops.
Sources