Key takeaways
- Agree the field mapping before the first import, not after it.
- Check every incoming lead against the records you hold before it lands.
- A lead without an owner and a source is a lead nobody follows up.
- Move small batches you can check, rather than one large file.
What should you decide before you add leads to a CRM
Decide three things before you add leads to a CRM: which fields come across, who owns each new record and how you will mark where it came from. Without those rules, every person who exports a list makes the choices differently, and the CRM fills with records nobody trusts.
Write the rules on one page and keep it next to the CRM. A new hire who moves their first list should be able to follow it without asking.
How do you export leads to a CRM with the right fields
Map each column the prospecting tool gives you to exactly one CRM field, and leave out anything nobody will filter, route or write by. A long export feels thorough, but unused columns become empty fields that slow every search.
Keep the fields that make a lead usable on day one. Everything else can be added later, when someone needs it.
- Work email, kept in its own column, as the main matching key.
- First name, last name and job title, never combined into one field.
- Company name and website, so the contact links to the right company record.
- Lead source, such as the tool and the search or list it came from.
- Owner, the person who will make the first contact.
How do you avoid duplicates when you import prospects into a CRM
Avoid duplicates by checking every incoming lead against the records you already hold before it lands, using the work email as the first key. If the email matches, update the existing record or skip the lead; never create a second one.
A person can still slip through under a different address, so run a second pass on full name plus company. Leads that match on name but not email deserve a quick look by a person, because they may be a job change rather than a duplicate.
Who owns a lead once it moves from the prospecting tool into the CRM
The person who will make the first contact should own the lead from the moment it arrives in the CRM. Ownership set later tends not to be set at all, and an unowned lead sits untouched until it goes stale.
If leads arrive for a whole team, agree a simple rule in advance, such as by territory or by named account list. The rule matters less than writing it down, so nobody argues about who picks up a reply.
What changes when leads are found inside the CRM
When leads are found inside the CRM, or written to it by a connected assistant, there is no file to move, but the rules on fields, duplicates and owners still apply. The work shifts from cleaning a spreadsheet to reviewing records as they are created.
This is also the safer route for personal data. A list that never leaves the system is not copied into downloads folders, inboxes and shared drives along the way.
How to add leads to a CRM from a prospecting tool, step by step
Run the first batch slowly; the next ones go faster once the mapping is settled.
- Download the leads from the prospecting tool as a CSV with work email, names, job title, company and source in separate columns.
- Match each column to one CRM field, and drop the columns nobody will use.
- Search the CRM for each work email and company name, then update or skip the leads you already hold.
- Import a small first batch, set the owner and source on every record and add the batch to a named segment.
- Open a handful of the new records to confirm each value landed in the right field before you import the rest.
Where Pebbles Ai fits
- CapabilityProspecting & customer recordsLeads from Find fresh leads come from Pebbles Ai's own growing B2B contact database, GDPR compliant, and land as contacts in a segment in the CRM (in Beta), so there is no file to move. Leads from another tool come in through a CSV import.
- FoundationIntegrationsIf your team works in Attio or Pipedrive, an assistant can read records and create or update them from chat through the MCP connection. Each write is an approval action under the execution mode; it is not an automatic or background sync.
Common questions
Can I connect a prospecting tool to my CRM instead of importing files?
Many tools offer a direct connection, which removes the file but not the decisions. You still need to agree the field mapping, how duplicates are handled and who owns each new record.
Should I import every lead a prospecting tool finds?
No. Import the leads you plan to contact in the next few weeks. Leads parked with no owner and no plan go stale and clutter every search.
Does Pebbles Ai sync leads to Attio or Pipedrive automatically?
No. An assistant creates or updates Attio or Pipedrive records from the conversation through MCP, and each write follows the execution mode, so in Manual mode it waits for your approval. There is no background or two-way sync.
Which fields matter most when leads move into a CRM?
Work email, full name, job title, company, company website, owner and lead source. Any other field earns its place only if someone will filter or write by it.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
