--- title: "SAP Neo: why 2028 isn’t the most important deadline" date: 2026-09-03T11:55:00+02:00 author: Flexso canonical_url: "https://www.flexso.com/en/insights-blog/sap-neo-why-2028-isnt-the-most-important-deadline" section: cp.sections.blog --- ![SA Pience digitaltransformation ERP Roadmap event 1](data:image/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D%27http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%27%20width%3D%271360%27%20height%3D%27544%27%20style%3D%27background%3Atransparent%27%2F%3E) Let’s say your smartphone still works perfectly. You can use it to make calls, send emails, take photos, and the settings are perfectly tailored to your preferences. But then a notification pops up:*“New apps and features are no longer available for this model.”* What now? The latest innovations are passing you by. AI capabilities? Unfortunately not. New possibilities you never thought were possible? Only available on a new device. Your smartphone keeps working, but every day you fall further and further behind on what’s truly possible. That’s exactly the situation many companies find themselves in today with SAP Neo. With one difference: your smartphone keeps working for as long as you want it to. **Neo has a fixed end date.** SAP has announced that the SAP BTP Neo environment will be phased out by the end of 2028. They’re doing this because they’re focusing all their efforts on the possibilities of the SAP BTP Multi-cloud environment, with Cloud Foundry as the primary runtime - innovations, new technologies, AI implementations. For many organizations, that date feels like the ultimate deadline to switch to Cloud Foundry by then. But actually, that’s not the most important reason to start thinking about the move to Cloud Foundry today. **The real question is: How much innovation are you willing to miss out on between now and 2028?** ## Neo still works. But SAP is innovating elsewhere. For those who are unsure: there’s nothing wrong with a stable Neo environment. It may be running applications and extensions that have been working reliably for years and support critical business processes. You need a good reason to migrate a well-functioning (often complex) environment. Let this be a very good reason. SAP sees the future in Cloud Foundry. It’s already the strategic runtime environment within [**the SAP Business Technology Platform**](https://www.flexso.com/en/solutions/apps-extensions/sap-btp-business-technology-platform) (SAP BTP). New platform services, AI capabilities, development models, and innovations are being developed, tested, and implemented every day. Neo is falling by the wayside. SAP Neo will therefore continue to be supported until the end of 2028, but the real innovation is happening elsewhere. ## Migration isn’t the biggest cost When an organization starts discussing the migration of IT systems, the cost quickly becomes the main factor in deciding whether or not to proceed. How much work will this entail? Which applications and custom builds need to be adapted? What impact will this have on our business? These are valid questions. But what if you flip the perspective? What aren’t you migrating? How many opportunities are you already missing out on today? While SAP continues to invest in the**“Autonomous Enterprise”** with AI tools, modern development models, integrations, and new platform services, you’re still building on an environment where none of those innovations are available. “How much longer can we stay on Neo?” then becomes “Why should we wait to take advantage of what’s already available today and can enrich the organization?” The most important deadline is not the one SAP has set. It's the one you set yourself: the moment you decide you no longer want to wait for capabilities that already exist today. ## From migration project to modernization journey Not every Neo application needs to be rewritten A transition to BTP's multi-cloud environment is the ideal time to take a close look at your application landscape. Which extensions still create real business value today? Which applications have become more complex than necessary over the years? Or redundant? If you had the chance, which ones would you build fundamentally differently? All these considerations align perfectly with the **Clean Core principle** that SAP is emphasizing today. > ![Joren degreef](data:image/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D%27http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%27%20width%3D%27156%27%20height%3D%27156%27%20style%3D%27background%3Atransparent%27%2F%3E)By developing customizations outside the core of SAP S/4HANA as much as possible and using modern extensions on SAP BTP, you’re building a landscape that’s easier to maintain and supports future upgrades rather than hindering them. The transition to Cloud Foundry therefore doesn’t have to be a purely technical migration project. **It can just as easily be the starting point for a modernization effort that will propel your SAP landscape forward for years to come.** ## Modernize your SAP BTP environment with Flexso Every SAP environment is different. Some Neo applications can be migrated relatively easily, while others require a much broader evaluation or modernization effort. Where do you start? With an inventory. Which Neo applications do you have, which ones still deliver value, and which ones would you no longer build today? That exercise requires little effort and helps determine the rest of your migration journey. At Flexso, we therefore don’t just look at **how** to successfully migrate to Cloud Foundry, but (more importantly) **why** and **how** you can make the most of that transition. This way, the phase-out of SAP Neo isn’t just a mandatory migration project, but an opportunity to prepare your SAP landscape for the future. [Explore your options](https://www.flexso.com/en/contact) --- Written by ![Joren degreef](data:image/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D%27http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%27%20width%3D%2794%27%20height%3D%2794%27%20style%3D%27background%3Atransparent%27%2F%3E)**Joren De Greef** Share - [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.flexso.com%2Fen%2Finsights-blog%2Fsap-neo-why-2028-isnt-the-most-important-deadline"e=Authors%20%2B%20brand) - [LinkedIn](http://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fwww.flexso.com%2Fen%2Finsights-blog%2Fsap-neo-why-2028-isnt-the-most-important-deadline&title=Authors%20%2B%20brand&summary=&source=https%3A%2F%2Fwww.flexso.com%2Fen%2Finsights-blog%2Fsap-neo-why-2028-isnt-the-most-important-deadline) - [Whatsapp](whatsapp://send?text=https%3A%2F%2Fwww.flexso.com%2Fen%2Finsights-blog%2Fsap-neo-why-2028-isnt-the-most-important-deadline)