Farewell, Neo! SAP BTP, multi-cloud environment – the deployment environment of choice

[michael_ameling]

SAP's multi-cloud foundation for SAP Business Technology Platform (SAP BTP) has been the default development environment for new customers since 2020. It provides a choice of infrastructures, runtimes, and environments for SAP BTP services such as the Cloud Foundry environment, the Kyma environment, and the ABAP environment, available on all leading cloud infrastructure providers today. Due to these advantages, over 20,000 customers and partners have modernized to the cloud at their own pace and according to their own needs.

 

With this momentum, we are announcing today that the legacy Neo environment will sunset on December 31, 2028, subject to terms of customer or partner contracts.

 

Built on a proprietary technology stack and offered since 2012, the Neo environment is the oldest of the application environments offered by SAP BTP. Customers and partners have consistently told us that given the advances in cloud-native technologies and in particular rapid adoption of open source, the Neo environment no longer provides the best technological path forward for them in cloud or hybrid transformation journeys. We will continue to add security, availability, and compliance standards to protect customers' investments on the Neo environment. New features and innovations will only be added to the multi-cloud foundation for SAP BTP, which will continue to follow our 4+1 data center strategy. This includes core offerings like SAP Integration Suite, SAP Build, and SAP Datasphere.

What are the next steps for the existing customers?

Existing customer investments in the Neo environment and related services can remain in place until the sunset of the services on December 31, 2028. SAP intends to work with customers to help minimize the impact and will assist in their migration off the Neo environment. We will provide support for migrations including best practice documentation for migration projects and execution, and guidance to help lower migration costs.

Where can I learn more?

Please familiarize yourself with the multi-cloud environment for SAP BTP on the SAP Help Portal. You can find more information in the Neo sunset FAQ. If you have additional questions, please contact our migration experts.

[tmhew]

michael.ameling, will unified runtime be in multi-cloud environment to support the Neo migration?

 

[brunodelladucat]

Hi michael.ameling thank you for this information.

Is there a timetable for Neo customers to get migrated into the Cloud Foundry environment, initiated by SAP?
Or are Neo customers forced to plan the migration themselves?

Best Regards
Bruno

 

[kivancaktas]

Hi michael.ameling ,

Thanks a lot for updating the community.

IMO, SAP should re-consider to put all the important decommissioning/end of support topics on the same date, it is too early to talk now since we have 5 years, but I can't imagine the pressure in digital departments when they are approched to the deadline.

GRC Access Control 12 end of maintenance date is same (end of 2028) ->

https://blogs.sap.com/2023/05/09/grc-tuesdays-announcing-saps-plans-for-a-next-generation-governance...

Kind regards,

Kivanc

[former_member196507]

Hi Tauming Hew,

Thank you for the question. The term “unified runtime” describes our strategy, not a technical product as such. The strategic runtime(s) for SAP BTP are the Kyma runtime, the CF runtime, and the BTP ABAP environment.  These are all available in the multi-cloud environment as of today and are our recommended runtimes for CAP / RAP based applications on SAP BTP. 

Kind Regards,
Christian

[former_member196507]

Hi Bruno, thank you for the question. 

Customers can choose when and how they want to migrate to a multi-cloud environment for SAP BTP. This is not specified or determined by SAP. The sunset date at the end of 2028 provides you with more than 5 years to plan and execute your migration at a time that is appropriate for you and your solutions. 

From the SAP side, we are committed to help our customers in this journey. You can find more information in the FAQ and our migration guide. 

Kind Regards,
Christian

[former_member196507]

Hi Kivanc, 

Thank you for your suggestion.  

SAP selects the end of maintenance date for a product considering various factors, including the maintenance strategy for the specific product, when it was introduced, etc. We generally try to align these dates to the end of a quarter or, more commonly, the end of a year to minimize impacts on customers. We have a broad portfolio of products with different life cycles so it’s quite possible that dates may coincide.

Please notice that customers can choose when and how they want to migrate to a multi-cloud environment for SAP BTP. This is not specified or determined by SAP. The sunset date at the end of 2028 provides you with more than 5 years to plan and execute your migration at a time that is appropriate for you and your solutions. 

Kind Regards,
Christian

[RyanChamplin]

Also, the FAQ refers to a way to engage our SAP experts for support on the migration.  Here is a white paper that provides a little more detail on this: https://www.sap.com/documents/2023/04/58b4e49b-6c7e-0010-bca6-c68f7e60039b.html

Thanks,

Ryan

[Summitt12]

Thanks for updating the community

my understanding is Forms Adobe services still use Neo to connect to S4 system on RISE contract

Are their any plans to make this service work on CF

Thanis

[steffenschad]

Hello Manish,

Thank you for your question. Like our customers and partners, SAP will also move our own services and applications from SAP BTP, Neo environment to the strategic SAP BTP multi cloud environment. 

Kind regards, Steffen