How do you improve data quality in Salesforce?

Default fills gaps and blocks duplicates: a CRM Record Updated workflow enriches records with empty fields from a provider waterfall, and Match Record runs before every create. Salesforce validation rules and duplicate rules add checks when records are saved, and Default handles the records its workflows enrich and create.

How do I automate data hygiene in Salesforce?

In Default, a workflow on the CRM Record Updated trigger with an is NULL condition runs Enrich Data and writes the missing values back with Update Record. To reach older records nobody edits, check a custom Enrich now box on a small batch, and the same workflow picks them up.

What are the best practices for Salesforce data cleansing?

Default's backfill guidance: filter to empty fields first, since Update CRM record in Tables overwrites values and can't be undone, write enriched data to separate fields, and test on a small batch before a large run. Then put Match Record before every create so new duplicates stop at the source.

More than Salesforce data cleansing

Fill empty Salesforcefields automatically

Default fills empty Salesforce fields from a waterfall of data providers when records change.

Request a Demo

Salesforce lead backfill log with empty fields written back, and records kept as is when no data is found

Backfill empty fields

Filter records on an empty field, enrich them, and write the values back to Salesforce.

CRM Record Updated trigger with an is NULL condition, followed by Enrich Data and Update Record

Enrich on change

When a record with empty fields changes, a workflow enriches it and fills the gaps.

Workflow with Match Record before Create Record on the No Match branch

Duplicates stopped at create

Match Record checks Salesforce for an existing lead or contact before every create.

Checklist of Salesforce data hygiene practices, each mapped to a Default feature with record counts and status

Data hygiene checklist

Fill only empty fields, keep enriched data in its own fields, and test on a small batch first.

Empty fields get filledautomatically

A CRM Record Updated workflow with an is NULL condition runs Enrich Data and writes the result with Update Record. To pull in older records nobody is editing, check a custom Enrich now box on them.

Workflow enriching a Salesforce lead with an empty industry from 4 providers and writing the fields back

Backfill docs

Backfill

Fill missing fields from Tables, a CRM Record Updated workflow, or your own script through the API.

Enrichment nodes docs

Enrichment nodes

Enrich Data looks up the person, the company, or both, from 1 provider or a waterfall.

Clean up a whole listin Tables

In Tables, in beta, filter a view to records with an empty field, run Enrich, and review the new columns. Update CRM record then writes them to Salesforce, 100 records per run.

Tables docs

Tables

Build a view from Salesforce leads, contacts, or accounts, enrich it, and review the values before they reach Salesforce.

Waterfalls docs

Waterfalls

Clearbit, Apollo, People Data Labs, and Wiza in your order, with no provider accounts or API keys.

Duplicates are stopped at create

Match Record checks for an existing record before every create. In Data Model, source priority sets which source, such as a Salesforce contact or a form, fills the fields on Default's own person and company records.

Match Record before Create Record, beside the source priority list for the Person object

Duplicates docs

Duplicates

Match before create, Update on conflict in Salesforce, and a read-only scan for the duplicates you already have.

Objects docs

Field priority

Rank sources such as Salesforce leads, contacts, and form captures, and the highest source with a value wins.

FAQ

Questions about Salesforce data cleansing

Default fills gaps and blocks duplicates: a CRM Record Updated workflow enriches records with empty fields from a provider waterfall, and Match Record runs before every create. Salesforce validation rules and duplicate rules add checks when records are saved, and Default handles the records its workflows enrich and create.
In Default, a workflow on the CRM Record Updated trigger with an is NULL condition runs Enrich Data and writes the missing values back with Update Record. To reach older records nobody edits, check a custom Enrich now box on a small batch, and the same workflow picks them up.
Default's backfill guidance: filter to empty fields first, since Update CRM record in Tables overwrites values and can't be undone, write enriched data to separate fields, and test on a small batch before a large run. Then put Match Record before every create so new duplicates stop at the source.