SAP CRM End of Maintenance 2027: Migration Paths and Data
SAP CRM 7.0 mainstream maintenance ends December 31, 2027. Technical extraction methods, data mapping challenges, and three real migration paths explained.
Planning a migration?
Get a free 30-min call with our engineers. We'll review your setup and map out a custom migration plan — no obligation.
Schedule a free call- 1,500+ migrations completed
- Zero downtime guaranteed
- Transparent, fixed pricing
- Project success responsibility
- Post-migration support included
SAP CRM End of Maintenance 2027: Migration Paths and Data
SAP CRM 7.0 (enhancement packages 2–4) mainstream maintenance ends December 31, 2027 (asug.com). After that date, a system without extended maintenance moves to customer-specific maintenance, where SAP no longer adapts the release to legal changes or new technologies (asug.com). Your system keeps running — SAP isn't remotely disabling anything — but you carry the risk. Optional extended maintenance is available through the end of 2030 at an additional fee (news.sap.com).
Migrating off SAP CRM is not a simple lift-and-shift. SAP CRM uses a highly specific, normalized data model built around Business Partners and 16-byte raw GUIDs. Moving this data to platforms like Salesforce, Microsoft Dynamics 365, or SAP Sales Cloud requires structural data translation, not just a flat-file export.
This guide covers the exact timeline, what changes at each maintenance stage, the extraction methods available for SAP CRM with throughput considerations, three real migration paths with a selection framework, and the data mapping challenges engineering teams must solve to maintain referential integrity in the target system.
For context on how data layer failures derail enterprise migrations, see Why ERP Migrations Fail at the Data Layer: 9 Core Patterns.
What Does the SAP CRM 2027 Deadline Actually Mean?
End of mainstream maintenance means that, after December 31, 2027, SAP CRM 7.0 on-premise moves to extended maintenance if you contract for it, or to customer-specific maintenance if you do not. In customer-specific maintenance you keep paying your annual support fee and keep many support features, but SAP no longer adapts the release to new or changed external requirements such as legal changes (asug.com). The platform does not shut down, but running a release that no longer keeps pace with legal and technical change creates compliance and security exposure.
Here's the maintenance timeline:
| Milestone | Date | What changes |
|---|---|---|
| Mainstream maintenance ends (EHP 2–4) | December 31, 2027 | Mainstream maintenance stops; you choose extended maintenance or move to customer-specific maintenance |
| Optional extended maintenance | January 1, 2028 – December 31, 2030 | A scope of support similar to mainstream, at a +2 percentage point premium on your maintenance basis |
| Customer-specific maintenance | After extended maintenance ends (or from 2028 if skipped) | Problem solving for known issues at unchanged fees; SAP no longer adapts the release to legal changes or new technologies |
If you do not opt for extended maintenance by the end of 2027, SAP moves you to customer-specific maintenance automatically (news.sap.com). SAP keeps solving known issues at unchanged fees, but the release no longer follows legal and technical change. That is an operational risk many enterprise compliance teams will not accept for long.
On an older enhancement package? SAP's 2027 date covers the latest three enhancement packages of SAP CRM 7.0 (support.sap.com). If you run an older one, check SAP Note 1648480 for its dates, because your system may already be past mainstream maintenance.
How Much Does SAP Extended Maintenance Cost?
Extended maintenance for SAP Business Suite 7 — which includes SAP CRM 7.0 — comes with a premium of two percentage points on the maintenance basis for all support offerings for the scope of SAP Business Suite 7 (support.sap.com). For example, if your support rate is 22% of license value, it becomes 24%, roughly a 9% increase on your annual maintenance invoice.
Extended maintenance runs from January 1, 2028 to the end of 2030 and requires a separate contract on top of your support agreement (asug.com).
Two structural constraints to understand:
- The premium is priced on the Business Suite 7 scope. SAP applies it to the maintenance basis for the scope of SAP Business Suite 7, so model the cost against your full Business Suite 7 basis, not just the CRM component. Confirm the exact basis with SAP before you budget.
- It is not automatic. You must actively contract for it. If you do nothing, customer-specific maintenance applies by default.
Compliance implications: SAP CRM houses business partners, service contracts, and interaction histories containing PII. Holding that data on a release that has left mainstream maintenance, measured against GDPR Article 32 (which requires "appropriate technical and organisational measures" to ensure security appropriate to the risk) and CCPA Section 1798.150 (which establishes private right of action for security breaches involving unprotected personal information) creates exposure. Once SAP stops adapting the release, demonstrating compliance with Article 32 to a supervisory authority becomes harder.
What Data Lives Inside SAP CRM 7.0?
Before evaluating migration paths, understand what you're moving. SAP CRM's data model has four major object categories: business partners, business transactions (the One Order framework), interaction history, and marketing attributes.
Business partners
A business partner (BP) is the central master-data object in SAP CRM. Every customer, contact, employee, and vendor is stored as a business partner, linked by a GUID that connects the partner to every transaction they participate in. A business partner record includes:
- General data: name, category, and other central data (stored in
BUT000), with addresses, identification numbers, and bank details in related tables - Roles: sold-to, ship-to, bill-to, employee, competitor, prospect (stored in
BUT100) - Relationships: links between partners ("is contact person of," "is ship-to party of"), stored in
BUT050andBUT051 - Classification and marketing attributes: industry sector, customer groupings, stored in the classification system (
KLAH,KSSK,AUSP) - Sales area data: sales org, distribution channel, division-specific pricing and shipping terms
Business transactions (the One Order framework)
SAP CRM stores all transactional data — opportunities, activities, service orders, contracts, leads, complaints — in a unified structure called the One Order framework. This is the most complex part of any SAP CRM migration. A single transaction's data is distributed across dozens of tables:
| Table | Content |
|---|---|
CRMD_ORDERADM_H |
Transaction header (GUID, type, dates, status) |
CRMD_ORDERADM_I |
Transaction items |
CRMD_PARTNER |
Partner functions (sold-to, contact, employee responsible) |
CRMD_ACTIVITY_H |
Activity-specific header data |
CRMD_OPPORT_H |
Opportunity-specific header data |
CRMD_BINREL / SRRELROLES |
Document flow — links between related transactions |
CRM_JEST |
Status of each transaction |
STXL |
Cluster table storing long texts (compressed, not directly readable) |
Each transaction links back to business partners through partner functions, and those links preserve the 360-degree customer view. The STXL cluster table is a frequent extraction failure point: its contents are stored in compressed binary format and cannot be read with a direct SELECT — they require the SAP text retrieval API (READ_TEXT function module) to decompress correctly.
Interaction history
The Interaction Center creates interaction records logging every customer touchpoint — calls, emails, chat sessions — and links them to the business transactions created during that interaction. This is typically the highest-volume data category and requires explicit scope decisions about retention depth before migration begins.
Marketing attributes
Customer segmentation data, campaign assignments, and target group memberships. These are stored relationally in the classification system — not as standard columns — in tables KLAH (class header), KSSK (object-class assignment), and AUSP (characteristic values). Because they are dynamic key-value pairs rather than fixed schema columns, they never map 1:1 to any target system and require a pivot transformation during migration.
Migration Path Selection Framework
Before evaluating each path in detail, the following framework identifies which path fits your environment. Apply these criteria in order:
| Condition | Recommended path |
|---|---|
| S/4HANA already deployed or on roadmap within 18 months; primary goal is consolidation | Path 1: S/4HANA Customer Management |
| S/4HANA not yet deployed; SAP ecosystem preferred; few Z-table extensions; Interaction Center customization is light | Path 2: SAP Sales/Service Cloud V2 |
| S/4HANA not in roadmap; Salesforce or Microsoft contract already in place; heavy IC customization that would require full rebuild regardless; total cost of SAP ecosystem exceeds non-SAP alternatives on 5-year basis | Path 3: Salesforce / Dynamics 365 / HubSpot |
| Heavy custom IC extensions (many Z-tables, BAdI-heavy), no S/4HANA deployment, no existing non-SAP contract | Evaluate Path 2 vs. Path 3 based on rebuild cost — both require full re-implementation of custom logic |
The number of custom Z-tables is a strong complexity signal. Heavily extended installations need a Z-table audit before any timeline or cost estimate is reliable — each table needs an individual disposition decision (migrate, archive, or discard).
Where Are SAP CRM Customers Migrating?
Path 1: SAP S/4HANA Customer Management
SAP S/4HANA Customer Management embeds CRM capabilities directly into the S/4HANA core, eliminating the middleware layer that connected SAP CRM to SAP ERP. It is one of SAP's two in-house routes, alongside SAP Sales Cloud and SAP Service Cloud Version 2.
The migration is a structural translation, not an upgrade. The One Order framework was redesigned in S/4HANA — data distributed across the normalized tables listed above gets restructured around S/4HANA's simplified data model. Every custom extension, every Z-table, and every enhancement built against the old model needs re-evaluation.
Known failure modes on this path: Customizations built against CRM WebUI and the CRMD namespace often have no direct equivalent in S/4HANA Customer Management. Functional gaps can exist — check that the CRM 7.0 features you use are available in your target S/4HANA release. Teams that migrate data before confirming functional parity often discover mid-project that target functionality requires a workaround or is unavailable entirely.
Trade-off: Preserves SAP investment and keeps CRM data on the same database as finance and logistics. Requires a running S/4HANA system as a prerequisite, and functional coverage may be narrower than what you use in SAP CRM 7.0.
Path 2: SAP Sales Cloud V2 or SAP Service Cloud V2
SAP Sales Cloud Version 2 and SAP Service Cloud Version 2 are SAP's cloud CRM products. They are separate products from SAP Cloud for Customer (V1), and SAP publishes transition tools for V1 customers (help.sap.com). The move from SAP CRM on-premise to V2 is a new implementation project with data migration, not a version upgrade.
SAP provides prepackaged integration flows in SAP Cloud Integration that replicate code lists and master data — organizational units, business partners, business partner relationships, product groups, and products — from SAP CRM to Version 2, one way only (help.sap.com). Transactional data such as opportunities, activities, and service orders is outside that integration, so plan a separate load for it.
Known failure modes on this path: Custom fields (Z-fields) from the CRM namespace require field-by-field mapping to V2's extension model. Marketing attributes stored in the classification system require pivot transformation before they can be loaded. Interaction Center customizations built on CRM WebUI do not transfer — they must be rebuilt following V2's Clean Core extension approach.
Trade-off: You stay in SAP's portfolio, with SAP-provided integration content. Custom extensions require rebuild, not migration.
For the comparable challenge in the SAP Commerce space, see SAP Hybris End of Life 2026: The Enterprise Migration Framework.
Path 3: Leave SAP — Salesforce, Dynamics 365, HubSpot
Many organizations use the 2027 deadline as the trigger to leave SAP's CRM ecosystem entirely. The most common non-SAP targets are Salesforce, Microsoft Dynamics 365 Sales, and HubSpot CRM.
This path requires a full data model translation:
| SAP CRM object | Source tables | Salesforce equivalent | Dynamics 365 equivalent |
|---|---|---|---|
| Business partner (organization) | BUT000, BUT100 |
Account | Account |
| Business partner (person) / Contact | BUT000, BUT100 |
Contact | Contact |
| BP relationships | BUT050, BUT051 |
Account Contact Roles / Related Accounts | Connections |
| Opportunity (One Order) | CRMD_ORDERADM_H, CRMD_OPPORT_H |
Opportunity | Opportunity |
| Activity (phone call, visit, task) | CRMD_ORDERADM_H, CRMD_ACTIVITY_H |
Task / Event | Phone Call / Appointment / Task |
| Service order | CRMD_ORDERADM_H + service-specific sets |
Case | Case |
| Marketing attributes | KLAH, KSSK, AUSP |
Custom fields or Campaign Member | Marketing List / Segments |
| Interaction record | CRMD_ORDERADM_H + IC sets |
Activity History | Activity |
| Long text / notes | STXL (cluster, compressed) |
Description / Note body | Description / Note |
Salesforce-specific considerations: Salesforce enforces a daily API request allocation that depends on edition and license count. For a multi-million-record SAP CRM instance, loading through Bulk API 2.0 (which processes records in jobs rather than individual calls) is essential, because single-record calls at that volume would exhaust the daily allocation. Salesforce data storage costs (additional storage billed per GB) also force explicit decisions about how much historical interaction data to migrate versus archive.
Dynamics 365 considerations: SAP's unified Business Partner model must be translated into Dynamics 365's distinct Account and Contact entities. As we detail in our SAP ECC to Dynamics 365 migration playbook, Dynamics 365 enforces strict relational integrity at the Dataverse layer — attempting to load Contact records referencing non-existent Account GUIDs will generate hard failures at import, not silent nulls. This means the migration sequence is strictly ordered: Accounts before Contacts, Contacts before Activities, Opportunities before opportunity-linked Activities.
The hard part across all non-SAP targets: SAP CRM's partner functions don't map to any other CRM's relationship model. A single opportunity in SAP CRM can have a sold-to party, a ship-to party, a bill-to party, an employee responsible, and a contact person — each stored as a partner function row in CRMD_PARTNER. Most target CRMs use a simpler owner + contact model. During migration, you must decide: which partner functions become primary object relationships, which become lookup fields, and which become metadata only. This decision is irreversible post-migration and must be made before the mapping is locked.
Extracting Data from SAP CRM
Getting data out of SAP CRM is non-trivial due to clustered tables, compressed text storage, and binary primary keys. You cannot run a SELECT * against the database and get usable data. The viable extraction methods, with their practical constraints:
OData via SAP NetWeaver Gateway
OData is the most structured method for extracting data from SAP CRM. By exposing SAP data as RESTful APIs via the NetWeaver Gateway, you extract Business Partners, Opportunities, and Activities in structured JSON or XML format, respecting the application-layer business logic, authorization checks, pagination, and delta-sync markers.
Throughput characteristics: OData calls through NetWeaver Gateway are synchronous and subject to application server work process limits. Throughput depends on payload size, server load, and network latency, so measure it on your own system during the sample migration. High-volume interaction history requires careful batching by date range or object type to avoid timeouts and work process saturation.
Our extraction preference is API > JSON > CSV because API extraction preserves data types, respects authorization boundaries, and supports incremental sync without file management overhead.
BAPIs and RFCs
Function modules accessed via Remote Function Calls (RFCs) are the traditional SAP integration method. Relevant modules include BAPI_BUPA_CENTRAL_GETDETAIL (Business Partner general data) and CRM_ORDER_READ (One Order transactions). These preserve business logic and return data in well-documented structures.
Throughput characteristics: Each RFC call is a synchronous round-trip to the SAP application server. Bulk historical extraction via RFC — particularly for CRM_ORDER_READ, which reconstructs an entire transaction object on each call — is slow at high volume. Parallelizing RFC calls across multiple work processes reduces this but increases application server load and risks dialog process exhaustion during business hours. RFC-based extraction is best suited for targeted data subsets or delta changes, not full historical dumps.
IDocs (Intermediate Documents)
IDocs are SAP's standard format for asynchronous data exchange. SAP's own integration with Sales Cloud Version 2 uses IDoc message types such as CRMXIF_PARTNER_SAVE_M for business partners, driven by change pointers (help.sap.com). The same mechanism can push data to external middleware or a staging database. IDocs suit capturing delta changes during parallel operation (before cutover) because change pointers record each change as it is saved.
Limitation: Parsing IDoc segment structures requires tooling that understands SAP's hierarchical segment model. Generic ETL tools without SAP-specific connectors will treat IDocs as raw XML without understanding the semantic relationships between segments. IDoc-based full extraction of historical data requires triggering mass output, which can generate very high volumes and stress outbound processing queues.
SAP BW Extractors
If you have an SAP BW system, some CRM data — such as activities, opportunities, and campaign data — may already be pre-extracted in a more accessible format. This can shortcut extraction for specific data domains and avoid application server load on the CRM system.
Limitation: BW extracts represent the data as it was modeled for reporting, not as it exists in the transactional system. Delta records may exist in BW that don't reflect current CRM system state if the BW load was not recent. Validate BW data against CRM source before treating it as the extraction of record.
Direct Database Extraction (Not Recommended)
Extracting directly from the underlying database (SAP HANA, Oracle, or MS SQL) is the fastest method for raw byte volume but produces unusable data in several critical areas:
STXLcluster table: Long texts are stored in compressed binary format. DirectSELECTreturns undecompressible binary blobs. Only theREAD_TEXTABAP function module decompresses these correctly.- RAW16 GUIDs: Primary keys across nearly all CRM tables are stored as 16-byte raw binary. Direct extraction returns binary strings that must be hex-converted before they can be used as join keys or external IDs.
- Authorization bypass: Direct DB extraction bypasses SAP's authorization layer entirely. Any field-level access restrictions, deletion flags, or archiving markers are ignored, potentially pulling data that the application layer would suppress.
Direct DB extraction is an option only when no application-layer access exists — for example, in disaster recovery scenarios — and always requires post-extraction transformation to handle the above issues.
Data Model Translation Challenges
Splitting the Business Partner
A Business Partner in SAP CRM is a centralized entity that can be a person, an organization, or a group. The BP's roles (from BUT100) dictate its function. Modern CRMs split this into separate entities: Accounts (organizations) and Contacts (people).
The migration logic requires querying BUT000 for the BP category field (category 1 = natural person, category 2 = organization, category 3 = group), then:
- Category 2 BPs → Accounts in the target system
- Category 1 BPs with an organizational relationship → both a Contact and an Account (linked)
- Category 1 BPs without an organizational relationship → Contact only (or Account, depending on business rules)
Relationship records in BUT050/BUT051 define which organization a person belongs to and must be used to link the resulting Contact to the correct Account. If these relationships are not migrated first, the Contact→Account linkage is lost and must be rebuilt manually.
Converting RAW16 GUIDs
SAP CRM uses 16-byte raw GUIDs as primary keys across almost all tables (for example, PARTNER_GUID on business partners and GUID on transaction headers). These binary strings are not natively readable or storable as standard text fields in target CRMs.
The conversion: apply a hex-encode function to each RAW16 value to produce a 32-character uppercase hexadecimal string (e.g., 4F3A9B2C1D7E8F0A4B5C6D7E8F9A0B1C). This string must be stored in a dedicated external ID field in the target CRM — not discarded — because it is the only mechanism for maintaining referential integrity between migrated records. When a migrated Activity needs to reference its parent Opportunity, the GUID is the join key. Without it, all parent-child relationships must be reconstructed from scratch.
Flattening Marketing Attributes
SAP CRM marketing attributes are stored as dynamic key-value pairs in the classification system: KLAH (class definitions), KSSK (object-to-class assignments), and AUSP (characteristic values). Because the attribute schema is not fixed, a BP with 12 marketing attributes has 12 rows in AUSP, not 12 columns in BUT000.
Migrating to a target CRM requires a pivot transformation: each unique characteristic becomes a field on the target Account or Contact object. If the attribute list is volatile (new attributes added frequently), consider replicating the key-value structure as a custom child object rather than pivoting to flat fields — otherwise each new attribute requires a schema change in the target system.
Reconstructing Document Flow
SAP CRM's document flow, stored as binary relations in CRMD_BINREL, links related transactions — an email activity linked to an opportunity, a service order linked to a service contract. This document flow must be reconstructed in the target system to preserve timeline coherence. The sequence dependency is strict: parent objects must exist in the target before child objects can reference them. Migration batch ordering must follow the document flow graph, not alphabetical or volume-based sequencing.
The STXL Long Text Problem
Long texts — notes, descriptions, activity summaries — are stored in the STXL cluster table in compressed format. Direct database extraction produces unreadable binary. Correct extraction requires calling the ABAP READ_TEXT function module with the correct text object, text ID, and language key for each record. This is a one-at-a-time operation that cannot be bulk-parallelized easily, and for installations with millions of activity records each carrying a text, this step alone can dominate extraction runtime.
Custom Z-Tables
Many SAP CRM installations have custom tables extending standard objects. Each needs an individual disposition decision:
| Disposition | When appropriate |
|---|---|
| Migrate | Data is actively referenced in business processes; target system has a logical home for it |
| Archive | Data is required for audit/legal retention but not day-to-day operation; move to cold storage |
| Discard | Data is obsolete, duplicated elsewhere, or outside retention requirements |
Z-tables with no clear target-system mapping are the most common cause of scope expansion and timeline extension in enterprise SAP CRM migrations. A Z-table audit — documenting each table, its record count, its last write date, and its business owner — should be completed before any timeline estimate is locked.
Timeline Estimation Methodology
Migration timelines depend on three variables: record volume, extraction throughput, and transformation complexity. A rough formula:
Estimated migration days = (Total records ÷ Sustainable throughput rate) + Transformation buffer + Validation time
Practical reference points:
- Source throughput: measure OData and RFC rates on your own system during the sample migration, because they depend on payload size, server load, and work process limits
- Target CRM load rate (Salesforce): use Bulk API 2.0 jobs and plan around your org's daily API allocation
- Target CRM load rate (Dynamics 365 Web API): Dataverse allows 6,000 requests per user in a five-minute window, 20 minutes of combined execution time, and 52 or more concurrent requests per web server by default (learn.microsoft.com)
Most migrations complete within 1–5 business days, depending on data volume, complexity, and API rate limits. For large, heavily customized instances, the Z-table audit and transformation build dominate the total timeline, and the data movement runs once the mapping is approved.
Two different clocks: The figures above describe the data migration — extracting from SAP CRM and loading into the target system. They do not describe the customer's replatform, rebuild, or implementation project, which is a separate and longer effort. We move the data; we do not rebuild the application. The bulk historical load runs on the working days before go-live while your users keep working in SAP CRM. Go-live is a Monday morning: SAP CRM is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and users log in to the new system that day. Start scoping at least 3–4 months before your internal go-live deadline to allow time for Z-table audit, mapping approval, and sample validation cycles.
For a detailed breakdown of the end-to-end migration process, see The Ultimate CRM Data Migration Checklist.
What to Validate Before You Commit to a Path
- Check your enhancement package. The 2027 date covers the latest three enhancement packages. If you run an older one, check SAP Note 1648480, because the urgency may be higher than you think.
- Run a Z-table audit. Count Z-tables in the CRM namespace, their record counts, and their last-modified dates. This is the most reliable predictor of migration complexity and cost.
- Confirm functional parity before committing to Path 1 or 2. Identify your top 20 CRM business processes and verify each has a supported equivalent in the target system before signing contracts.
- Decide what to migrate vs. archive. Closed opportunities from 2014 probably don't need to be in Salesforce. Interaction records older than your retention policy can go to cold storage. Record volume directly impacts throughput time and target-system storage costs.
- Map your integration landscape. SAP CRM connects to SAP ERP (via middleware or direct RFC), SAP BW, and often third-party systems via IDocs or web services. Each integration needs a plan for the target architecture before the CRM data migration begins — otherwise you migrate the CRM data and then discover the ERP integration is broken.
- Run a sample migration with real data. Synthetic test data does not expose real data quality issues — duplicate Business Partners, invalid GUIDs, missing relationship records, corrupted
STXLentries. Only real data surfaces real problems.
For related guidance on data migration planning, see What Data Should You Actually Migrate to Your New ERP?.
Getting the Data Migration Right
SAP CRM migrations are structurally harder than most CRM-to-CRM moves because of the One Order framework's complexity, GUID-based linking across dozens of tables, the multi-role Business Partner architecture, compressed cluster table storage, and deep integration with SAP ERP. Partner functions, document flow chains, STXL long texts, and interaction records all require translation logic that generic ETL tools don't provide out of the box — you either build that logic or work with a tool that already has it.
The technical risks are concentrated in four areas: the STXL decompression requirement, RAW16 GUID conversion and preservation, Z-table disposition decisions, and document flow sequencing in the target load. Organizations that underestimate any one of these typically discover it during a failed sample migration — which is recoverable — or after go-live, which is not.
ClonePartner has handled 1,500+ successful migrations. We are independently audited for SOC 2 Type II and ISO 27001, with GDPR, CCPA, and HIPAA safeguards in our data handling pipeline. Our commercial model is a fixed price per project starting at $500 — no hourly billing, no per-record metering, no change orders.
Frequently Asked Questions
- When does SAP CRM 7.0 end of maintenance happen?
- Mainstream maintenance for SAP CRM 7.0 (EHP 2–4) ends December 31, 2027. Optional extended maintenance runs through December 31, 2030 at a two-percentage-point premium on your maintenance basis. The 2027 date covers the latest three enhancement packages. If you run an older enhancement package, check SAP Note 1648480 for its dates.
- What replaces SAP CRM on-premise?
- SAP's own routes are customer management inside SAP S/4HANA and SAP Sales Cloud and SAP Service Cloud Version 2, for which SAP publishes master data integration from SAP CRM. Customers also move to Salesforce, Microsoft Dynamics 365, or HubSpot. The move to any of these is a reimplementation with data migration, not a version upgrade.
- How much does SAP extended maintenance cost after 2027?
- SAP charges a premium of two percentage points on the maintenance basis for all support offerings in the scope of SAP Business Suite 7. For example, a 22% support rate would become 24% — roughly a 9% increase on the annual invoice. Extended maintenance runs from January 1, 2028 to December 31, 2030.
- How long does an SAP CRM data migration take?
- The data migration itself — extracting from SAP CRM and loading into a target system — typically completes within 1–5 business days depending on data volume, complexity, and API rate limits. The broader replatform project (process redesign, integration rebuilds, UAT) is a separate effort measured in months.
- What is the difference between an SAP Business Partner and a Salesforce Account?
- SAP uses a unified Business Partner model that can represent a person, organization, or group based on assigned roles. Salesforce uses distinct Account (organization) and Contact (person) objects. During migration, the SAP BP must be evaluated by role and dynamically split into the correct target entities while maintaining the linkage between them.