Job titles nobody can segment
"VP Sales", "V.P. of Sales", "vp, sales" and "Head of Revenue" all mean a senior seller, and no filter catches all four. Cadences built on title rules miss buyers they were written for and enroll people they were not.
Titles in five spellings, phone numbers in four formats, free-text countries, people who bounced or left, and owners who moved on. Twopir Consulting finds the wrong, missing and stale values in the Salesforce records your Salesloft team works, corrects them in bulk with a backup behind every change, and checks that the sync carries the clean value to both systems. Records you keep, with values you can trust.
Trusted by 500+ organizations — including SaaS, technology and services teams that run sales engagement and CRM with Twopir Consulting.
What We Cleanse
Most Salesloft-connected orgs do not need fewer records. They need the records they have to say something true. Values go wrong in four ways: inaccurate, incomplete, outdated and inconsistent. These are the six places we find them most often.
"VP Sales", "V.P. of Sales", "vp, sales" and "Head of Revenue" all mean a senior seller, and no filter catches all four. Cadences built on title rules miss buyers they were written for and enroll people they were not.
Brackets, dots, missing country codes and extensions typed into the number field. Call steps dial the wrong thing or nothing, and a mobile number sits in the office phone field where nobody looks for it.
"USA", "U.S." and "United States"; "CA" meaning California or Canada; industry and lead source values retired years ago. Territory rules, routing and every regional report depend on exactly these fields.
"Acme", "ACME Inc." and "Acme Corporation" with three different websites, some with a path or a tracking parameter attached. People and activity hang off the Account, so its name and domain are what every rollup reads.
Emails that bounced, contacts who changed jobs, and records still marked active at a company the person left two years ago. Every one of them is a cadence step that cannot land and a number that inflates the funnel.
Records still owned by inactive users, reps who changed territory, or a holding queue nobody works. Salesforce ownership carries into Salesloft, so a stale owner means a buyer nobody is prospecting, or two reps who both think they are.
Salesloft data cleansing is the work of correcting the values inside Salesforce and Salesloft records that should stay: values that are inaccurate, incomplete, outdated or inconsistent. It profiles each field the revenue team depends on, writes normalisation rules for titles, phone numbers, country and state, picklists, account names and domains, retires or flags people who bounced or left, reassigns stale owners, applies the corrections in bulk with a backup and rollback plan, and then verifies that the sync carries the clean values to both systems.
Three parties are involved. Salesforce is your CRM and, for most fields, the system of record. Salesloft is the revenue orchestration platform your reps work in. It connects to Salesforce through Salesloft Data Sync, the free managed package documented on the Salesloft Data Sync AppExchange listing, and the sync runs in both directions with a priority set per field. Twopir Consulting plans and runs the cleanse across both, so a corrected value is not overwritten by the old one on the next sync.
Cleansing fixes values. It does not merge records: duplicate Leads, Contacts and Accounts are handled by our Salesloft Salesforce deduplication services. The rules that stop bad values coming back are designed in Salesloft Salesforce data quality consulting, and if you first need to measure how much is wrong, start with a Salesloft Salesforce data quality audit. All of them sit under our Salesloft integration services.
A wrong value is rarely contained to one record. In a Salesloft-connected org it feeds cadence targeting, assignment, reporting and the sync itself, and each of those multiplies it.
| Where it lands | What the bad value does |
|---|---|
| Cadences | Title and segment filters enroll the wrong people, personalised fields print a misspelt company or a blank, and steps aimed at bounced or departed people never land. |
| Routing and territories | Assignment rules in Salesforce read country, state, industry and size. A free-text "Calif." sends a lead to the default queue instead of the rep who covers it. |
| Ownership | Salesforce record ownership carries into Salesloft, so an inactive or wrong owner in Salesforce becomes the wrong person working the buyer in Salesloft. |
| Reporting | Reports group by value. Four spellings of one country become four rows, and activity that Salesloft logs as Tasks rolls up to an Account nobody recognises. |
| The sync | Salesloft and Salesforce sync both ways with a priority per field. Clean only one side, against the priority, and the next sync can bring the old value back. |
| Validation | A new validation rule that bad historical values fail can start rejecting legitimate sync updates to those records, which is why rules follow the cleanse rather than precede it. |
Who owns each field, and which way it should sync in future, is a governance decision. If those rules are not written down yet, we settle them alongside the cleanse through our Salesloft data quality consulting.
Every cleanse is a set of rules: what a correct value looks like, how each wrong variant maps to it, and what happens to the values no rule can resolve. These are the standards we usually start from, agreed with your team before anything changes.
| Field | Standard we apply | Before → after |
|---|---|---|
| Job title | Keep the title the person uses, trimmed and cased. Derive seniority and department into picklist fields, which is what cadence and segment rules should read. | "vp, sales" → VP, Sales · seniority VP · department Sales |
| Phone | One international format with the country code, extensions in their own field, and mobile and direct numbers in the fields built for them. | "(555) 010-0199 x12" → +1 555 010 0199 · ext 12 |
| Country and state | One value set, ideally Salesforce State and Country/Territory Picklists, with every free-text variant mapped to it and ambiguous codes resolved from other fields. | "U.S.A." / "Calif." → United States / California |
| Picklists | Retired and near-duplicate values mapped to the active set for industry, lead source, lead status and similar fields, then the retired values deactivated. | "Hi-Tech" / "Technology" → Technology |
| Account name | The name the company trades under, consistent casing, legal suffixes handled one way, and no rep notes in the name field. | "ACME INC (old - do not use)" → Acme Inc. |
| Website and domain | The root domain only: no protocol, no path, no tracking parameters. It is the value matching and enrichment rely on. | "https://www.acme.com/about?ref=x" → acme.com |
| Trimmed, lower case and syntactically valid. Addresses known to have bounced are flagged so they leave cadences, rather than deleted. | " J.Doe@Acme.COM " → j.doe@acme.com | |
| Record owner | Every active record owned by an active user who covers it, using your assignment rules, with inactive owners and holding queues cleared. | Inactive user → territory owner per assignment rule |
A person who left a customer is still part of that Account's history: the activity, the opportunities they influenced, the relationship. We flag them as no longer at the company, take them out of cadences and keep the record.
Where they moved to is a new person at a new Account, created through your normal entry path.
How bounce and opt-out status is recorded in your Salesloft instance, and whether it reaches Salesforce fields such as Email Opt Out, depends on configuration. We confirm that path in discovery before any status field is cleansed.
Opt-outs are never cleared by a cleanse. They are only made consistent across both systems.
Incomplete records often need data from outside: a missing phone, an industry, a company size. Whichever enrichment source you use or choose, these six decisions decide whether it improves the data or adds a new kind of wrong.
Enrichment writes to one system, usually Salesforce, and the sync carries it on.
Filling an empty field is low risk. Replacing a value a rep entered is not.
An enriched value is only as good as the match between your record and the source's.
Every enriched field should say where its value came from and when.
Enrichment needs clean match keys going in and returns values in its own format.
Enrichment adds personal data, so it follows the same consent rules as everything else.
A cleanse touches thousands of live records that reps are working today. Every step is built so that nothing changes that has not been tested, and nothing changes that cannot be put back.
We measure fill rate, format variants, picklist conformance and age for every field the revenue team relies on, in Salesforce and in Salesloft, and list who writes to each.
DeliverableField profile and priority list
Normalisation rules, value mappings, owner reassignment logic and the treatment of bounced and departed people, agreed with sales, marketing and RevOps before any record changes.
DeliverableSigned-off rule set and review list
The rules run against a sandbox copy first, with your automation, validation rules and flows switched on, so we see what each update triggers before production does.
DeliverableTest results and sample sign-off
A full export of every field we will touch, keyed by record ID, then the update in planned batches outside peak cadence hours. Any batch can be restored from the export.
DeliverableBackup, load log and rollback file
We sample records in both systems after the pull interval has passed, review the Salesloft sync log for failed updates, retry or fix them, and confirm the clean value held on each side.
DeliverableSync verification report
The rules become reports, scheduled checks and, where it makes sense, entry controls, so the next cleanse is smaller. We hand them to your team or run them with you.
DeliverableHygiene runbook and reports
Salesloft pushes its own updates to Salesforce as they happen and pulls changes from Salesforce on an interval of 1, 5 or 10 minutes, so verification waits for at least one pull. For loading techniques and the tools we use, see our guides to loading data into Salesforce and to data deletion and org cleanup.
Data decays: people change jobs, reps leave, new sources arrive with their own formats. The rules from the cleanse become a short list of recurring checks, each with a frequency and someone to run it.
| Check | How often, and what it catches |
|---|---|
| Sync log failures | Daily. Updates rejected by a validation rule, a picklist value or a missing link, before they accumulate. |
| Bounced and departed people | Weekly. People still in cadences after a bounce or a job change. |
| Format conformance | Weekly. New phones, countries, states and titles outside the standard, by source. |
| Inactive and mismatched owners | Monthly, and after every team change. Records owned by people who left or who no longer cover the territory. |
| Required-field completeness | Monthly. Cadence-ready records missing the fields targeting and routing need. |
| Picklist and mapping drift | Quarterly. Values added in one system and not the other, and fields whose mapping changed. |
Which roles own these checks and the thresholds that trigger action are part of the governance model in our Salesloft Salesforce data quality consulting. For the tooling side, our article on improving Salesforce data quality with Validity covers one option.
A cleanse usually has a trigger: something about to depend on the data, or something that already broke because of it. These are the situations we see most.
Connecting a new Salesloft instance syncs whatever Salesforce holds. Cleaning first, as part of Salesloft implementation, means reps start on values worth working.
Title and segment filters return too few people, or the wrong ones. The fix is in the values the filters read.
Old lists and departed contacts are being emailed. We flag them, take them out of cadences and keep the history.
New territories need clean country, state and size values before assignment rules can move a single record correctly.
Thousands of records owned by inactive users. Owners are reassigned by rule in Salesforce, and Salesloft follows.
A second database arrives with its own picklists and formats. Its values are mapped to yours before reps see them.
Regional and segment reports split one market across five spellings. Normalised values make the rows add up.
A new validation rule or picklist rejects updates to old records. Cleaning the historical values clears the backlog.
We follow the delivery model we use across the practice, Audit, Architect, Implement, Operate, applied to the values that move between Salesloft and Salesforce. Scope is set by the fields, record volumes and other systems involved, and agreed after discovery.
A fixed list of fields and objects, such as titles and regions ahead of a territory change, or bounced and departed people ahead of a new cadence programme. Profile, rules, test, update and verify, then a short handover.
Suits a team with a clear trigger and a date it has to meet.
A wider cleanse across the fields your cadences, routing and reports depend on, followed by the hygiene checks above, run by your team with our runbook or run with you on a schedule.
Suits a team that has cleaned before and watched it decay.
Either way, the first step is the same: we look at the data before we quote the work. If you want a full diagnostic across objects, mappings and sync errors first, that is the Salesloft Salesforce data quality audit, and duplicate records found along the way go to deduplication.
The goal is not a perfect database. It is records your reps can act on without checking them first, and reports your leaders can read without a footnote.
Title, seniority and region values that filters can read, so enrollment matches the audience each cadence was written for.
Bounced and departed people are out of cadences, and phone numbers are in a format call steps can dial.
Country, state and industry on one value set, so assignment and territory rules send each record where it belongs.
Active owners on every active record in Salesforce, carried into Salesloft, with no accounts left to a rep who has gone.
One spelling per market and segment, so regional and pipeline reports group the way leaders expect.
Corrections made on the side the field priority favours, verified in both systems, so the old values do not sync back.
Twopir has no published Salesloft case study yet, so this page claims no figures. For measured results from our wider CRM, integration and revenue operations work, see our success stories and how we run revenue operations end to end.
A bulk update is a change to production. It fires automation, meets validation rules and travels through the sync, so it needs the same care as any other release.
Flows, triggers, assignment rules and validation all run on a bulk load. We plan around them in the sandbox, not after production finds them.
We read the Salesloft field configuration before touching Salesforce, so corrections go to the side the priority favours and survive the next sync.
Every field we touch is exported first, keyed by record ID, so any batch can be restored. The load log shows exactly what changed.
We start with the fields your cadences, routing and reports read, not with the whole schema, so effort goes where it changes what reps do.
When a cleanse turns up more, the same team can audit, deduplicate or govern it, using tools such as Duplicate Check for Salesforce where they fit.
They correct the values inside the Salesforce and Salesloft records your revenue team keeps: job titles, phone numbers, country and state, picklists, account names and domains, bounced and departed contacts, and stale record owners. Twopir Consulting profiles each field, writes normalisation rules, tests them in a Salesforce sandbox, applies them in bulk with a backup and rollback plan, verifies that the sync carried the clean values to both systems, and hands over a hygiene runbook.
Cleansing fixes wrong, missing, stale or inconsistent values in records that should stay. Deduplication finds records that describe the same person or company and merges them. The two often run in sequence, because clean domains, emails and names make duplicates easier to match, but they are separate projects with separate risks. Duplicate Leads, Contacts and Accounts are covered by our Salesloft Salesforce deduplication services.
On the side the field priority favours. Salesloft and Salesforce sync in both directions, and admins choose which platform takes priority for each field and which fields each system may update. For most fields Salesforce is the system of record, so corrections are made there and flow into Salesloft. Cleaning the other side first can see the old value synced back.
Not always. Every cleanse starts by profiling the fields it will touch, which is enough when the problem is already known, such as titles before a territory change. If you do not yet know which objects, mappings or sync errors are causing the trouble, a Salesloft Salesforce data quality audit measures that first and tells you which cleanse is worth running.
It can fill gaps, under rules. Decide which system receives enriched values, usually Salesforce, whether each field is filled only when empty or overwritten when the source is newer, which match keys and confidence to accept, and how source and date are recorded. Clean domains and emails first, because enrichment matches on them. We work with whichever enrichment source you use or choose.
We found no pre-send email validation in the Salesloft documentation we reviewed. We therefore check address syntax during the cleanse, flag addresses known to have bounced, and take departed contacts out of cadences. How bounce and opt-out status is recorded in your instance, and whether it reaches Salesforce fields such as Email Opt Out, is something we confirm in discovery.
A thorough cleanse is usually a one-off project, followed by small recurring checks: sync log failures daily, bounced and departed people and format conformance weekly, owners and required-field completeness monthly and after team changes, and picklist and mapping drift quarterly. A target list gets its own check before every major cadence or campaign.
A first conversation covers which fields your cadences, routing and reports depend on, where the worst values come from, and how your Salesloft field priority is set: enough to say what a cleanse would cover and where to start. No obligation to proceed.
Talk to a Salesforce architect about cleansing your Salesloft data