New: LendNX, the AI‑powered lending platform for banks and NBFCs. Meet LendNX
EONE Technologies, an EvonSys company

Ready for ODC? Find out in 5 questions.

A quick readiness check gives you a score and a first migration plan. Then AI-generated tests compare every output until legacy and ODC agree.

Question 1 of 5ODC readiness check

0

Why move to ODC now.

ODC is where OutSystems’ newest AI capabilities live.

Cloud-native scale

Apps run as independent services that scale automatically.

Mentor

OutSystems’ AI coding agent builds apps, agents and workflows from a description.

Agent Workbench

Build and orchestrate AI agents with human oversight.

Lower running cost

Less infrastructure to manage and faster releases.

Apps move in waves

Start using ODC before you finish moving.

The ODC Data Fabric connector for O11 extends your trusted O11 data into ODC. Your teams can build new apps and AI agents on ODC straight away, while existing O11 apps keep running and move in waves.

O11 data available in ODCNo disruption to O11 appsAI agents on day one

A low-risk migration, step by step.

We move in tested waves. Old and new run side by side until every result matches.

1Weeks 1 to 2

Assess

AI-assisted scan of apps, code, data and dependencies.

2Week 3

Plan

A wave-by-wave plan with risks, effort and dates.

3Weeks 4 to 10

Migrate

Apps refactored for ODC in small, tested batches.

4Week 11

Run in parallel

AI-generated tests compare old and new outputs.

5Week 12

Cut over

A rehearsed switch, with a rollback plan ready.

The OutSystems capabilities behind the move.

Migration is the start. These are what your teams get on ODC.

OutSystems Developer CloudODC

What it isOutSystems’ cloud-native platform. Apps run as independent services that scale automatically and ship on their own.

How we use it hereYour apps move to cloud-native services that scale and release independently.

Data FabricData layer

What it isA single virtual layer over your databases, APIs, legacy systems and SaaS apps. Data stays where it is and keeps its permissions.

How we use it hereThe ODC Data Fabric connector for O11 lets new ODC apps use O11 data during the move.

MentorAI coding agent

What it isOutSystems’ platform-native AI agent. Describe what you need and it generates apps, AI agents, workflows and libraries for engineers to review.

How we use it hereSpeeds up refactoring and lets your teams build new apps faster after the move.

Agent WorkbenchAI agents

What it isBuilds and orchestrates AI agents across your data, workflows and systems, with built-in human oversight. Plug in any major LLM.

How we use it hereOnce on ODC, AI agents can be added to migrated apps.

Governance & MCPControl

What it isODC roles, approvals and audit trail, which also apply when engineers build and ship through OutSystems MCP.

How we use it hereEvery release is tracked, approved and can be rolled back.

280+certified OutSystems professionals
50+projects delivered
[X]apps migrated to ODC

Four commitments on every migration.

No data loss

Every record reconciled before and after the move.

Parallel run

Old and new run together until results match.

Rollback plan

A tested way back, agreed before cutover.

Rehearsed cutover

We practise the switch before the real one.

Questions banks ask us.

Will our customers notice the migration?

No. We migrate in waves and run old and new in parallel, so customer journeys keep working.

Can we use ODC before every app has moved?

Yes. With the ODC Data Fabric connector for O11, new ODC apps and AI agents can use O11 data during the migration.

How long does an O11 to ODC migration take?

Around 12 weeks for a typical mid-size estate. Your plan comes out of the assessment.

Do we need to rebuild everything?

No. The assessment shows which apps move as they are, which need changes and which to retire.

Get your ODC migration plan.

Start with a free assessment. We map your estate and show you the safest path to ODC.