{"ref":"capability:platform-migration","page":"/capabilities/platform-migration","json":"/capabilities/platform-migration.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"platform-migration","name":"Platform migration","domain":"operations-and-runtime","ecosystems":["btp","cap"],"universal":false,"description":"Moving an application, integration or database from one platform to another: assessing what exists, converting what tooling supports, and adapting what cannot carry over. Language-level compatibility is a separate concern from moving the platform around an application.","short":"Moving an application, integration or database to another platform","core_coverage":{"state":"core-and-community","assessed_at":"2026-09-14","relationship":"unassessed","what_core_does":"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.","where_it_stops":"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.","community_adds":"AWS's [Modernization Agents for SAP on AWS](artifact:aws-modernization-agents-for-sap) 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.","sources":[{"url":"https://github.com/SAP-samples/btp-neo-java-app-migration","title":"SAP-samples/btp-neo-java-app-migration — Migration Guide for Java Applications from the Neo Environment to the Cloud Foundry Environment","checked":"2026-09-14","quote":"The Neo Java Web API dependency is not provided in Cloud Foundry, so it must be replaced by SAP Cloud SDK dependencies."}],"note":"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."},"coverage_by_ecosystem":{"cap":{"state":"core-only","assessed_at":"2026-09-14","what_core_does":"The SAP HANA Application Migration extension turns an XS Advanced or XS Classic application into a CAP project on [SAP HANA Cloud](artifact:btp-hana-cloud): database artifacts become CDS, `.xsodata` files become a `service.cds` with a `service.js`, and `.xsjs` and `.xsjslib` files become handler files.","where_it_stops":"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.","sources":[{"url":"https://github.com/SAP-samples/xsa-cap-migration-using-basextn","title":"SAP-samples/xsa-cap-migration-using-basextn — README","checked":"2026-09-14","quote":"While the extension automates a large portion of the migration process, the converted output is not guaranteed to be 100% runnable or semantically equivalent."},{"url":"https://github.com/SAP-samples/xsa-cap-migration","title":"SAP-samples/xsa-cap-migration — XS Advanced Programming Model To SAP Cloud Application Programming Model Migration Guide","checked":"2026-09-14","quote":"For creating the rename procedure we use `toRename` function of CDS compiler"}],"note":"Both sources are SAP-samples READMEs; no capire or help.sap.com page was checked."}},"framing_by_ecosystem":{"cap":{"description":"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."},"btp":{"description":"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 readiness](capability:abap-cloud-readiness), not this."}},"drafted_with_ai":true,"history":[{"date":"2026-10-17","field":"description","from":"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 readiness](capability:abap-cloud-readiness), not this.","to":"Moving an application, integration or database from one platform to another: assessing what exists, converting what tooling supports, and adapting what cannot carry over. Language-level compatibility is a separate concern from moving the platform around an application.","reason":"Keep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit."},{"date":"2026-10-26","field":"core_coverage.state, core_coverage.relationship, core_coverage.community_adds, core_coverage.note","from":"core-only; note: \"The repositories answering this in the batch are SAP-samples guides, utilities and a workshop, which demonstrate rather than provide, so core-only reads what SAP's own tools and guides cover. ...\"","to":"core-and-community with relationship unassessed; community_adds names the AWS Modernization Agents for SAP as a partner kind of answer; note no longer explains core-only.","reason":"Reassessed against the graph (check:capabilities): a partner artifact serving the BTP door provides this capability, which the core-only state contradicted. The core stays, since what_core_does is sourced."}]},"sap_delivery":{"door":"btp","all":null,"by_flavor":{}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:aws-modernization-agents-for-sap","name":"Modernization Agents for SAP on AWS","json":"/artifacts/aws-modernization-agents-for-sap.json","ecosystem":"abap","origin_ring":"partner"}],"samples":[{"ref":"artifact:sap-samples-btp-neo-java-app-migration","name":"btp-neo-java-app-migration","json":"/artifacts/sap-samples-btp-neo-java-app-migration.json"},{"ref":"artifact:sap-samples-iq-to-hdl-migration","name":"iq-to-hdl-migration","json":"/artifacts/sap-samples-iq-to-hdl-migration.json"},{"ref":"artifact:sap-samples-teched2025-in161","name":"teched2025-IN161","json":"/artifacts/sap-samples-teched2025-in161.json"},{"ref":"artifact:sap-samples-xsa-cap-migration","name":"xsa-cap-migration","json":"/artifacts/sap-samples-xsa-cap-migration.json"},{"ref":"artifact:sap-samples-xsa-cap-migration-using-basextn","name":"xsa-cap-migration-using-basextn","json":"/artifacts/sap-samples-xsa-cap-migration-using-basextn.json"},{"ref":"artifact:sap-samples-xsc-cap-migration","name":"xsc-cap-migration","json":"/artifacts/sap-samples-xsc-cap-migration.json"},{"ref":"artifact:sap-samples-xsc-to-native-hana-cloud","name":"xsc-to-native-hana-cloud","json":"/artifacts/sap-samples-xsc-to-native-hana-cloud.json"},{"ref":"artifact:sap-samples-xsc-xsa-migration","name":"xsc-xsa-migration","json":"/artifacts/sap-samples-xsc-xsa-migration.json"}],"explained_by":[{"ref":"content:simplifying-abap-proxy-migration-from-sap-po-to-integration-suite-no-mdr-require","name":"Simplifying ABAP Proxy Migration: From SAP PO to Integration Suite (No MDR Required)","json":"/content/simplifying-abap-proxy-migration-from-sap-po-to-integration-suite-no-mdr-require.json"},{"ref":"content:product-updates-for-sap-build-code-june-2025-edition","name":"Product Updates for SAP Build Code – June 2025 Edition","json":"/content/product-updates-for-sap-build-code-june-2025-edition.json"},{"ref":"content:teched-2026-da114","name":"Modernize your database landscape with SAP HANA Cloud","json":"/content/teched-2026-da114.json"},{"ref":"content:teched-2026-da200","name":"Agentic SAP BW modernization: Your path to SAP Business Data Cloud","json":"/content/teched-2026-da200.json"},{"ref":"content:teched-2026-in202","name":"Accelerate your migration to SAP Integration Suite","json":"/content/teched-2026-in202.json"},{"ref":"content:teched-2026-in203","name":"Mercedes-Benz’s journey to SAP Integration Suite","json":"/content/teched-2026-in203.json"},{"ref":"content:teched-2026-in212","name":"Modern integration at TÜV Rheinland: APIs, events and cloud transformation","json":"/content/teched-2026-in212.json"},{"ref":"content:teched-2026-in260","name":"Modernisation and migration to SAP Integration Suite made simple","json":"/content/teched-2026-in260.json"},{"ref":"content:teched-2026-in810","name":"Roadmap to upgrade from SAP Process Orchestration: Agentic era preparation","json":"/content/teched-2026-in810.json"},{"ref":"content:teched-2026-par1115","name":"B2B integration factory: How Versuni verified more than 200 EDI interfaces","json":"/content/teched-2026-par1115.json"},{"ref":"content:teched-2026-st113","name":"AkzoNobel: Modernizing integration at enterprise scale","json":"/content/teched-2026-st113.json"}],"normative_context":[]}}