Data · Export and backups

Export, import and backups

How to export contacts, companies and deals to Excel, import them back without duplicates, and keep a daily copy of all your data in your own storage.

Exporting a table

The contacts, companies and deals lists have an "Експорт" (Export) button: CSV or XLSX with exactly what the table shows, filters and search included. On Settings → "Дані" (Data) → "Експорт та імпорт" (Export and import) you can export everything you can see.

You export only what you see: a manager without access to others' contacts does not get them in the file. Export and import share the same columns: id, the record's fields, company or stage by name, owner by email, tags separated by commas, custom fields by key.

Import

A row with the id of an existing record updates it. Without an id, Bordee looks for a duplicate (a contact by phone or email, a company by code or name) and otherwise creates a new record. So your own export, fixed in Excel, goes back in place without duplicates.

Export and import each need their own role permission.

Backups

Settings → "Дані" (Data) → "Резервні копії" (Backups), administrators only. Bordee puts a copy of all the business's data into your storage every day:

Storage: any S3-compatible service, such as AWS S3, Cloudflare R2, Backblaze B2, Wasabi, Hetzner Object Storage. Endpoint, bucket, region, folder and keys. We recommend a write-only key: with it, earlier copies cannot be read or deleted.
Daily copy: once a day at night; a failed copy is retried.
Encryption: a ZIP with AES-256 and your password, which opens in 7-Zip, WinRAR or Keka.

Buttons: check the connection (writes a test file), make a copy now (queues one), and download an archive (built for download from the history within an hour). The history shows time, size, row counts and errors.

What the archive holds

manifest.json        what the archive is, schema version, tables with row counts and checksums
data/<table>.ndjson  each table's rows, one JSON per line
portable/*.csv       contacts, companies and deals: the same files as an export
README.md            how to read the archive and what to reconnect after a restore

Files (the media library, attachments, the Gmail archive) go to the storage as separate objects, new ones only. The archive never contains secrets: channel tokens, passwords, service keys or API tokens.

Restoring

An archive never overwrites a live workspace: it is restored into a new one. Write to us and we restore the data from your archive. After a restore, channels have to be connected again and staff passwords set anew.