SAP BTP's Neo environment is set to reach end of availability on December 31, 2028. But knowing the date does not answer the question that matters: what do you have running on Neo today, and what do you need to do about it?
SAP Basis specialists · RISE/ECS experience · 15+ years of SAP experience
In organizations that have used BTP for years, there can be applications, services, integrations and components deployed on Neo whose criticality is not always clear: some are still in active use, others depend on production systems, and others may have been effectively forgotten.
Before you define a migration, you need to understand your exposure.
SAP has confirmed that the Neo environment of SAP BTP will sunset on December 31, 2028, subject to the contract terms of each customer or partner. No renewals or extensions beyond that date will be approved. Until then, SAP will keep delivering security and compliance updates for Neo, but new features and innovation will only land in the multi-cloud foundation for SAP BTP (Cloud Foundry, Kyma and ABAP), which has been the default for new customers since 2020.
The products most affected are those running SAP Integration Suite, SAP Build or SAP Datasphere on Neo. As part of the transition, SAP offers best-practice documentation, guidance to help minimize migration costs, and, for its partners, a free migration assessment service.
Waiting until Neo becomes an urgency narrows your alternatives and forces projects that may need coordination across applications, integrations and the business, all at once. Understanding your current scenario early turns an end-of-service date into a plan instead of an emergency.
Let's talk about your current scenario and what you need to understand before deciding what comes next.