Home/Knowledge Base/Security & Compliance/Backups, Reliability, and Getting Your Data Out
Back to Security & Compliance

Backups, Reliability, and Getting Your Data Out

4 minBeginnerLast updated: January 2, 2026

Backups, reliability, and getting your data out

The protection that matters most day to day

Most data loss is not infrastructure failure. It is someone removing something they should not have.

UniAsset is designed so that is hard to do.

Archive, never delete. Assets, documents, images, people, locations, departments, categories, statuses, custom fields, PM rules, and checklist templates all archive rather than delete. History stays attributable and the action is reversible.

History is append-only. Asset timelines, billing events, escalation logs, stock ledger rows, and incident snapshots are written once and never modified or deleted — by anyone.

Hard deletion is reserved for the deliberate erasure of an entire organization, which is Owner-only and carries a 30-day recoverable grace period.

So the everyday recovery path is not a restore request. It is unarchiving.

Restoring something

RemovedHow to get it back
An archived assetRestore it
An archived document or imageUnarchive it — the file was retained, and the storage quota is re-added
An archived person, location, category, or departmentUnarchive it
A deactivated userReactivate them
An organization pending deletionCancel the deletion within the 30-day window

Resilience

UniAsset is delivered as multi-tenant SaaS on managed cloud infrastructure. There is no self-hosted deployment, which is a deliberate product decision — operational complexity stays on the platform's side rather than yours.

The application is built to degrade gracefully rather than fail outright. A transient database problem is retried once; if a non-essential part of a page still cannot load, that section offers an inline retry while the rest of the page keeps working.

Keeping your own copy

Whatever the platform does, keeping your own extract is good practice — particularly before anything irreversible.

Assets, reports, and the Fixed Asset Register export to CSV, Excel, and PDF.

Export before:

  • Deleting an organization
  • A large bulk update
  • A migration
  • A year-end close

The Fixed Asset Register snapshot is the one place a report becomes a fixed artefact, which makes it the right thing to keep at year end.

See How to export your data.

Important An export is a point-in-time extract, not a restore path. There is no route to re-upload an export and reconstruct an erased organization.

Organization deletion is genuinely permanent

Once permanent erasure completes, no customer file remains and there is no recovery.

The 30-day grace period exists precisely because that is irreversible. Use it.

Related articles

Need Help?

If you have questions not covered in this article, our support team is here to help.

Contact Support