LambogeniusA staged migration workflow with persisted evidence
Lambogenius Integration Migration analyzes existing integration assets, generates source-flow evidence, plans an Azure target, creates a migration candidate, validates generated artifacts, prepares a deployment package, and estimates monthly Azure running costs before deployment approval. Each stage writes inspectable outputs so a run can be reviewed, resumed, or gated in CI.
Full batch runs report input, output, total model tokens, and call counts when each executed stage finishes or fails (sample notifications and single-stage limitations). The Azure cost estimate is separate from AI model usage and license metering.
The command name is route-neutral, but the current implementation is AIS-focused. Do not assume a source-to-target route is supported unless its adapter and validation gates have been implemented.
Ways to work
Interactive CLI
Run li with no subcommand to open the persistent interactive experience. Use natural requests or slash commands to precheck, discover, plan, convert, test, inspect results, and change logging.
Non-interactive CLI
Run explicit subcommands for PowerShell, GitHub Actions, Azure Pipelines, or another CI runner. Commands return non-zero exit codes on failure and can emit machine-readable JSON where supported.
VS Code compatibility experience
Select a source folder, inspect flow and dependency visualizations, generate plans, execute conversion tasks, run black-box tests, and export analysis or planning reports from VS Code.