Migrating from O11 to ODC is a multi-stage process, where each stage builds upon the previous one to strengthen the foundation for the next. While planning covers all aspects of the transition, execution is always challenging, as it often reveals unforeseen issues that can’t be anticipated, regardless of how thorough the planning was.

As you begin to prepare your O11 application for migration to ODC, it’s crucial to refactor and adjust your existing implementation to ensure a smooth transition. Despite the many similarities between O11 and ODC, significant adjustments will still be required to ensure your application is fully compatible with the cloud-native ODC platform.

The patterns which are encountered during the transition journey could be classified into following major categories:

1. Assets consuming System elements

2. Patterns which need to be fixed in O11

3. Not supported patterns in ODC

4. Patterns that need to be fixed in ODC

During the session we are going to dive into each of these categories and the patterns that fall under. We will understand the OutSystems suggested guidelines to fix those different patterns in order to make the applications ready or compatible with ODC platform.

Note: 10 Lucky Winners from the Masterclass would get an opportunity to win the exciting prizes.

**It is mandatory to attend all the sessions of Masterclass to get a chance to win. Winners will be announced in last session of the Masterclass.