Code and dependency review
Identify runtimes, frameworks, libraries, custom code and external services. Separate confirmed limits from unknowns that need investigation.
Services
Choose the change the application can support responsibly.
A first review establishes the current system and the business behavior that needs to be preserved.
Language and framework upgrades
Review a suitable target, compatibility changes and test coverage. Use controlled stages rather than assuming a large version jump is straightforward.
Deployment and infrastructure changes
Document how the application is built, configured and released. Review scheduled jobs, storage, queues and other operating dependencies as well as the website process.
Data and interface renewal
Improve agreed screens or move data with explicit mappings and checks. Preserve records, relationships and the useful tasks that depend on them.
Phased replacement
Replace a defined part where the boundary is understood. Agree which system owns each record while old and new parts coexist, and how mismatches are resolved.
Discuss the first review. If a previous build stalled, see abandoned project rescue.