Originally published by Angus Kennedy on 16 July 2024. Updated on 28 September 2026 to reflect current OutSystems guidance.
Moving from OutSystems 11 to OutSystems Developer Cloud is a portfolio decision, not a single platform switch. Start with the applications, data, integrations, users and operational dependencies you have today.
Decide what to extend and what to convert
OutSystems now documents an approach for extending O11 applications with ODC capabilities while retaining O11 resources. A complete conversion may suit other parts of the portfolio. Assess each application against business value, architecture, data dependencies, security and the change it needs.
Plan the transition around real dependencies
Map application logic, data, APIs, identity, permissions and integrations. Define how existing and new applications will communicate, what must move, and how records will be checked. The chosen route should include testing, operational monitoring, recovery and clear release ownership.
Deliver in controlled stages
A useful plan prioritises a bounded first workload, validates it with users and measures what changes in the operation. Systems iO can help assess the estate, shape the architecture, build and test the transition, and support the resulting applications. Scope and service commitments are agreed for each engagement.
For current platform guidance, see OutSystems’ official documentation on Extending O11 with ODC and OutSystems 11 to ODC conversion. Contact Systems iO to discuss your application portfolio.
