CedarHealth is moving a legacy clinical application with many undocumented database and network dependencies. Downtime tolerance is low. What should guide the migration sequence?

1. Measure success only by how many servers are copied.
2. Select the newest service for every component without compatibility checks.
3. Move all components simultaneously before documenting dependencies.
4. Discover dependencies, rehearse representative migrations, and use phased cutovers with measured recovery plans.