Storage migration economics come down to four costs: the storage rate at the destination, the retrieval fee to read data once it is there, the egress charge to move it out of its current location, and the one time cost of the transfer itself. A move to a colder tier or another provider only pays when the lower storage rate, applied over how long the data sits, exceeds the egress to move it plus the retrieval you expect to pay. Cold, rarely accessed data with a long retention life is the clear win. Frequently read data is where archive tiers and cross cloud moves backfire, because retrieval and egress quietly erase the headline saving.
Here is how each cost behaves and how to find the break even before you commit to a migration.
What are the four costs in any storage move?
- Storage rate. The headline price per unit per month at the destination tier. Archive and cold tiers can be a fraction of standard, which is what makes the move tempting.
- Retrieval fee. Many cold and archive tiers charge to read data back, sometimes with a delay. This is the cost most teams forget, and it scales with how often you actually access the data.
- Egress. Moving data out of a cloud carries data transfer charges that can dwarf the storage saving for large datasets. Egress is materially cheaper on OCI than on the hyperscalers, which changes cross cloud maths.
- Transfer and operations. The one time cost to copy the data, plus request and operation charges that add up for datasets made of many small objects.
How do you find the break even?
Express the decision as a simple comparison over the data's expected life. The saving is the difference in storage rate multiplied by the volume and the number of months the data will sit. The cost is the egress to move it, plus the transfer and operations, plus the retrieval you realistically expect across that life. If the saving over the retention period clears the move and retrieval cost with margin, the migration pays. The two variables that decide it are access frequency, which drives retrieval, and retention length, which drives how long the cheaper rate compounds. Cold data held for years almost always clears. Warm data read weekly rarely does once retrieval is honest.
How does this differ across the four clouds?
The shape is consistent but the rates and rules differ. On AWS the choice runs from standard through infrequent access to archive tiers, each with its own retrieval fee, and lifecycle policies automate the transitions; the move from gp2 to gp3 volumes is a standing win on block storage that is separate from object tiering. On Azure, blob access tiers behave similarly and lifecycle management moves data automatically. On GCP, storage classes from standard to archive carry retrieval and minimum storage duration rules. On OCI, the lower egress pricing meaningfully improves the case for moving data out or running data heavy workloads there. Always verify the current published rates rather than relying on memory, and treat any figure here as indicative.
A worked example
A Fortune 500 retailer planned to push a large analytics dataset to an archive tier to cut storage cost, expecting a clean saving. Modelling the access pattern showed the data was read often enough by downstream jobs that retrieval fees would have wiped out most of the storage saving and added latency. We instead moved genuinely cold historical partitions to archive, kept the actively queried partitions on a warmer tier, and automated the transition with a lifecycle policy so data aged into the cheaper tier only once access fell off. The targeted move captured a durable saving the blanket move would have lost. It was one lever in a program that left the estate materially lighter. Figures are verified against billing data and anonymised.
Frequently asked questions
When does cloud storage migration save money?
Why do archive tiers sometimes cost more?
Does egress affect storage migration decisions?
Model the move before you pay to make it
We model storage migration economics across AWS, Azure, GCP, and OCI so a move only happens when retrieval and egress leave a real saving behind. Independent and buyer side, with zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or no risk Gainshare basis. Book a strategy call, and follow more in The Cloud Spend Navigator.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.