The Neo environment of SAP BTP has an end date—and your contract may expire sooner. Here is what to review before migrating.
The Neo environment has an end date
SAP has set an end date for the Neo environment of the SAP Business Technology Platform (BTP): December 31, 2028 (SAP Note 3351844). Neo is SAP’s original cloud environment, available since 2012 and built on proprietary technology. For years, it was where many companies hosted everything they wanted to run "in the SAP cloud" without modifying their ERP.
It often runs more than people remember: integrations—Cloud Integration, which many still call "CPI"—connecting SAP to banks, portals, marketplaces, and logistics providers; portals and launchpads (SAP Cloud Portal, Fiori Launchpad); custom applications that extend the ERP without touching it; and the identity and connectivity services that support everything above.
What is changing and when it actually affects you
It is worth being precise, as this is something clients can verify. The only thing SAP states unambiguously is that after December 31, 2028, contractual usage rights for the Neo environment will end. What technically happens to your integrations on that day? SAP has not declared it—and it is best not to infer. What is certain is contractual and governance risk: continuing to operate on an environment whose right of use has expired is, in itself, an exposure to non-compliance and audit risks.
And there is a detail that often speeds up the timeline. For many clients, the date that truly dictates the pace is not December 2028, but earlier: during BTP Neo contract renewals, SAP is actively driving the move to Cloud Foundry. That is why the first number to put on the table is when your Neo subscription expires. That date—and not 2028—typically defines your actual window to decide and plan.
Added to this is a fundamental point. SAP will continue providing security and compliance standards for Neo, but new features and innovations are only added to the multi-cloud environment—specifically mentioning SAP Integration Suite, SAP Build, and SAP Datasphere. Staying on Neo also means forfeiting whatever comes next.
SAP's official path and what it leaves behind
The path recommended by SAP is its multi-cloud foundation, with Cloud Foundry, Kyma, and ABAP environments running on top of major infrastructure providers. For integrations, the destination is SAP Integration Suite. It is a solid path: it has been the default environment for new clients since 2020.
SAP provides a tool that transfers content from one tenant to another, along with documentation and a list of known incompatibilities (SAP Note 2903776). However, its own documentation warns that the tool does not do everything. Scripts with environment variables, custom-developed adapters, key stores/certificate repositories, and especially endpoints—which change completely and must be communicated to every connected system, alongside updating firewalls and allowlisted IPs on both sides—must be rebuilt separately.
In other words: SAP provides the moving truck, but it doesn't assemble the furniture. The content travels; the connections and everything plugged in around it must be reconstructed. That is where the project requires hands-on execution.
The step that is almost always missing: knowing what you have
Before moving anything, there is a question SAP’s tool does not answer: what is currently running in your Neo environment? In practice, many teams lack an accurate inventory—the interfaces no one remembers are precisely the ones that don't show up—and quoting a migration without that inventory is estimating blind.
As an SAP Partner, Novis approaches the Neo-to-multi-cloud migration as a complement to the official path: we accelerate it and resolve what remains on the client's side. Our approach relies on four concrete pillars:
- We know where the gaps are before starting: If your tenant contains iFlows with environment variables in their scripts or a custom adapter, that won't transfer via SAP’s tool. We catch it during the initial diagnostic, not mid-project.
- A more comprehensive inventory: In our assessments, deployed interfaces surface that the internal team didn't realize were still active. They are migrated—or retired—with clear judgment, not by oversight.
- Local support: On go-live cutover day, the team responding is in your same time zone.
- Solving what the official path leaves open: New endpoints, allowlisted IPs on both ends, and coordination with every calling system—no tool handles that automatically.
Start with a assessment of your Neo systems
The first step isn't hiring a migration project, but getting clarity on two things: when your Neo contract ends, and what is actually running in it. You can confirm the former with your SAP account executive; for the latter, we perform an inventory and migratability assessment of your Cloud Integration tenant on Neo. Once access requirements are met, within 2 to 3 business days you get a breakdown of what is running, what can be directly migrated, what needs to be rebuilt, and an effort estimate by waves.
The requirement is minimal: your tenant administrator grants a one-time, 30-minute read-only access that allows us to connect our proprietary discovery tools. We don't install anything, deploy anything, or modify any artifacts. And you do not need to have SAP Integration Suite contracted yet to do it.
The Novis team features consultants certified by SAP in SAP Business Technology Platform and SAP Integration Suite.
Neo has an end date—and your contract may have a closer one. The exit plan starts by knowing what needs to be moved.
Written by: Hugo Atenas, Deputy Manager of Transition Projects and Technical Consulting, Novis
→ Book an X-ray of your Neo environment.