Hello everyone,
Hope you are all doing well. I’m looking for guidance and real-world experience regarding the detachment process from OutSystems ODC.
I’m aware that there is an official document describing the detachment process for OutSystems 11 (O11) here: https://success.outsystems.com/support/licensing/the_detach_process_for_outsystems_11/
I have also referenced Q&A regarding the process in our community. However, I haven’t been able to find any equivalent or detailed guidance specifically for ODC.
In particular, I’m very interested in understanding what the downloaded .NET solution/project/database structure looks like when detaching from ODC:
-Is the generated .NET solution structure similar to the OutSystems 11 detach bundle (database, projects, folders, runtime libraries, etc.)?
-Are there any notable differences in how modules/screens/entities are translated to .NET projects in ODC compared to O11?
If anyone has already gone through a detachment from ODC, or received preliminary documentation or guidance from OutSystems on how ODC detachment will work and what the .NET output looks like, I’d really appreciate any insights, pointers, or lessons learned.
Thanks in advance!
Duong
Hi Duong,
What I’m sharing below is my understanding of your question and how I see the situation. I’m sure there may be colleagues in the community who can provide more detailed or official information.
From an architectural perspective, ODC does not follow the same detachment model as OutSystems 11.
In O11, detachment generates a full .NET solution bundle, including database scripts, projects, runtime components, and infrastructure elements that allow you to host and maintain the solution independently.
ODC is fundamentally different. It is cloud-native and fully managed by OutSystems. There is currently no equivalent public mechanism that generates a traditional .NET solution package similar to O11.
A few important considerations:
So, you should not expect a Visual Studio solution, standalone database scripts, or a structure identical to O11.
If detachment is a strategic or compliance requirement, I would strongly recommend engaging your OutSystems account team early to clarify what is contractually and technically possible in ODC.
Hope this helps.
What Miguel, correctly explains in detail, can be summarized to this: there is no official detach process available nor documented for ODC. If you have questions regarding this topic best is to address them to your OutSystems account manager.
Regards,
Daniel