How the Codacle platform works
Proven result: 500 Delphi forms and 70 batch processes migrated to Spring Boot + React in 14 months. The manual projection was 16 years.
Intelligent analysis
Generation of a detailed knowledge graph from legacy code to capture relationships between procedures, functions, tables, and databases, identifying and avoiding migration of dead code.
Modern architecture design
Establishment of a new microservices architecture, including REST APIs.
Automated backend code generation
Backend implementation in Spring Boot, .NET 8, node.js, etc., covering controllers, services, entities, and repositories. Ask about other technology stacks.
Frontend design and generation
Creation of React, Angular, etc. user interfaces that reflect the screens and interactions of the original application. Ask about other technology stacks.
Human + AI validation
Expert-led reviews, adjustments, and client validations throughout the migration process. Autonomous validation pipeline over hundreds of elements from the original source code.
AI-assisted testing
Automated generation and execution of unit tests. Execution of functional tests to ensure accurate replication of functionality.
What the documentation service includes
Documentation generation
Generation of detailed technical and functional documentation for your source code.
Automatic updates on code changes
Optionally, we can connect to your repository and automatically update the documentation when code changes.
Access to virtual agent
Optionally, you can use our virtual agent, Barbara, which can answer technical and functional questions about your source code by traversing the graph where we represent each part of your software and its connections. Additionally, we can integrate this agent into your developers' IDE as long as they support MCP (for example, Visual Studio Code or Cursor).
Migration service deliverables
- Migrated code that meets client standards.
- README files and Swagger for APIs.
- Unit tests with at least 80% coverage on average.
- Evidence of unit test and functional test results. Evidence from the automated validation pipeline.
Additional deliverables can be included at extra cost.
(*) Functional test scripts and data must be provided by the client. Alternatively, the client can perform these tests and report any issues.
Client responsibilities
To ensure a smooth migration process, we require clients to:
- Clearly describe technical standards and preferences, including coding conventions, folder structures, library versions, or any other relevant guidelines. Code generated by Codacle will strictly adhere to these standards.
- Provide secure access to code repositories and test databases.
- Specify delivery preferences. By default, we deliver migrated code directly to your repositories, but we can adapt to any CI/CD pipeline or deployment process you have, which may influence overall pricing.
- For us to execute functional tests, provide detailed descriptions of the tests or record a video using the main form on the database we will use for testing, so we can replicate the steps on the migrated form and validate its functional equivalence before delivering for client validation.
Discovery and guarantee
Discovery session
We offer free discovery sessions to evaluate the feasibility of your project. Our commitment: the migrated code will meet the same functionalities as the original application. In that sense, we deliver a "turnkey" solution, only with significantly shorter timelines and costs.
Security
Storage and processing
All our processes run on secure networks and computers. Your source code will be stored on these computers, as well as in Microsoft OneDrive folders for the duration of the project. Subsequently, all copies will be removed from our storage.
Use of cloud LLMs
We will send your code to LLMs in the cloud for processing and conversion. Our use of LLMs is restricted to APIs implemented by Azure, AWS, Google, and Anthropic. At the moment, we do not use locally installed open-source LLMs (e.g., in your data centers), because in our experience they do not offer sufficient intelligence for this type of work.
Authorization and authentication
Regarding authorization and authentication of the migrated application, by default we use your existing scheme. For example, if you have tables with usernames, passwords, and user-allowed access to certain functions in your systems, we will continue to use those tables. However, we can integrate with other methods (such as AD) or even create new ones from scratch for your project, subject to additional cost.