Why Salesforce has a freshness problem
Salesforce is an orchestration tool, not a freshness tool. It consolidates the data you put in but does nothing to verify it over time. Concretely, in a typical mid-market Salesforce:
- 40 to 60% of Leads created more than 12 months ago contain at least one stale field
- 15 to 25% of Contact emails have gone invalid without any system noticing
- The history of job changes is completely missing — a Contact stays "VP Sales at TechCorp" even though they've been CEO somewhere else for 2 years
The Salesforce ecosystem offers solutions (Data.com retired, Lightning Data, Salesforce Data Cloud) but they're expensive, heavy to configure, and limited to the US market. For mid-market EU teams, what's missing is a light, affordable layer. That's where Ovalead fits.
Ovalead × Salesforce integration: where we stand
Today, the integration runs through CSV export/import. Not ideal but battle-tested: every Salesforce IT team supports this workflow and thousands of data hygiene operations happen this way every day.
In Q3 2026, Ovalead will ship the native integration via OAuth Connected App, which automates the workflow below into a continuous sync.
The 4-step CSV workflow
Step 1 — Export from Salesforce
Two methods, depending on your volume:
- Salesforce Data Loader (free, up to 5M rows per export): SELECT on the necessary fields (Id, FirstName, LastName, Email, Title, Company, LinkedIn URL if you have a custom field)
- Salesforce Reports (direct UI, up to 50k rows): create a Tabular Report on Contacts with the same columns, export to CSV
Critical field: the Salesforce ID (the 18-character Id). It's the reconciliation key on re-import. Never leave it out of the export.
Step 2 — Import into Ovalead
Drag-and-drop the CSV into the Ovalead import screen. Columns are auto-detected:
Id(Salesforce) → kept as-is for re-importFirstName+LastName→ contact identificationEmail→ SMTP verificationTitle,Company→ change detectionLinkedIn URL(if present) → primary verification source
Step 3 — Ovalead processes and exports
Ovalead runs the verification (1 to 4h depending on volume and number of active sources). At the end you get an enriched CSV with the original columns plus:
trace_status: updated, job_changed, email_invalid, not_foundtrace_new_title,trace_new_company: detected new valuestrace_email_score: 0-100, SMTP validity scoretrace_last_seen: timestamp of the last verificationtrace_company_industry,trace_company_size: company enrichment
Step 4 — Re-import into Salesforce
Three options, depending on your technical comfort:
- Salesforce Data Loader (Update): match on
Id, map thetrace_*fields to your Salesforce custom fields. This is the recommended method for > 10k contacts. - Salesforce Inspector (free Chrome extension): direct re-import from the browser, ideal for 1k-10k contacts.
- Salesforce Native Import (Setup UI → Data Import Wizard): capped at 50k contacts, but dead simple for small databases.
3 concrete use cases
Case 1 — Quarterly deep clean (RevOps)
Once a quarter, export the 80,000 Leads and Contacts that haven't been updated in 90 days. Push them through Ovalead. Re-import the delta into Salesforce. Typical result over a quarter:
- ~3,200 job changes detected (4% of volume)
- ~5,600 emails invalidated (7%)
- ~12,000 records enriched with refreshed company data
That operation takes ~6 hours of RevOps time per quarter — vs. weeks of equivalent manual work.
Case 2 — ABM campaign prep (Marketing)
Before launching an ABM campaign on 100 target accounts, export the associated Contacts (Decision Makers + Influencers, ~600-800 contacts), push through Ovalead, re-import the delta. You gain:
- A solid email deliverability rate (no bounces flagging your domain)
- An up-to-date view of decision-makers (who may have moved between two campaigns)
- A refreshed pitch (the company record may have tripled headcount since your last outreach)
Case 3 — Waking up dormant Leads (Sales)
Your Closed Lost - No Decision Leads from 2024 have become valuable: 18 months later, many have changed jobs or been promoted. Pull that segment into Ovalead, identify the 10-15% who have moved, create Salesforce Tasks for the SDRs with a "congrats on the new role" angle.
Best practices for Salesforce × Ovalead
1. Create 5 Ovalead custom fields in Salesforce
On the Contact (and Lead) object: trace_last_scan (Date), trace_status (Picklist), trace_email_score (Number), trace_job_changed (Checkbox), trace_previous_company (Text). Those fields become your native filters.
2. Use Workflow Rules on trace_job_changed
When Ovalead marks trace_job_changed = true on re-import, trigger:
- Automatic Task creation for the AE owner
- Slack notification to the manager
- Lead re-routing to the SDR for the new vertical if the industry has changed
3. Preserve the Salesforce audit trail
Enable Field History Tracking on Title, Company, Email before launching the Ovalead import. You keep the full history of changes (useful for internal audits and reporting).
4. Work by segments, not in bulk
Instead of a massive 500k-contact export, segment: "Active Pipeline Contacts", "Leads > 6 months inactive", "Q3 ABM Accounts". Each segment has its own optimal scan frequency (weekly for pipeline, quarterly for inactive).
Native integration roadmap
In Q3 2026, Ovalead will ship:
- Connected App OAuth (installable from the AppExchange)
- Two-way sync of Lead + Contact + Account
- Salesforce → Ovalead webhook for triggered scans (e.g. new Lead created → immediate verification)
- Lightning Component to display "Ovalead status" directly on the Salesforce record
- Bulk API v2 to handle volumes > 1M contacts
Early-access users will get preview access from Q2. If you're interested, email hello@ovalead.com with subject "Salesforce early access".
FAQ
Does the CSV workflow scale to 1M contacts?
Yes. Salesforce Data Loader handles 5M rows in a single export, and Ovalead processes up to 100k contacts per scan in parallel (with 5 active sources, ~6h for 100k). Beyond that, segment in chunks of 50k.
And Salesforce Marketing Cloud?
Ovalead works at the core CRM level (Sales/Service Cloud). For Marketing Cloud, sync happens through the Data Extensions linked to Contacts, so indirectly. Native Marketing Cloud integration is being considered for 2027.
What's the additional cost on the Salesforce side?
None. Ovalead uses standard Salesforce APIs, which are included on every Enterprise plan and above. On Professional Edition, check the API call quota per 24h (1,000 calls/license, generally enough).
What about GDPR and DPA contracts?
Salesforce and Ovalead each have their own DPA. Ovalead provides a separate DPA for the processing phase between your exports and imports. See our subprocessors list.