Get started
Your data: exports and deletion
How to export a list or a whole workspace, what the export holds and leaves out, and what deleting a lead or a workspace does today.
Updated 2 October 2026
Exporting one list as CSV
In a workspace's Settings, the General tab has buttons to export that workspace's leads, calls or commissions as a CSV file. These exports need the org.manage permission. The Export CSV button on the Payments page downloads the ledger with the filters you have on screen. In the agency's Settings, Export All Data on the Danger Zone tab downloads one CSV of leads, calls, deals or commissions across every client, with a client_name column on each row. That agency-wide export needs the leads.export permission across the whole organisation, so a member pinned to one client cannot run it. The payments export and the agency-wide export are each written to the organisation's audit log. A deleted lead is left out of every leads export, including the full workspace export below.
The full workspace export
On the same Danger Zone tab, Download full workspace export builds one zip file of everything in a client workspace that SIGNL can export today. Only the organisation owner can start it, and it cannot be started from a SIGNL staff session. The file is built in the background and the download link is emailed to you. The link works for 7 days. One export per workspace runs at a time. You can start one while the workspace is read-only or locked, as well as while it is active.
What the zip holds
| File | What it holds |
|---|---|
| leads.csv and leads.json | Your leads, with each lead's notes in the JSON copy |
| calls.csv and bookings.csv | Every call, and separately the calls booked through a booking page |
| deals.csv, payments.csv, commissions.csv | The deal book, the payments ledger and commission entries |
| form_submissions.csv and tasks.csv | Form submissions and tasks |
| events.json | The events recorded against your leads |
| config/automations.json, config/forms.json, config/pipelines.json, config/booking_pages.json | How your automations, forms, pipelines and booking pages are set up |
| recordings.json and vsl.json | Recordings as download links, and your videos by title and Bunny Stream id |
| manifest.json | What is in the file, what is not, and how many rows each dataset has |
| Recordings are not inside the zip: each one is listed with its own download link, which also works for 7 days. | |
| For videos the export carries titles and Bunny Stream ids only, with no download links. |
What it never holds
API keys, webhook signing secrets, connection credentials, passwords and booking cancel or reschedule tokens are never exported. Anything in the exported settings that is, or looks like, a credential is replaced with a redaction marker, and the manifest lists where each one was.
What it does not hold yet
The manifest names what the export does not cover yet, including offers, payment plans, contracts, cadences, webinars, tracked links, team and talent records, SOPs and files uploaded through your forms. A dataset is read up to 100,000 rows, and one that reaches that ceiling is listed in the manifest as cut short rather than shipped as if complete.
When a workspace leaves active use
A workspace becomes read-only for one of five reasons: a downgrade, a closed account, an unpaid invoice, a payment dispute or a pause. While it is read-only you can still view and export everything. After 30 days read-only it locks, and a locked workspace's data is kept but not shown. Its deletion date is 90 days after it became read-only, and it does not move when the workspace locks. The owner is emailed a warning 14 days and again 7 days before that date. A pause holds the clock, so a paused workspace is never locked or deleted while the pause runs, and an open payment dispute stops deletion while it is open. When the owner resubscribes, workspaces that went read-only after a downgrade, a close or an unpaid invoice come back to active, up to the plan's client limit. A workspace that comes back keeps its data and loses its deletion date.
What deleting does today
A lead
Deleting a lead marks its record deleted rather than removing it from the database. It needs the leads.delete permission, and each deletion is written to the audit log. Erasing one lead's personal data from SIGNL entirely is not available yet.
Archiving and offboarding a client
On the agency's Clients page, archiving a client takes it out of the agency view and Login As, and you can restore it from Archived clients. In a workspace's own Settings, Archive sets the client's status to inactive and Offboard sets it to churned; both change the status only.
A whole workspace
Workspace deletion is a daily job that only deletes once SIGNL has switched it on; until then it is a dry run that records which workspaces it would delete and deletes nothing. When it is on, it deletes a workspace only once it is locked, its deletion date has passed, both warnings have gone out and no legal hold or open dispute applies. The deletion runs in one database transaction, and if it fails, nothing outside the database is touched. After the database delete, the job removes the workspace's stored files and videos, releases its phone numbers on SIGNL's Twilio account, removes its app connections and detaches its custom domains.
Some copies sit outside SIGNL's reach, and each deletion records them: ad audiences synced to your ad accounts, email delivery logs, Twilio message and call logs, audio sent to Deepgram, and database backups for up to 7 days after deletion.