migration-agent

Automating Java-to-Python migration involves chunking .java files, using LLM-driven translation, and reassembling the code into idiomatic Python 3.11 modules. The process yields a formatted python_project tree, a dependency-based requirements.txt, and a migration_map.json for traceability.

LLM-driven code conversion translates Java source files into Python 3.11 by processing chunked code segments through a language model and reassembling them. It generates an idiomatic python_project tree while preserving the original business logic and structure.

Automated Java to Python migration handles formatting by applying Black and running flake8 lint checks during post-processing. It validates syntax, logs warnings, and marks files needing review to ensure the output python_project meets Python 3.11 standards.

Yes, you can migrate a legacy Spring microservice to a Python FastAPI service by converting the Java source files. The workflow preserves business logic while producing a python_project output and a migration_map.json for reviewer traceability.

Java code conversion generates a python_project tree containing the translated modules, a migration_map.json for traceability, a migration_state.json for tracking pipeline state, and a requirements.txt derived from mapped Java dependencies.

A limitation of automated Java to Python migration is that complex translations may not pass validation cleanly, causing the tool to log warnings and mark files requiring manual review. The process also requires a manifest of .java files to begin chunking and translation.