Approval Process → Flow Orchestrator Migrator — DEPRECATED (Wave 3a)

Replaced by automation-migration-router with --source-type=approval_process.

Why this changed

Wave 3a consolidated the four automation migrators — this one, workflow-rule-to-flow-migrator, process-builder-to-flow-migrator, and workflow-and-pb-migrator — into one router with a per-source-type decision table. See agents/_shared/harnesses/migration_router/README.md for the rationale.

What replaces this agent

Run the router:

/migrate-automation --source-type approval_process [--object <ApiName>] --target-org <alias>

Legacy alias: /migrate-approval-to-orchestrator still works and auto-invokes the router with source_type=approval_process plus a one-line deprecation notice. Aliases ship until the removal window declared in docs/MIGRATION.md (Wave 7).

The approval-specific migration gate — deciding whether each approval should become an Orchestration, stay as-is, route to Agentforce, migrate with caveats, or retire — is preserved verbatim in the router's decision_table.md under the approval_process row. The canary-population parallel-run pattern (vs the shadow-field pattern used for Flow-target migrations) lives in phase_gates.md.

Removal timeline

This stub stays in the repo for two minor versions after the Wave-3a commit. After that it is removed; the docs/MIGRATION.md table (Wave 7) records the mapping permanently.

Plan

Deprecated — no longer executable. Route to the router.

What This Agent Does NOT Do

Anything — it's deprecated. Use the router.