reversa-strategist

Choosing a legacy modernization migration strategy requires evaluating trade-offs among Strangler Fig, Big Bang, Parallel Run, and Branch by Abstraction. The optimal path depends on your migration brief constraints, paradigm gap, and risk appetite.

Planning a cutover for a legacy system rebuild involves generating a cutover_plan.md derived from your migration context. This plan is produced alongside a migration strategy document and a risk register with explicit risk ownership.

You need a risk register for a paradigm shift migration when the change is large and involves regulatory constraints. It explicitly registers operational risks and assigns risk ownership based on business-rule constraints.

Strangler Fig compares to Big Bang by offering incremental migration versus a single event transition. Evaluating them requires analyzing your migration brief and target paradigm decision to justify the recommended approach with explicit trade-offs.

Parallel Run is applicable for legacy modernization with regulatory constraints when you need both old and new systems operating simultaneously. Selection depends on analyzing business-rule constraints and your target paradigm decision.

To start migration strategy evaluation, you need the migration brief and target paradigm decision artifacts. These inputs enable analysis of business-rule constraints to generate migration_strategy.md, risk_register.md, and cutover_plan.md.