Data cleaning for CRM imports
Comparison
Email verification vs list cleaning: what each one does (and doesn't)
These are two different jobs, and people confuse them all the time. One fixes how an address is written. The other checks whether that address can actually receive mail. List cleaning repairs "name@gmail,com" into "name@gmail.com". Email verification connects to the mail server to confirm the mailbox is real. You often want both, but you want them in the right order, and only one of them costs money.
Clean your list in Sift, free →
What list cleaning does (Sift)
List cleaning fixes the shape of the data. Sift runs in your browser and, with a before/after diff you approve, it repairs email format and syntax (a comma typed for a dot in "name@gmail,com", or "name at gmail dot com" wording), trims stray leading and trailing spaces, lowercases addresses so "John@X.COM" and "john@x.com" stop being treated as two people, and repairs garbled characters (mojibake). It then dedupes exact and fuzzy matches, merges duplicates into one record, and maps your columns to your CRM's import template so the file will actually load. All deterministic, all on your device.
What email verification does (a verifier)
Email verification checks the reality of the mailbox. A dedicated verifier (services like NeverBounce or ZeroBounce) connects to the receiving mail servers to check that the mailbox actually exists, and flags catch-all domains, disposable addresses, and role addresses like info@ or sales@. From that it estimates bounce risk. A perfectly written address can still be dead, and only a verifier can tell you that. This is SMTP deliverability verification, and it is not something Sift does or can claim to do.
Use both, in order
The practical workflow is simple: clean the format for free first, then verify deliverability if the campaign needs it. Cleaning first is worth doing even if you plan to verify, because a verifier bills you per address. Sending it "name@gmail,com" wastes a credit on an address that was never going to resolve; fix the typo for free, drop the exact and fuzzy duplicates, and you send the verifier fewer, cleaner addresses. Then, if you have a real deliverability need, pay per verification on what's left.
- Clean the format in Sift, free and in your browser: repair syntax, trim spaces, lowercase, fix mojibake, dedupe, and map to your CRM template.
- Verify deliverability with a verifier, per address, only if the campaign actually needs proof the mailbox is live.
When you need a verifier, not Sift
Sift does not, and cannot, do SMTP verification. If your job is to know whether an address is live, Sift is the wrong tool and a verifier is the right one. Reach for a verifier when:
- You're doing cold outreach to addresses you didn't collect yourself and can't trust to be live.
- You have a bounce-rate target from your email platform and need to stay under it.
- You need to confirm a mailbox is actually live, or flag catch-all, disposable, and role addresses, before you send.
Sift's honest lane is the format half: it fixes how the address is written and gets the file import-ready, for free. When you need to know whether mail will land, that's a verifier's job.