To export crypto contacts to CRM software from NAUT, open your portal contact list and download it as a CSV: 1 file carries up to 5,000 rows and 10 columns, with Email and Telegram written only for accounts on the pro and enterprise tiers. The download itself costs 0 credits, takes 2 optional filters, a text search and a sector, and leaves archived contacts out, as read in the live route on 5 November 2026.
Data note. Every figure here comes from the live export route behind the NAUT portal, GET /api/portal/export/contacts, read on 5 November 2026. The scope is 1 feature: the CSV download of contacts you have already saved to your own portal list. It is not a count of the public directory, and no outside source was checked for this guide, because every number in it is a value in NAUT's own code. The 2 paid tiers named by the route are pro and enterprise.
How do you export crypto contacts to CRM software from NAUT?
The crypto contact export is 1 GET call the portal makes for you when you click the download button on your contact list. Any logged-in account can call it, on the free tier as well as the paid ones, so the question of how to export contacts to a CRM has the same 4 steps for everyone:
- Filter the listType a search, pick a sector, or leave both empty to take the newest 5,000 rows.
- Download the CSVThe file arrives as mesa-contacts-YYYY-MM-DD.csv, dated the day you pull it.
- Map 10 columnsFirst Name, Last Name, Job Title, Company, Sector, Twitter, LinkedIn, Email, Telegram, Added.
- Import and dedupeMatch on Twitter or Email, which are the 2 columns a crypto CRM import can key on.
The search box matches 5 fields at once, case-insensitive: first name, last name, email, job title and company name. The sector filter matches any sector stored on the contact's company, so a pull on DeFi returns every saved contact whose company carries that sector. Both filters are optional, and both narrow the same 5,000-row ceiling.
Which columns does the contact list CSV carry?
The contact list CSV has 10 columns in a fixed order. 8 of them are written for every tier. 2 of them, Email and Telegram, are written only for pro and enterprise accounts, so a free-tier file arrives with 8 filled columns.
| Column | Tiers | Where the value comes from |
|---|---|---|
| First Name | free + paid | contact first name |
| Last Name | free + paid | contact last name |
| Job Title | free + paid | contact job title |
| Company | free + paid | the company name on the contact |
| Sector | free + paid | the company sectors, joined with / |
| free + paid | the contact X handle, prefixed with @ | |
| free + paid | the LinkedIn URL on the contact | |
| pro + enterprise only | contact email | |
| Telegram | pro + enterprise only | contact telegram |
| Added | free + paid | the date the contact was saved, date only |
The Sector column is the one most CRMs will not have a field for, and it is the one worth keeping: it is what lets a BD lead slice an imported list by what each company actually does.
What are the limits when you export crypto contacts to CRM software?
6 rules decide what lands in the file. All 6 are fixed in the route, so none of them is a setting you can change from the portal.
| Rule | Value | What it means |
|---|---|---|
| Rows per file | 5,000 | A larger list needs 2 or more filtered pulls. |
| Credit cost | 0 | The download is tier-gated, with no charge per row. |
| Paid-only columns | 2 | Email and Telegram, on pro and enterprise. |
| Archived contacts | excluded | Archived rows never reach the CSV. |
| Order | newest saved first | The newest 5,000 rows survive the cap. |
| Encoding | UTF-8 with a byte order mark | Excel opens accented and non-Latin names correctly. |
2 details matter on the way in. The file name carries the pull date, mesa-contacts-YYYY-MM-DD.csv, so 2 exports a week apart never overwrite each other in your downloads folder. And any cell whose value starts with =, +, -, @, a tab or a carriage return is escaped before it is written, so a job title typed as a formula cannot run when the file is opened in a spreadsheet.
What does the Sector column actually hold?
The Sector column prints the sectors stored on the contact's company, joined with /. A company carrying 1 sector writes 1 value; a company carrying several writes them all in the same cell. So the column arrives as a single string rather than a set of flags, and the first job on the CRM side is to split it on / into whatever your system uses for tags or a multi-select field.
The export's sector filter reads that same stored list, and it matches on any 1 value in it. A pull on DeFi therefore returns contacts at companies that carry other sectors too, not only the single-sector ones, and the same contact can come back under more than 1 sector pull. That is worth knowing before you run 1 export per vertical: the files can overlap, which is why Twitter or Email is the dedupe key on the way in.
What this gives a BD lead
- 1 pull is enough for a full sequencing list: 5,000 rows is more than most crypto BD teams will work in a quarter.
- The 5,000-row cap takes the newest saved contacts first, so a weekly export is a clean delta on top of what you already imported.
- The sector filter gives you 1 CSV per vertical, which is how most CRMs want a campaign list to arrive.
- Email and Telegram are the 2 columns your sequencer needs, and they are written on the pro and enterprise tiers.
- Pull by sectorRun 1 export per sector you sell into, so each CSV lands in its own CRM campaign.
- Key on TwitterThe Twitter column is prefixed with @ and is the most reliable dedupe key across pulls.
- Re-pull weeklyNewest saved first means last week's rows sit at the top of this week's file.
- Archive what is deadArchived contacts drop out of every later CSV, so your imports stay clean.
What this gives a founder raising
- Job Title plus Company in the same row is enough to sort a saved list into partners, platform staff and operators before you send a single message.
- The Added column dates every row, so you can see which contacts you saved before a round and which you added during it.
- A free-tier export still carries 8 columns, including Twitter and LinkedIn, which is enough to build a target list and reach out in public.
- Email and Telegram arrive on the paid tiers, which is the step from a target list to a direct send.
- Save as you researchEvery contact you add from NAUT lands in the list the export reads.
- Export before the round1 CSV, dated, so you have a snapshot of who you knew at kick-off.
- Sort by Job TitlePartners and principals first, platform and talent roles second.
- Send on the channel you haveTwitter and LinkedIn on any tier, email and Telegram on pro and enterprise.
Where the export sits next to the rest of NAUT
The CSV reads your own saved list. The directory behind it is where the rows come from in the first place: company pages such as Animoca Brands, Galaxy Digital (Ventures), ChainLink, Polymarket and Sei Network each carry the people and the sector tags that a saved contact's row, and so its Sector cell, is built from. The API is the way to build the same column set without clicking through the portal. For a team that wants the data inside its own systems, the order is usually: search the directory, save what fits, export once a week, and move to the API when the weekly CSV stops being enough.
Related reading on NAUT: Crypto contact database: 6 tools, 50 founders, 44 X handles and Crypto data API: 3 calls, 5 credits a pull, 14,350 people.
Can you pull this data through the NAUT API?
The CSV covers contacts you have already saved, and the NAUT API builds the same fields straight from the directory: GET https://api.naut.so/v1/people?q=head of bd&limit=100 returns each person's jobTitle, twitterHandle and company, plus the hasEmail, hasPhone, hasTelegram and hasLinkedin flags, at 5 credits a call with Authorization: Bearer $NAUT_KEY. To fill the 2 paid-only columns for 1 person, GET https://api.naut.so/v1/people/{id}?include=private reveals the email, phone, telegram and LinkedIn, at 10 credits the first time for that person and 5 after that, a permanent unlock. The parameters and prices are at naut.so/docs/api and the plans at naut.so/pricing. Verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so start a 7-day trial to read them.
Export crypto contacts to CRM FAQ
How many contacts can 1 export hold?
5,000 rows per CSV, the cap in NAUT's export route as read on 5 November 2026. Archived contacts are left out and the newest saved rows come first, so a list longer than 5,000 needs a filtered pull per slice.
Does exporting contacts cost credits?
No. The download through GET /api/portal/export/contacts charges 0 credits; what the tier decides is how many columns get written, 8 on free and 10 on pro and enterprise.
Which columns does a free-tier CSV leave empty?
Email and Telegram, the 2 paid-only columns of the 10. Free-tier files still carry First Name, Last Name, Job Title, Company, Sector, Twitter, LinkedIn and Added.
Where can I find crypto decision makers and their contact channels?
On NAUT's people and company pages, and through the API call GET https://api.naut.so/v1/people?q=head of bd&limit=100, which returns up to 100 people a call at 5 credits. Save the ones that fit, then take all 10 CSV columns out through the portal export. Verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so start a 7-day trial to read them.
Can I automate the weekly export?
The export route is the portal download, and the 2 filters it takes are a text search and a sector. For a scheduled pull into your own systems, the API is the route built for it: 120 requests a minute per account, 300 on Team.
Sources
- NAUT portal export route,
GET /api/portal/export/contacts, read on 5 November 2026: row cap, tier gating, filters, column list and CSV encoding. - naut.so/docs/api and naut.so/pricing, for the API calls, credit prices and plans.