What we do
The first deliverable of a transformation is not a migration list but a decision table: for each workload the cost, gain and risk of moving are calculated separately. Some workloads clearly win in the cloud (variable load, fast growth, geographic spread); some are better on premises (steady load, per-core licensing, data-residency rules).
Migration runs in stages: low-dependency systems first, critical loads step by step after. The rollback scenario for every step is written before the cutover.
Typical projects
Moving test and development environments; migrating web and API tiers to a scalable design; shifting file archives to cloud storage; shrinking the data centre so only what must stay on premises stays.
How we hand over
Two documents remain at the end: the operations guide for the new architecture and the list of systems that were not migrated, with reasons. The second is worth as much as the first — three years later, "why didn't we move this" has a written answer.