What Salesforce fields should enriched lead data populate?

At minimum: First Name, Last Name, Email, Phone, Title, Company, Website, Industry, Number of Employees, and Lead Source. If you track tech stack, funding stage, or hiring signals, create custom fields for those. Map every enrichment column to a specific API field name before you import — Salesforce silently ignores columns it cannot match.

How do I avoid creating duplicate leads when syncing from a spreadsheet?

Use an upsert operation keyed on email address or an external ID field. Salesforce's Data Import Wizard has a duplicate-check option, but it only catches exact matches. For fuzzy deduplication — same person, slightly different email format — run a dedup pass in your spreadsheet or use a tool like Dedupely before the import.

Can I auto-populate Salesforce fields directly from an enrichment tool without exporting a CSV?

Yes, if your enrichment tool has a native Salesforce integration. Orange Slice exports enriched rows directly to Salesforce. Alternatively, connect via Zapier or Make: trigger on a new enriched row, map fields in the zap, and push to Salesforce as a new Lead or update an existing record. This removes the manual CSV step entirely.

Should enriched data overwrite what my reps have already typed into Salesforce?

No. Set your sync to 'update only if field is blank' for fields reps own, like deal notes or custom qualification fields. For firmographic fields like employee count or industry — which reps rarely edit manually — allow the enrichment data to overwrite so the CRM stays accurate as companies change.

What is the cleanest workflow for ongoing lead enrichment into Salesforce?

Build a spreadsheet or agent that pulls new prospects on a schedule, enriches them automatically, and pushes net-new records to Salesforce as Leads while updating existing Contacts with fresh firmographic data. Orange Slice's workflow layer can run this end-to-end. The result is a CRM that self-updates rather than decaying between manual imports.

How do I handle enriched leads that already exist as Contacts in Salesforce but I imported them as Leads?

Salesforce keeps Leads and Contacts in separate objects. Before importing, check whether your enriched records already exist as Contacts by running a SOQL query or using a tool like Cloudingo. If they do, update the Contact record, not the Lead object, to avoid the same person living in both places and skewing pipeline metrics.

Sync Enriched Leads from Spreadsheet to Salesforce

How to Sync Enriched Leads from a Spreadsheet to Salesforce

To sync enriched lead data from a spreadsheet into Salesforce, clean and deduplicate the sheet first, map every column to its exact Salesforce API field name, then push records using a native export, middleware like Zapier or Make, or Salesforce's Data Import Wizard. Automate the sync so enriched fields overwrite stale CRM data on a schedule — a one-time import decays within weeks.

Orange Slice is one tool that handles this end-to-end: it enriches prospects and exports directly to Salesforce without a CSV round-trip. But the steps below apply regardless of which enrichment tool you use.

Why Does the Spreadsheet-to-Salesforce Gap Hurt Pipeline?

You built a solid prospecting spreadsheet. Every row has a verified email, a job title, firmographics, maybe a tech stack signal or two. Then the data sits there while your reps work out of a Salesforce org that still shows the same stale records from six months ago.

The gap between enriched spreadsheet and live CRM is where pipeline accuracy dies. Closing it requires doing four things in the right order: clean the data, map the fields, choose the right sync method, and automate it so it does not decay again.

Step 1 — Clean and Deduplicate Before You Touch Salesforce

Pushing dirty data into Salesforce does not clean it. It multiplies the problem.

Before any export or import, do three things in your spreadsheet:

Remove incomplete rows. Any row missing an email address is not a lead — it is a placeholder. Delete it or move it to a separate tab for manual research.

Standardize field formats. Phone numbers should follow one format. Company names should not mix "Inc.", "Inc", and "Incorporated" for the same org. Salesforce's duplicate matching is case-insensitive but not format-tolerant.

Flag existing records. Export your current Salesforce leads and contacts as a CSV. Do a VLOOKUP or a MATCH formula against your enriched sheet keyed on email address. Tag rows that already exist in Salesforce as UPDATE and net-new rows as CREATE. You will use this flag in the next step.

If you skip deduplication here, you will end up with the same prospect as both a Lead and a Contact, or two Lead records for the same person — which corrupts conversion reporting and makes your reps look like they have more pipeline than they do.

Step 2 — Map Every Column to a Salesforce API Field Name

Salesforce does not import by column header display name. It imports by API field name. If your spreadsheet column is called "Company Size" and the Salesforce field is NumberOfEmployees, the import will either fail silently or prompt you to manually re-map every time.

Do this mapping once, document it, and enforce it as a standard in your enrichment spreadsheet template.

Spreadsheet Column	Salesforce Object	Salesforce API Field Name
First Name	Lead / Contact	`FirstName`
Last Name	Lead / Contact	`LastName`
Email	Lead / Contact	`Email`
Direct Phone	Lead / Contact	`Phone` or `MobilePhone`
Job Title	Lead / Contact	`Title`
Company	Lead	`Company`
Website	Lead / Contact	`Website`
Industry	Lead / Contact	`Industry`
Employee Count	Lead / Contact	`NumberOfEmployees`
LinkedIn URL	Lead / Contact	`LinkedIn_URL__c` (custom)
Tech Stack	Lead / Contact	`Tech_Stack__c` (custom)
Funding Stage	Lead / Contact	`Funding_Stage__c` (custom)
Lead Source	Lead	`LeadSource`
Enrichment Date	Lead / Contact	`Enrichment_Date__c` (custom)

Custom fields (ending in __c) need to be created in Salesforce before you import. Do that in Setup → Object Manager → Fields & Relationships. If you skip this, those columns are dropped.

The full list of standard Lead API field names is documented in Salesforce's Lead object reference.

Step 3 — Which Sync Method Should You Use?

You have three real options. Each has a different tradeoff between speed, control, and ongoing maintenance.

Option A: Native Export from Your Enrichment Tool

If your enrichment tool has a direct Salesforce integration, use it. It handles field mapping internally and supports upsert logic — meaning it will update an existing record if the email matches, or create a new one if it does not.

Orange Slice exports enriched rows directly to Salesforce from the same interface where you built the prospecting sheet. You describe your ICP, the sheet auto-populates with verified emails, firmographics, and signals, and you push to Salesforce without touching a CSV. That removes the entire manual export-import loop and the field-mapping errors that come with it.

This is the right choice if you are running enrichment regularly and want the sync to be part of the workflow rather than a separate manual step.

Option B: Middleware (Zapier, Make, or n8n)

Connect your spreadsheet (Google Sheets or Airtable) to Salesforce via a Zap or scenario. The trigger is a new or updated row; the action is "Create or Update Lead in Salesforce."

This works well when:

Your enrichment tool does not have a native Salesforce export
You want conditional logic (e.g., only push rows where ICP_Score is above a threshold)
You want to route different lead types to different Salesforce queues or record types

The downside: middleware adds latency, has per-task pricing that scales with volume, and requires someone to maintain the connection when Salesforce or the sheet schema changes. Zapier's published pricing starts at $19.99/month for 750 tasks and scales to hundreds of dollars per month at high task volumes — costs that compound quickly for teams syncing thousands of enriched rows weekly. Check /pricing to compare what native export costs versus building a middleware layer.

Option C: CSV Import via Salesforce Data Import Wizard

This is the manual fallback. Export your enriched sheet as a CSV, go to Salesforce Setup → Data Import Wizard, select Lead or Contact, upload the file, and map columns to fields in the UI.

Use this when:

You are doing a one-time backfill of a large list
You need to import into a Salesforce sandbox for testing
Your volume is low enough that a monthly manual import is acceptable

The Data Import Wizard supports upsert on email address. Select "Match by Email" and choose "Update existing records and insert new records" to avoid duplicates. Salesforce documents the full Data Import Wizard process in their help article on importing data.

Do not use this as your ongoing sync method. Manual imports decay. The moment you close the CSV, the data starts going stale.

Step 4 — Set Overwrite Rules That Protect Rep-Owned Data

This is the step most teams skip, and it causes the most friction with sales reps.

When your enriched data syncs into Salesforce, it should not overwrite fields that reps manage manually. A rep who has corrected a job title or added a personal note should not have that work erased by an automated enrichment sync.

Define two categories of fields:

Enrichment-owned fields — overwrite freely on every sync. These are firmographic fields that change as companies grow: employee count, industry classification, funding stage, tech stack, website. Enrichment data is more accurate and more current than what a rep typed in two quarters ago.

Rep-owned fields — update only if blank. These include deal notes, custom qualification fields, and any field your reps use to track relationship context. Set your sync logic to if field is null, write; if field has value, skip.

If you are using a middleware like Zapier, implement this with a "Find Record" step before the update step. Pull the existing Salesforce record, check whether the rep-owned field is populated, and only update if it is empty.

If you are using a native export, look for a "blank fields only" option in the export settings.

Step 5 — How Should You Automate the Ongoing Sync?

A one-time import is not a workflow. It is a patch.

The goal is a system where new enriched leads flow into Salesforce automatically, and existing records get refreshed when the underlying data changes. That means either:

Trigger-based sync: Every time a new row is enriched and marked ready, it pushes to Salesforce within minutes. Best for SDR teams doing daily prospecting.
Scheduled sync: A batch job runs nightly or weekly, enriches a defined segment of your ICP, and pushes net-new and updated records. Best for RevOps teams maintaining CRM hygiene at scale.

Orange Slice's workflow layer supports both patterns. You can build a multi-step workflow that finds prospects matching your ICP, enriches them, scores them for qualification, and pushes them to Salesforce as Leads — all without a human touching a CSV. The CRM agent handles the Salesforce-side logic: upsert rules, field mapping, and object routing.

For teams that want to see how this plays out in practice, the Pirros case study shows how a real team automated their prospecting-to-CRM pipeline end to end.

What to Do When the Sync Breaks

Salesforce API connections break. Field schema changes. OAuth tokens expire. Build a simple monitoring step:

After every sync, query Salesforce for records updated in the last 24 hours and count them.
If the count is zero when it should not be, send an alert to Slack or email.
Keep a sync log in your spreadsheet: timestamp, rows pushed, rows failed, error codes.

Error codes to know:

DUPLICATE_VALUE — your dedup logic missed something; check the matching field
FIELD_INTEGRITY_EXCEPTION — a picklist value in your sheet does not match the allowed values in Salesforce
REQUIRED_FIELD_MISSING — you are missing a field Salesforce requires (usually LastName or Company on a Lead)

Fix these in your spreadsheet template, not in Salesforce, so the next sync is clean from the start.

When Is a Native Integration the Wrong Choice?

Orange Slice exports directly to Salesforce, HubSpot, Instantly, and CSV. But it is not the right tool for every part of this problem. If you need to sync enriched data back from Salesforce into a data warehouse, or build complex multi-object relationships across Salesforce Accounts, Contacts, and Opportunities simultaneously, you need a dedicated RevOps tool or a custom integration. Orange Slice is built for the prospecting-to-CRM handoff, not for full Salesforce data architecture.

For the prospecting side — building the enriched list in the first place — see how the lead generation agent works and the use cases library for specific plays.

Pick your sync method based on your volume and cadence. If you are pushing enriched leads to Salesforce more than once a week, set up a native integration or middleware connection now — the time you spend on that setup pays back within the first month of not manually exporting CSVs. Start with one object (Lead), get the field mapping right, validate the upsert logic against a handful of test records, then scale it up.