What can I export from the dashboard?

Every primary table exports to CSV: jobs, companies, job seekers, job alert subscribers, blog posts, blog authors, and blog tags. Open the '...' menu in the table toolbar and choose Export. Employer accounts are still exportable over the API. The jobs export includes per-job views, apply clicks, and native application counts. Application records themselves are not exportable by the board operator; they belong to the employer's hiring pipeline.

Where is the Export action?

Each table has a '...' menu in its toolbar, next to the primary action. Export sits inside that menu, so the same step works on Jobs, Companies, Job seekers, Job alerts, and the blog tables.

Does export re-import cleanly?

Yes for jobs, companies, and blog posts. Those exports use the same field vocabulary as the matching CSV import, so a file you export can be re-imported without remapping columns.

Are candidate resume links in the export public?

No. The candidates export includes authenticated resume download links, never public file URLs. Only signed-in operators with candidate read permission can open them.

How large an export is supported?

Typical boards download immediately. Exports above 10,000 rows switch to a 'Preparing export...' state and produce a download link when ready, up to a hard cap of 200,000 rows.

Can I export over the API?

Yes. Call GET /api/v1/{entity}/export with format=json for an inline response (up to 10,000 rows) or format=csv to run an async operation. Poll the operation, then download the finished CSV from the download endpoint. This matches the existing subscribers export endpoint.

Export your data

Export any table on your board (jobs, companies, job seekers, subscribers, blog posts, authors, and tags) to CSV from the dashboard or the API.

By Abi Tyas Tunggal and Jack Walsh

Export any table on your board to CSV. Use it to back up your data, analyze it in a spreadsheet, move a subset into another tool, or hand a clean file to a teammate. Export is the inverse of Import: where import brings jobs, companies, and blog posts in, export takes any of your primary tables out.

Where export lives

Every primary table has a ... menu in its toolbar, next to the primary action (for example, next to Import on Jobs, or next to Add on Companies). Open that menu and choose Export. The same step works everywhere, so you do not have to learn a different control per page.

Open the table you want to export (Jobs, Companies, Job seekers, Job alerts, or a blog table).
Click the ... menu in the toolbar.
Choose Export.
Your browser downloads a CSV named for the entity and your board.

What you can export

Seven dashboard tables are exportable:

Table	Sidebar location	What the file contains
Jobs	Jobs	Every listing with its company, location, salary, application URL, custom fields, status, timestamps, plus lifetime views, apply clicks, and native applications
Companies	Companies	Company name, website, summary, description, social links, status, and timestamps
Job seekers	Job seekers	Job-seeker profiles with contact details, authenticated resume links, and timestamps
Job alert subscribers	Job alerts	Subscriber email, status, confirmation state, preferences, and digest timestamps
Blog posts	Blog	Post title, slug, body, excerpt, author and tag references, status, and timestamps
Blog authors	Blog	Author name, slug, bio, avatar, and timestamps
Blog tags	Blog	Tag name, slug, description, and timestamps

Employer accounts are not a sidebar table. Export them with GET /api/v1/employers/export if you need the person-level employer directory.

Every file is comprehensive. Alongside the fields you authored, each row carries its id, its status, and its created and updated timestamps, so an export is a complete snapshot of the table.

The jobs and companies files include a source column for how the row was created: manual, import, public_submission, api, or backfill (jobs Cavuno collected via Backfill). Historical forager values are rewritten to backfill on export.

Exports that re-import cleanly

Jobs, companies, and blog post exports use the same field vocabulary as the matching CSV import. That means a file you export round-trips: you can re-import it (into the same board or a new one) without remapping columns. See Import jobs from CSV or XML and Company and subscriber import for the field details.

Large exports

Typical boards produce the CSV immediately and the browser download starts at once. When a table has more than 10,000 rows, the export switches to a Preparing export... state and prepares the file in the background. You can leave the page while it runs. When it finishes, the action gives you a download link for the completed file.

Large exports are capped at 200,000 rows. If a table is larger than the cap, export the rows you need by filtering the table first, or reach out and the team can help with a full extract.

Permissions

Exporting a table requires that entity's read permission (for example, jobs.read for the jobs export, candidates.read for the candidates export). Account owners and admins have these permissions by default, so on most boards export just works. Members on a restricted role only see the Export action for tables they can already read.

Exports above 10,000 rows prepare in the background and additionally require the operations.read permission to prepare and download the file. Account owners and admins hold it by default; a restricted role needs it added before a large export can run.

Resume links in the candidates export

The candidates export includes each candidate's resume as an authenticated download link, never a public file URL. Opening a link requires a signed-in operator with candidate read permission, so a resume cannot be reached by anyone who happens to hold the CSV. Treat the exported file itself as sensitive: it contains candidate contact details and links to their documents.

Export over the API

Every dashboard export has a matching v1 API endpoint:

text

1GET /api/v1/jobs/export
2GET /api/v1/companies/export
3GET /api/v1/employers/export
4GET /api/v1/candidates/export
5GET /api/v1/blog/posts/export
6GET /api/v1/blog/authors/export
7GET /api/v1/blog/tags/export

Each endpoint takes a format parameter:

format=json returns the rows inline in the response, for up to 10,000 rows. Use it for scripts and small tables that you want to process directly.
format=csv starts an async operation and returns an operation record. Poll the operation, then download the finished CSV from GET /api/v1/operations/{id}/download once it succeeds. Use it for large tables and for a file you want to store.

This is the same pattern as the existing subscribers export endpoint (GET /api/v1/subscribers/export). See the API reference for authentication, pagination, and the full parameter list.

Application records are not exportable

Application records (the candidate's submission in the employer's pipeline) do not have an operator export, by design. An application belongs to the employer's hiring pipeline, not to the board operator. The jobs export does include per-job counts: lifetime views, apply clicks (a visitor clicked Apply and was sent to the ATS — not a confirmed submission), and applications (confirmed native-ATS submissions only; blank for external-apply jobs). Those counts are analytics on the listing, not the employer's pipeline.

Next steps

To bring data back in, see Import and export for the import flows. To move an existing board onto Cavuno, export from your current tool, then follow Import jobs from CSV or XML and Company and subscriber import.