Platform migration
In CAP this is the arrival side of an XS migration: HANA CDS entities rewritten as CAP CDS and XS services turned into CAP service definitions and handlers.
Overview
The SAP HANA Application Migration extension turns an XS Advanced or XS Classic application into a CAP project on SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp: database artifacts become CDS, .xsodata files become a service.cds with a service.js, and .xsjs and .xsjslib files become handler files.
Not covered: At a first draft of the service layer. SAP states that the converted output is not guaranteed to run or to behave the same, and proxy CDS for cross-container schemas is not generated.
Both sources are SAP-samples READMEs; no capire or help.sap.com page was checked.
No community artifact is documented here.
Artifacts
Nothing is mapped here yet.
Content
Seen working
Directed at single-tenant applications, which the guide states as its scope. The migration path it uses also has no option to select individual containers, so it migrates every container in the given space.
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