If your organization is running Java applications on SAP BTP, Neo environment, 2028 is a date worth planning for now. Migrating to Cloud Foundry is the path forward — but it is not a simple redeploy. Runtime models, service bindings, deployment formats, authentication, and namespace conventions all change.
The sap-btp-neo-migration plugin addresses this with 22 AI agent skills that cover the full migration journey: from transforming Java source code and generating MTA deployment descriptors, to migrating subaccount trust and role assignments. Using the orchestrator, a complete end-to-end migration takes approximately 30 minutes.
This post walks through what actually changes between Neo and Cloud Foundry, what the skills cover across both the developer and administrator tracks, and how to get started.
