Legacy Discovery & Code Conversion
Understand your legacy applications. Plan your next move.
Build a clearer picture of your existing systems before you modernise. OneBusiness ERP brings application evidence, architecture findings and documentation into one workspace, helping your team prepare for informed code conversion.
Legacy Discovery
Discover what your application depends on
Legacy applications often hold business rules and dependencies that are difficult to trace. Begin with the evidence available, identify what it reveals and record the questions that need further investigation.
Register your applications
Create a discovery project and register the applications within scope. Capture business and technical ownership, criticality and reported technology details.
Collect supporting evidence
Register and collect the sources needed to understand each application. Keep evidence organised so findings can be reviewed in context.
Analyse and review
Run an analysis, examine the findings and review the architecture identified from collected evidence. Track observations and unresolved questions as your understanding develops.
Generate current-state documentation
Bring reviewed findings together into an architecture document that supports technical discussions, handovers and modernisation planning.
Coverage
Know what the evidence supports
See the number of registered evidence sources, collected sources, findings and open questions for each application.
Coverage describes the evidence collected and processed within the analysis scope. It does not establish that every part of the legacy system has been discovered. Use it to guide further investigation and identify gaps.
Evidence sources
Sources collected
Findings
Open questions
Code Conversion
Prepare for code conversion
Move from understanding the current application to defining how it should change. Use discovery findings to establish conversion scope, select a target technology and identify business behaviour that must be preserved.
Define the scope
Identify the components to convert, their dependencies and the boundaries of the work.
Define the scope
Identify the components to convert, their dependencies and the boundaries of the work.
Define the scope
Identify the components to convert, their dependencies and the boundaries of the work.
Define the scope
Identify the components to convert, their dependencies and the boundaries of the work.
How it works
From discovery to a reviewed conversion
Discovery
1
Register
Define the project, applications and owners.
2
Collect
Gather the evidence needed for analysis.
3
Discover
Review architecture, findings and open questions.
4
Document
Establish the current-state baseline.
Conversion
5
Register
Define the project, applications and owners.
6
Validate
Check the results and resolve outstanding issues.
Discovery produces analysis and documentation. Code conversion is a separate stage, with its own scope, review and validation.
Give your team a shared starting point
Help business owners, architects and developers work from the same evidence. Make application knowledge easier to review, keep unknowns visible and build a documented basis for modernisation decisions.
Start with a clearer understanding
Register your first application and begin building the evidence for its next chapter.