Source estate discovery
Inventory BizTalk solutions and MSI packages, then trace applications, bindings, orchestrations, schemas, maps, pipelines, endpoints, and custom-code dependencies back to source evidence.
Migration engineeringComing soon
Move BizTalk integrations to Azure with evidence, controls, and repeatable gates.
LambOGenius Integration Migration discovers existing behavior, designs an Azure Integration Services target, generates a migration candidate, validates it, and prepares an auditable deployment package.
Current compatibility routeBizTalk → Azure Integration Services
PASS prerequisites and policyDONE 12 integration flows discoveredDONE target plans validatedDONE migration candidate generatedPASS build, Bicep, and static tests
One governed workflow
From source evidence to a deployment-ready candidate.
Each stage persists inspectable artifacts. Incomplete or unsupported behavior becomes a gap or review item—it is never silently treated as migrated.
- 01
Precheck
Verify source, toolchain, policy, and target prerequisites.
- 02
Discover
Build an evidence-backed inventory of flows, artifacts, dependencies, and gaps.
- 03
Plan
Design target architecture, action mappings, resources, and workflow dispositions.
- 04
Convert
Generate a controlled migration candidate in approved write paths.
- 05
Validate
Run project build, policy, Bicep, and static deployment tests.
- 06
Package
Create a manifest-backed deployment package with checksums and provenance.
What the tool does
A migration workspace built for real integration estates.
Dependency diagnostics
Scan nested solutions and projects without AI, package restore, or source changes. Missing, external, dynamic, ambiguous, and relocated references remain explicit for review.
Evidence-backed planning
Translate verified source behavior into target architecture, action mappings, resource selections, workflow designs, gaps, and documented human decisions.
Controlled generation
Generate Logic Apps Standard workflows, supporting Functions, infrastructure, tests, and pipeline assets only inside approved repositories and write paths.
Validation before delivery
Build generated projects and check policy, naming, prohibited resources, Bicep, and static deployment structure before a candidate can be packaged.
Batch, parallel, and resumable runs
Process one solution or a discovered estate, isolate each generated repository, run bounded parallel work, and resume safely from persisted stage checkpoints.
Provider choice
Use supported agent providers—including hosted coding agents and local Ollama models—while deterministic tools retain control of source facts, validation, and writes.
Auditable operations
Produce offline HTML, Markdown, and JSON reports with stage outcomes, timings, token usage, provenance, checksums, cost estimates, and deployment records.
Command-line interface
Interactive for guided work. Automation-ready for delivery pipelines.
The route-neutral li command runs individual stages or a resumable, end-to-end estate migration. The same governed workflow works at a terminal, in CI, and behind the VS Code experience.
Operate at estate scale
Discover .sln and .msi inputs recursively, run independent solutions in parallel, and continue after isolated failures.
Resume without losing verified work
Persist stage state, reuse completed artifacts, and preflight a resume before invoking an AI provider or writing files.
Gate every handoff
Use deterministic precheck, policy, build, Bicep, and static deployment checks with machine-readable exit states.
Package with provenance
Create a deployment bundle with application source, infrastructure, pipelines, environment parameters, manifests, and SHA-256 hashes.
Estimate and deploy deliberately
Estimate Azure retail cost, then explicitly queue an existing Azure DevOps pipeline without bypassing its approvals.
Integrate with CI
Consume JSON output and JSON Lines run events for status, policy, cost, package, and deployment automation.
li dependencies --source ./biztalk --output ./reports/dependencies
li config check --config migration.config.yaml
li precheck --config migration.config.yaml
li convert --config migration.config.yaml --batch --resume
li status --config migration.config.yaml --json
li package-deployment --config migration.config.yaml
li estimate-cost --config migration.config.yamlMigration Studio for VS Code
Run the migration estate from one visual workspace.
Migration Studio is the visual front end for the same li workflow. Configure a batch, start or cancel runs, and watch every solution move through its governed stages while the CLI remains the execution and audit authority.
- Dashboard: estate-wide progress, concurrency, elapsed time, token usage, stage status, and actionable failures.
- Solutions and settings: manage batch scope and migration configuration without hiding the underlying YAML.
- Agents: inspect the AI activity and review trail behind each solution and migration stage.
- Reports and history: open generated report pages as they arrive and return to previous runs.
Safety by design
AI recommends. Deterministic tools establish facts. People approve consequential decisions.
- Read-only references: source and shared repositories can be locked against writes.
- Write allowlists: generated artifacts stay inside configured repositories and paths.
- Visible unknowns: unsupported behavior becomes evidence requests and review items.
- Explicit deployment: Azure deployment is disabled by default and requires configured authorization.
Current release boundary
Built from the working implementation—not the future roadmap.
The current compatibility implementation is focused on BizTalk sources and Azure Integration Services, including Logic Apps Standard. Broader MuleSoft, TIBCO, healthcare, AWS, and Google Cloud routes remain planned and are not presented as supported capabilities.
Explore the workflow