What SAP Sales Cloud V2 Can't Do Yet: An Honest Assessment

We are going to do something unusual for an SAP partner: tell you exactly where SAP Sales Cloud V2 falls short.

Not because we think V2 is a bad product. We implement it, we recommend it, and we have built our practice around it. But every CRM platform has gaps, and pretending otherwise is how trust gets destroyed. Clients figure out the limitations eventually — usually during implementation, when it’s too late to adjust expectations.

So here is the honest version. Every gap we cover below comes from real project experience. We include workarounds where they exist, SAP roadmap status where it’s public, and a frank assessment of who each limitation actually affects.

TL;DR: SAP Sales Cloud V2 is, in our view, the best enterprise CRM for organisations running SAP ERP. The native S/4HANA integration, the clean API-first architecture, and the speed of deployment are genuinely excellent. But it has real gaps: territory management maturity, CPQ integration depth, a smaller app ecosystem, fewer certified consultants, and offline capabilities that trail Dynamics 365. None of these are dealbreakers for most buyers — but you need to know about them before signing. We cover each one below with workarounds and roadmap context.

Why We’re Writing This

Search for “SAP Sales Cloud V2 limitations” and you’ll find almost nothing. Every SAP partner publishes glowing product pages. Analyst firms write balanced but surface-level overviews. Nobody publishes a dedicated, detailed, honest assessment of what the platform can’t do.

That’s a problem for buyers. If the only information available is promotional, how do you make a serious purchase decision? You end up discovering limitations during implementation — exactly when they’re most expensive to handle.

We’ve implemented V2 across manufacturing, professional services, and distribution. We’ve hit every limitation listed in this article first-hand. Some of them cost our clients time. Some required creative workarounds. A few were genuine project risks that we had to manage carefully.

You deserve to know all of this before you commit. Not after.

For the full product overview, see our SAP Sales Cloud V2 solution page. For how it compares to alternatives, see our analyses of V2 vs Salesforce, V2 vs Dynamics 365, and V2 vs HubSpot.

The Feature Gaps (Current as of Q1 2026)

Each limitation below includes: what’s missing, who it affects, workarounds if any, and SAP roadmap status where publicly known.

Territory Management Maturity

V2’s territory management is functional. You can define territories, assign accounts and sales reps, and use territory hierarchies. The basics are covered.

What it lacks is the depth that large, complex sales organisations need. Salesforce’s Enterprise Territory Management supports rule-based assignment, territory forecasting, territory-specific reporting, and multi-dimensional territory models (geography + product + industry simultaneously). V2’s model is simpler — largely geography-and-hierarchy based with less flexibility for overlapping territories or complex matrix structures.

Who it affects: Organisations with 200+ sales reps operating across multiple territory dimensions. A 30-person sales team? V2’s territory management is likely sufficient. A global enterprise with field reps, inside sales, and channel partners all covering overlapping territories? You’ll feel the limitations.

Workaround: Use BTP to build custom territory assignment logic. We’ve done this for a client with a three-dimensional territory model (geography, industry vertical, and account tier). The extension runs on SAP BTP and syncs assignments back to V2. It works, but it’s custom development — budget 3-4 weeks of effort.

Roadmap: SAP’s innovation roadmap includes territory management enhancements in their 2026 release cycles. The direction is toward rule-based assignment and tighter forecasting integration. No specific delivery date published.

Advanced CPQ Integration

SAP has its own CPQ product (SAP CPQ, formerly CallidusCloud). In the V1 era, CPQ integration with Sales Cloud was tight — embedded quote generation, synchronised product catalogs, seamless handoff from opportunity to quote.

V2’s CPQ integration exists but isn’t as deeply embedded. The integration works through APIs and pre-built connectors, but the in-context experience — starting a quote directly from within an opportunity, seeing quote status updates in real time, managing revisions without leaving Sales Cloud — is not as seamless as it was in V1 or as it is in Salesforce’s native CPQ.

Who it affects: Companies with complex product configurations, volume-based pricing, or multi-step approval workflows for quotes. If your sales process is “pick a product, set a price, send a PDF,” this limitation won’t bother you.

Workaround: The API-based integration works. It just requires more clicks. Some clients embed CPQ as a mashup within V2’s UI to reduce context switching. We’ve also seen clients use the SAP Integration Suite to build near-real-time sync between CPQ quote data and V2 opportunity fields. Functional, but not native-feeling.

Roadmap: SAP has signalled tighter CPQ-Sales Cloud V2 integration as a priority. The direction is toward an embedded quoting experience within V2. Incremental improvements have appeared in quarterly releases, but the fully embedded experience comparable to V1 is not yet delivered.

Marketing Automation

This one is straightforward: SAP Sales Cloud V2 does not include built-in marketing automation. No email campaigns, no journey orchestration, no lead nurturing workflows, no marketing analytics.

SAP’s answer is Emarsys — their dedicated marketing platform. It’s a good product with strong personalisation and omnichannel capabilities. But it’s a separate licence, a separate system, and a separate implementation. The integration between Emarsys and Sales Cloud V2 works, but it’s not “one platform” the way HubSpot’s marketing and CRM work together.

Who it affects: Marketing-first organisations that want a single platform for both marketing and sales. If your primary use case is marketing automation with CRM as a secondary need, this architecture creates friction.

Workaround: Licence Emarsys for marketing, or integrate a third-party marketing platform (Marketo, HubSpot Marketing Hub, Klaviyo) via API. The SAP Integration Suite simplifies the plumbing. Budget for the additional licence and the integration effort.

Roadmap: SAP’s strategy is a suite approach — best-of-breed products with pre-built integration. We don’t expect native marketing automation to appear inside Sales Cloud V2. The investment is going into tighter Emarsys integration instead.

App Ecosystem

Salesforce’s AppExchange has over 7,000 apps and components. You need a contract management add-on? There are twenty options. A data enrichment tool? Fifty. A specific industry vertical solution? Probably exists.

SAP’s BTP Marketplace is growing, but it’s smaller by an order of magnitude. The SAP Store and BTP partner solutions cover the major categories — document management, e-signature, data enrichment — but the long tail of niche, industry-specific, and workflow-specific apps is thinner.

Who it affects: Organisations that rely heavily on third-party add-ons to extend CRM functionality. If your CRM strategy depends on plugging in a dozen specialised tools from an app marketplace, V2’s ecosystem will feel limited compared to Salesforce.

Workaround: Build custom extensions on BTP. V2’s API-first architecture makes this cleaner than you might expect — the APIs are well-documented, the extension framework is modern, and BTP provides the runtime. But “build it” is inherently more expensive than “buy it from an app store.” For must-have integrations (e-signature, enrichment), pre-built connectors typically exist. For niche needs, plan for custom development.

Roadmap: SAP is actively growing the BTP partner ecosystem. The number of available solutions increases quarterly. But matching AppExchange’s breadth is a multi-year proposition. If a specific app is critical to your workflow, verify its availability before committing.

Talent Pool

There are far more certified Salesforce administrators and developers than certified SAP Sales Cloud V2 consultants. The Salesforce ecosystem has been building for twenty years. V2 is relatively new.

This has practical implications: hiring is harder, contractor rates are higher, and your dependence on your implementation partner is greater.

Who it affects: Everyone, to some degree. Large enterprises planning to bring CRM administration in-house feel this most acutely. Finding an in-house Salesforce admin is straightforward. Finding someone with deep V2 expertise requires more effort.

Workaround: Invest in training. SAP Learning Hub offers V2 certification paths. Partner with a consultancy (like us) that can provide ongoing managed services while you build internal capability. Some clients adopt a hybrid model: internal team handles day-to-day administration, partner handles complex configuration and extensions.

Roadmap: This is a market maturity issue, not a product issue. As V2 adoption grows, the talent pool will expand. SAP is investing in enablement programmes and partner certification. But realistically, closing the gap with Salesforce’s ecosystem will take years.

Reporting and Analytics

V2’s built-in analytics are solid. Dashboards, standard reports, pipeline analytics, and forecasting views cover the core sales management needs. The interactive charts and drill-down capabilities work well for day-to-day operations.

Where V2 falls short is advanced customisation. Salesforce’s reporting engine allows users to build highly custom reports with complex filters, cross-object joins, bucketing, and formula fields — all without leaving the platform. V2’s reporting is more structured: you work with pre-defined report types and have less flexibility to create ad-hoc analyses.

Who it affects: Organisations with power users who build complex, custom reports weekly. If your VP of Sales lives in Salesforce reports and has built fifty custom dashboards, V2’s reporting will feel constrained.

Workaround: SAP Analytics Cloud (SAC) is the answer for advanced analytics. It connects natively to V2 and provides the full business intelligence experience — custom calculations, blending data sources, predictive analytics, planning. The catch: it’s another licence and another tool. For quick, one-off analyses, exporting data and using Excel or a BI tool is common practice.

Roadmap: V2’s native reporting improves with each quarterly release. SAP is adding more customisation options and dashboard flexibility. But the strategic direction is to position SAC as the advanced analytics layer, not to replicate a full BI engine inside Sales Cloud.

Offline Capabilities

V2 offers a mobile app with basic offline support. You can view cached records and create new records offline. When connectivity returns, changes sync.

But it’s not yet at the level of Microsoft Dynamics 365’s offline capabilities, which support more complex offline workflows — including relationship hierarchies, custom forms, and offline-aware business logic. For field sales teams working in areas with unreliable connectivity (construction sites, remote regions, manufacturing floors), the difference matters.

Who it affects: Field sales organisations where reps spend significant time in low-connectivity environments. If your team sells from an office or visits clients in urban areas, this is unlikely to be an issue.

Workaround: Ensure critical data is cached before going to the field. Some clients build lightweight companion apps on BTP or use mobile-optimised web apps that cache more aggressively. Not ideal, but functional for specific workflows.

Roadmap: SAP has committed to improving mobile offline capabilities. Quarterly releases have expanded the scope of what works offline. The trajectory is positive, but parity with Dynamics 365’s offline depth is not yet achieved.

Complex Approval Workflows

V2’s workflow engine handles standard approval scenarios: opportunity approval, discount approval, quote approval with single or multi-step routing. For straightforward processes, it works fine.

Complex scenarios — parallel approvals with conditional routing, escalation chains with SLA enforcement, approval workflows that span multiple objects or involve external system calls — push beyond what the built-in engine supports cleanly.

Who it affects: Organisations with heavily regulated or multi-layered approval processes. Pharmaceutical sales, government contracting, financial services with compliance-driven approval chains.

Workaround: Extend with BTP. SAP Build Process Automation (formerly SAP Workflow Management) handles complex multi-step approval processes and integrates with V2 via API. We’ve built approval workflows that route through three levels of management with conditional logic, SLA tracking, and escalation to compliance officers. It works well — but it’s a BTP extension, not a configuration in V2.

Roadmap: V2’s workflow capabilities expand with each release. The built-in rule engine is becoming more flexible. But for the most complex approval scenarios, BTP extensions will likely remain the recommended approach. SAP’s architecture favours extensibility over monolithic feature accumulation.

The Integration Gaps

Non-SAP ERP Integration

V2’s native integration with S/4HANA is genuinely excellent — real-time data synchronisation, pre-built business processes, shared master data. It’s the single biggest technical advantage V2 holds over every competitor.

But if you run Oracle, Microsoft Dynamics, Infor, or any other non-SAP ERP, that native integration doesn’t apply. You’ll need middleware: SAP Integration Suite, MuleSoft, Boomi, or a custom integration layer. The integration is absolutely doable — these are well-trodden paths — but the cost, complexity, and maintenance overhead are real.

Who it affects: Organisations running non-SAP ERP systems. If you’re on Oracle E-Business Suite or Microsoft Dynamics 365 Finance & Operations, integrating with V2 requires the same middleware effort as integrating any other CRM. You don’t get the “native SAP advantage.”

Workaround: SAP Integration Suite provides pre-built integration flows for many common ERP systems. Third-party iPaaS platforms (MuleSoft, Boomi, Workato) also work. Budget for integration design, development, testing, and ongoing maintenance. For a non-SAP ERP integration, expect 4-8 weeks of additional effort depending on the complexity of your data model and business processes.

Roadmap: SAP Integration Suite continues to expand its library of pre-built connectors. But native-level integration with non-SAP ERPs is not on the horizon. The architectural advantage of SAP-to-SAP will remain.

Third-Party Connector Ecosystem

Related to the app ecosystem point above: the number of pre-built connectors for third-party tools is smaller than what Salesforce or HubSpot offer. Need to connect V2 to a niche industry tool, a specific project management platform, or a regional payment provider? You may need to build the connector yourself.

The mainstream tools are covered — DocuSign, Microsoft 365, Google Workspace, LinkedIn Sales Navigator, major data enrichment providers. But the long tail of integrations requires more custom work.

Who it affects: Organisations with diverse tech stacks that include specialised or niche tools. The more standard your tech stack, the less this matters.

Workaround: V2’s REST APIs are clean and well-documented. Building custom integrations is straightforward for a competent development team. SAP Integration Suite reduces the plumbing work. For truly niche integrations, expect to build and maintain them yourself.

What’s on SAP’s Roadmap

SAP publishes an innovation roadmap for Sales Cloud that’s updated regularly. Here’s what we know as of Q1 2026:

Quarterly release cadence. V2 receives feature updates every quarter. Each release has brought meaningful improvements — not just minor patches. The pace of development is faster than what V1 ever had.

Joule AI expansion. SAP is investing heavily in Joule, their AI assistant integrated into V2. Current capabilities include natural language queries, opportunity summaries, activity suggestions, and email drafting. The roadmap includes deeper analytics, predictive pipeline scoring, and autonomous workflow execution. We wrote a detailed hands-on guide for Joule based on real project experience.

Improved customisation tools. SAP is expanding the no-code/low-code customisation capabilities — more flexible page layouts, richer workflow rules, and easier extension development. The direction is to reduce the need for BTP extensions for common customisation scenarios.

Enhanced mobile experience. Each release improves mobile capabilities, including offline support. The investment signals that SAP recognises the gap.

Partner ecosystem growth. SAP is actively recruiting ISV partners to build on BTP and publish solutions in the SAP Store. Expect the ecosystem to grow, but not to match AppExchange scale in the near term.

When V2 Is Still the Right Choice (Despite These Gaps)

We recommend V2 to most of our clients, full stop. Here’s why these limitations don’t change that recommendation for most buyers:

You run SAP ERP. The native S/4HANA integration alone justifies the choice. No other CRM connects as deeply, as reliably, or as cost-effectively to SAP ERP. The integration cost savings versus a third-party CRM with middleware are $20K-$50K per year for a mid-size deployment. We’ve broken down the full cost picture in our V2 pricing guide.

You’re deploying CRM for the first time. Greenfield implementations are V2’s sweet spot. No legacy data models to accommodate, no V1 migration complexity, no ingrained user habits to retrain. V2’s modern architecture shines when you’re building from scratch.

You need fast time to value. V2 implementations are typically faster than Salesforce enterprise deployments. The pre-built sales processes, standard data model, and guided configuration reduce the design phase. We regularly deliver initial go-lives in 8-12 weeks.

You’re planning to stay in the SAP ecosystem. If your IT strategy includes S/4HANA, BTP, Emarsys, Service Cloud, or CDP, V2 becomes the CRM hub. Cross-product integration improves with every release, and the total cost of ownership drops as you consolidate.

When You Might Want Something Else

Honesty means admitting when V2 isn’t the best fit.

You run a non-SAP ERP with no plans to change. Without the native integration advantage, V2 competes on features alone. It’s still a good CRM — but the decisive advantage is gone. Evaluate it alongside Salesforce, Dynamics 365, and HubSpot on feature merit and total cost. See our comparison with Dynamics 365 for details.

You’re a marketing-first organisation. If marketing automation is your primary use case and CRM is secondary, a platform like HubSpot — where marketing and CRM are deeply unified — may serve you better. V2 plus Emarsys is architecturally capable but operationally more complex. Our V2 vs HubSpot comparison covers this in depth.

You depend on a massive app ecosystem. If your CRM strategy requires plugging in a dozen specialised third-party tools, Salesforce’s AppExchange gives you options that BTP can’t match today.

You have field teams in consistently offline environments. If offline-first mobile CRM is non-negotiable, Dynamics 365 currently offers more robust offline capabilities. This gap is closing, but it hasn’t closed yet.

Frequently Asked Questions

Is SAP Sales Cloud V2 ready for enterprise use?

Yes. V2 is in production at thousands of organisations globally, including large enterprises. The platform is stable, performant, and receives quarterly feature updates. The limitations in this article are real, but they don’t make V2 immature — they make it a product that’s still evolving in specific areas. Every enterprise CRM has a similar list.

Is V2 better than V1?

In almost every respect. V2 is faster, has a cleaner UI, better APIs, a more modern architecture, and a faster release cadence. The migration from V1 to V2 requires planning — the data models differ and some V1 customisations need reworking — but the end result is a better platform. We’ve written a detailed guide on the V1 to V2 migration.

Should I wait for V2 to mature before migrating from V1?

No. V2 is mature enough for production use today, and SAP has signalled that V1 will enter maintenance mode. Waiting only accumulates technical debt on V1 and delays the benefits of V2’s modern architecture. Start planning now, migrate in phases if needed, but don’t defer indefinitely.

What features is SAP adding to V2 next?

SAP’s public roadmap points to territory management enhancements, deeper Joule AI capabilities, improved mobile offline support, and expanded CPQ integration. Exact delivery dates vary — check the SAP Road Map Explorer for the latest.

Can I migrate to V2 gradually, or is it all-or-nothing?

SAP supports phased migration. You can run V1 and V2 in parallel during the transition, migrating teams or regions incrementally. This is the approach we recommend for most organisations — it reduces risk and allows user adoption to happen naturally.

How do V2’s limitations compare to Salesforce’s limitations?

Every platform has gaps. Salesforce’s limitations include significantly higher total cost of ownership, complex pricing with expensive add-ons, native SAP integration that requires expensive middleware, and an overwhelming configuration surface that demands specialised admin staff. V2’s limitations are different in character, not necessarily worse. The right choice depends on your specific priorities and existing technology stack.

Our Commitment

We’ll update this article as V2 evolves. When SAP ships a feature that addresses one of these gaps, we’ll note it. When we encounter new limitations in project work, we’ll add them.

Honest assessment isn’t anti-SAP. It’s pro-client. The best purchase decisions happen when buyers have complete information — not just the marketing version.

If you want to discuss how these limitations would affect your specific situation, [talk to us](/en/contact/?topic=SAP Sales Cloud V2&message=I read your honest assessment of V2 limitations and would like to discuss how they apply to our situation.). We’ll give you the same candour in person that we’ve given here.