Bill shocks, exits and official sources
Cloud exit costs and lock-in: what it costs to leave a host, and how to keep the door open
Where exit costs come from (egress, proprietary services, commitments, licences, people's time), an illustrative exit estimate, and the contract and design choices that keep leaving affordable.
Exit costs are what it costs to stop using a host and take everything with you. They come from five places: outbound data transfer (egress) to move your data, re-engineering where you relied on services the next provider does not offer in the same form, commitments and minimum terms still running, licences tied to the old platform, and people's time. For a simple website on shared hosting, exit is cheap. For an application built on one cloud's proprietary databases, queues and identity services, the re-engineering line can dwarf the egress bill. You cannot avoid all lock-in, but you can price it before you sign and keep the door open with a few habits.
This guide belongs to the section overview, why cloud bills blow out. It links to hosting migration costs, renewal price shocks and egress and network charges. Figures are illustrative, ex GST.
Where exit costs come from
| Source | Example | How to estimate it |
|---|---|---|
| Egress | Copying 2 TB of files and database backups out | GB × the provider's data-out rate, unless an exit waiver applies |
| Proprietary services | A managed queue, serverless functions or a proprietary database with no direct equivalent | Developer hours to rebuild or adapt |
| Commitments and terms | Eight months left on a reservation; a 24-month managed hosting term | Remaining committed payments or early termination fees |
| Licences | Licences bought through the provider's marketplace that cannot move | Cost of new licences elsewhere |
| Data formats | Exports in a format the next platform does not import directly | Conversion time |
| People and overlap | Planning, testing, cutover; paying both providers | As in a migration budget |
| Account and domain control | Domain or account held in a contractor's name | Delay, possible dispute |
Some large cloud providers have announced arrangements that waive data transfer charges for customers moving their data off the platform, usually subject to conditions such as notifying the provider and closing the account or completing the move within a set time. These programs and conditions vary and change; check the provider's current terms rather than assuming egress will be free.
An illustrative exit estimate
A small business runs an online booking app on a public cloud, using virtual machines, object storage and one proprietary managed messaging service. Contractor rate: an illustrative $140 an hour.
| Line | Basis | Cost |
|---|---|---|
| Egress: 2,000 GB at $0.12 | 2,000 × $0.12 | $240 |
| Replace the proprietary messaging service | 40 h × $140 | $5,600 |
| Rebuild servers and storage at the new host | 16 h × $140 | $2,240 |
| Remaining commitment: 6 months × $120 | $720 | |
| Testing, cutover, DNS | 10 h × $140 | $1,400 |
| Overlap: 1 month at $900 | $900 | |
| Total | $11,100 |
Egress is 2% of the total. The proprietary service is half. That is a typical shape for small applications: the data is cheap to move, the design is not.
Lock-in is a trade-off, not a mistake
Proprietary managed services often save time and money while you use them: no servers to patch, automatic scaling, built-in backups. The question is whether the saving while you stay is worth the cost of leaving later. A simple test:
- Monthly saving from the proprietary service (versus running an open equivalent yourself): for example $300 a month in admin time avoided.
- Extra exit cost (from the table above): $5,600.
- Break-even: $5,600 ÷ $300 = about 19 months. If you expect to stay longer than that, the proprietary service pays for its own exit.
Habits that keep the door open
- Keep the cloud account and domain in your business's name, with admin access held by the business, not only a contractor.
- Prefer portable building blocks where the cost is similar: standard databases, containers, open file formats.
- Keep your own regular exports of databases and files in a format you can restore elsewhere, stored outside the provider.
- Document the setup: DNS records, firewall rules, scheduled tasks and integrations. A one-page diagram saves hours at exit.
- Align commitments with your horizon: avoid three-year terms on systems you may replace.
- Read the exit clauses before signing: how long data is kept after cancellation, how to request exports, any assistance fees, and data deletion confirmation.
- Test a restore elsewhere once a year: restoring a backup on another platform proves you could leave.
Contracts: exit terms worth negotiating
- A period after termination (for example 30 days) during which you can still retrieve data.
- Exports in a stated, standard format.
- Help with transition at stated rates.
- Written confirmation that data, including backups, has been deleted at the end of retention.
- For managed services: handover of documentation and all credentials.
Exit is also a privacy matter: if the host holds personal information on your behalf, confirm deletion in line with APP 11's requirement to destroy or de-identify information you no longer need.
Frequently asked questions
Is egress always the biggest exit cost?
For large data volumes it can be. For most small businesses, re-engineering and people's time cost more than the data transfer.
Can a provider hold my data if I dispute a bill?
Contract terms often allow suspension for non-payment. Raise disputes early and in writing, and keep your own backups so a dispute cannot stop your business. Small business commissioners can help.
Does the unfair contract terms regime affect exit clauses?
It can apply to one-sided termination or data-retention terms in standard-form small business contracts. See hosting contract terms.
How often should I test that I could leave?
A yearly restore test on another platform is a reasonable rhythm for most small businesses.
Sources
- Office of the Australian Information Commissioner — APP 11 destruction and de-identification of personal information
- Australian Competition and Consumer Commission — unfair contract terms in small business contracts
- Australian Small Business and Family Enterprise Ombudsman — dispute help
- Australian Cyber Security Centre (ASD) — backup and recovery guidance
