Archive instead of delete, almost every time

A record that has stopped being useful clutters every list, and the obvious response is to delete it.

The problem is that records refer to each other. A deleted customer still has invoices, jobs and emails pointing at a name that no longer exists.

Deletion reaches backwards

Last year's reports read this year's records, so removing a supplier changes what a completed quarter appears to have contained.

That is not a display problem. It means two people running the same report a year apart get different answers, and neither can tell why.

Archiving separates today's list from the history

An archived record stops appearing in pickers, searches and active lists while remaining attached to everything that references it.

The list somebody works from gets shorter, and the past stays exactly as it was, which is what most people actually wanted.

The things worth archiving

• A customer or supplier the business has stopped dealing with entirely.
• A staff member who has left, whose work still appears on past jobs.
• A product or service the business has stopped selling.
• A completed project, which nobody needs in a picker and everybody may need in a report.
• A field or a table somebody built and nobody uses.

Each of those clutters a list today and matters in a report later, which is exactly the shape archiving suits.

Deleting is right when nothing points at it

A duplicate created ten minutes ago, a test record, or a typo with no history behind it can go entirely.

The test is simply whether anything else references it. Where nothing does, there is nothing to preserve.

Duplicates need merging, not deleting

Two records for the same customer each hold part of the history, and deleting either loses whatever attached to it.

Our guide to cleaning up duplicates covers merging them so both sets of history survive.

Some records must not be deleted at all

Trust ledgers, invoices issued and anything with a statutory retention period are append only for legal reasons rather than technical ones.

A system that refuses those deletions is protecting the business, and the right response is to correct forwards rather than to remove.

Say what archived means, to everybody

A staff member who cannot find a customer assumes a fault and creates a second record for them, which is worse than the original problem.

A visible way to see archived records, and a note explaining where they went, prevents that entirely.

Control who can archive and who can delete

Archiving is reversible and deletion generally is not, so they deserve different permissions.

Most people need the first. Very few need the second, and separating them takes a minute.

Export before any bulk removal

A bulk delete is the single most regretted action in any business system, and it is always discovered after the backup would have helped.

An export first takes a minute and makes the decision reversible, whatever the intention was.

Archiving a field is not the same as removing it

A field nobody fills in still holds data on older records, and deleting it takes that history with it.

Hiding the field from the form, while keeping the values, clears the screen without losing what those records once said.

Review the archive occasionally

Archived records still take space in exports and searches, and after several years some genuinely have no further purpose.

A periodic review, with a retention rule behind it, is how a business decides that deliberately rather than in a panic about clutter.

What to change first

• Archiving becomes the default for anything with history behind it
• Deletion stays for records nothing else references
• Duplicates merge rather than disappear
• Records with retention obligations stay append only
• Staff can see the archive, so nobody recreates a record
• Archive and delete carry different permissions
• An export precedes any bulk removal