SAP Rebrand Registry

Every name an SAP product has carried, when it carried it, and who says so. One source per period, at the precision the source actually gives.

Register Timeline Analysis Source & data

Search Sort

Family

Has a

How to read a date

Dates keep the precision of their source. Where only a year is documented, a year is what you see. No day is invented to make the table look tidy.

launched / announced / effective: The source names this date for this event.
in use by: The earliest date we can prove the name was in use. The real start may lie earlier, and usually does. Most of these come from SAP's annual reports, which appear once a year — a rename in April shows up in the following February at the earliest.

The three kinds of transition

Rename: The product carries on, the name changes. The only kind that feeds the statistics.
Assimilation: An acquired product takes the SAP prefix. Predictable enough that counting it would make bought-in families look restless. Measured separately, as time to SAP-ification.
Generation: A technology or generation change rather than a rebrand. Never counted.

What this is not

An independent research project with no connection to SAP. Product names and trademarks belong to SAP SE. No claim to completeness: a product is listed once its chain of names can be sourced, and several known chains are still missing their early years.