Plan the migration of 300 applications from an on-premises data center to the cloud in 18 months.
Short answer
Discover and map dependencies, classify applications with the 7 Rs, build the landing zone and a migration factory, group applications into dependency-based waves starting with low-risk ones, use replication-based cutovers with rollback plans, and track progress, cost and decommissioning.
Detailed answer
- Months 0–3: discovery tools and interviews, dependency mapping, 7 Rs disposition, TCO/business case, landing zone, team training, pilot migrations (5 apps).
- Months 3–15: waves of 20–30 apps grouped by dependency and business calendar; rehost/replatform at scale with automation (AWS Application Migration Service, Azure Migrate, Google Migrate to Virtual Machines); databases via DMS/replication; cutover runbooks and rollback criteria.
- Months 12–18: remaining complex apps, decommission hardware, exit contracts; optimization (rightsizing, managed services).
- Governance: weekly wave reviews, risk log, KPIs (apps migrated, incidents, cost vs plan).
What the interviewer expects
Discovery and dependency focus, factory approach, risk management, realistic timeline.
Common mistakes to avoid
Migrating without dependency mapping, ignoring licensing, no rollback plan, leaving optimization for "later" indefinitely.