What cloud migration actually changes

Moving a workload changes who can reach it, how it is deployed, how it is backed up, and how a failed release is reversed. A diagram of cloud services does not answer those questions.

Decide the boundary first

Identity, network access, and the database path should be designed before any server is copied. If the database cannot be reached safely from the application, the rest of the design is premature. Public database access is not an acceptable shortcut.

Move one workload with a rollback

Prove deployment, backup restore, and monitoring on a single workload. Expand only after that path has been used, not merely documented.