Quick start

Configure and run a single migration

1. 1
   Create a starter configuration.

   li config init --file migration.config.yaml

2. 2
   Edit source, application-starter, generated-output, report, provider, and policy settings.

   Keep source, starter, shared infrastructure, and pipeline-template repositories read-only.

   For the individual commands below, use single mode with a separately prepared writable application target and repository scaffolding disabled. Use batch mode when the CLI should copy a read-only starter into a generated target, even for one solution.

3. 3
   Validate configuration and provider authentication.

   li config check --config migration.config.yaml
   li auth status --provider codex

4. 4
   Run the persisted migration stages.

   li precheck --config migration.config.yaml
   li discover --config migration.config.yaml
   li plan --config migration.config.yaml
   li convert --config migration.config.yaml
   li test --config migration.config.yaml
   li package-deployment --config migration.config.yaml

5. 5
   Estimate Azure monthly running costs before deployment.

   li estimate-cost --config migration.config.yaml

   Open azure-cost-summary.md in the configured report directory. Review the environment, currency, monthly total, assumptions, and exclusions. Cost-estimation walkthrough →

6. 6
   Review status, reports, and recorded usage.

   li status --config migration.config.yaml

   Check each command's exit code and report before continuing. Batch runs also provide end-of-stage token summaries; direct single-stage commands do not currently provide that accounting. Status output can be incomplete even with exit code zero.

Add --log-file <path> to long-running stages. Use --log-level debug or --log-level verbose when troubleshooting.