Skip to main content
Back to Blog
data management archive history ux

Archive and Soft Delete

Swifty Team Aug 15, 2025 2 min read

Deletion is often the wrong choice, even when it feels like the right one.

A contact who left the organization, a project that was cancelled, an invoice that was voided — these records have history attached to them. Other records reference them. Activity trails mention them. Deleting them creates gaps that are hard to explain later.

Archive gives you a better option.

Archive vs. Delete

When you archive a record, it's removed from your active views without being permanently destroyed. Your list of active projects no longer shows it. Your reports don't include it. Your team doesn't have to scroll past it.

But it's still there. You can find it by switching to the archive view. You can restore it if circumstances change. You can reference it in reports that need historical completeness.

Permanent deletion is still available for records where it's genuinely appropriate. But archive is now the default option — the choice that preserves your data's history while keeping your active workspace clean.

Restoring Records

Archived records can be unarchived with a single action. If a project is put on hold rather than cancelled, it lives in archive until work resumes. When the team is ready to pick it back up, restore it and it returns to the active list with all its data intact.

This is significantly better than recreating a record from scratch, which loses the history attached to the original.

Archive Filters

List views now include an archive toggle. By default, you see active records. Switch the toggle and you see archived records instead. Combined with your existing filters and search, finding a specific archived record is as easy as finding an active one.

Some reports and analytics include archived records by default where historical completeness matters — revenue reporting, for example, shouldn't exclude voided invoices.

The Practical Effect

Teams that adopt archive over delete find their active views stay cleaner and their historical data stays intact. Less noise in daily work, more context when reviewing history. A small but meaningful improvement to how your workspace ages over time.

Related posts

Composed Data Sources

Chain and relate data sources for rich dashboards — compose complex data views from simpler sources without writing code.

Computed Expressions

Transform data with template expressions and built-in functions — format, combine, and derive values from your data without code.

Cross-Source Data Joins

Combine data from multiple sources in one view — join records from your database with data from external services using a shared key.