Bill Shocks, Migration, Exit and Official Sources
Exit costs and lock-in when leaving a hosting or cloud provider: what to check before you sign
What leaving a host or cloud costs: data transfer out, rebuilding managed services, notice periods and prepaid terms, plus a contract checklist.
Leaving a hosting or cloud provider costs money and time: data transfer out of the old provider, rebuilding anything that depended on its managed services, running both setups during the switch, unused prepaid terms or commitments, and the staff or consultant work. Lock-in is the share of that cost you cannot avoid. You can reduce it from day one by keeping the domain separate, owning your accounts, documenting the setup, avoiding long prepaid terms until a provider has proved itself and reading the exit terms before signing. This guide shows the cost items with an illustrative budget. It belongs to the bill shock patterns overview.
The main exit costs
| Exit cost | What drives it |
|---|---|
| Data transfer out | Volume of files, databases and backups; the old provider's egress price |
| Rebuild of managed services | Managed databases, queues, serverless functions, proprietary tools |
| Parallel running | Paying both providers for weeks or months |
| Unused prepaid term | Shared hosting or VPS prepaid for years; refund terms |
| Commitments | Reserved instances or savings plans that run past the exit |
| Notice period | Contract notice for managed services or dedicated servers |
| Licences | Licences tied to the old provider (licence-included) |
| Domain and email | Domain transfer, DNS changes, mailbox migration |
| People | Planning, testing, cutover |
Data transfer out at exit
Moving data out is egress like any other. Illustrative: 5 TB (5,000 GB) at an illustrative ₹7 per GB = ₹35,000. Some large clouds have announced programmes that waive data transfer charges for customers moving all their data off the platform, usually on request and subject to conditions and time limits. Ask your provider in writing before starting. See egress charges.
Rebuilding managed services
The deeper you use a provider's proprietary services, the more you rebuild at exit. Plain virtual machines, standard databases and open formats move easily; provider-specific serverless functions, queues, identity setups and analytics tools may need redesign.
| Service type | Portability (general) |
|---|---|
| VMs with standard OS | High |
| Open-source databases (self-run or managed) | High to medium |
| Object storage | Medium (similar APIs exist) |
| Container platforms using standard tools | Medium to high |
| Proprietary serverless, queues, AI and analytics | Low |
This is a trade-off, not a reason to avoid managed services; they can save a lot of work while you use them. Just count the exit cost honestly.
Illustrative exit budget: two app servers, a managed database and 5 TB of files
| Item (illustrative) | ₹ |
|---|---|
| Data transfer out, 5 TB | 35,000 |
| Rebuilding database and app servers at the new provider | 90,000 |
| Parallel running, 1 month at the new provider | 40,000 |
| Unused months of a 1-year commitment (4 × ₹6,500) | 26,000 |
| Testing and cutover | 30,000 |
| Total | 2,21,000 |
If the new provider saves ₹1,20,000 a year, the exit is recovered in about 1.8 years (2,21,000 ÷ 1,20,000 ≈ 1.84), before any growth in the saving. Check with the migration payback calculator.
Shared hosting and VPS exits
- Prepaid terms: refunds after the first weeks are often limited. Check the refund policy.
- Backups: download a full backup (files, databases and email) before cancelling; providers may delete data soon after closure.
- Domain: if the domain was registered through the host, unlock it and get the transfer code before cancelling. Keep domains at an independent registrar from the start.
- Email: move mailboxes before changing DNS records, and lower DNS time-to-live a day in advance.
Contract terms to read before signing
- Data export: format, tools and support for export.
- Data retention after termination: how long data is kept and when it is deleted.
- Notice period and auto-renewal.
- Termination fees and refund terms for prepaid periods.
- Exit assistance from a managed service partner: documentation, credentials and a transition period.
- Account ownership: whether the cloud account is in your company's name.
- Data processing terms: deletion or return of personal data at the end of the service, as the DPDP Act expects of data processors acting for you.
How to keep lock-in low from day one
- Keep the domain and DNS independent of the host.
- Keep infrastructure documented, ideally as scripts or templates.
- Prefer open formats for data and backups.
- Keep at least one backup outside the provider.
- Commit only the baseline, for one year at first. See the break-even example.
- Diary renewal and commitment dates. See renewal price jumps.
Tax and records
Keep the old provider's invoices and your GST records; credit claims and audits may need them later. Companies must keep books of account and related records for the periods required by law, so make sure back-ups of accounting data are retained when you close a hosting account. Ask your CA.
Related guides
Plan the entry and the exit together with migration cost and payback.
FAQ
Can a provider refuse to give me my data?
Terms vary, but most allow export during the term. Unpaid bills can lead to suspension, so settle accounts and export before cancelling.
Is multi-cloud a way to avoid lock-in?
Running on several clouds adds cost and complexity. For most MSMEs, good documentation, portable designs and backups outside the provider are enough.
How long does an exit take?
Similar to a migration: weeks for a few servers, longer if managed services must be rebuilt.
Should I tell my provider I am leaving?
Yes, in writing, within the notice period, after you have exported data and confirmed the new setup works.
Sources
- MeitY — DPDP Act duties when a processor's service ends
- CBIC GST — GST records and credit
- Ministry of Corporate Affairs — books of account in electronic form
- CERT-In — log retention that continues after a move
