Organizing Your Data — Move, Clone & Clean Up

As your vault grows, you may want to reorganize things — move a database to another vault, clone its structure, or remove unused ones. Zero makes this straightforward while keeping your data secure.

Moving databases between vaults

You can move an entire database — its schema and all rows — to another vault:

Open the database you want to move.
Click Move.
Select the destination vault.
Confirm the move.

This is useful when you want to:

Separate personal and work data.
Clean up your default vault.
Archive finished projects to a dedicated vault.

What happens during a move?

Schema and all rows are moved to the destination vault.
Encrypted fields remain encrypted end-to-end; no re-encryption is required.
Attachments (file fields) continue to work. Files stored on disk remain under your local /media folder; DB-stored files move with the data.
If a database with the same name already exists in the destination, rename your database first to avoid conflicts.

Cloning a database (structure only)

Need the same layout for a different purpose? Clone the schema without copying any rows.

Open the database you want to reuse.
Choose Clone (structure only).
Name the new database and pick a vault.
Create it, then start adding data.

Common uses:

Standardizing layouts across teams/projects.
Testing schema changes without touching live data.
Starting a new tracker with a familiar structure.

Template alternative

You can also save a schema as a reusable template in the Template Manager, then create new databases from that template whenever you need.

Deleting databases — soft vs hard

Soft delete

Moves the database to the Bin.
You can restore it later.
Good for temporary cleanup.

Hard delete

Permanently removes the database from disk.
This is irreversible.

Note: Soft-deleted databases remain encrypted on disk while in the bin.

Quick comparison

Action	Moves data	Keeps structure	Affects source	Undo
Move	Yes	Yes	Source database is removed	No (use a backup if needed)
Clone	No	Yes	Source unchanged	Delete the clone
Soft delete	—	—	Moved to Bin	Yes (restore)
Hard delete	—	—	Removed from disk	No

Keeping things tidy

Use clear, descriptive names for databases.
Group related databases into separate vaults.
Clone schemas or use templates to stay consistent.
Periodically review and soft-delete what you don’t need.

Important security note

Moving, cloning, and soft-deleting do not weaken protection: encrypted fields remain fully encrypted at rest. Hard delete permanently removes the database from your system — back up first if you might need it later.

Next Up

Encryption in Zero — How Your Data Stays Safe

Organizing Your Data — Move, Clone & Clean Up