Migration Reports

3 min readReferenceUpdated 2026-05-23

What you'll find here

The safe-to-share report generated from an adjacent runtime migration plan. Reports summarize what can import automatically, what needs manual review, which secrets were skipped, and which validation steps remain before apply mode is considered.

Reports explain the migration without carrying source secrets.

Every item links a source object to its proposed Craik target object. Secret-like source fields are listed by field path only; raw values are not included in JSON output, text output, receipts, logs, or docs examples.

Command

craik migrate report --source ./adjacent-runtime --kind agent-runtime

Use JSON output for automation:

craik migrate report --source ./adjacent-runtime --kind agent-runtime --json

Sections

Section

Purpose

Notes

summary

counts

Counts object maps by importable, partial, manual, unsupported, and skipped-secret status.

importable_objects

automatic

Objects with a direct target schema and target id.

manual_actions

operator review

Partial or manual objects that require operator action before import or enablement.

skipped_secrets

redacted

Secret-bearing objects with skipped field paths and reconfiguration actions.

security_posture_changes

risk review

Authority boundaries that change during migration, such as gateway, sandbox, channel, approval, or credential posture.

unsupported_capabilities

blocked

Objects with no defined Craik migration target.

recommended_next_commands

next steps

Commands for re-running plans, reconfiguring providers, or inspecting unsupported source state.

validation_checklist

release gate

Checks operators must complete before moving from dry-run to apply-mode migration.

Determinism

Report items are sorted by source id. Re-running a report over the same source state produces stable section ordering and status counts, which makes the output suitable for review, CI snapshots, and release readiness evidence.

What's Next

ReferenceMigration mapsThe object map source for migration reports.ReferenceSecret migration policyHow skipped secrets are handled.GuideAdjacent runtime migrationRun inspect, plan, report, and import dry-runs.