How to Enrich Custom Fields in Your CRM from a Sales Platform (2026)

Standard CRM fields cover the basics: name, email, job title, company, phone.

But the data that actually drives smarter outreach and better pipeline decisions usually lives in custom fields.

The tech stack a prospect uses, the trigger event that made them relevant now, the persona tier they belong to, the LinkedIn URL you need for re-enrichment later.

The problem is that custom fields don't fill themselves.

Most CRM setups leave them blank because there's no automated path from the sales platform where the data lives to the CRM field where it needs to go.

This guide covers how to map, populate, and maintain custom CRM fields using data from LinkedIn Sales Navigator and the tools that sit between them. In this guide:

• Why Custom Fields Matter for Outbound and Pipeline Management
• What Data Can Be Enriched into Custom CRM Fields
• Step 1: Map Your Custom Fields Before You Build Anything
• Step 2: Export Enriched Data from Sales Navigator with Evaboot
• Step 3: Map Fields on Import to Your CRM
• Step 4: Automate the Flow with Zapier or n8n
• Step 5: Keep Custom Fields Current with Re-enrichment
• Common Custom Field Enrichment Setups by CRM
• FAQs

Let's dive in.

Why Custom Fields Matter for Outbound and Pipeline Management

Default CRM fields tell you who someone is. Custom fields tell you why they matter right now.

The difference shows up in a few specific ways:

• Lead scoring: You can't score a lead on persona fit or buying signals if those attributes don't exist as fields in your CRM. Custom fields are the foundation of any scoring model beyond basic firmographics.
• Sequence personalisation: Most sequencing tools pull merge variables from CRM fields. If you want to reference a prospect's tech stack, their LinkedIn activity, or a recent trigger event in your first email, that data needs to be in a field the tool can read.
• Segmentation and filtering: Filtering your CRM by "prospects using HubSpot" or "contacts who changed jobs in the last 90 days" is only possible if that data lives in a structured field, not buried in a note.
• Reporting: Understanding which ICP tiers convert fastest, which trigger events produce the most pipeline, or which persona types have the shortest sales cycles requires those attributes to be tracked as fields from the start.

What Data Can Be Enriched into Custom CRM Fields

The fields worth enriching depend on your ICP and outbound motion, but these are the most commonly useful custom fields for B2B sales teams. The right data enrichment tools automate most of them.

From LinkedIn profiles

• LinkedIn profile URL (essential anchor for re-enrichment)
• Connection degree at time of export
• Years in current role
• Previous company
• Skills keywords (e.g. HubSpot, Salesforce, Python)
• Education institution
• LinkedIn activity status (recently active vs dormant)

From Sales Navigator searches

• ICP match tier (e.g. Tier 1, Tier 2, Tier 3 based on filter criteria)
• Saved search name or segment label
• Filter match status (from Evaboot's No Match Reasons column)
• Export date (useful for tracking data freshness)
• Changed Jobs flag (did this contact recently change roles)

From enrichment tools and third-party data

• Technology stack (tools and platforms the company uses)
• Funding stage and last round date
• Headcount growth rate
• Intent score or buying signal flag
• Company revenue estimate

Step 1: Map Your Custom Fields Before You Build Anything

The most common mistake in custom field enrichment is building the import workflow before deciding exactly which fields you need and how they should be formatted.

You end up with fields that are named inconsistently, formatted differently across records, or duplicating data that already exists under a different label.

Cleaning this up later is significantly harder than getting it right the first time.

How to map your fields

1. List every data point you want to track in your CRM for outbound contacts
2. Check whether a standard field already exists for it before creating a custom one
3. Define the field type for each: text, dropdown, date, checkbox, or number
4. For dropdown fields, define the picklist values upfront so data enters consistently
5. Name fields with a consistent convention, for example all Sales Navigator fields prefixed with "SN_" for easy identification
6. Document the mapping between your export file column headers and your CRM field names before you start importing

This document becomes your field mapping reference for every future import and automation setup.

Step 2: Export Enriched Data from Sales Navigator with Evaboot

Sales Navigator is the starting point for most LinkedIn-sourced custom field data. The filters you apply during your search become the basis for custom field values in your CRM.

Evaboot exports this data in a clean CSV with consistent column headers, which makes field mapping straightforward.

What Evaboot includes in every export

• First name, last name (cleaned)
• Current job title (cleaned and standardised)
• Current company name (cleaned)
• Company website
• LinkedIn profile URL
• Location
• Verified email address (if email finding is enabled)
• No Match Reasons (flags profiles that don't match your search filters)

Adding custom data to your export

Before importing, you can add custom columns to the Evaboot CSV manually for fields that come from your search context rather than the profile itself:

• Add a "Segment" column and label every row with the search name or ICP tier it came from
• Add an "Export Date" column with today's date for data freshness tracking
• Add a "Source" column with a value like "Sales Navigator" for attribution
• If you're running multiple searches for different persona tiers, add a "Persona" column before combining the files

These additions take two minutes in a spreadsheet and make the CRM data significantly more useful for segmentation and reporting.

Step 3: Map Fields on Import to Your CRM

Every major CRM has a field mapping step during CSV import. This is where you connect the column in your Evaboot export to the corresponding field in your CRM.

HubSpot

HubSpot's import wizard lets you map each column to an existing contact property or create a new one on the fly. For custom properties, create them in Settings before the import so the field type is correct.

Key things to get right:

• Map LinkedIn URL to a URL-type property, not a text field
• Map job title to the standard Job Title property unless you need to preserve both the raw and cleaned versions
• Use the deduplication setting to match on email address so existing records are updated rather than duplicated

Salesforce

Salesforce requires custom fields to be created in the object schema before import. For contacts, go to Setup, Object Manager, Contact, Fields and Relationships.

Create each custom field with the correct data type before running the import. Use Data Loader or the standard import wizard depending on volume.

• Field API names in Salesforce use underscores and end in __c for custom fields
• Set field-level security so custom enrichment fields are visible to the right profiles
• Consider using a separate "Enrichment Status" field to track which records have been enriched and when

Pipedrive

Pipedrive's custom fields live under Settings, Data Fields. Create the fields before import and use the import mapping tool to connect CSV columns.

Pipedrive supports text, number, date, monetary, phone, email, address, and option set field types for contacts and deals.

Step 4: Automate the Flow with Zapier or n8n

Manual CSV imports get the data in, but they require someone to remember to run the export, add the custom columns, and do the import on a regular basis. Automation removes that dependency.

Evaboot connects to Zapier and n8n natively, which means you can build a workflow that triggers when an Evaboot export completes and pushes contacts directly to your CRM with field mapping handled automatically.

Basic Zapier workflow

1. Trigger: Evaboot export completed
2. Action 1: Create or update contact in HubSpot
3. Map Evaboot fields to HubSpot properties including any custom fields
4. Add a step to set the "Enrichment Date" property to today's date
5. Add a step to set the "Source" property to "Sales Navigator"

More advanced n8n workflow

For teams with more complex requirements, n8n gives you more control over the logic:

• Pull the Evaboot export via webhook or scheduled file check
• Run a deduplication check against existing CRM contacts before creating new records
• Add conditional logic: if the contact already exists, only update blank fields rather than overwriting all values
• Route contacts to different pipelines or sequences based on the Segment or Persona field value
• Log each enrichment event with a timestamp in a separate activity field

This conditional update logic is important for custom fields specifically. You want enrichment to fill blank fields without overwriting data your reps have manually entered.

Step 5: Keep Custom Fields Current with Re-enrichment

Custom fields go stale at the same rate as standard fields, sometimes faster for dynamic data like job title, tech stack, or funding stage. Treat upkeep as ongoing lead enrichment, not a one-time import.

A few practices that keep custom fields accurate over time:

• Schedule re-enrichment by field age: Add an "Enrichment Date" field to every contact record. Set a CRM workflow that flags any contact where this date is more than 90 days old and triggers a re-enrichment pass.
• Use Sales Navigator's Changed Jobs filter: This filter surfaces contacts in your saved lists who have updated their LinkedIn profile with a new role. Export those contacts with Evaboot and update only the job title, company, and LinkedIn URL fields in your CRM. This recurring refresh is the core of LinkedIn contact enrichment.
• Re-enrich before campaigns, not after: Run a re-enrichment pass on the segment you're about to contact before the sequence goes live. Personalisation based on stale custom fields is worse than no personalisation at all.
• Protect manually entered data: Build your automation logic to only populate blank custom fields, not overwrite fields your reps have already filled in. An enrichment tool should add data, not replace good data with worse data.

Common Custom Field Enrichment Setups by CRM

HubSpot

HubSpot's native enrichment via Breeze Intelligence populates standard fields automatically for known companies.

For custom fields, the most reliable approach is Evaboot exports pushed via Zapier with explicit field mapping. HubSpot's workflow automation can then trigger sequences or internal notifications based on custom field values.

Salesforce

Salesforce gives you the most control over field schema and data governance.

For custom enrichment fields, using a dedicated enrichment status field and last enriched date field alongside the data fields themselves makes it easy to track and automate re-enrichment at scale.

Data Loader handles bulk updates; Zapier or a native integration handles real-time single-record updates.

Pipedrive

Pipedrive's simpler schema makes custom field setup fast but limits the complexity of automation you can build natively.

Zapier integrations handle most use cases. For teams using Pipedrive at scale, a middleware layer like n8n gives more control over conditional field update logic.

Conclusion

Custom field enrichment closes the gap between having contact data and having useful contact data.

The process is straightforward when you build it in the right order: define the fields you need before you touch any tool, export clean data from Sales Navigator with Evaboot, map fields correctly on import, automate the flow so it runs without manual steps, and schedule re-enrichment so the data stays current.

The teams that do this well don't just have cleaner CRMs. They have better segmentation, more relevant outreach, and reporting that actually tells them what's working.

FAQs

What is the difference between a standard CRM field and a custom field?

Standard fields are built into your CRM by default: name, email, phone, company, job title, and so on.

Custom fields are ones you create to track data specific to your business or outbound process. Custom fields let you store anything not covered by the defaults, from ICP tier and persona label to tech stack and LinkedIn URL.

Can Evaboot populate custom fields in HubSpot or Salesforce directly?

Evaboot exports contact data as a CSV with consistent column headers. To populate custom CRM fields directly without a manual import step, connect Evaboot to HubSpot or Salesforce via Zapier or n8n.

Map each Evaboot output column to the corresponding CRM field in the automation workflow. Once configured, completed exports push automatically to your CRM without any manual file handling.

How do I prevent enrichment from overwriting fields my reps have already filled in?

In Zapier and n8n, use conditional logic to check whether a field already has a value before writing to it. The typical rule is: only update a field if it is currently blank.

This preserves data your reps have entered manually while still filling gaps that automation can cover. In HubSpot specifically, the "Don't overwrite" option on import handles this for CSV-based updates.

What is the best way to track data freshness in a CRM?

Add an "Enrichment Date" or "Last Enriched" date field to your contact object and update it every time a record is enriched.

Then build a CRM workflow or report that flags any contact where this date is more than 60 or 90 days old. This gives you a live view of which records need refreshing without manually auditing the database.

How many custom fields should I create for outbound contacts?

Only create fields you will actively use for segmentation, scoring, or personalisation.

A CRM cluttered with custom fields that are rarely populated or never used in workflows adds noise without adding value. Start with five to ten fields that directly support your outbound motion, validate that they're being used and updated consistently, then expand from there.