Proof, not vignettes
One real sample migration. Honestly labeled as exactly that.
We'd rather show you one real, verifiable result than a page of polished but unverifiable client vignettes. Below is a complete sample migration — run against a public OutSystems Forge component, not a paying client — with the actual numbers the pipeline produced.
OutTracker: OutSystems to React/Node.js
Source: OutTracker, a sample OutSystems Forge solution (a publicly available OutSystems component, not a client's proprietary application) — chosen specifically so the full output could be shown here without any confidentiality concern.
Target: React 19 frontend, Node.js backend, SQL database via Prisma ORM.
Method: OML parsed into a structured intermediate representation (entities, action-flow business logic, screens, REST contracts, roles, client-side logic, timers, config, cross-module dependencies) — then generated into idiomatic target code, then verified with integration tests comparing behavior against the original.
| Metric | Result |
|---|---|
| Modules extracted | 7 |
| Files generated | 103 |
| Database models | 18 |
| API modules | 17, with 35 business logic methods |
| Frontend pages | 17, fully implemented |
| Client hooks | 8 |
| External API clients | 11 typed integrations |
| Attribute coverage | 96% |
| Integration tests | 49 passing |
| Authentication | JWT + role-based (4 roles) |
What "96% attribute coverage" means: a validation report mapping every OutSystems attribute to its new database counterpart — the 4% gap is disclosed, not hidden, and represents attributes flagged for manual review rather than silently dropped.
What's next on this page
A live-engagement case study, once one is cleared for publication.
Adapt has active and completed engagements we can't name yet — client confidentiality and, in some cases, still-open deals mean we don't publish account names or unverified figures. When an engagement clears for publication, it will appear here with the same honesty as the OutTracker entry above: real numbers, explicit method, and disclosed limitations.
Next step
Want to see it on your own code, not a sample?
The Proof of Architecture Diagnostic runs the real pipeline against one of your actual modules.