← All postsHow-to

Document archiving: moving things out without losing them

Document archiving separates what you must keep from what you work with daily. How to decide what moves, what the archive must guarantee, and why deletion is part of it.

How-toD

Document archiving is the deliberate move of material out of daily working storage into somewhere it stays findable but stops getting in the way. It is not backup, which protects against loss, and it is not deletion, which is the end of the line. Confusing the three is why so many organisations hold everything forever: nobody is sure which of the three they are doing, so they do none of them.

What document archiving has to guarantee

  • Findability years later — by content and metadata, not by remembering a folder name somebody chose in 2021.
  • Integrity: the archived copy is the final version, with the working drafts left behind or clearly marked.
  • A retention date attached to each item, so the archive knows when something may go.
  • Restricted but possible access, with a record of who retrieved what.
  • A format that outlives the application. An export nobody can open is a liability dressed as diligence.

Deciding what moves

The trigger should be an event rather than a date where possible: a project closes, a contract expires, an employee leaves, a case concludes. Event-based archiving matches how people think and produces a complete set; time-based archiving produces a slice of whatever happened to be open that quarter. Where a date is the only available trigger, pair it with a completeness check — the question is not "what is old" but "is everything from that matter here".

Archive the context, not just the files. A folder of documents with no index, no dates and no record of who was involved is technically retained and practically useless. One summary page per archived matter costs ten minutes and is what makes the archive answerable.

Deletion is part of archiving

  1. Set a retention period per category before anything is archived, not after.
  2. Record the basis — statutory, contractual or business need — because that is what you will be asked.
  3. Review on schedule and actually delete what has expired, including from backups as the cycle rolls over.
  4. Log destructions with date and approver; an unlogged deletion looks identical to a loss.
  5. Suspend deletion immediately when a legal hold applies, and record the suspension.

The failure everybody repeats

Keeping everything indefinitely feels safe and is not. It raises the cost of every future search, enlarges the blast radius of any breach, and in a dispute hands the other side material you had no obligation to keep. The organisations that handle this well are not the ones with the biggest archives; they are the ones that can say what they hold, why, and until when.

Ettex Storage suits the archive side directly: folders by matter with a retention date and basis recorded per item, restricted access with an exportable log, and a summary page sitting alongside the files. The schedule itself belongs next to it as a records retention schedule rather than in somebody's memory.

Frequently asked

Is archiving the same as backup?

No. A backup is a copy for recovery and is overwritten on a cycle; an archive is the authoritative retained version, kept deliberately for a defined period.

How long should documents be archived?

By category and by the basis for keeping them — statutory minimums, contractual terms, then business need. A single retention period for everything is always wrong in one direction or the other.

What about documents under legal hold?

Deletion stops immediately for anything within scope, and the hold is recorded. Routine schedules must not quietly delete material somebody has asked you to preserve.

MI
Written by Maria I.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.