OutSystems migration to ODC
Everything for a smooth transition to the OutSystems Developer Cloud
Prepare yourself with “ODC Ready” OutSystems applications for a future migration to OutSystems Developer Cloud (ODC). Set up your application development “ODC Ready” to ensure you can use the scalable cloud-native architecture within the ODC platform in the future. You also won’t deliver any extra development work that requires conversion.
One of the low-code promises is that subsequent platform versions are always backward compatible. In other words, the same code always works even if the underlying technology changes. OutSystems calls this the “Build-for-the-Future Promise”.
However, this is not always the case. Sometimes there are such disruptive technology shifts that even low-code platforms can’t bridge this. This was the case with the transition from “traditional web” to “reactive web” (modern front-end technology) and also now, with the shift to a scalable cloud-native architecture.
New possibilities with OutSystems ODC
With ODC, OutSystems offers its customers a platform with advanced cloud-native architecture, unlimited scalability, and new AI functionalities. It also offers simplified maintenance and faster and more secure deployment processes. OutSystems labels ODC as the platform for the future and to use for low-code application development.
ODC cloud-native benefits
The primary difference between OS11 and ODC is that ODC is cloud-native. This means it is purposefully designed for deployment and operation within cloud environments, marking a significant departure from traditional platforms. Besides this, ODC is a modernization of OS11: you can do everything in OS11, with extra new features that allow you to keep up your applications with the latest trends. Read about all the benefits of ODC in our article, why choose ODC?
But what does this mean for existing OutSystems applications? The answer is simple: to take advantage of the benefits of the ODC platform, a migration is necessary.
Transition from OS11 to ODC
The migration to ODC may seem challenging at first and will raise many questions. At LINKIT we will support you on this path. As an OutSystems partner, we offer extensive advice and support. We identify and implement the best OutSystems ODC solution for your organization.
How and when to migrate?
OutSystems defined four stages for the migration from OutSystems 11 (or earlier versions) to ODC. These are the stages of the migration, but there is still a lot to do before this. For example, answering whether a migration is necessary and when.
Until this day OutSystems continues its engineering investment in OutSystems 11. OutSystems supports OS11 applications in the OutSystems cloud and self-managed private cloud environments until at least March 2027. Even this date is not yet the final end-of-support date. They will announce the final date at least two years in advance.
Migration is not yet urgent. Certain functionalities are not yet available in ODC (such as running ODC on a private cloud environment). In some cases, new customers still start developing applications in OutSystems 11. In other cases, migration cannot happen soon enough to take advantage of the scalable cloud-native architecture and other advantages of the ODC platform.
Whichever scenario applies to your situation, we recommend that you consider a future migration in any case. Whether it involves an existing application built with “traditional web” technology, a modern OutSystems 11 application based on “reactive web,” or even a newly built application in OS11. In all cases, make preparations and consider a future migration, making your applications “ODC Ready”.
ODC Ready and the ODC Migration Toolkit
OutSystems eases the transition from OS11 to OutSystems ODC with a dedicated migration toolkit. They expect to launch the tool in Q3 2024, and it will help with migrating code and data to the ODC platform. However, this will only succeed if your applications are “ODC Ready”.
An application is “ODC Ready” if the architecture, code, screens, and data align with the ODC standards. Your current applications probably are not ready at this point. Implement ODC best practices on all these points in your development process as quickly as possible. By delivering extra development work, you can prevent the need for additional work later on.
In addition, it is smart to solve issues that the ODC migration tool does not provide. For example, screens developed in “traditional web”. You have to migrate these to “reactive web” screens to migrate with the OutSystems migration toolkit.
Another preparation is converting Forge components to ODC. These building blocks from the OutSystems 11 marketplace are not automatically available in the ODC marketplace.
Check out this article on ITNEXT for more technical background information about migrating to ODC.
Ready for the migration to ODC?
Start with the migration toolkit to make your applications “ODC Ready”. We are happy to help you with a (future) migration. This will enable you to transfer your data and applications successfully and safely at the desired time.
Start the conversation about making your application landscape ODC Ready and the benefits of OutSystems ODC. LINKIT supports you on your way to fully utilizing your potential.
Dion Drost
