Transitioning from OutSystems 11 (O11) to OutSystems Developer Cloud (ODC) is a multi-stage journey, where each step builds upon the previous one to ensure a solid migration foundation. While careful planning helps anticipate many aspects of the transition, unexpected challenges often arise during execution.

To ensure a smooth migration, it’s crucial to analyze, refactor, and adjust your O11 application. Despite similarities between O11 and ODC, key architectural differences demand modifications to ensure full compatibility with ODC’s cloud-native environment.

Through this session, we’ll break down migration patterns into four major categories:

1️⃣ System-Dependent Assets – Handling assets that consume system elements.

2️⃣ Pre-Migration Fixes – Patterns that must be addressed in O11 before migration.

3️⃣ Unsupported Patterns – Features and implementations that require alternative solutions in ODC.

4️⃣ Post-Migration Fixes – Adjustments necessary after transitioning to ODC.

We’ll deep dive into each category, discussing OutSystems’ recommended best practices to resolve these patterns efficiently. By applying these strategies, you can make your applications ODC-ready while minimizing disruptions.