Platform migration
Moving an application, an integration or a database off an older SAP platform (SAP HANA XS Classic or XS Advanced, the SAP BTP Neo environment, SAP Process Orchestration, SAP IQ) onto the platform SAP's own migration guides and tools lead to. The work has the same shape each time: assess what exists, convert what a tool can convert, and rewrite what will not carry over. Moving ABAP code into the ABAP Cloud language subset is ABAP Cloud readinessABAP Cloud readinessWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.SAP and community, unassessed, not this.
Overview
SAP publishes the move of Java applications from the Neo environment to Cloud Foundry as a guide with sample applications: upgrade to Jakarta EE 10, replace the Neo Java Web API, which Cloud Foundry does not provide, with SAP Cloud SDK dependencies, set up authentication and authorization again, and redeploy as a multitarget application.
Not covered: At guidance. There is no converter for Neo applications, and each Neo service an application uses, among them destinations, connectivity, mail, the keystore and persistence, is a separate scenario to rework by hand.
SAP's own answers on this door are guides, utilities and a workshop in SAP-samples, which demonstrate and are not a presence themselves, so the core reads from the guide's content. No help.sap.com page was checked for the Neo guide; it rests on SAP's repository.
AWS's Modernization Agents for SAP on AWSModernization Agents for SAP on AWSAWS's suite of agents for SAP modernisation work: custom ABAP converted for S/4HANA, PI/PO interfaces moved to Integration Suite, BW objects moved to SAP Datasphere, deployed into a customer's own AWS account and reached only after registration.partner, abap are a partner kind of answer: AI agents deployed into a customer's AWS account that carry PI/PO interfaces to SAP Integration Suite and BW objects to SAP Datasphere, with a gated repository behind registration.
Artifacts
Content
Show 8 more
Seen working
Directed at single-tenant applications, which the guide states as its scope. Migration of the whole delivery unit or package fails if any source file has errors; the README gives JavaScript files containing unknown characters as its example.
Details
Coverage
For your agent
- Ref
capability:platform-migration- JSON
- /capabilities/platform-migration.json
- MCP
- Connecting an agent