Cloud Migration: Business Case and Common Failures
A retailer does not move to the cloud because servers are boring. It moves because festival traffic can double overnight, product teams need faster releases, and a one-hour outage can damage both revenue and trust.
The trap is to treat cloud migration like shifting furniture from one building to another. The winners redesign the operating model; the failures simply move old problems to a more expensive address.
- Cloud migration means moving applications, data, infrastructure and operating processes from on-premise or one cloud environment to another.
- The business case has four lenses: cost, speed, resilience and strategic flexibility.
- Do not assume cloud is automatically cheaper. It becomes economical when workloads are right-sized, governed and actively managed through FinOps.
- The main migration paths are retain, retire, rehost, replatform, refactor and repurchase.
- The biggest failures are weak business ownership, poor application dependency mapping, security gaps, cost sprawl and unchanged ways of working.
- Track value using TCO, unit cloud cost, availability, deployment frequency, change failure rate and MTTR.
- Interview answer: start with business objective, segment workloads, choose migration path, size benefits and risks, then define governance.
Big Picture: Cloud Migration Is a Value Case, Not a Server Move
A strong cloud migration case starts with the business problem, not the technology. If the company is solving slow product launches, poor uptime, data fragmentation or high fixed infrastructure cost, cloud may be the enabler. If the problem is unclear, first apply defining the problem before solving it before recommending migration.
Core Explanation: Build the Business Case Before Choosing the Cloud
The big idea is simple: cloud migration is justified only when the future operating model creates more value than the migration cost and risk. That value may come from lower total cost, faster time-to-market, better availability, stronger data access, or scalable customer experience.
The Four-Lens Business Case
Use these four lenses to avoid sounding like a technical brochure:
The Six Migration Paths: Do Not Treat Every Workload the Same
One of the easiest ways to spot a shallow answer is the phrase “migrate everything to cloud.” In real migrations, each application gets a path based on business criticality, architecture, compliance and cost.
Good Business Case vs Weak Business Case
A weak case says “cloud will reduce cost.” A strong case says “these workloads have variable demand, we will retire redundant systems, right-size compute, improve release frequency, and govern spend weekly.” That is the difference between intent and economics.
The Numbers: What to Measure in a Cloud Migration
There is no universal “good” cloud number because workloads differ. A payment system, analytics sandbox and ecommerce search engine have different economics. In interviews, say that the strongest comparison is against the company’s own baseline and service-level objective.
Worked Example: A Simple Cloud Business Case
Suppose a company spends ₹10 crore per year running a customer-facing application in its own data centre. A proposed cloud migration has ₹3 crore one-time migration cost and ₹7.5 crore expected annual run cost after optimization.
The three-year comparison is:
- Status quo cost = ₹10 crore x 3 = ₹30 crore.
- Cloud cost = ₹3 crore migration + ₹7.5 crore x 3 = ₹25.5 crore.
- Three-year saving = ₹30 crore - ₹25.5 crore = ₹4.5 crore.
- Payback period = ₹3 crore migration cost / ₹2.5 crore annual saving = 1.2 years.
Now add the consulting nuance: this is attractive only if service reliability, security, compliance, vendor lock-in and operating capability are acceptable. If the business case is actually a cost-reduction case, compare it with other levers from recommending cost reduction without killing growth before assuming cloud is the best lever.
Common Failure Patterns
Most cloud migration failures are not caused by the cloud provider. They happen because the firm migrates technology without changing ownership, architecture, controls and behaviour.
Definitions You Can Say in One Breath
- Cloud migration: moving applications, data, infrastructure and operating processes from on-premise or one cloud environment to another.
- Cloud computing: NIST describes cloud as on-demand network access to shared configurable computing resources (NIST SP 800-145).
- Business case: the quantified and qualitative justification for investing, including benefits, costs, risks, timing and ownership.
- TCO: total cost of ownership across build, run, migration, people, tooling, risk and exit costs.
- Landing zone: the governed cloud foundation covering accounts, networks, identity, security, monitoring and policy.
- FinOps: the operating discipline that connects cloud spend, engineering choices and business accountability.
Case Study: Swiggy and the Business Case for Elastic Digital Scale
Swiggy shows why cloud is often a scale, speed and reliability decision first - with cost control becoming valuable only when governance catches up.
Swiggy’s business has sharp demand variability: lunch peaks, dinner peaks, city-level events, rain, offers and festive spikes can change traffic patterns quickly. Owning fixed infrastructure for every possible peak would be strategically limiting, while under-provisioning would hurt customer experience.
The AWS customer story on Swiggy describes Swiggy’s use of AWS to support its digital platform. The primary business driver is elasticity - the ability to scale technology capacity around demand. Supporting drivers include engineering speed, managed infrastructure, observability, automation and the ability to support data-heavy use cases across ordering, logistics and customer experience.
The lesson is not “Swiggy wins because it uses cloud.” The better answer is: cloud supports Swiggy’s variable-demand operating model; the win comes from elasticity as the primary driver, supported by engineering capability, data systems, automation and spend governance.
How AI Changes Cloud Migration
AI makes cloud migration more strategic because cloud is increasingly the platform on which AI workloads, data pipelines and digital operating models run. It also makes migration execution faster, but not risk-free.
Practical student workflow: upload a company annual report, cloud migration notes and a vendor case study into NotebookLM. Ask it to generate: “What is the migration business case, which workloads should move first, what risks should a consultant test, and what metrics prove value after go-live?” Then practise the answer aloud using AI as a mock interviewer.
Interview Relevance
A retail bank wants to migrate its core digital channels to the cloud. Build the business case, identify risks and explain why such migrations fail.
In consulting-style answers, say “I would not migrate by application count; I would migrate by value, dependency and risk.” That single sentence signals maturity.
Common Mistake
The mistake: saying “cloud migration reduces cost” as if it is automatic. Why it costs candidates: it ignores migration cost, over-provisioning, duplicate environments, vendor lock-in and the operating model shift. One-line fix: say “cloud reduces cost only when workloads are right-sized, waste is retired and spend is governed through FinOps.”