VB.NET and PL/SQL to .NET and React
Business logic split between WinForms code-behind and Oracle packages is the hardest kind to move, because neither half makes sense alone. ARC traces rules across both before anything is rebuilt.
Half the rule is in the database
A typical line-of-business app from the 2000s validates an order on the form, recalculates it in a PL/SQL package, and enforces the last constraint in a trigger. Rewriting the screens in React without the database logic produces a system that looks right and behaves wrong.
Reading both layers together
- Code and schema in one index. VB.NET parsed into syntax trees alongside the database's tables, packages, procedures and triggers.
- Rules traced end to end. A rule found in a form is linked to the procedures it calls, so its full behaviour is one cited record.
- Keep the schema if you need to. Many teams keep the Oracle schema frozen and move only the application. The plan records that as a decision and builds around it.
What the rebuild looks like
The target is typically a .NET API with a React front end. Each capability becomes a specification that owns the legacy rules it must preserve, and the harness builds it with tests per story. Defects that the business relies on are kept on purpose and listed, not silently fixed.
Move the behaviour, not just the screens.
What you get
Timelines depend on access to code and people; we confirm them on the scoping call.