CPEA or BTPEA at Your Next Renewal: What the Migration Actually Means

BTPEA is the strategic successor model for SAP BTP. But for many existing customers, the next renewal is not automatically the right time to migrate. The decision depends on concrete questions that need to be answered before the renewal window opens. This article gives you the criteria to assess your situation clearly.

---

Why the Model Choice Is More Than a Contract Formality

CPEA and BTPEA share the same fundamental logic: pre-purchased credit budget, flexible consumption across a defined service catalog, and monthly balance statements. The differences lie in service scope and deprecation policy.

CPEA offers a historically grown catalog of roughly 85 to 90 BTP services. That catalog is no longer being expanded. New services that SAP has developed since CPEA's introduction are exclusively accessible through BTPEA (source: ASUG, SAP Experts Detail New SAP BTP Enterprise Agreement).

BTPEA has been the strategic default model for new customers since 2024. It includes newer services, among them SAP Analytics Cloud and new AI services from the SAP AI portfolio. It also introduces a structured deprecation policy: services are classified into Group 1 (support guaranteed through contract end) and Group 2 (discontinuation possible with at least six months' notice).

This governance moment, the model choice itself, does not only determine the price per Capacity Unit. It determines which services you can access during the next contract term and how much governance overhead you are taking on.

---

Six Questions Before the Renewal

1. Which BTP Services Are You Actively Using Today?

This sounds like a straightforward question. In practice, it often is not. BTP subaccounts grow over years. Services get activated and never decommissioned. Entitlements exist that no one can map to an active workload anymore.

Before making a renewal decision, you need a complete inventory: which services are active in which subaccount, which ones are generating actual credit consumption, and which are enabled but seeing little or no use (shelfware)?

This inventory is the starting point for any model decision. Without it, you are negotiating on incomplete information.

2. Are All Services You Use Available in the BTPEA Catalog?

BTPEA removed low-adoption services from its catalog. If your processes depend on one of those services and it is not included in BTPEA, you have two options after migration: you continue running that service as a separate subscription, or you plan a migration to an alternative technology.

Both options create effort and cost that must factor into the decision. The SAP Discovery Center Service Catalog (discovery-center.cloud.sap) shows in real time which services are available under which model. That inventory belongs in every renewal preparation process.

3. Which BTPEA-Exclusive Services Are You Planning for the Next Term?

Consuming SAP Analytics Cloud through an enterprise agreement, deploying new AI services from the SAP AI portfolio, or using future innovation services: all of that is only possible through BTPEA.

If your platform strategy for the next three to five years is built on these services, that is a clear argument for migration. If your current CPEA coverage is sufficient and there is no immediate need for BTPEA-exclusive services, the pressure to act is lower.

This governance moment calls for an honest assessment: what do you actually plan to use, and what is merely on a technology wish list?

4. Which Services Fall Into Group 2 Under BTPEA?

BTPEA's deprecation policy is a structural feature that CPEA does not have in this form. Group 2 services can be removed from the catalog with at least six months' notice.

If you are running productive workloads on services that are classified as Group 2 under BTPEA, the new contract carries a deprecation risk that you will need to actively manage. That does not mean those services will be discontinued. It means you need to establish monitoring that alerts you promptly when an announcement comes.

This overhead is manageable if it is planned from the start. It becomes a problem when it is ignored.

5. How Do the Commercial Terms Compare?

This is the most sensitive governance moment: the terms in BTPEA may differ from your existing CPEA terms. Negotiation history, commitment level, and discount structure will all be renegotiated.

A fair comparison requires three elements: first, the credit price per Capacity Unit in both scenarios; second, total cost including any services that would need to continue as separate subscriptions; and third, the impact on your flexibility structure if your BTP consumption changes during the next term.

Anyone who does not fully work through these three elements is making a decision on incomplete information.

6. How Much Lead Time Do You Have Before Renewal?

This is often the most underestimated question. Renewal negotiations under time pressure produce worse outcomes, not because pressure is inherently bad, but because a well-founded model decision takes time: time for the service inventory, the deprecation review, the commercial comparison, and the negotiation itself.

A practical rule of thumb: for a structured renewal preparation at mid-sized BTP volumes, start at least four to six months before the renewal date. For larger portfolios with complex subaccount structures, six to nine months is a realistic lead time.

---

Decision Checklist: CPEA or BTPEA?

The matrix below summarizes the relevant criteria. It does not replace an individual analysis, but it provides a structured starting point.

Criterion	CPEA Remains the Right Choice	Migration to BTPEA Makes Sense
Service inventory	All services in use are covered by the CPEA catalog	Need for BTPEA-exclusive services (SAC, AI)
Forward planning	Stable service mix, no new SAP additions planned	New SAP AI services or SAC via EA planned
Deprecation risk	No productive workload on potential Group 2 services	Productive use of Group 2 services with monitoring capacity in place
Commercial comparison	CPEA terms are better or equivalent	BTPEA terms are comparable or better, overall picture is positive
Lead time	Less than four months until renewal	Sufficient lead time for a thorough analysis
Migration	Legacy services with no BTPEA equivalent in active use	All active services available in the BTPEA catalog

If the left column predominates: continuing with CPEA is a valid decision. SAP has not announced a discontinuation of the model. If the right column predominates, or if individual criteria send a clear signal (especially demand for SAC or AI services), the next renewal is the right governance moment for migration.

---

What the Migration Means Technically

A common misconception: migrating from CPEA to BTPEA involves a technical cutover with downtime and data migration. That is not the case.

The global account, all subaccounts, running services, and their configurations remain unchanged. The new commercial terms are activated on the existing global account (source: ASUG, SAP Experts Detail New SAP BTP Enterprise Agreement). What changes is the contractual framework, not the technical environment.

The effort is on the commercial and governance side: negotiating new terms, resolving service scope differences, integrating the deprecation policy into your monitoring, and defining internal accountability for the new requirements.

This work is manageable. But it should not be approached under time pressure or without a complete service inventory.

---

Four Governance Moments in Renewal Preparation

Renewal preparation is not a single conversation. It consists of several governance moments that involve different roles across the organization.

Usage: Before the renewal, analyze the consumption pattern of the past twelve months. Which services were used how heavily? Where did unplanned overconsumption occur? This data is the foundation for a realistic sizing of the new credit budget.

Entitlements: Which entitlements were activated but never used? Which services are configured in subaccounts that are no longer tied to an active project? Shelfware in the BTP context draws on the credit budget without delivering value in return. Renewal is the right time to clean up these items.

Infrastructure: If BTPEA is under consideration, which services fall into Group 2? Are productive workloads affected? Is deprecation monitoring in place in your organization to keep a continuous eye on this area?

Cost: How has the ACV of the BTP line item developed over the current contract term? Are there derived charges, costs that cannot be read directly from the contract documents? Renewal preparation is the point at which all cost items should be verified for accuracy before they go into the negotiation.

---

Conclusion

CPEA or BTPEA is not a question that can be answered in the abstract. It depends on your specific service inventory, your platform strategy, and the commercial terms available at the time of renewal.

One thing holds in every case: preparation does not begin two weeks before the renewal deadline. It begins with the service inventory, continues with the commercial comparison, and ends with a negotiating position grounded in complete information.

Those who approach these governance moments systematically make a reasoned decision. Those who leave it to time pressure decide on the basis of the default that SAP proposes.

---

Next Steps

If you want to understand how your current BTP contract model aligns with your actual usage, and which governance moments you should approach in a structured way before your next renewal, a contract review is a practical first step. In four weeks, you get clarity on your current contract situation and a solid basis for your decision.

Request a contract review | Go to the BTP FinOps Hub page

---

Further reading: CPEA vs. BTPEA: What You Need to Know About the Two Credit Models | Understanding Capacity Units and Depreciation Groups