We moved a business-critical SAP BTP application suite off NEO and rebuilt its core on Cloud Foundry, CAP and HANA Cloud.
The challenge
InfraBuild’s EzyCommerce application was business-critical, but it was approaching end-of-life on SAP BTP NEO. SAP’s deprecation of the NEO environment meant the platform needed to move to Cloud Foundry, but the application was not a simple candidate for standard migration tooling.
The solution combined a Portal frontend with multiple UI5 applications, an XSA application accessing SAP HANA Enterprise, and a native Node.js/Express.js application integrated with SAP S/4HANA. Each layer had different runtime dependencies, authentication patterns, routing behaviours and data access methods. The challenge was to re-platform the whole application suite without losing functionality, data integrity or operational confidence.
What we did
Beta Digital designed a custom migration and modernisation approach for each layer of the application. The most significant architectural change was replacing the XSA data layer with a modern SAP Cloud Application Programming Model application running against SAP HANA Cloud.
The new CAP application took responsibility for schema creation, database artefacts and data access patterns. Existing HANA stored procedures were carefully integrated into the CAP model using Actions and Functions, preserving important business logic and performance characteristics while aligning the application with SAP’s recommended Cloud Foundry patterns.
We also reworked the security and routing model. Authentication flows, token handling and authorisation checks were adapted for Cloud Foundry and IAS, with Express.js middleware used where required to preserve expected behaviours. The UI5 and Portal layers were updated for the new service endpoints, request paths and authentication model, while the HANA Enterprise to HANA Cloud data migration was executed through staged validation and cutover activities.
What it delivered
InfraBuild gained a fully modernised application running on SAP BTP Cloud Foundry, with a contemporary CAP-based backend and SAP HANA Cloud data foundation. The project removed dependency on the retiring NEO runtime and positioned EzyCommerce for longer-term supportability, security and future enhancement.
Rather than simply moving the old architecture to a new runtime, the migration improved the application’s technical posture: clearer ownership of the data model, modern development patterns, stronger identity controls, and a platform foundation aligned to SAP’s current BTP direction.
The full measure of the engagement
Planning a similar engagement?
We help SAP customers on BTP, AWS, and beyond — across Apps and adjacent capabilities. If this story rhymes with something you're working through, we'd like to hear about it.