What a Cloud Migration Actually Costs in India (With Rupee Ranges)

Ask three vendors what it costs to move 50 servers to Azure and you will get three numbers that are not comparable: one quotes services only, one bundles the first year of cloud, one leaves out the two months of running both environments at once. None of the three is wrong. They are answering different questions. This article breaks cloud migration cost in India into the four line items that make up the budget, gives planning ranges in rupees for a 20, 50 and 200-server estate, lists what a quote should contain, and gives you the questions that expose what it does not.

The short answer. For a lift-and-shift to Azure at Indian delivery rates, plan for roughly ₹6.5–13.5 lakh one-time for 20 servers, ₹17–35 lakh for 50 and ₹64 lakh to ₹1.5 crore for 200, excluding licences and re-architecture, and then the monthly Azure bill. These are planning ranges for comparing quotes, not prices.

The ranges are planning figures, built from typical migration scoping assumptions and Indian delivery rates in 2026. They assume a lift-and-shift or light replatform to Azure, which is what most Indian mid-market estates should do first; our article on migration versus modernisation explains why. They are not a quote, and they are not CloudSwift's price list. A quote is built from your estate, and it will sit inside these ranges only if your estate is ordinary.

Reviewed October 2026. The ranges reflect Indian delivery rates and Azure list prices at the time of writing, and both move. Treat the tables as a yardstick for comparing quotes, not as a price, and confirm current figures before you budget.

• 70%+: of a lift-and-shift budget is people and process, not cloud meters
• 1–2 months: of running on-premise and Azure in parallel that most estates should budget for
• 10–15%: a sensible contingency to hold back for change orders

The four line items that decide the number

Every migration budget reduces to four buckets. Vendors differ mainly in which of them they put in the quote.

• 1. Assessment and planning. What it pays for: Discovery of every server and dependency, the wave plan, the landing zone design, the business case; Typical share of a lift-and-shift budget: 10–15%
• 2. Landing zone and execution. What it pays for: Building the Azure foundation (identity, network, policy, monitoring), replicating and cutting over each wave, testing; Typical share of a lift-and-shift budget: 50–65%
• 3. One-time cloud and network cost. What it pays for: Replication storage and compute during the move, dual running, data transfer, any new links such as ExpressRoute or a VPN gateway; Typical share of a lift-and-shift budget: 10–15%
• 4. Hypercare and stabilisation. What it pays for: The first 30–90 days after cutover: tuning, right-sizing, backup and DR verification, handover to operations; Typical share of a lift-and-shift budget: 10–15%

The fourth bucket is the one most often missing from a quote and most often needed. A cutover that goes to plan still leaves an estate that has never run in its new home, and the first month on Azure is where the cost and performance surprises surface. Hypercare is not optional; it is either in the quote or it is a change order later.

Where the money goes. In a lift-and-shift, the cloud meters during the migration are the smallest bucket. The budget is engineers, testing and the discipline of doing 50 cutovers without breaking revenue. That is why two vendors with the same Azure bill can be 2× apart on the project price, and why the cheaper one is not necessarily wrong.

Azure migration cost: planning ranges for three estate sizes

The three profiles below are illustrative. Each assumes Windows and Linux servers of ordinary complexity, a mix of application, database and file servers, no mainframe or Oracle Exadata, and a target of Azure Central India or South India. Figures exclude Microsoft licences, which you may already own, and exclude any application re-architecture.

• Typical organisation. 20 servers: 100–300 people, one site, one or two line-of-business applications; 50 servers: 300–1,000 people, several applications, a database tier that matters; 200 servers: 1,000+ people, multiple sites, regulatory scope, 24/7 workloads
• Data to move. 20 servers: 2–5 TB; 50 servers: 10–30 TB; 200 servers: 50–200 TB
• Timeline. 20 servers: 4–6 weeks; 50 servers: 8–12 weeks; 200 servers: 4–6 months, in waves
• Assessment and planning. 20 servers: ₹1–2 lakh; 50 servers: ₹2.5–5 lakh; 200 servers: ₹8–15 lakh
• Landing zone and execution. 20 servers: ₹4–8 lakh; 50 servers: ₹10–20 lakh; 200 servers: ₹40 lakh–1 crore
• One-time cloud and network. 20 servers: ₹0.5–1.5 lakh; 50 servers: ₹2–5 lakh; 200 servers: ₹8–20 lakh
• Hypercare, 30–90 days. 20 servers: ₹1–2 lakh; 50 servers: ₹2.5–5 lakh; 200 servers: ₹8–15 lakh
• Planning total, one-time. 20 servers: ₹6.5–13.5 lakh; 50 servers: ₹17–35 lakh; 200 servers: ₹64 lakh–1.5 crore
• Azure run-rate after migration, per month. 20 servers: ₹1.5–3 lakh; 50 servers: ₹4–8 lakh; 200 servers: ₹15–35 lakh

Three observations on the table.

The project cost scales roughly with server count, but not linearly: the landing zone is built once, and a 200-server estate is cheaper per server than a 20-server one. What breaks the curve is complexity, not count. One badly documented application with twelve undocumented dependencies costs more to move than thirty clean web servers.

The run-rate is the number that matters over three years. For the 50-server estate, ₹17–35 lakh one-time against ₹48–96 lakh a year of Azure spend means the configuration choices described in our guide to the Azure cost calculator are worth more than any negotiation on the project price. A migration that lands on pay-as-you-go without reservations or Hybrid Benefit will cost more in its first year than the vendor saved you on the quote.

The one-time cloud line is small but real, and it is the one that surprises finance, because it arrives on the Azure invoice rather than the vendor's. Replication storage for every disk, the compute for test cutovers, and one or two months of paying for on-premise and Azure at the same time are the usual contents.

Illustrative 50-server lift-and-shift, one-time budget split (₹26 lakh midpoint plus ₹3 lakh contingency)

• Landing zone and execution: ₹15 lakh
• Assessment and planning: ₹3.75 lakh
• Hypercare and stabilisation: ₹3.75 lakh
• One-time cloud and network: ₹3.5 lakh
• Contingency held by the customer: ₹3 lakh

The costs that are not in anyone's quote

Five items sit outside the four buckets and inside the real budget. Decide who owns each one before signing.

1. Internet or ExpressRoute capacity for the data transfer. Moving 30 TB over a 100 Mbps line takes four weeks of saturated bandwidth; most estates either upgrade the link for the migration window or ship the first copy on Azure Data Box Disk (Data Box for 40 TB and above).
2. Licences. Windows Server and SQL Server licences with Software Assurance travel with you through Azure Hybrid Benefit; licences without it are repurchased by the hour. Third-party software with per-server or per-core licensing may need a new agreement for a cloud deployment.
3. Your own people's time. A migration needs application owners available for testing at each cutover. The engagements that slip are rarely short of engineers; they are short of the business user who can confirm the ERP works on Thursday night.
4. Downtime. A cutover window is usually a few hours per wave, at night or at the weekend. The cost of that window is yours, and it should be in the business case even when it is small.
5. The servers you do not move. Every estate has workloads that stay on-premise for compliance, latency or sheer age. They still need to be managed, and the hybrid connection to them is a permanent cost, not a migration cost. Our on-premise and hybrid infrastructure service exists for exactly this remainder.

Hold a contingency. Ten to fifteen percent of the project value, held by you rather than priced into the vendor's quote. It is spent on the dependency nobody mapped, the application that needs a newer OS before it will move, and the second cutover attempt. If it is not spent, it funds the first reservations.

What a migration quote should contain

A quote you can compare with another one has the following in it. If any line is missing, ask for it before comparing prices.

• Scope. What to look for: The server list by name, the applications, the data volume, the target region, what is explicitly out of scope
• Method. What to look for: Rehost, replatform or a mix, per workload, with the reasoning
• Wave plan. What to look for: How many cutovers, in what order, with the dependency map that justifies the order
• Landing zone. What to look for: What is built: subscriptions, identity, network, policy, logging, backup, and whether it follows Microsoft's Cloud Adoption Framework
• Testing. What to look for: Who tests each wave, what counts as a pass, and who signs off
• Rollback. What to look for: For each wave, how the workload returns to on-premise if the cutover fails, and for how long that option stays open
• One-time cloud cost. What to look for: An estimate of the Azure charges during the migration, separate from the services fee
• Hypercare. What to look for: How many days, who is on call, what the response times are
• Run-rate forecast. What to look for: The expected monthly Azure cost after migration, with reservations and Hybrid Benefit shown separately from pay-as-you-go
• Commercial terms. What to look for: Fixed price or time and materials, what triggers a change order, payment milestones, INR or USD, GST

The run-rate forecast is the line that separates a migration vendor from a migration partner. A vendor can move your servers without ever telling you what they will cost to run. A partner cannot.

Seven questions to ask any vendor

Use these in the same order with every vendor and write the answers down. The differences will be more informative than the prices.

1. How did you count the servers, and what happens to the price if discovery finds 20% more? A vendor who ran Azure Migrate or an equivalent discovery before quoting has a defensible number. One who used your spreadsheet does not.
2. Which workloads are you proposing to replatform rather than rehost, and why? The answer tells you whether they have looked at the estate or applied a template.
3. What is in the landing zone, and who owns it after go-live? A landing zone built to a framework is an asset; one built ad hoc is a liability you will pay to rebuild.
4. What is the rollback plan for the database tier? Everything else can be re-copied. Databases cannot be un-cut-over without a plan made in advance.
5. What are the Azure charges during the migration, and who pays them? If the answer is "minimal", ask for the number anyway.
6. What is the monthly Azure cost after migration, and is it quoted with reservations and Hybrid Benefit applied? A forecast at pay-as-you-go rates is a worst case, not a plan.
7. What happens in the first 30 days after the last cutover, and is it in the price? This is the hypercare question. The answer is either a number of days and a response time, or a change order waiting to happen.

What this looks like with CloudSwift

Our cloud and infrastructure migration services are quoted against a discovery run on your estate, not a server count from a spreadsheet, and the quote carries every section in the table above, including the Azure charges during the move and the run-rate forecast with commitments applied. Migration is the first phase of a three-phase model, migrate, stabilise, modernise selectively, and the hypercare period is where the second phase begins.

If you are at the stage of comparing numbers, the most useful thing we can do is run the discovery and give you a planning range for your actual estate, with the four line items separated so you can compare it with anyone else's. Book a migration assessment; the licence and cost questions it raises are the same ones in our Cloud Cost Audit Checklist, which is free and does not need a call.

Frequently asked questions

How much does a cloud migration cost in India?

For a lift-and-shift to Azure at Indian delivery rates, a planning range of ₹6.5–13.5 lakh for 20 servers, ₹17–35 lakh for 50 and ₹64 lakh to ₹1.5 crore for 200, one-time, excluding licences and re-architecture. The monthly Azure bill afterwards is a separate and larger number over three years. Treat these as ranges to compare quotes against, not as prices.

Why do quotes for the same estate differ so much?

Usually because they cover different things. The common omissions are hypercare, the Azure charges during the migration, the landing zone build and the run-rate forecast. Ask every vendor for the four line items separately and the quotes become comparable.

Does Microsoft pay for part of an Azure migration?

Microsoft runs partner and migration funding programmes whose names, eligibility and amounts change regularly, and they are usually accessed through a partner rather than applied for directly. Ask any vendor whether your estate qualifies for current programmes and how that affects the quote; do not build the budget on it until it is confirmed in writing.

How long does a 50-server migration take?

Eight to twelve weeks for an estate of ordinary complexity, including discovery, the landing zone build and three to five cutover waves. Hypercare adds 30–90 days after the last cutover. Timelines slip on undocumented dependencies and on the availability of application owners for testing, not on the technical work.

Should the migration budget include modernisation?

No. Modernisation is a separate programme with a different team, timeline and risk profile. Migrate first, stabilise, then decide which applications are worth re-architecting with a year of cost and performance data behind the decision.