Understanding Data Archiving Costs
Data archiving quotes for a comparable project can vary by a factor of two or three between vendors. This variation is not typically the result of overcharging. It reflects the fact that data archiving cost is not a single figure but the sum of several independent variables, and each vendor prices a different set of assumptions about data volume, retrieval frequency, and regulatory obligations.
These variables affect more than the IT budget. An archiving contract determines what finance pays for storage, what legal can retrieve during litigation, and what compliance can produce during an audit. A buying committee that understands the underlying cost drivers can compare vendor proposals on the actual variables that determine total cost, rather than on a single headline number.
The following sections outline the factors that determine data archiving cost.
Data volume, and what it hides
Volume is the starting point for most cost estimates. Higher data volume generally increases cost. However, a quote based on raw volume alone, without accounting for compression or data structure, provides an incomplete cost basis.
Structured data from a database and unstructured files such as PDFs, emails, or chat logs archive differently and carry different processing costs. A vendor pricing both categories at the same rate per terabyte is misrepresenting the cost structure of at least one category.
Key question: How does the quote break down by data type, and does the rate differ between structured and unstructured data?
Compression, the lever nobody mentions upfront
Compression is one of the largest cost variables in archiving pricing and one of the least standardized. Well-compressed archived data occupies a fraction of its original storage footprint. A vendor with a strong compression engine can charge a higher setup fee and still produce a lower total cost over five years compared to a vendor with a lower headline rate and weaker compression.
Compression ratios are frequently described in sales materials using qualitative terms such as “significant” or “substantial” rather than quantified figures.
Key question: What is the actual compression ratio achieved on data similar to ours, based on production deployments rather than best-case examples?
Where the data lives
Active, high-performance storage costs substantially more than cold storage designed for infrequent access. The boundary between these tiers, and whether the archive resides in the cloud, on-premises, or a hybrid configuration, materially changes the pricing structure.
Cloud archival tiers are commonly advertised with low per-gigabyte storage rates. These rates typically cover storage only and do not include retrieval costs.
Key question: What is the per-gigabyte rate for each storage tier, and what determines when data moves between tiers?
Getting the data back
Storage cost and retrieval cost are separate line items in most archiving contracts. Retrieval speed and cost during an audit or legal hold are frequently the more consequential variable.
Some vendors include retrieval within the base storage price. Others meter retrieval separately, and these fees can increase substantially for organizations with frequent legal or regulatory requests. Two organizations with identical storage volumes and identical contract prices can carry very different total costs depending on retrieval frequency.
Key question: Is retrieval included in the base price, and if not, what is the fee structure per request or per gigabyte retrieved?
How long you have to keep it
Retention period is typically set by regulatory requirement rather than organizational preference, and cost compounds over the retention period. A three-year retention requirement and a ten-year retention requirement represent substantially different total costs even at an identical annual rate, since the longer period accumulates the annual cost over more than three times the duration.
Retention policies are not always verified against actual regulatory requirements, and data is sometimes retained beyond the required period.
Key question: Does our current retention policy match the minimum period required by applicable regulation, or does it exceed it?
The application you kept running for one report
Legacy applications are frequently kept operational, along with associated license fees, administrative overhead, and maintenance contracts, to preserve access to historical records that are infrequently queried.
Archiving the underlying data separately and decommissioning the application eliminates license, personnel, and maintenance costs associated with that application. For organizations operating multiple legacy systems for this reason, application retirement savings can exceed the savings generated by storage cost reduction alone.
Key question: Which currently active applications are being maintained primarily to preserve access to historical data, and what would decommissioning each one save annually?
What regulation requires, not what is nice to have
Regulated industries carry cost requirements that are not discretionary. Immutable storage, commonly referred to as WORM (write once, read many), encryption standards, and audit trail capability all add cost. Financial services organizations are subject to SEC recordkeeping requirements. Healthcare organizations are subject to HIPAA. Organizations holding data on EU residents are subject to GDPR, which carries penalties of up to four percent of global revenue.
Incorporating these requirements at implementation is generally lower cost than addressing a failed audit or penalty after the fact.
Key question: Which compliance certifications and storage standards are included by default in the vendor’s platform, and which are billed as separate add-ons?
How the vendor actually charges you
A flat pricing model is straightforward to compare across vendors. A pricing model segmented into storage, retrieval, migration, and reactivation fees requires more detailed analysis to compare accurately.
Data extraction fees, charged when an organization moves its archive to a different provider, warrant specific attention. Some vendors charge per gigabyte for extraction, and the total cost can reach five or six figures for organizations with large archives. This fee structure affects an organization’s ability to change vendors and therefore affects negotiating leverage for the duration of the contract.
Key question: What is the fee structure for full data extraction if we choose to switch providers, and is that fee specified in the contract?
Why two similar quotes rarely cost the same
These variables do not combine independently. A vendor with strong compression performance can offset a higher per-terabyte rate and still produce a lower total cost. An organization with infrequent legal discovery needs will not be materially affected by a competitor’s retrieval fees. An organization retiring a substantial number of legacy applications may find that application retirement savings alone offset the entire archiving cost, independent of storage pricing.
The relevant comparison across vendor proposals is not the storage cost per terabyte in isolation. It is the projected total cost over a defined period, typically five years, calculated using the organization’s actual data volume, retention obligations, compliance requirements, and retrieval patterns applied against each vendor’s specific pricing structure.
Questions worth asking before you sign anything
What is your typical compression ratio on data similar to ours?
Are retrieval and eDiscovery requests included in the base price, or billed separately?
What happens to our cost if our retention period changes next year?
Do you charge a fee if we later choose to export our data and switch providers?
Which compliance certifications and storage standards come standard, and which are paid add-ons?
How does the price change once we start retiring legacy applications rather than archiving only active data?
Summary
Data archiving cost is determined by eight variables: data volume, compression efficiency, storage tier, retrieval cost, retention period, application retirement potential, compliance requirements, and vendor pricing structure. Each vendor weights these variables differently, which is why proposals with similar headline pricing can produce substantially different total costs.
Organizations that calculate their own data volume, retention obligations, and retrieval patterns against these variables before vendor discussions can evaluate proposals against a defined cost basis rather than a vendor-provided estimate.
A data archiving ROI calculator can translate these variables into projected figures for storage, eDiscovery, and application retirement savings, ahead of vendor discussions.