What the migration service includes
Intelligent analysis
Generation of a detailed knowledge graph from your legacy code to capture the relationships between procedures, functions, tables, and databases, identifying and avoiding the migration of dead source code.
Modern architecture design
Establishment of a new microservices architecture, including APIs.
Automated backend code generation
Implementation of backend in Spring Boot, covering controllers, services, entities, and repositories. Other backend technologies can be requested on demand.
Frontend design and generation
Creation of React-based user interfaces that reflect the screens and interactions of the original application. Other frontend technologies can be requested on demand.
Continuous human validation
Expert-led reviews, adjustments, and validations with our client throughout the migration process.
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).
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 results and functional tests (optional).
Additional deliverables can be included at extra cost.
(*) The 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. The code generated by Codacle will strictly adhere to these standards.
- Provide secure access to their code repositories and test databases.
- Specify delivery preferences. By default, we deliver the migrated code directly to your repositories, but we can adapt to any CI/CD pipeline or implementation process you have, which may influence the overall price.
- In case they require functional testing on our part, provide detailed descriptions of the tests required for each form, including available test data and access to an appropriate test environment.
POCs and guarantee
Proof of concept (POC)
We do not offer free POCs; however, we guarantee that the migrated code will meet the same functionalities as the original application. In that sense, we are equivalent to the migration services of any traditional software factory. That is, we deliver a "turnkey" solution, only with significantly shorter times 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, and Google. In other words, we do not go directly to OpenAI or Anthropic, but use the implementations of Azure and AWS. At the moment, we do not use locally installed open-source LLMs (for example, in your data centers), because in our experience they do not offer enough intelligence for this type of work.
Authorization and authentication
Regarding the 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.