Build a prospect list
Inside a Business Lead CSV: Sample File and Field Guide
Revision note: Added a practical workflow, labeled examples, evidence limits, and relevant next steps.
A sample CSV should answer practical questions before you configure an export: what does one row represent, which fields can be blank, and how should several contact values be handled?
Download the illustrative business leads sample. It uses the current Leadz export headers with fictional businesses and safe example values. It demonstrates structure, not live inventory, current contactability or a production export entitlement.
Understand the row before the columns
Treat each row as a business record that may represent a location. Do not assume it is a unique company or a named person. Multiple locations can share a domain or central contact channel, while duplicate source records can require review.
Actual exports depend on the selected columns. Business Name is required in the export dialog; the other listed columns are configurable. CSV export is available through eligible paid plans. Check current pricing and the export confirmation in your account for the applicable access and credit requirements.
Field dictionary
Business Name: the business title associated with the record. It is not necessarily the legal entity name.
Category: the primary business category used to describe the record.
Additional Categories: other recorded category values, flattened into a semicolon-separated cell where present.
Primary Phone: the primary phone value. It may reach a location or shared business line.
All Phones: additional recorded phone values in a semicolon-separated cell. Formats can differ from Primary Phone.
Phone Count: the export's count of stored phone entries, with a fallback for an available primary phone. It is not a count of distinct people.
Primary Email: the primary email value. Its presence does not establish mailbox verification or the reader's role.
All Emails: recorded email values in a semicolon-separated cell. Inspect these alongside Primary Email instead of assuming the two fields have identical coverage.
Email Count: the export's count of stored email entries, with a primary-email fallback. It does not establish distinct recipients or verified mailboxes.
Website: the business website value, useful for further account research and possible duplicate matching.
Address: the recorded business address. Compare it with city, state and ZIP information before merging locations.
City: the recorded city value; spelling or formatting may need normalization in your working copy.
State: the recorded state value. Check format before joining it with another dataset.
Zip Code: the postal code value. Import as text to preserve leading zeros.
Rating: the stored rating value, where exported. It is not a buying-intent or contact-verification score.
Reviews: the stored review count, where exported. It does not establish the number of customers currently served.
Interpret blank cells conservatively
A blank means no value was emitted for that field in the export. It does not establish that the business lacks a website, phone or email in the real world. The current formatter can also leave zero-valued rating or review fields blank, so a blank review cell should not be interpreted as a confirmed zero.
Do not replace every blank with zero: that creates misleading numeric values and hides missing information. Keep the raw sample or export unchanged, then add researched values and notes in a working copy.
Import a small batch and inspect it
Open the CSV through your spreadsheet's import flow and review the preview. Keep phone numbers and ZIP codes as text. Check that quoted values stay in one cell and semicolon-separated additional contacts remain understandable.
Map Business Name to an account or company field, not a person's first name. If your CRM requires named contacts, create them only after appropriate role research. Do not create one new company for every additional address in All Emails.
Inspect a small batch before importing the complete segment. Compare the source row count with the imported record count and document any rows rejected or intentionally excluded.
Add workflow fields separately
Source date, account owner, suppression status, role evidence and next action are useful fields for your working system. They are not included in the current export column list. Keep that distinction clear for teammates reviewing a sample.
Use the deduplication workflow before a CRM import and the availability guide before labeling a contact as usable. Then browse the relevant business category to build a segment that matches the actual account criteria.