Neo is Dead, Long Live Cloud Foundry!

• SAP will sunset SAP Cloud Integration Neo-type tenants by the end of 2028.
• An alternative is available--Multi-Cloud Foundation (Cloud Foundry) tenants.
• Hosted on AWS and Azure, these tenants offer better performance, reduced latency, and enhanced tools like API Manager, Trading Partner Manager, and Integration Advisor.
• Migration from Neo to Cloud Foundry is not automatic and must be managed by the customer—or with the help of a trusted partner like VASS.

More than a year ago, SAP announced that Neo tenants would be phased out by the end of 2028. Although 2029 seems distant, delaying action could lead to significant disruptions, as integration processes will cease to function. Moreover, the migration process is more complex than it might initially appear.

Background

Since 2012, SAP has hosted its SAP BTP (formerly SAP Cloud Platform) on proprietary hardware and technology, with Neo tenants serving as the backbone for its popular integration platform, SAP Cloud Integration (CI). However, starting in 2020, SAP introduced the Multi-Cloud Foundation, allowing BTP to be hosted on third-party servers like AWS and Azure. This shift provided clients with access to better hardware and a more dynamic technology stack. SAP has now deemed Neo outdated, making Multi-Cloud Foundation (Cloud Foundry) the recommended alternative.

Differences Between Neo and Multi-Cloud Foundation

SAP provides a detailed overview of the benefits of migrating to Multi-Cloud Foundation:

Find the full table here: https://help.sap.com/docs/btp/migrating-from-neo-environment-to-multi-cloud-foundation-cloud-foundry-and-kyma/why-you-should-migrate-from-neo-environment-to-multi-cloud-foundation

In short, Cloud Foundry CI environments provide better performance, support more languages and runtimes, and offer advanced tools in the Integration Suite, such as:

• API Management: Manages APIs, allows bundling, adds routing/access control, and enables API monetization. It also enhances authorization and routing for complex integration scenarios.
• Trading Partner Management and Integration Advisor: SAP’s initial AI-driven integration tools. Though still developing, they offer promising mapping tools for complex integration scenarios.

The user experience remains consistent between Neo and Multi-Cloud Foundation tenants, meaning no additional training is needed for your Cloud Integration teams.

Next Steps and Migration

SAP does not offer an automatic migration solution, leaving the responsibility to customers. Since Cloud Integration is central to many client landscapes, the migration process will likely involve more than just moving content. It may require changes to server certificates, authorization setups, and Cloud Connector configurations, necessitating collaboration across various teams.

SAP provides a Postman collection to assist with migration, but it has technical issues and complexities, making it suitable only for larger migration projects with over 20-30 integration flows .

Although the deadline seems far off, planning should begin now to avoid future disruptions. For questions or migration estimates, please contact us here

Happy Migrations!