Create an export
1
Pick People or Companies
Fixed once you save.
2
Choose the filter
Pick a template, or describe your own in plain English.
Describe a change refines it. Edit the query opens the raw JSON.

3
Choose the columns
One column per field, with a recommended set already selected.
The picker starts on Recommended for you; the link beneath shows every
group. Both list only the fields your team can read. If a saved exportβs
columns stop being readable, editing it drops them.

4
Name it, then set size, cadence, and format
The match count and credit estimate update as you go.

5
Review and start
Accept the terms, then Start export. The first run starts immediately.

Filters
An export filter is the same filter tree that Person Search and Company Search accept.search.query and custom
sorts. Sort the file after you download it.
For fields and operators, see the
Person Search reference and the
Company Search reference.
Schedules
Your rows per run decide which cadences you are offered.
- Run now triggers an extra run at any time, including on a paused export.
- Pause schedule stops future runs. Resume schedule waits one full period before the next run, so a daily export resumed today runs tomorrow.
- Missed runs are never replayed. An overdue export runs once, then returns to its cadence.
- Three failed scheduled runs in a row pause the export.
- Edits apply to the next run. A run in progress keeps the configuration it started with.
Files
Both formats download gzipped.Lists in CSV
List fields spread across numbered columns namedpath[i].leaf. Selecting
experience.employment_details.past.title gives you
experience.employment_details.past[0].title,
experience.employment_details.past[1].title, and so on. Every row gets as many
slots as the widest row needs.
The list fields are education.schools and current and past employment for
people, and basic_info.all_domains, basic_info.markets, funding.investors,
locations.all_office_addresses, revenue.public_markets.stock_symbols, and
the taxonomy lists for companies. Pick JSONL to keep the nesting.
Limits
- Rows per run. Prefilled with 100,000, or your ceiling if that is lower.
The default ceiling is 1,000,000 and your teamβs may differ. A search matching
more rows than your cap still runs, writes up to the cap, and marks the run
capped. - Concurrency. One run at a time per export, two per team. A run that cannot start is skipped and recorded, not queued.
Runs
Every run lands in the exportβs history with its status, rows written out of rows matched, credits, duration, and a download link. Expand a run for its completion report, which shows how many rows carried a value in each column.
Download links are minted on click and last one hour. Anyone with the link can
download the file.
Pricing
A run bills per row written, at your planβs Person Search or Company Search rate. Premium filters and columns add their own per-row charge.- Previews are free.
- Failed and skipped runs cost nothing.
- A run that stops part-way bills only the rows it wrote.
- If your balance will not cover the first run, you can still save. The run is skipped until you top up.
When a run does not finish
Running out of credits mid-run stops the run at its next checkpoint, keeps the
rows already written, and bills only those. It shows as
Partial.
Roles
Managed exports
Bulk dumps Crustdata provisions for your team appear under Managed exports, below your own, each with its own run history. They are read only here; to change one, contact your account manager.Terms
Creating an export means accepting the Terms of Service and the Data Export Terms: internal use only, no resale or redistribution, and you handle personal data under the privacy laws that apply to you.What to do next
Person filters
Every field and operator an export filter accepts.
Company filters
The same for companies.
Track changes instead
For only what is new since last time, use a discovery watcher.

