What you can export
The exports give you the underlying data as you put it in plus what TalkValue derives (de-duplication keys, channel attribution). They don’t include behavioral analytics summaries (those are recomputed on import).
In these CSVs, a value that starts with
=, +, -, or @ gets a leading apostrophe (') so spreadsheet apps don’t run it as a formula. A phone number such as +1-415-555-0199 exports as '+1-415-555-0199.
People export
Two paths, same data. From the CLI. The fastest repeatable export is:talkvalue path person export.
From the dashboard. Open Path → People. The toolbar above the table has an Export CSV button that downloads people.csv with every person in the workspace, using the same columns as the CLI export.
Event registrant export
Runtalkvalue path event person export <eventId> to emit a CSV of every registrant on that event: name, email addresses, company, job title, phone numbers, address, avatar and social URLs, and the date the person joined the event. For an event still taking registrations, export at the end for the final state.
Badge event exports
Open an event in Badge and use the Export button in the page header. It offers two CSVs, and both write timestamps in the event’s own time zone, formattedYYYY-MM-DD HH:MM:SS. Booth leads download separately from Lead Capture.
Attendees. One row per attendee on the event, with these columns:
Name, First Name, Last Name, Email, Company, Job Title, Phone, Ticket Name, Coupon Code, Status, Origin, Barcode, Last Checked In At.
Origin says how the attendee joined the event: EXTERNAL (synced from Eventbrite or Luma), IMPORT (a CSV upload), or WALK_IN (added at the check-in desk).
Badge print log. One row per badge printed at the event. Use it to reconcile label stock against check-ins, or to trace which station printed a given badge.
Booth leads. One row per lead for one booth, earliest scan first, with the columns
Name, Email, Company, Job Title, Scanned At, Rating, and Note. Download it from the booth’s row on Lead Capture, or from the booth’s own console. See Lead capture.
Round-trip exports (CLI)
The CLI gives you both halves of the round-trip when you need to export, transform externally, and re-import. Remove the leading apostrophe from values such as phone numbers before you re-import an exported file. See Recipe: CSV import for the canonical pattern, or usetalkvalue path person list --json for structured output when CSV columns aren’t enough.
Account-level portability
For a full account-level portability package (everything tied to your account across every workspace, in a single bundle), email support@trytalkvalue.com from the account email. Include the account email, your preferred format (JSON, CSV, or both), and the workspaces to include (or “all”). Support replies within 2 business days and delivers a signed download link valid for 7 days. The package is account-scoped: it captures data tied to your account, not the entire workspace. For a full workspace bundle, use the per-resource exports above as the workspace Admin.Retention after deletion
When you delete a workspace (General → Delete workspace), data is removed from the live application immediately and purged from backups within the standard retention window. After the purge, the data cannot be restored. When you delete your account, your account identity is removed and your memberships are dropped from every workspace. Workspace data you created stays with the workspaces, and each workspace keeps its activity history intact. Request a full data wipe explicitly if you want every trace removed. Export anything you want to keep before either deletion. There is no undo window once the deletion completes.Related
talkvalue path person export. CSV export from the CLI.- Recipe: CSV import. The matching round-trip pattern.
- People. The dashboard surface that the export mirrors.
- QR scan check-in. Where the badge print log entries come from.
- Delete your account. Pull a copy first.
- General. Workspace lifecycle, including deletion.