Metrofile Cloud Why people paying for file storage that is not used

For most South African law firms, the data problem is not growing — it has already grown. Years of closed matter files, scanned title deeds, FICA documentation, deposition recordings, email archives and historical correspondence sit on storage, waiting in case someone needs them. POPIA, the Legal Practice Act, the rules of the relevant Provincial Council and a long list of professional obligations make sure they keep waiting.

The retention requirement is non-negotiable. The storage bill, on the other hand, is more flexible than most firms realise.

Where the cost actually comes from

The default at most firms is to keep everything — current matters and concluded ones — in the same cloud storage environment. That environment is usually backup or hot storage, engineered for fast recovery and instant access. It is the right home for the matters the firm is actively working on. It is an expensive home for the twelve-year-old conveyancing file nobody has opened since the transfer cleared.

The savings opportunity sits in that gap.

Two tiers, one obligation

Cloud storage is not a single product. It comes in tiers designed for different jobs.

Hot or backup storage is built for speed: live matters, working files, current systems. It costs more per GB because it has to deliver instant retrieval and continuous protection.

Object storage, sometimes called archive storage, is built for long-term retention at a much lower per-GB cost. It is engineered for durability and scale.

The detail that matters for legal readers: object storage is not offline archiving. Files are not in a vault that needs to be opened on request. They remain accessible on demand. A practice manager pulling a five-year-old FICA document for an audit is not waiting hours; they are retrieving it when asked.

This single point — that the data is still there, still accessible, still under the firm’s control — is usually what settles the conversation for compliance officers and firm IT leads.

What goes where, in a legal context

Once the principle is clear, the candidates for object storage are familiar:

  • Closed matter files and historical correspondence
  • Title deeds, signed contracts and registration documents from concluded transactions
  • Deposition recordings, court bundles and discovery archives
  • Email archives held for evidentiary or regulatory purposes
  • FICA documentation past the active client lifecycle
  • Legacy backups and duplicates of duplicates

These are the categories that grow steadily, never shrink, and quietly inflate the monthly cloud invoice. They are also exactly the categories the firm cannot delete.

The retrieval question — and the fees behind it

A specific concern firms have raised with hyperscale providers: paying once to store data, and again to retrieve it. Industry shorthand calls these ingress and egress fees — the charges for putting data into the platform and for pulling it back out. For a firm responding to a discovery request, a compliance audit or a client query, retrieval is not a hypothetical. It is part of the job.

Cloud Vault S3, the object storage product from Metrofile Cloud, was built without those charges. There is no fee for uploading data, and no fee for pulling it back. What appears on the invoice is what the firm pays, and the pricing stays predictable from month to month.

For firms handling client information under POPIA, there is a secondary point worth noting: the platform is hosted locally, which makes data sovereignty conversations shorter when they come up.

What this is, and what it is not

Object storage is not a compliance product. POPIA, the Legal Practice Act, FICA and Provincial Council rules remain the firm’s responsibility, supported by its retention policy and information governance practices. What object storage does is make the obligation cheaper to meet, by giving the firm an appropriate place to keep what it is required to retain — without paying live-system rates to do it.

Implementation, in practical terms

There is no large IT project here. A workable policy is usually a single paragraph: matters closed for more than [X] days move to object storage; current files remain in active storage; retrieval, when needed, happens on demand. Once the rule is set, the migration runs in the background.

The result is a noticeable monthly saving with no change to how staff work, no change to compliance posture, and no extra steps when a file needs to come back out.

To learn more about Cloud Vault S3, visit https://metrofile.com/cloud/simple-storage-service-s3/?utm_source=tech4law_s3_article_may&utm_medium=referral&utm_campaign=cloud_vault_s3

LEAVE A REPLY

Please enter your comment!
Please enter your name here

18 − ten =