Skip to content
LambogeniusDocs

Integration Migration Tool

Outputs and reports

The evidence each stage writes, and how to inspect it in automation.

Current compatibility routeBizTalk → Azure Integration ServicesThese docs describe the current buildable implementation.

Review the evidence behind every stage

  • Discovery: flow groups, per-flow analysis, architecture, components, dependencies, patterns, and gaps.
  • Planning: target architecture, action mappings, resource selections, workflow designs, and artifact dispositions.
  • Conversion: Logic Apps, Functions, infrastructure, tests, manifests, checkpoints, and generated repository changes.
  • Validation: project build, policy, Bicep, and static deployment test results.
  • Delivery: checksummed deployment packages, provenance, and explicit deployment records.
  • Cost estimation: Azure monthly cost reports, assumptions, exclusions, and retail price meters.
  • Batch usage: per-stage and per-solution token counts, aggregate totals, model-call counts, and model execution duration.

Use li status --config migration.config.yaml --json to inspect persisted artifacts. Parse the reported stage completeness when gating automation; the status command can exit zero with incomplete stages.