Bill Shocks, Migration, Exit and Official Sources
Cost of migrating to cloud or a new host: one-time costs, parallel running and payback
One-time costs of moving servers to cloud or a new host, the parallel-run period plans miss, and an illustrative payback calculation.
Migrating to cloud or to a new host has one-time costs that plans often understate: assessment and design, re-configuring or re-platforming applications, running old and new systems in parallel, moving data, testing, training and a consultant or partner. These are recovered only if the new setup saves money each year or avoids a cost such as a hardware refresh. In the illustrative example below, a ₹3 lakh migration with ₹50,000 of written credits pays back in about 1.37 years and nets about ₹3.17 lakh over three years. The payback depends entirely on the yearly saving being real. This guide belongs to the bill shock patterns overview.
The one-time costs
| Cost | What it covers | Often missed? |
|---|---|---|
| Assessment | Inventory of servers, apps, dependencies, data size | Sometimes |
| Design | Network, security, backups, region choice | Sometimes |
| Re-configuration | New servers, OS, software installs, DNS, SSL | Rarely |
| Re-platforming | Moving to managed databases or containers | Often underestimated |
| Data transfer | Upload time, data transfer charges from the old host | Often |
| Parallel running | Paying old and new providers for 1–3 months | Very often |
| Testing | Functional and load tests, restore tests | Often |
| Downtime window | Lost sales or overtime during cutover | Often |
| Training | Staff learning the new console or processes | Often |
| Licences | New licences or transfer fees for software | Sometimes |
| Exit fees from old provider | Early termination, notice period, data export | Often |
Common migration routes and their cost drivers
| Route | Main cost driver |
|---|---|
| Shared hosting → VPS | Server setup and security hardening |
| Shared or VPS → managed WordPress or app hosting | Testing plugins, redirects and email moves |
| Office server → cloud VM ("lift and shift") | Licences, network to office, parallel run |
| Office server → managed services | Re-platforming effort, new skills |
| One cloud → another | Data transfer out of the old cloud, re-building managed services |
| Cloud → VPS or dedicated (repatriation) | Re-building what managed services did |
Illustrative migration: four office servers to cloud
| One-time item (illustrative) | ₹ |
|---|---|
| Assessment and design by a partner | 60,000 |
| Building and configuring cloud servers | 80,000 |
| Data transfer and verification | 20,000 |
| Parallel running: one month of the new cloud bill while the office servers still run | 50,000 |
| Testing and cutover weekend | 40,000 |
| Training | 20,000 |
| Contingency | 30,000 |
| Total | 3,00,000 |
The provider confirms ₹50,000 of migration credits in writing. Net one-time cost: ₹2,50,000.
The yearly saving
| Yearly item (illustrative) | Office | Cloud |
|---|---|---|
| Hardware, spread over 5 years | ₹2,00,000 | – |
| Power, UPS and cooling | ₹1,20,000 | – |
| AMC and repairs | ₹80,000 | – |
| Server licences | ₹2,00,000 | Included in the cloud bill |
| IT vendor time on servers | ₹1,80,000 | – |
| Cloud bill after rightsizing, licences included | – | ₹5,40,000 |
| Partner management fee | – | ₹60,000 |
| Total | ₹7,80,000 | ₹6,00,000 |
Yearly saving: ₹7,80,000 − ₹6,00,000 = ₹1,80,000. Count only costs that will really stop. If the IT vendor's retainer stays the same after the move, its ₹1,80,000 is not a saving and the case disappears.
Payback
With a ₹1,80,000 saving growing 5% a year:
- Year 1: ₹1,80,000 (cumulative ₹1,80,000)
- Year 2: ₹1,89,000 (cumulative ₹3,69,000)
- Year 3: ₹1,98,450 (cumulative ₹5,67,450)
The ₹2,50,000 is recovered during year 2: 1 + (2,50,000 − 1,80,000) ÷ 1,89,000 = 1 + 0.37 = about 1.37 years. Net saving over three years: ₹5,67,450 − ₹2,50,000 = ₹3,17,450. These are the migration payback calculator defaults.
When migration does not pay back on cost alone
If the yearly saving is small or negative, the move may still be justified by:
- avoiding a large hardware refresh,
- resilience (power cuts, floods, theft),
- remote access for branch or home staff,
- the ability to grow quickly.
Write these down as reasons, not as hidden savings.
Reducing migration cost
- Clean up first. Delete data and servers you do not need before moving; less to move and less to pay for later.
- Move the simplest workload first to learn.
- Keep the parallel run short with a clear cutover plan, but not so short that you cannot roll back.
- Get credits and partner funding in writing; verbal promises do not count.
- Plan the exit as you plan the entry: document everything so that a future move is cheaper. See exit costs and lock-in.
- Check the renewal or notice terms of the old provider so that you do not pay an extra term. See renewal price jumps.
Tax and compliance points
- One-time partner fees and new cloud bills carry 18% GST; a registered business usually claims credit.
- Hardware retired early may affect depreciation; ask your CA.
- Keep logs during and after the migration as the CERT-In directions require.
- If personal data moves to a new processor, update your contracts and records. See Indian regions and data rules.
FAQ
How long does a small migration take?
For a few servers, often a few weeks to a couple of months including testing. Complex apps take longer.
Do providers really give migration credits?
Some programmes offer credits or partner funding under conditions. Get the amount, conditions and expiry in writing.
Should I re-platform during the migration?
Lift-and-shift first is often cheaper and less risky; optimise afterwards. Re-platforming during the move adds risk.
What is the biggest hidden cost?
Usually the parallel-run period and staff time.
Sources
- CBIC GST — GST on migration services and cloud bills
- CERT-In — log retention during changes
- MeitY — DPDP Act processor contracts
- Income Tax Department — depreciation and TDS
