I will examine the current system and produce a practical migration plan before implementation begins. The deliverable can cover the current state, target architecture, dependency sequence, data or schema changes, validation gates, rollback controls, cutover steps, and a phased execution backlog.

This is suitable for framework upgrades, database migrations, cloud moves, platform changes, and major dependency transitions. The outcome is a proceed, revise, or stop decision supported by a sequenced plan.

Implementation, destructive testing, production credential handling, and open-ended consulting are excluded unless separately scoped.

Buyer supplies: repository access or technical evidence, current stack, target stack, deployment context, known constraints, required deadline, and the reason for the migration.