OutSystems 11 end of support: rebuild on ODC or replatform?

What the OutSystems 11 to ODC move involves

OutSystems Developer Cloud (ODC) is OutSystems' cloud-native platform. A July 2026 agency review (RapidDev, citing lowcodemigration.com) states that OutSystems 11 (O11) code does not compile or run on ODC, so moving an O11 estate is a full rebuild rather than an upgrade. The same review says O11 is supported until at least March 2027. We could not confirm either point on OutSystems' own pages, so ask OutSystems for your support end date and its migration approach in writing.

What to count before you choose

List every O11 application, its integrations, users and the application objects it consumes. Estimate developer weeks per application, then add the period when you pay for O11 and ODC at once. The agency review describes this parallel licensing as a double cost that grows the longer the move is deferred. Treat that as a claim to test against your own contract.

The cost and lock-in question it reopens

A forced rebuild reopens a decision most teams made years ago. The same review reports that neither O11 nor ODC offers source-code export that runs outside OutSystems. If that holds for your contract, rebuilding on ODC restarts the clock on the same exit cost. Run the exit scan on the platform you are leaving and on each candidate, and ask for the licence metric and renewal terms in writing.

If you rebuild anyway, rebuild where you can leave

Betty Blocks states that it offers AI-powered migrators for OutSystems and Power Apps, and that its React frontend and WebAssembly backend can be exported. Its June 24, 2026 release notes add a self-serve code download, gated by role-based permissions. These are vendor statements read in October 2026. Ask any candidate, Betty Blocks included, to migrate one real application and hand over the code before you commit the estate.

Your vendor checklist

• Ask OutSystems in writing for your O11 support end date.
• Count apps, application objects and developer weeks to rebuild.
• Price parallel licences during the transition.
• Ask every target platform to demonstrate a code export.
• Agree contract terms for the rebuild before you start it.

More field guides

• What the AI price tag leaves out.
• A credible exit has five dimensions.
• An export button is not an exit plan.
• Turn exit obligations into buying questions.
• Give teams freedom with a clear boundary.
• Moving apps off Power Apps, OutSystems or Mendix.