vulkro-sf migration-risk
Assesses what will break when you migrate one org's metadata onto another.
vulkro-sf migration-risk ./source-org ./target-org
vulkro-sf migration-risk ./source-org ./target-org --format json > migration-risk.json
Both arguments are offline snapshots (retrieved metadata folders or SFDX source trees), the same inputs consistency and metadiff take. It builds a component map and reference graph for each.
| Finding | Meaning |
|---|---|
SF-MIGRATION-RISK-001 | Breaking reference: source references a custom component the target is missing. |
SF-MIGRATION-RISK-002 | Deprecated API blocker: a target Apex class, trigger or flow is pinned to apiVersion 30.0 or lower. |
SF-MIGRATION-RISK-003 | High risk overall: the rolled-up verdict is HIGH or CRITICAL. |
It is static only. Dynamic SOQL, Type.forName dispatch, managed-package callers and live-org-only wiring are invisible, so confirm with a deploy dry run against the target org.
| Argument or flag | What it does |
|---|---|
<SOURCE> | The org being migrated from. |
<TARGET> | The org being migrated onto. |
--format <table|json> | Output format. Default table. |
Exit codes
| Code | Meaning |
|---|---|
0 | Low risk: nothing found. |
1 | Risks found and reported. |
2 | Error (unreadable folder, no metadata in either, unknown --format). |