SAP CRM on-premise (SAP Customer Relationship Management, CRM 7.0 with Enhancement Packages 1–4) is the customer management platform running sales force automation, customer service, marketing campaign management, and partner channel management for thousands of large enterprises. SAP CRM is deeply integrated into the broader SAP landscape — it shares master data with SAP ECC or S/4HANA (customers, products, pricing conditions via SAP pricing procedures and Condition Technique), it runs interaction centre workflows integrated with SAP HR organisational structures, and its service management processes are tightly coupled with Plant Maintenance and Materials Management modules in the back-end ERP. This level of integration means that SAP CRM on-premise cannot be casually replaced with SAP Sales Cloud or Salesforce in a 12-month project without significant ERP re-integration work.
SAP's strategic direction is clear: SAP CRM on-premise is a legacy product. SAP no longer invests in new functionality for SAP CRM and is directing all CRM development investment into SAP Sales Cloud, SAP Service Cloud, and SAP Marketing Cloud — collectively SAP Customer Experience (CX), formerly C/4HANA. SAP's renewal conversations for SAP CRM maintenance increasingly include migration incentives, cloud subscription proposals, and pressure tactics designed to accelerate the transition to SAP CX. Third-party support on SAP CRM 7.0 cuts annual support costs by 50–65%, removes SAP's migration leverage, and gives you control of the timeline for any eventual CRM platform decision.
Running SAP? See how much you can save before your next renewal. Free analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
SAP CRM 7.0 (ECC-CRM integration generation) mainstream maintenance ended December 2025. SAP CRM 7.0 Enhancement Package 4 customers are now in extended maintenance, which carries a mandatory surcharge of 2–4% of your licence NLV on top of standard 22% maintenance fees. SAP has not published a definitive EOS date for SAP CRM 7.0 EHP4 beyond the extended maintenance window, but the commercial pressure to transition is significant and accelerating. For all SAP CRM organisations, the question is no longer if TPS makes sense — it is when to make the transition. See our SAP TPS complete guide for the strategic framework.
SAP CX Cloud Migration — The ERP Re-Integration Problem
SAP Sales Cloud, SAP Service Cloud, and SAP Marketing Cloud are cloud-native SaaS applications built on the SAP Business Technology Platform (BTP), with a fundamentally different integration architecture from SAP CRM on-premise. SAP CRM on-premise communicates with SAP ECC and S/4HANA via BDOC (Business Data Objects) and the CRM Middleware layer — a proprietary synchronisation engine that manages business partner, product, pricing, and transaction data flows between the CRM system and the ERP back-end. SAP CX does not use BDOC. SAP CX connects to SAP S/4HANA via SAP Integration Suite (formerly CPI/Cloud Platform Integration) using SOAP, REST, and OData APIs.
A SAP CRM to SAP Sales Cloud migration for a large manufacturer (5,000 users, 200+ pricing procedures, ECC materials management integration, field service management, IC agent workflows) requires: migrating all pricing condition types and access sequences to SAP Revenue Cloud or SAP Sales Cloud pricing; rebuilding all CRM service ticket workflows in SAP Service Cloud; recreating all IC agent scripts and interaction centre configurations; re-integrating with SAP ERP via BTP Integration Suite (replacing the CRM Middleware BDOC flows); migrating all opportunity management, pipeline reporting, and activity management data; and retraining 5,000 users on a fundamentally different UX paradigm. System integrator estimates for this scale of migration range from £1.5M–£5.5M with an 18–36 month timeline. GoVendorFree SAP TPS on the existing SAP CRM environment cuts annual costs immediately while you evaluate a CRM platform decision on your own commercial terms.
SAP CRM Version Matrix — TPS Eligibility
| Version | Key Features | SAP Support Status | TPS Available |
|---|---|---|---|
| SAP CRM 5.0 / 6.0 | Classic IC Web Client, foundational CRM functions | Customer-specific maintenance only | ✓ Yes — legacy TPS candidate |
| SAP CRM 7.0 (base) | Web Client UI, BOL/GenIL framework, CRM Middleware 7.0 | Customer-specific maintenance only | ✓ Yes — large TPS cohort |
| SAP CRM 7.0 EHP1 | Enhanced service orders, campaign management updates | Customer-specific maintenance only | ✓ Yes |
| SAP CRM 7.0 EHP2 | SAP Fiori integration introduction, extended IC functions | Extended maintenance (surcharge) | ✓ Yes |
| SAP CRM 7.0 EHP3 | Digital engagement, omnichannel service advisory | Extended maintenance (surcharge) | ✓ Yes |
| SAP CRM 7.0 EHP4 | Latest release — enhanced analytics, BTP preparatory features | Extended maintenance (surcharge) | ✓ Yes — primary TPS candidate |
GoVendorFree TPS Coverage for SAP CRM On-Premise
GoVendorFree's SAP TPS covers the full SAP CRM on-premise stack — the CRM application server, CRM Middleware, and the integration layer to SAP ECC or S/4HANA. Coverage includes:
- CRM Web Client UI and BOL/GenIL Framework: Web Client UI stability and performance; Business Object Layer (BOL) and Generic Interaction Layer (GenIL) configuration stability; custom component and view enhancement stability (BSP, ABAP OO); navigation bar profile configuration; view configuration and search help stability; CRM Web Client SSO and authorisation advisory
- Sales Force Automation: Opportunity management lifecycle stability; activity management (tasks, appointments, phone calls) workflow; pipeline reporting and forecasting stability; product and pricing determination (Condition Technique) via CRM pricing advisory; territory management and account/contact hierarchies; campaign integration and lead management workflow stability
- Service Management: Service order and service contract lifecycle stability; installed base and iObject management; spare parts management and service resource planning (SRP) advisory; interaction centre (IC) Web Client agent desktop stability; computer telephony integration (CTI) adapter advisory; email response management system (ERMS) workflow stability; complaint and returns management (CRM SD integration)
- CRM Middleware and ERP Integration: CRM Middleware adapter framework stability (R/3 Adapter, qRFC queues); BDOC synchronisation object stability (business partners, products, pricing conditions, orders); subscription monitoring and replication error handling advisory; SMOEAC business partner synchronisation advisory; CRM-ECC order replication stability; CRM Middleware performance and queue management
- Marketing and Campaign Management: Marketing plan and campaign stability; segment builder and marketing attributes advisory; campaign execution and communication medium stability; product recommendations (personalization engine) advisory; marketing analytics integration; customer retention management (loyalty management) stability
- Technical and BASIS Layer: SAP BASIS administration advisory for CRM-specific components; Java stack (SAP Web AS Java) stability for IC-specific Java components; ICM (Internet Communication Manager) configuration; transport and change management for CRM customising; ABAP performance advisory for CRM BOL queries and reports
Telco, Manufacturing, and Utilities — The SAP CRM TPS Primary Cohort
SAP CRM on-premise's dominant deployment cohorts in telecommunications, manufacturing, and utilities all have specific reasons why SAP CX migration is more complex than SAP's migration guides acknowledge.
In telecommunications, SAP CRM manages postpaid customer accounts, service contract lifecycle (SIM card activation to contract renewal to portability/churn management), billing dispute handling, and dealer/partner channel management. The integration between SAP CRM's service management and SAP ECC SD (billing via IS-T Telecommunications industry solution) creates a dependency chain that SAP Sales Cloud cannot replicate without a complete IS-T re-implementation. Telecoms SAP CRM customers typically have a 5–10 year horizon before an SAP CRM replacement is commercially feasible given the IS-T dependency. Our technology industry practice covers the telco-specific SAP CRM TPS framework.
In manufacturing, SAP CRM is the installed base management and service contract platform that connects field service engineers to plant equipment records via SAP Plant Maintenance (PM) integration. A manufacturing company with 200,000 installed base objects, 15,000 active service contracts, and field service resource scheduling running through SAP CRM Service Resource Planning (SRP) has a migration complexity that SAP's standard C/4HANA migration accelerators do not address. Our manufacturing practice covers the SAP CRM PM integration framework relevant to TPS decisions.
In utilities, SAP CRM manages customer master data and service connections that are tightly coupled with SAP IS-U (Industry Solution for Utilities) — the billing and meter management layer used by energy and water companies. SAP CRM-IS-U integration covers customer contact history, service disconnection workflows, meter reading dispute management, and prepayment account management. This IS-U coupling means that any SAP CRM replacement must also address IS-U integration continuity — a constraint that makes SAP CX migration a multi-year programme, not a standalone CRM replacement project.