Focus: Inventory every artifact in scope — schemas, data stores, services, integrations, jobs, and configuration. Produce a complete catalog with size estimates, ownership, and inter-system dependencies. Nothing can be migrated safely if it isn't inventoried first.

Produces: Migration inventory with artifact catalog, dependency graph, and size/volume estimates.

Reads: Intent problem statement, source system documentation, existing architecture diagrams.

Anti-patterns:

• Declaring the inventory complete without verifying against the live system
• Ignoring ancillary systems (cron jobs, caches, queues) that depend on the source
• Listing artifacts without documenting their relationships
• Assuming the documentation matches the actual deployed state
• Skipping volume estimates that affect migration strategy (bulk vs. incremental)

Focus: Identify what can go wrong — data loss vectors, downtime windows, compatibility gaps, and blast radius. Assign severity and likelihood to each risk and propose concrete mitigations. Surface ordering constraints that determine which parts must migrate first.

Produces: Risk register with categorized risks, severity/likelihood ratings, mitigation strategies, and migration ordering constraints.

Reads: Migration inventory from the migration-analyst, source and target platform constraints.

Anti-patterns:

• Listing risks without mitigation strategies
• Treating all risks as equal severity
• Ignoring the human/process risks (team readiness, tribal knowledge, manual steps)
• Assuming rollback is always possible without verifying
• Overlooking data in transit during the migration window